This policy describes what data Securovix collects, why, and what we do with it. We follow the principle of data minimisation — we keep only what we need to run the Service.
| Data | Why | Stored where |
|---|---|---|
| Email address | Account login + recovery | Our server (hashed password) |
| Display name | Greeting on the dashboard | Our server |
| Google profile (if you use Google sign-in) | Account creation + avatar | Our server |
| Scan target URLs + run history | So you can revisit past scans | Our server |
| LLM API keys | Routing inference requests | Encrypted organization secret store (Supabase in production) |
| Source code submitted to Code Scan | Security analysis and sending to the selected LLM provider | Process memory during the run and for up to 30 minutes afterward; not written to the database by Code Scan |
| Messages or links submitted to Personal Shield | Read-only phishing, scam, suspicious-link, and prompt-injection triage | Request memory only; submitted content is not stored and is not sent to an AI provider. The audit trail stores only risk level and finding categories. |
| Findings, reports, audit and operational events | Delivering the security service, support, and incident investigation | Supabase database and private object storage |
| Usage and billing records | Enforcing plan limits and administering subscriptions | Our database and Stripe when billing is enabled |
| Session cookie | Keep you signed in | HttpOnly, SameSite=Lax cookie |
| Acceptance of Terms + Privacy timestamp | Legal record | Our server |
When you connect an LLM API key, Securovix sends scan inputs and prompts to that provider under their privacy policy:
If you use Google Sign-In, you also agree to Google's terms.
We use first-party HttpOnly cookies for the signed-in session, active organization, and short-lived OAuth/OIDC state. The session is HMAC-signed, uses SameSite=Lax, and expires after 30 days. We do not use advertising cookies.
You have the right to:
To exercise any of these rights, email privacy@securovix.com. We respond within 30 days.
Passwords are hashed with PBKDF2-SHA256 (120,000 iterations, 16-byte salt). Sessions are HMAC-SHA256 signed. Organization credentials are encrypted at rest. Production deployments use HTTPS. Payment-card data is handled by Stripe when billing is enabled; Securovix does not store full card numbers.
Our servers and Supabase database may be located outside your country. By using the Service you consent to your data being transferred and processed in those locations under appropriate safeguards (Standard Contractual Clauses where required).
The Service is not intended for users under 18. We do not knowingly collect data from minors.
If we materially change this policy we'll update the date above and notify signed-in users by email or in-app banner.
Privacy questions or requests: privacy@securovix.com.
See also: Terms of Service