Privacy
Privacy Policy
Plain-language overview of what Red Flag Sentinel collects and how it is used. Applies to the selected beta.
Information RFS may collect
- Email address used to sign in or request access.
- Beta request details you submit (such as your context or use case).
- Watched token mints you add to your watchlist.
- Alert history related to your watched tokens.
- Technical logs needed for security, debugging, abuse prevention, and service reliability.
How RFS uses information
- Operate the product and your account.
- Monitor tokens you have selected.
- Deliver alert emails and service messages.
- Improve reliability, accuracy, and safety of the service.
- Prevent abuse of the platform.
RFS does not sell user data.
Email use
RFS may send you:
- Sign-in / authentication emails.
- Beta access status emails.
- Alert emails for observed signals on your watched tokens.
- Occasional service updates.
Abuse protection
- Cloudflare Turnstile is used to reduce automated abuse.
- Rate limiting is applied to sensitive endpoints.
- Where consistent with current implementation, RFS avoids storing raw IP addresses and uses hashed abuse identifiers.
Third-party providers
RFS relies on infrastructure and data providers that may process limited data on its behalf, including:
- Supabase (database, auth, storage).
- Lovable and associated email infrastructure.
- Cloudflare Turnstile (abuse protection).
- Blockchain and market data providers used to observe on-chain signals.
User responsibility
Do not submit secrets, private keys, seed phrases, wallet credentials, or any other sensitive authentication material to RFS. RFS does not need them and will never ask for them.
No overpromises
RFS does not claim data is perfectly secure, that no logs are ever stored, or that the service is fully anonymous. RFS aims to be careful and transparent, and does not claim formal legal certifications beyond what is actually implemented.
Contact
For privacy questions, see the Contact page.
