Cloak API
Privacy model
Cloak breaks the direct on-chain link between sender and recipient. It does not make blockchain activity invisible.
What Cloak protects
The deposit and payout are separate transactions. Veilo sends the payout from a shared pool after a variable delay, so the recipient is not directly linked to the sender's wallet.
| Public information | What it reveals |
|---|---|
| Deposit | A wallet sent funds to the Cloak pool, but not who received the payout. |
| Payout | The pool sent funds to a recipient, but not which wallet funded that payout. |
| Timing and amounts | They can still provide clues, especially when activity is low or an amount is unusual. |
Do not promise anonymity
Deposits, payouts, and fees remain visible on-chain. Describe Cloak as private or unlinkable on-chain, not anonymous, untraceable, or fully hidden.
How to describe it
| Accurate | Avoid |
|---|---|
| “Private transfer” | “Anonymous transfer” |
| “Unlinkable on-chain” | “Untraceable” |
| “The recipient is not directly linked to your wallet” | “Nobody can see the transaction” |
| “Breaks the link between sender and recipient” | “Fully hidden” or “off-chain” |
What reduces privacy
- Unusual amounts. A unique deposit and payout may be easier to correlate.
- Low activity. Fewer concurrent orders mean fewer possible matches.
- Later activity. Anything the recipient does next remains public on-chain.
This follows Veilo's broader privacy guidance. See What Veilo does not claim.