Security

How we protect your data.

What's in production today, and what's on the roadmap.

In place today

Encryption in transit

TLS on every connection (1.2 and 1.3); HSTS header pinned (1-year max-age, includeSubDomains, preload).

Where data is stored

App accounts are stored by Supabase in the United States and encrypted at rest (AES-256). The website's accounts and our contact index live on our own servers at Hetzner in Germany, reachable only with key-based logins behind a firewall, and are backed up nightly. Stripe handles all payment-card data — we never see or store card numbers.

Geofenced data access

CA / TX / VT / OR resident contacts are blocked at every API endpoint and at data ingest. EU contacts are filtered out of the contact index's results, and its reveal and export endpoints refuse requests from EU IP addresses.

Application security

Content-Security-Policy enforced (script / style / connect / frame sources allowlisted, frame-ancestors none, object-src none, base-uri self). Plus X-Frame-Options DENY, X-Content-Type-Options nosniff, Referrer-Policy strict-origin-when-cross-origin, Permissions-Policy lockdown. Parameterized queries throughout (no SQL injection vectors). Rate-limited APIs with anti-bot UA filtering.

Authentication

Bcrypt password hashing. Session tokens stored as httpOnly cookies, 30-day rolling expiry. Per-IP login attempt rate-limiting.

On the roadmap

Not yet shipped
  • ›Content-Security-Policy nonce-based hardening
  • ›Two-factor authentication (TOTP) for accounts
  • ›Encryption at rest on our own servers and their backups
  • ›Geographic-redundant, off-site backups
  • ›SOC 2 Type 1 certification
  • ›Automated dependency vulnerability scanning
  • ›Bug bounty program

We'll update this page when each item lands. We won't claim certifications or controls we don't have.

Breach disclosure

We maintain an incident response plan and will notify affected users within 72 hours of a confirmed data breach, as required by applicable regulations.