Privacy policy
How this release handles wallet and application data. Effective October 18, 2026.
Data kept on your device
Darkpool stores UI preferences, favorite assets, recent selections, saved public addresses, and minimal transaction receipts in browser local storage. This storage is not encrypted and is accessible to someone using your browser profile. Private keys, seed phrases, and privacy notes are never requested.
Activity persistence can be disabled in Settings. You can export receipts, clear history, reset local data, and disconnect wallets. Clearing local data does not remove public blockchain records.
Data sent to service providers
Connecting a wallet reveals its public address to the app. Quote requests include public sender and recipient addresses, asset identifiers, chains, amount, and slippage. LI.FI and selected route infrastructure receive information needed to quote and execute. RPC providers receive public balance and transaction queries and network metadata.
Vercel hosts the app and may process IP addresses, request metadata, and platform security logs under its own policies. External wallets, RPC operators, and transaction providers have independent privacy policies. No marketing analytics or advertising tracker is intentionally added by Darkpool in this release. Privacy signing material and decrypted balances are held in memory; the EVM SDK caches encrypted outputs in IndexedDB. Partner orders, addresses and status are stored for seven days in the operator’s Redis service, with a random recovery reference in session storage. Read-only exchange keys and secrets are processed transiently by Darkpool to sign requests to the selected exchange and are not persisted by the application.
Retention and limitations
Darkpool does not maintain an application account database or centrally store portfolio history in this release. Server caches may temporarily hold public network/token data and rate-limit counters. Hosting and upstream providers control their own log retention.
Privacy protocols do not eliminate all metadata exposure. Public addresses, timing, amounts, and network requests can be correlated. No anonymity or untraceability guarantee is made.
Questions and updates
Use the in-app handbook and FAQ for wallet, transfer, and data-management guidance. Never share wallet secrets, private notes, exchange credentials, or sensitive transaction details in public channels.
This policy describes the current implementation. Additional account, analytics, or provider functionality requires updated disclosures before activation. The project owner must establish a private contact channel and applicable data-controller details before a broader commercial launch.