← Back to Securovix
Securovix
Pentest Framework

Privacy Policy

Last updated: 18 September 2026

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.

AI keys are isolated by organization. Anthropic / OpenAI / Google / Zhipu keys are encrypted before storage, are never returned by our API, and are decrypted only inside the service that performs an authorized scan.

1. Data we collect

DataWhyStored where
Email addressAccount login + recoveryOur server (hashed password)
Display nameGreeting on the dashboardOur server
Google profile (if you use Google sign-in)Account creation + avatarOur server
Scan target URLs + run historySo you can revisit past scansOur server
LLM API keysRouting inference requestsEncrypted organization secret store (Supabase in production)
Source code submitted to Code ScanSecurity analysis and sending to the selected LLM providerProcess 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 ShieldRead-only phishing, scam, suspicious-link, and prompt-injection triageRequest 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 eventsDelivering the security service, support, and incident investigationSupabase database and private object storage
Usage and billing recordsEnforcing plan limits and administering subscriptionsOur database and Stripe when billing is enabled
Session cookieKeep you signed inHttpOnly, SameSite=Lax cookie
Acceptance of Terms + Privacy timestampLegal recordOur server

2. Data we do NOT collect

3. Third-party providers

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.

4. Cookies

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.

5. Data retention

6. Your rights (UK GDPR / EU GDPR)

You have the right to:

To exercise any of these rights, email privacy@securovix.com. We respond within 30 days.

7. Security

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.

8. International transfers

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).

9. Children

The Service is not intended for users under 18. We do not knowingly collect data from minors.

10. Changes

If we materially change this policy we'll update the date above and notify signed-in users by email or in-app banner.

11. Contact

Privacy questions or requests: privacy@securovix.com.

See also: Terms of Service