How we protect your genomic and medical data.

Your DNA and lab results are some of the most personal data you own. This page describes the technical and organizational controls that keep them safe — what is encrypted, who can see what, how we log access, and how quickly we delete data when you ask.

Encryption at rest and in transit

All data is encrypted in transit over TLS 1.2+ between your browser and our servers.
Data at rest in Firebase Firestore and Cloud Storage is encrypted with AES-256 using Google-managed keys.
Uploaded DNA and lab files are stored separately from parsed results and never served back out without an authenticated request.
Backups inherit the same encryption — no unencrypted copies exist.

Authentication and session security

Sign-in through Firebase Authentication with email/password, Google, or Apple — we never see your password.
Server-side API routes verify the Firebase ID token on every request via the Admin SDK — no shared secrets live in your browser.
Session tokens rotate automatically on a short schedule.
Admin dashboards sit behind a role gate and a separate audit trail.

Access controls

Firestore security rules restrict every read and write — a user can only touch their own uploads, reports, findings, and preferences.
Internal access to production data is limited to a small set of engineers and is logged per session.
Third-party integrations (Stripe, Resend, OpenRouter) receive only the minimum fields they need — never your raw genome or full lab history.

Audit logging

Admin actions (viewing user records, editing knowledge-base entries, reprocessing reports) are written to a permanent audit log.
As a user, you can request a copy of every action taken on your account under Settings → Privacy.
Unusual access patterns trigger alerts to our on-call engineer.

Data retention and deletion

You can delete any upload, report, or your entire account at any time from Settings → Delete Data.
Deletion is a cascading purge: raw file, parsed variants, derived findings, recommendations, notifications — all of it.
Anonymous leads collected from the free quiz auto-expire after 30 days unless you create an account.
Backups are rotated on a 30-day window; once expired, nothing can be recovered.

Infrastructure

Application runs on Vercel (edge + serverless). Data lives in Google Cloud regions chosen for your residency.
Build artifacts are scanned for known vulnerabilities on every deploy.
Dependencies are locked via package-lock and reviewed on upgrade.

Compliance posture

We design to HIPAA-aligned principles even though we are not a covered entity — encryption, access controls, audit logging, and breach notification.
We will sign a BAA with healthcare partners on a case-by-case basis for enterprise engagements.
For EU/UK users we operate under GDPR principles: lawful basis, data minimization, right of access, right to be forgotten.

Breach response

If we ever detect unauthorized access to your data, we will notify affected users by email within 72 hours of confirmation, including what was exposed and what actions you should take.
We publish a post-mortem for any incident that affects more than a single user.
Report a suspected issue: security@vogelview.health — we triage every report within one business day.

Talk to us

Security questions from researchers, journalists, enterprise buyers, or curious users are all welcome. We try to reply within one business day.

security@vogelview.health See also: Privacy Policy →

Security at Vogelview