How GenomeInsight Works

Your DNA never leaves your device. Here's exactly how.

Data Flow

1

You select your raw DNA file

Choose the .txt or .csv file you downloaded from 23andMe, AncestryDNA, or MyHeritage. The file stays on your device.

2

Browser parses the file locally

JavaScript running in your browser reads the file using the File API. The raw text is parsed into structured SNP data (rsID, chromosome, position, genotype). No network request is made.

3

Variants are matched against our database

Your genotypes are compared against a bundled database of 500+ clinically relevant genetic variants. This database ships with the page — it's already in your browser before you upload anything.

4

Results are generated in-browser

Risk scores, pharmacogenomics interactions, carrier status, traits, and ancestry estimates are all computed locally using JavaScript. Results are displayed immediately.

5

Nothing is sent anywhere

Your raw DNA data, parsed genotypes, and analysis results stay entirely in your browser. When you close the tab, the data is gone (unless you explicitly save a report).

What Leaves Your Browser

Standard web requests

Page assets (HTML, CSS, JavaScript, images) are loaded from our CDN when you visit the site. This is normal web browsing — no genetic data is involved.

Anonymous analytics

We use Vercel Analytics to count page views. No genetic data, no personal identifiers.

Authentication (optional)

If you create an account, login credentials are handled by Supabase Auth. Your genetic data is never linked to your account on any server.

Your raw DNA file

Never uploaded. Never transmitted. Never stored on any server.

Your genotype data

Never sent in any API call, webhook, or analytics event.

Your analysis results

Never transmitted to our servers or any third party.

Verify It Yourself

Don't take our word for it. You can verify that no genetic data leaves your browser:

  1. 1. Open DevTools — Press F12 or Ctrl+Shift+I (Cmd+Option+I on Mac)
  2. 2. Go to the Network tab — This shows every request your browser makes
  3. 3. Upload your DNA file and run the analysis
  4. 4. Search for any genotype data — Filter requests by content. You'll find zero requests containing SNP IDs, genotypes, or raw file contents
  5. 5. Check the request payloads — Click on any request and inspect its body. No genetic information appears anywhere

Technical Details

Framework: Next.js with React — server-side rendering for fast page loads, but all genetic analysis runs client-side

File parsing: The browser's FileReader API reads the raw file. A custom parser extracts SNP data based on the detected file format (23andMe, AncestryDNA, MyHeritage, VCF)

Variant database: A curated database of clinically relevant SNPs ships as part of the JavaScript bundle. It includes risk alleles, odds ratios, and population frequencies sourced from peer-reviewed literature

Analysis engine: Pure JavaScript functions compute risk scores, metabolizer phenotypes, carrier status, and trait predictions. No external API calls

Storage: Results can be saved to your browser's localStorage for convenience. This data never leaves your device. Clearing browser data removes it permanently