Security & data handling
What we do with the names you screen, and how your account and records are protected.
Last reviewed October 27, 2026
The names you screen
- Names you screen while signed in are stored in your account so you have a record of each check. They are visible only to you (and your workspace, if you use one), except on the verification page of a PDF record you choose to issue, described below.
- Screened names and results are never sent to advertising or marketing-analytics tools.
- Anonymous homepage searches are not saved to any account.
- One optional feature sends data to a provider: if you ask for a plain-language explanation of a match, the name you screened and the matched record go to OpenAI to write it. It isn't used for advertising, and we don't use your screening inputs to train AI models.
Your records
- Each screening record is written by our servers from the server's own search results — not from what a browser reports — so a record reflects what was actually searched.
- Screening history cannot be edited or deleted by users through the app, so the record stays intact. Reviewer decisions are added alongside it with a timestamp.
- PDF records include the lists searched and when each list was last refreshed.
- Each PDF record has a record ID (80 random bits, so it cannot be guessed), the SHA-256 hash of its full content, and a QR code to its verification page. A record's stored content cannot be changed after it is issued.
- PDFs are kept in private storage. Only the person who issued a record and members of its organization can download it, through a link that expires after two minutes.
- The verification page is public to anyone with the record ID. You choose whether it shows the record's details (organization name, name screened, result, list dates) or only confirmation and the hash. It never shows email addresses.
Account and access
- All traffic is encrypted in transit (HTTPS/TLS).
- Sign-in is handled by Supabase Auth; we never see or store your password in plain text. Google sign-in is available.
- Database access is restricted per account with row-level security, and admin-console actions are restricted to administrators and logged.
- API keys are shown once and stored only as a SHA-256 hash.
Payments
Payments are processed by Stripe. Card details go directly to Stripe and never touch our servers.
Service providers
- Cloudflare — hosting, network and bot checks (Turnstile).
- Supabase — database and authentication.
- Stripe — payments.
- Resend — account, alert and contact-form email.
- Google — website analytics (Google Analytics) and optional Google sign-in.
- OpenAI — match explanations, only when you ask for one.
The privacy policy lists what each provider processes.
What we don't claim
We don't currently hold a SOC 2 report or other certification. If your procurement process needs a security questionnaire answered, contact us and we'll answer it accurately.
Reporting a vulnerability
Please report suspected vulnerabilities through the contact form. We appreciate responsible disclosure.