Legal
Privacy Policy
This policy explains what RevokeRadar collects, why it is needed, and how wallet-related data is handled.
Last updated: July 29, 2026
Information we collect
- Wallet address and account status when you sign in with your wallet. We do not receive or store seed phrases, private keys, or wallet passwords.
- Public blockchain data needed to scan approvals, calculate risk context, and run monitoring that you enable.
- Subscription and payment metadata such as tier, expiry, transaction hash, token, amount, and payment network. We do not custody funds.
- Notification details that you configure. Notification secrets are encrypted before they are stored where the feature is enabled.
- Operational data such as hashed rate-limit identifiers, error logs, and basic request metadata used to prevent abuse and keep the service reliable.
How we use information
- Provide scans, risk explanations, revoke transaction preparation, monitoring, alerts, and subscription access.
- Prevent abuse, investigate failures, protect the service, and maintain audit records for payments and notifications.
- Improve reliability and product behavior using aggregated or operational diagnostics.
Service providers
RevokeRadar may send necessary data to infrastructure providers such as Supabase, blockchain RPC/data providers, and notification providers you choose. Their own policies apply to the data they process. Wallet addresses and blockchain activity are public by nature, but we do not sell personal data or private keys.
Retention and requests
We retain account, subscription, payment, security, and operational records for as long as needed to provide the service, prevent abuse, resolve disputes, and meet accounting or legal obligations. To request access or deletion of account data, contact [email protected] with the wallet address involved. Never include a seed phrase or private key.
Changes
We may update this policy as the product changes. The date above shows the latest version. Continued use after an update means you have had an opportunity to review the revised policy.
This is a plain-language product policy. Before a broad commercial launch, the operator should have it reviewed for the jurisdictions and user groups being served.