Privacy

Effective July 2026, Version 1.0. This notice is incorporated into the Conditions of Sale and the Terms of Service.

The canonical copy of this document now lives in the Minthouse documentation, alongside the technical reference for the escrow contract and the auction engine. The text below is kept in step with it; where the two ever differ, the documentation governs.

What we collect

  • Your account. Your handle and sign-in identity: a verified email address through Privy, or a wallet address proved by signature. Where password sign-in is supported and you choose one, we keep only its salted hash.
  • Your wallets. The wallet addresses you connect or that Privy creates for you.
  • Your activity. Your bids, invoices, consignments, payments, and payouts.
  • The audit trail. The house keeps an append-only record of what the auction engine did and when, including actions on your account.

We do not collect more than the auction needs. There is no advertising, no tracking pixels, and no analytics service on the site.

Why we hold it

To run the auction: taking bids, issuing invoices, settling sales, and paying consignors. Wallet addresses are used for compliance screening where screening is enabled, for bid collateral where the bid escrow is enabled, and for settlement. Contact details are used to run your account and to send the notices the Terms of Service describe. Nothing is sold to third parties, and bidder identities are never published; bid histories show anonymized handles.

Where it goes

  • Privy handles email sign-in, so it processes your email address under its own terms.
  • Peer Pay provides the onramp and cash-out rails. An order you place with it is your relationship with it, under its terms.
  • The chain. Deposits, locks, and settlements involving the escrow contracts pass through the configured RPC provider. Anything written to a blockchain is public, permanent, and outside anyone’s power to delete, including ours. A bid lock records the standing maximum plus the published auction house fee, so observers can infer that maximum from the on-chain amount.
  • Google Fonts. The site’s typefaces load from Google’s servers, which see your IP address when a page loads.

In your browser

Minthouse writes four localStorage keys: your theme, a signed-out watchlist, the last wallet name and kind, and portfolio display preferences. Consignment drafts, card details, email addresses, references, reserves, and private agreement capabilities are not stored there. Opening the consignment page deletes the legacy mhConsign24 cache without reading it.

Before a signed-out consignment is sent, the browser creates a random 256-bit private capability and stores only that value in this tab’s origin-scoped sessionStorage. It is sent in a request header when the submission is created and in a POST body when the same tab resumes it; it never enters a URL, browser history, or a referrer. Refreshing the tab can therefore restore the agreement and tracker. Closing the tab loses the capability, and the page purges it once the journey is terminal. The server stores only its SHA-256 digest. Signed-in consignment history comes from the account-protected server record. Minthouse also sets a sign-in cookie that expires after 30 days. There are no advertising or analytics cookies. WalletConnect stores its own session data under its own terms.

Retention

Account data is kept while the account stands. The ledger and the audit trail are append-only by design: the record of a sale is the record of the sale, and rows are not rewritten or deleted. On-chain data is permanent by nature.

Your rights

Requests about your data, including access, correction, and deletion requests under laws such as the GDPR or the CCPA, go to notices@minthouse.io. The house answers what the applicable law requires of it. Deletion has limits: invoices, the ledger, the audit trail, and anything on chain are kept or immutable as described above.

Contact

Write to notices@minthouse.io, or by post to Minthouse Markets, Inc., New York.