How we protect your DNA
We cannot leak, sell or be forced to hand over your genome. We never have it.
The report generator runs inside your browser tab. Your DNA file is read in memory, matched against the catalog and turned into a PDF on your own device. This page shows exactly what leaves your computer, how to check it yourself, and what that does and does not protect you from.
Data flow
Two sides of a line.
Stays on your device
- ●Your raw DNA file, and the archive it came in
- ●Every genotype read from it
- ●The PDF report, written and downloaded locally
Reaches our servers
- ○Your email address and a password hash (Neon Auth)
- ○Your credit balance and Stripe payment records
- ○For each generation: the report type, its status and timestamps. No DNA, no report contents.
Verify it yourself
Thirty seconds with your browser's developer tools.
01
Sign in, open the account page and select your raw DNA file.
02
Open the developer tools (F12, or Cmd-Option-I on a Mac) and switch to the Network tab.
03
Generate a report. You will see the generator module download once, and two small requests that reserve and complete a credit; their bodies contain the report type only.
04
Look for anything the size of your file (tens of megabytes) leaving the page. There is nothing.
The same check works on any raw-data service: if you see an upload the size of your file, your DNA has left your device. We also publish a security.txt with a contact for researchers.
Threat model
What this design protects you from, and what it does not.
Protects against
| Threat | Why |
|---|---|
| A breach of our servers | There is no genome to steal. The 2023 23andMe breach exposed millions of profiles because they were stored centrally; here nothing of the kind exists. |
| A sale or bankruptcy | Nothing genetic can change hands with the company, because the company holds nothing genetic. |
| Subpoenas and requests | We can only hand over what we have: an email address, payment records and report types. |
| Insiders | No employee, contractor or founder can look at a DNA file or a report; they never reach us. |
Does not protect against
| Threat | Why |
|---|---|
| Malware on your device | If your computer is compromised, your file and your PDF are exposed like any other document on it. |
| Sharing the PDF | Once you email or upload the report somewhere, that recipient has it. Treat it like a medical record. |
| Your DNA provider's copy | 23andMe, AncestryDNA or MyHeritage still hold your sample and data; deleting them is a separate step, covered in our guides. |
Services and retention
Who else is involved, and how long we keep what.
Services we use
| Service | What it receives |
|---|---|
| Neon (authentication, database) | Email, password hash, credit balance, generation records. |
| Stripe (payments) | Your payment details and email, under Stripe's own privacy terms. We never see card numbers. |
| Vercel (hosting, analytics) | Serves the site and the generator module; cookieless page-view and funnel analytics with no cross-site identifier. |
| SendGrid (newsletter) | Only the email address you type into the newsletter form, if you subscribe. |
| Google Ads tag | Not active at the moment: no Google script loads. If advertising is ever switched on, the tag would load on marketing pages only, never on the sign-in or generator pages, with consent defaults set to denied in the EEA, the UK and Switzerland. |
Retention
| Data | Kept |
|---|---|
| Account | Until you ask us to delete it. |
| Purchase records | As long as accounting rules require. |
| Generation records | Report type, status and timestamps; never the PDF or your DNA. |
What we have not done yet
Honest about the gaps.
- —No third-party security audit has been performed yet.
- —The report generator's source code is not public yet; the data it uses, the GWAS Catalog, is.
- —We claim no certification (no ISO, HIPAA or similar). There is nothing server-side to certify, and we would rather say so plainly.
Found a security issue? Write to support@full-human.com · security.txt