What this protects, and what it doesn’t
How it works
A plan wallet is created from a seed only the keeper holds. Your deposit goes there. Buys happen from two new
wallets, on a jittered schedule, for uneven amounts, and the tokens are sent to the destination you sealed to the
keeper’s key.
What the operator can see
- The database stores the destination encrypted. The browser never asks the keeper to reveal it.
- The operator who holds the database key and the keeper key can still connect your deposit to the destination until deletion.
What anyone can see
- Solana itself shows the plan wallet, the buy wallets, and the destination. Timing and round amounts reduce how obvious that trail is. They do not remove it.
How buys are made
- Privacy Cash mixing is installed as a disabled backend. Buys are direct Jupiter swaps.
Data and providers
- Destination history checks are done from the server, so the RPC provider sees the address you asked about.
- No ads, no analytics, no fee added on top of the network and the DEX.