Getting started

Privacy and what we do with your data

Encryption at rest, subprocessors, live voice processing, and how to delete everything if you ever change your mind.

4 min read · updated Sep 27, 2026

Genomic data is sensitive. Haeckel uses Clerk for account authentication, provider encryption at rest for stored uploads, and application-layer encryption for selected genomic-result fields.

Encryption at rest

Raw uploads are stored in Cloudflare R2 with provider encryption at rest. This is distinct from application-layer encryption of analysis results.

Selected genomic-result fields use application-layer encryption before database storage, including ancestry, polygenic scores, key variants, health markers, kinship panels and phenotype predictions. Provider encryption at rest and TLS are separate protections; this does not claim that every stored field has the same encryption coverage.

Where your data goes

The Privacy Policy describes provider processing and retention. The service categories below are an overview, not a certified or exhaustive subprocessor register:

  • A frontier-model LLM provider for Mirror conversations. Receives the assembled context plus your current message. Never the raw DNA file.
  • ElevenLabs for voice: it receives live microphone audio when you start Scribe transcription, and Mirror's response text for speech synthesis. If Scribe is unavailable, your browser's built-in speech-recognition service may process microphone audio under the browser vendor's terms. Neither voice path receives your raw DNA file.
  • An embeddings provider for the Networks recommender. Receives a sanitised text profile, never raw genotypes.
  • A hosting provider and an application-database provider, both with encrypted-at-rest storage.
  • Cloudflare R2 for raw uploads, with provider encryption at rest.
  • An authentication provider that sees identity fields but never genomic data.
  • An error-monitoring provider where sensitive fields are scrubbed at the SDK layer before any payload leaves the application.

No data goes to any third party for training, marketing, or research without explicit per-feature consent. There is no consent screen at signup that hides such permission in the fine print. No data goes to any insurer or employer; we will never share, sell, or otherwise transfer identified or pseudonymised genetic data to either category, regardless of legal pressure short of a court order with proper jurisdiction (in which case you are notified before disclosure unless we are legally prohibited from doing so).

Audit log

The application records selected activity and security events. This is not a complete history of every data read, and a downloadable access audit is not currently available.

Data export

Account and genome-file export are currently unavailable. For a data request, contact privacy@herugenomics.com.

How full-account deletion works

Open Settings → Privacy → Delete all my data. After the confirmation step, Haeckel first verifies that any paid membership is terminal and that no hosted checkout remains actionable or unresolved. If billing safety cannot be confirmed, deletion is temporarily blocked and nothing is erased; you can retry after Billing is reconciled. Once deletion completes, production data and backup retention follow the published Privacy Policy and applicable law. Whop and other payment providers may retain transaction records independently under their own terms and legal obligations.

Privacy questions and data requests

See the Privacy Policy for data-handling terms and contact privacy@herugenomics.com with questions or requests. This Help article describes product controls; it is not a compliance certification.

Ask Mirror about this for your own genome

Explain this article in the context of my own genome and tell me what is most relevant for me.

Help & Docs — Haeckel