Draft privacy notice

Clicking Connect starts wallet connection, then requests an expiring Sign-In With Solana message signature. No signature is requested merely on page load. The exact single-use challenge proves wallet control, not approval of a financial transaction. Sessions use Secure, HttpOnly, SameSite cookies; no bearer tokens are stored in localStorage.

The API processes wallet addresses, signed authentication messages, sessions, hashed IP/user-agent identifiers, risk-acknowledgement versions and timestamps, request IDs, security/audit records and public chain activity. Authentication evidence is stored server-side; signed financial transactions and credentials must not enter logs. Service operators and RPC/storage providers may observe requests.

The browser retains limited public transaction signatures, wallet/basket addresses and finality-recovery status to resume uncertain flows. It does not retain private keys, seed phrases, bearer tokens or privileged unsigned/signed transactions. A wallet may remember its own connection. Clearing site storage removes local recovery records, not public chain transactions.

No retention period or deletion promise is invented. Immutable security evidence and public chain history cannot be treated like editable profile text. Mainnet activation requires a counsel-approved retention and access/deletion process, verified processor agreements and a real privacy contact. Do not upload sensitive personal information to metadata.