Security Overview
How RAVIONIX is built.
A plain technical summary of how RAVIONIX protects the data it handles. We only describe what is in place today.
Reviewed October 2026
What we store, and what we do not
The links, messages and emails you check are hashed (SHA-256) at our edge and again on our server. The text itself is passed in memory to our API and to our AI provider to produce a verdict. We don't store it (our AI provider doesn't train on it and keeps it only for a limited time under its own retention policy). We keep a one-way hash, the verdict, the confidence, the scam type, the AI's short explanation (which can mention parts of what you checked) and when the check happened. If a check is rated a scam with high confidence, we also keep the website's domain name — never the full link, never linked to you. Domains flagged often are reviewed by a person, and confirmed scam domains may be published to a public blocklist that future RAVIONIX products and others can use; unreviewed names are deleted after a set period. Passwords are hashed in your browser and never leave your device; we keep the first 5 characters of that hash and the result.
Data protection
- All traffic is encrypted in transit with TLS.
- Data at rest is encrypted by our database provider. Especially sensitive fields are additionally encrypted by us with AES-256-GCM.
- Secrets are kept in our hosting provider's encrypted environment settings, not in our code, and automated secret scanning checks every pull request.
Sign-in and access
- Sign-in is handled by our sign-in provider with Google or Microsoft accounts, so your Google or Microsoft 2-step verification, if you've turned it on, also protects your RAVIONIX sign-in. RAVIONIX never stores a password.
- Every request is scoped to the account it belongs to, and automated tests check that one customer can't read another's data.
- Internal admin access is restricted to a named allowlist, and every admin view is written to the audit log.
Abuse and AI safeguards
- Free checks made without an account are protected by an automatic bot check, and all checks by server-side rate limits.
- We tell the AI to treat what you submit as data, not instructions, and every AI answer is checked against a fixed format before it is shown.
- A monthly AI spending cap protects the service from runaway use.
How we work
- Automated tests, secret scanning and dependency checks run on every pull request and every merge to our main branch.
- Security-relevant events go to an audit log that a database trigger protects against edits and deletes, kept for a limited time.
- Our database provider offers point-in-time recovery.
- No availability figure is published: uptime is not yet measured against a committed target.
Related policies
Contact us about this page
Security reports
security@ravionix.com