How we protect your data
Your genome is the most personal data in existence. Here is how it is protected — described fully enough to verify against our privacy policy, and no further.
Pseudonymization by design
Your identity and your genome never live together. They are stored in separated namespaces, joined only by a random surrogate genome ID. A compromise of one namespace reveals nothing about the other — there is no single place where "who you are" and "what your DNA says" sit side by side. The full mechanics of how these namespaces are separated, keyed, and mediated are deliberately not published.
Encryption, in transit and at rest
Uploaded DNA files live in private, AES-256-encrypted storage that is never publicly addressable — our systems reach them only through temporary, narrowly scoped access grants — and any genotype call we retain is additionally encrypted at the field level under data keys that rotate on an automated schedule. All traffic between your browser and our systems is protected with modern TLS, and stored data sits inside hardened, professionally managed cloud infrastructure whose physical and network security is maintained continuously by the platform provider — not by hope.
We sell reports, not genomes
Your genetic data is never sold, licensed, rented, or shared with insurers, employers, pharmaceutical companies, or anyone else. There is no advertising arm, no data-broker channel, no research-partnership exception. Our revenue comes from subscriptions to interpretation and monitoring — full stop.
Deletion that actually deletes
You can delete everything at any time, from your account, without contacting us. Deletion is immediate and irreversible: your raw DNA file is purged automatically (it is only retained at all if you explicitly opt in to keep it for re-analysis), and your reports and derived variant records are removed with it. Nothing lingers in a backup archive waiting to expire — deleted means deleted.
Least-privilege access control
Every record in the system is protected by row-level access controls enforced at the database layer — not by application code that could be bypassed. Users see only their own data; administrative operations are restricted to a small set of named administrators, and even those operations are performed against pseudonymized data.
Consent as an audit trail
Before you upload anything, you affirm a multi-point informed-consent checklist. The exact statements you affirmed — and the exact versions of the Terms, Privacy Policy, and Medical Disclaimer in force at that moment — are recorded verbatim. There is no ambiguity later about what you agreed to, and no processing occurs before consent is captured.
Standards we hold ourselves to
- Our controls are mapped against the SOC 2 Trust Services Criteria — security, confidentiality, and processing integrity — as the operating discipline our engineering and data practices are held to.
- Pseudonymization, encryption at rest, least-privilege access, and default-off retention follow the same principles that data-protection regulations like GDPR and HIPAA's Security Rule demand of sensitive-data custodians.
- The data-handling policy and these controls are reviewed on a recurring schedule by the governance layer of BP Technologies LLC — see our Corporate Structure page.
- All data — raw files, reports, and account records — is stored and processed exclusively in the United States, and our policy on government and law-enforcement access requests is public on our Transparency page.
Found a security concern?
If you believe you have identified a security or privacy issue, we want to hear from you — please report it privately and we will investigate promptly.
privacy@geneticcoding.comFor corporate and governance details, see Corporate Structure. For how we handle government and law-enforcement requests, see our Transparency policy.