Security & privacy

• Read-only by default. New keys can’t trade unless you opt in to trade:intents.
• Wallet-signed trades. Even trading keys only prepare trades. Every deposit and sell must be signed by the wallet that owns the key, so a leaked key can’t move funds.
• Hashed storage. Privy stores only a SHA-256 hash of each key. Plaintext is shown once at creation.
• Account isolation. Every account endpoint is scoped to the key owner. Another account’s IDs return 404, exactly like IDs that do not exist.
• No secrets in URLs. Keys are accepted only in the X-API-Key header.
• HTTPS only. All requests are served over TLS.

Your responsibilities

• Keep keys in server-side environment variables, never in client code or repositories.
• Use one key per integration and revoke unused ones.
• Rotate keys when a team member with access leaves.

Disposable, payment and proxy wallets

• Encrypted keys. Private keys are stored encrypted and are never sent to your browser unless you export them.
• You approve every move. Withdrawals, exports and proxy transfers from these wallets need a signed message from your connected wallet, bound to the exact amount and destination.
• Owner-only. Each wallet belongs to the account that created it; another account can’t see or use it.
• Locked mid-route. Proxy wallets can’t be exported or archived while their transfer executes, and retries check earlier signatures before sending anything new.

What Privy does not hide

Solana is a public ledger. Every deposit, payment, withdrawal and proxy hop is visible to anyone, and blockchain analysis can often link wallets together, for example through timing, near-identical amounts or a withdrawal back to your main wallet. Disposable wallets, payment links and proxy transfers reduce direct exposure of your main address. They do not provide anonymity, and you shouldn’t rely on them for it.