How DNA Match works.
Eluent's DNA Match maps your consumer SNP-array genotypes to per-peptide pharmacogenomic context. Built fully client-side so your genome never reaches our infrastructure. Research only.
Your raw DNA file never leaves this device. It is parsed in a Web Worker inside your browser, intersected against our curated PGx variant table, and rendered locally. There is no upload endpoint and no server log of your genotype.
- · Parses raw 23andMe / Ancestry / MyHeritage / LivingDNA / FTDNA exports.
- · Intersects ~600k of your SNP calls against ~50 curated PGx variants.
- · Renders per-peptide annotations with evidence levels and PMIDs.
- · Lets you cache the parsed map locally (encrypted) for return visits.
- · No upload to our server — ever.
- · No clinical PGx (CPIC dosing, CYP star alleles, FDA labels).
- · No ancestry / haplogroup / disease risk / carrier status.
- · No imputation of missing genotypes from linkage disequilibrium.
- · No raw-genotype display — per-peptide context only.
Which files are supported?
Raw DNA exports from 23andMe (v3 / v4 / v5), AncestryDNA (v1 / v2), MyHeritage, LivingDNA, and FamilyTreeDNA. Files larger than 50 MB are rejected — Eluent supports consumer SNP arrays only. VCF / whole-genome data is out of scope for this release.
Why client-side instead of OAuth (Connect 23andMe / Ancestry)?
23andMe deprecated their consumer API in 2025; AncestryDNA and MyHeritage never offered a customer-facing OAuth flow. Raw-file parsing is the only path that works across all five vendors. The privacy upside is also better — even if 23andMe re-opened API access, OAuth would require Eluent to receive your data en route. Client-side parsing means we never see it.
Why not just upload the file and parse on the server?
Genotype data is sensitive. Server-side parsing would require Eluent to become a controller of your special-category data under most privacy frameworks. Doing it in your browser keeps the threat model trivial — you trust your own machine; Eluent never enters the picture.
How do I verify Eluent isn't sneaking my file off-device?
Two ways: (1) open your browser's Network panel before dropping the file — you will see no outbound POST during the parse; (2) Eluent's service worker actively rejects any POST from the
/dna-matchroute as a second-line defense, so even a future regression would be blocked client-side.Does Eluent log that I uploaded a file?
We log only that a Pro user accessed
/dna-matchand how long the parse took. No file contents, no rsIDs, no genotype calls, no peptide names. The analytics whitelist is enforced for this route.What is the curated PGx variant database?
~50 SNPs curated against PharmGKB, ClinVar, gnomAD v3, and primary literature. Each variant carries an evidence level (A/B/C/D) and PMID citations. Updated quarterly. Coverage grows over time.
What does evidence A vs B vs C vs D mean?
A = high-confidence direct evidence (multiple GWAS / RCT studies); B = moderate-confidence indirect evidence (variant affects a binding pocket the peptide is known to engage); C = low-confidence functional inference (hidden by default — toggle "show speculative" to reveal); D = speculative / analogical only (never rendered in v1).
Will my results change over time?
Yes — quarterly DB updates can add or revise annotations. The match runs against the live DB at view time. We never retain old annotations if curation changes.
Is this medical advice?
No. DNA Match is a research-only tool. We do not provide diagnostic information, dosing recommendations, or carrier-status reporting. Talk to a clinician before acting on any genetic information.