Privacy without pretending chains are private.

Mint may process public wallet addresses, network and transaction identifiers, collection details, uploaded files and metadata, support communications, device and browser information, IP-derived security signals, diagnostic logs, and preferences necessary to operate the service. Mint does not need or request seed phrases or private keys.

Wallet addresses, transfers, mints, contract interactions, token ownership, prices, and transaction history may be permanently public on Robinhood Chain and related networks. Mint cannot edit or erase information recorded on a public blockchain.

Information may be used to operate wallet and collection features, index confirmed blockchain activity, prevent fraud and abuse, secure the service, provide support, debug failures, comply with legal obligations, and measure aggregate product performance.

Production infrastructure may include hosting, database, RPC, monitoring, support, and decentralized-storage providers. A final provider list, data-processing terms, international-transfer basis, and subprocessors page must be approved and published before mainnet.

Off-chain records should be retained only as long as necessary for service operation, security, dispute handling, and legal obligations. Final retention periods must be documented before launch. Public-chain and permanent Arweave records may remain available indefinitely.

Mint may use essential browser storage for wallet preferences, session protection, and interface state. Nonessential analytics or advertising technologies must remain disabled until an appropriate consent mechanism and provider disclosure are implemented.

Depending on location, users may have rights to access, correct, delete, restrict, or export eligible off-chain personal information and object to certain processing. These rights cannot remove data from public blockchains. A verified privacy-request channel must be activated before mainnet.

Mint uses technical and organizational safeguards appropriate to the service, but no system is risk-free. The production age threshold and any child-privacy restrictions must be established through jurisdictional review before launch.

Privacy requests and security incidents should use the channels listed on the Support & Incidents page. Material policy changes will be identified by a revised effective date.