Public chain.
Minimal app data.

What the service handles

Public wallet addresses, the selected network, collection commitments and content hashes, reservation and order identifiers, quote details, transaction identifiers, public signatures where they are required, operational request metadata, and security and audit events.

What stays in your browser

Wallet permission state and non-sensitive interface preferences may be stored locally. The key that opens a mint tracker is short-lived, scoped to one order, held in a single browser session, and never put in a URL. Private keys, seed phrases, wallet backup words, and complete signed PSBTs are never collected as analytics and never written to application logs.

Why any of it is processed

To verify the collection commitment and the final reveal, prevent duplicate mints, construct and reconcile transactions, index confirmed tokens, show your wallet inventory, prevent abuse, and investigate incidents.

What is kept, and who it reaches

Canonical collection records, transaction and accounting records, and immutable audit records are retained for integrity and legal obligations. Temporary reservations and rate-limit records expire. Public chain data is shared with the configured nodes, indexers, explorers, and mint services, only as far as the action you asked for requires.

What you can do about it

You can explore the artwork gallery without connecting a wallet. Disconnecting ends the active interface connection, though nothing can erase public blockchain history. A request about off-chain account data should identify the relevant public address or order ID and nothing more. Never send wallet secrets.