Privacy policy

Written to be read. Last updated on the build date of this deployment.

What we store

Your Google or X account identifier (never your handle as the primary key), your username, a display name and avatar if you provide them, your wallet address, an encrypted copy of your wallet secrets, payment records, payment links, notifications, and an operational audit log.

What we cannot read

Your mnemonic and your wallet private key. They are encrypted on your device, and CloakPay holds a copy it cannot open.

What we never store

Passwords, Google or X access tokens, private keys, or wallet secrets in readable form.

Provider tokens

Google and X access tokens are used once, to read your account identifier and profile, and then discarded. CloakPay cannot act on your behalf at those providers.

What the blockchain records

Every payment CloakPay makes today is an ordinary transfer: the chain records the two addresses involved, the amount, and the time. It does not record a username, and it does not record who the addresses belong to.

What the backend can infer

Because CloakPay routes a payment to a recipient account, the backend knows which account you are paying and when, and it holds the link between a username and an address. That link is not published: no page in the app and no receipt prints an address.

Analytics and logs

No third-party analytics run on CloakPay. Server logs record request paths and status codes — never tokens or wallet secrets.

Deleting your data

Deleting your account removes your records, including your encrypted wallet backup. If you did not write down your mnemonic, deletion means the wallet is gone for good. On-chain history cannot be deleted by anyone.

Contact

This is a testnet project under active development. Do not treat it as a regulated financial service.

Privacy policy · CloakPay