Your cloak address
Sign one fixed message and your browser derives a spend key and a view key from the signature. Nothing is uploaded, nothing is stored, and signing again on any device rebuilds exactly the same address.
Cloak a payment
Paste a cloak address and your browser derives a one-time Solana address for them. Paste an ordinary wallet address and it sends straight there, in the clear, like any other transfer.
The memo carries the one-time public key so the receiver can find this payment. It names nobody.
Payments cloaked to you
Every cloaked send taps one beacon address, so a single RPC call returns every announcement. Your view key tests them here, in this tab. The network never learns which one is yours.
Sweep
Move a cloaked payment into any wallet. Sweeping several notes into the same address links them to each other, so use a fresh destination when it matters.
RPC endpoint
CloakSend ships with a shared endpoint and falls back through free public ones if it is busy. A deep scan is heavy, so paste your own (Helius, QuickNode, Triton, anything) if you run them often. It stays in this browser only.
How this app treats your keys
Your spend and view keys are derived from one wallet signature and live in this tab's memory only. They are never written to disk, never sent anywhere, and are gone the moment you close the tab. Reconnecting and signing again rebuilds them exactly.