Placeholder — have a lawyer review this before launch, including GDPR if you operate from the EU or Switzerland

Privacy

This draft describes what the MVP actually stores. It is not a finished privacy policy.

If you join the waitlist, we store your email address in the local database. This build does not send email. If you type an email on a scan, we store it on that scan and can pass it to Stripe Checkout as the receipt address.

A scan stores the URL, hostname, verification token, score, platform guess, and findings. Proofs are redacted. LockShip does not keep full secret values or full database rows. A public certificate page shows the hostname, score, status, and dates. It does not show findings or the scan link.

Stripe processes the card payment. LockShip stores the Checkout session id, customer id, and subscription id Stripe returns. We do not store card numbers.

Scan and waitlist rows are stored in Postgres. The server connects with DATABASE_URL. Row level security is enabled and no policies are granted to the public anon or authenticated roles, so a Supabase anon key cannot read this data. The schema is supabase/schema.sql. A local run without DATABASE_URL uses an embedded Postgres on that machine instead.

To ask for a deletion once a real operator is named, write to the address published with the live site. This placeholder does not invent a support inbox.