Why we literally can't see your genome
Most “upload your DNA” services send your raw file to a server. Codon is built the opposite way on purpose — the genome is parsed and held only in your browser, and only a handful of question-relevant variants are ever sent anywhere.
- · Raw file read with FileReader
- · Parsed into a genotype map
- · ~700k markers held in memory
- · Optional on-device localStorage
- · Receives a tiny variant slice
- · Plus curated public evidence
- · Reasons, returns a plain answer
- · Never sees the whole file
The file is read locally
When you drop your file, the browser's FileReader API reads it as text. That happens on your machine. No network request carries the file — you can confirm it yourself in the Network tab.
Parsing happens in memory
Codon turns ~700,000 rows into an in-browser map of { rsid → genotype }. This map is the only place your genome exists, and it's never serialized to a server.
Only relevant variants leave — never the genome
When you ask a question, a client-side router figures out which variants matter, pulls just those, and sends them with curated public evidence. A hard server-side cap rejects any payload over 50 loci, so a bug can never exfiltrate the whole file.
You stay in control
Persistence is opt-in and lives in your browser's localStorage on this device only. One click wipes it. Nothing is tied to a genome on our side — ever.
Important. Codon is an educational tool that helps you interpret raw genetic data you already own. It is not a medical device and does not diagnose, treat, or prevent any condition. Genetic associations describe probabilities across populations, not your destiny. Always talk to a qualified clinician or genetic counselor before making any health decision.