Security

Version 1.1 — 27 October 2026

Principles

Two choices shape the rest: the attack surface is kept deliberately small, and we do not hold data we do not need. A breach cannot expose what was never collected.

Application

  • No npm in production. The site is static HTML, CSS and plain JavaScript, served next to Go functions with only two external dependencies (a PostgreSQL driver and a DKIM verifier). No framework and no build step that could pull in a compromised package.
  • Only the public folder is served. Source code, database migrations and configuration are never published.
  • Administration endpoints require a secret token and fail closed when none is configured.

Data

  • No passwords exist: sign-in is by one-time link. Email addresses are stored only as a keyed hash.
  • IP addresses are only stored hashed with a salt that changes daily, and are deleted after 30 days. A daily job enforces every retention period.
  • Subscription emails are verified against the platform's signature and discarded; only the platform, the account, the date and a keyed fingerprint are kept.
  • Sessions are signed cookies, inaccessible to scripts, sent over HTTPS only.
  • Encryption in transit throughout (TLS, including between our functions and the database).

Infrastructure

  • Database in Paris (Scaleway Serverless SQL), with access limited to a dedicated application key scoped to the project.
  • Functions run in Paris (Vercel, cdg1). Preview deployments are protected by single sign-on.
  • Separate databases and credentials for testing and production.

Reporting a vulnerability

Write to security@legit.fans. We aim to acknowledge within 48 hours and to keep you informed until the issue is fixed. We will not take legal action against researchers who act in good faith, avoid accessing or destroying other people's data, and give us reasonable time to fix the problem before disclosing it.

Incident response

People affected by a personal data breach are told without undue delay, and the CNIL within 72 hours where the breach is notifiable.

What we have not done yet

To be straight about the gaps: no external penetration test, no certification (SOC 2, ISO 27001), no formal bug bounty, no automated code-scanning pipeline, and backup restoration has not yet been tested. This is a beta, and we will update this page as each of these changes rather than imply a maturity we do not have.