Privacy

Last updated 11 November 2026. Questions: support@2cstudio.app.

Scanning

When you scan a wallet, its public address is sent to our server and on to our Solana data provider (Helius) to read the chain. We don't keep a record of which addresses were scanned. The same goes for checks made by AI apps through SealGuard's MCP server; for its rate limit we count calls per connection under a one-way hash of the IP address, kept for up to two days.

Signing in and the guard

If you sign in to set up the guard, we store your wallet address, your Telegram chat id once you link it, a summary of the wallet's last check (approvals, nonce and stake authorities, flagged tokens), and your payments (transaction signature, token, amount, date). We use them only to run the guard and keep payment records. Your browser keeps a sign-in token in local storage; there are no tracking cookies.

Logs and counts

Cloudflare, which hosts SealGuard, keeps standard request logs for a short time. We count visits without cookies: each open tab gets a random number that is gone when you close it, so we can see how many visits there were, from which country and to which page; nothing follows you from one day to the next. We also keep daily totals of scans and fixes (how many accounts were closed and the fee taken), with no wallet addresses. We don't sell or share data with anyone else.

Deleting your data

Write to support@2cstudio.app from any address with your wallet address, and sign a message we send you to prove it's your wallet; we'll delete the guard record. Payment records are kept as long as the law requires.