How RAVIONIX is built.

What we store, and what we do not

The links, messages and emails you check are hashed (SHA-256) at our Cloudflare edge. The text is processed in memory to produce a verdict and then discarded; only the hash and the verdict are stored. Passwords are hashed in your browser and never leave your device; we keep only a 5-character prefix of that hash.

Data protection

• All traffic is encrypted in transit with TLS.
• Data at rest is encrypted by our database provider. Especially sensitive fields, such as monitored email addresses, are additionally encrypted by us with AES-256-GCM.
• Secrets live in our hosting provider's encrypted environment settings, never in source code.

Sign-in and access

• Sign-in is handled by Clerk with Google or Microsoft accounts, so their 2-step verification protects you. RAVIONIX never stores a password.
• Every request is checked against the account it belongs to, so one customer cannot see another's data.
• Teams have owner, admin and member roles; billing and member changes are limited to the right roles.
• Internal admin access is restricted to a named allowlist, and every admin view is written to the audit log.

Abuse and AI safeguards

• Cloudflare Turnstile bot checks and server-side rate limits on every free check.
• What you submit is treated as data, never as instructions to the AI, and every AI answer is validated 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 change.
• Security-relevant events go to an audit log that cannot be edited or deleted.
• Our database provider offers point-in-time recovery.
• No availability figure is published: uptime is not yet measured against a committed target.
• Security never stops, and neither do we: we review and improve these controls continuously.