How genomic data is held
Selected genomic-result fields use application-layer encryption. Account controls and their current availability are described below.
Clerk auth · genomic-result encryption · account controls
Ownership and portability
Genomic data and the results derived from it belong to the user. Account and genome-file export are currently unavailable; data requests can be sent to privacy@herugenomics.com. Full-account deletion is confirmation-gated and completes only after any paid membership is terminal and no hosted checkout remains actionable or unresolved.
Encryption & the stack
Genomic results are encrypted at the application layer before storage, on top of provider encryption at rest and in transit.
Tenant isolation
Identity-scoped routes are forced dynamic and never cached across users. Responses set no-store and vary on the session cookie. Defense-in-depth checks reject any profile row whose owner does not match the authenticated user.
Deletion, export & consent
Current availability and limits of account controls.
The clinical boundary
Haeckel is an intelligence and modeling platform. It is not a diagnostic device.
What we never do
- Genomic data is never sold.
- Genomic data is never used for research or model training without explicit, revocable consent.
- One user’s data is never exposed to another. Isolation is enforced at the route level.
- Genomic data is never stored on the filesystem. Encrypted database and object storage only.