How genomic data is held.
Genomic results are encrypted at the application layer, isolated per identity, and exportable or erasable on request. Each statement below maps to a provider configuration or a live endpoint.
Clerk auth · application-layer genomic encryption · full export & deletion
Ownership and portability
Genomic data and the results derived from it belong to the user. The complete dataset exports as machine-readable JSON. Data and accounts delete permanently on request.
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
These are live endpoints in the product.
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.