Data Privacy

what we store, where, and how to delete it

our commitment

Privacy is a constraint we design around, not a marketing line. Where data must live on a server to deliver the product (cloud sync, multi-device, AI Coach history, persistent DNA findings), it lives in row-level-security-scoped tables that only you can read. Where it doesn't need to leave your device, it doesn't.

Local-First, Cloud-Synced When Signed In

Your intake answers and analysis results are kept in your browser's local storage. If you create an account and enable cloud sync, an RLS-scoped copy is stored in our Supabase database so the same profile loads across your devices.

Calibration Requires an Account

Calibration requires an account. The Free tier does not require a paid plan. Pro and Clinical features (cloud sync, AI Coach history, multi-profile, DNA persistence) require an authenticated Supabase account tied to your email.

Never Sold. Ever.

Your biology is not a product. We do not sell your health data to advertisers or brokers. Analysis and Coach calls go to Google Gemini as a processor — details below.

Data You Can Delete

You can delete your account and wipe all server-stored profile, analysis, chat, and genomic rows from inside the app at any time. Local-storage data is cleared from your browser when you sign out or clear site data.

Raw DNA Files Never Leave Your Device

Your raw DNA file (23andMe / Ancestry / etc.) is parsed entirely in your browser. We extract only the targeted SNP rows we interpret (currently 678 markers — rsid + genotype) and discard the raw file from memory. Those extracted rows are sent to our server for reviewed static lookup and, when signed in, stored in our RLS-scoped genomic_data table so findings can re-render across devices. When DNA is shown, analysis, diet, lifestyle, lab synthesis, and Coach may receive allowlisted reviewed phenotypes (gene, rsid, risk, interpretation) — never nucleotide genotypes. Hide DNA in the menu to keep those phenotypes out of AI context. Genetic details you type in a message still go to Gemini.

What We Collect

Intake profile: first name, birth year, biological sex, dietary protocol, health goals — kept in browser local storage; mirrored to RLS-scoped Supabase profile_data rows when you sign in and cloud sync is enabled
Health context: current medications, known conditions, allergies, pregnancy status, lifestyle flags (alcohol, smoking, nicotine, stress, sleep window if you enter one), optional surgeries/injuries, optional peptide protocols, and lab panels you upload or enter — same storage path as the intake profile
Intake drafts: a short-lived copy of an unfinished calibration form in browser local storage (cleared on save)
Current supplement stack and analysis results — local storage by default, mirrored to profile_data on cloud sync
AI Coach conversations — stored in our RLS-scoped chat_messages table for authenticated users so history persists across sessions
Supplement and medication label photos — sent to our AI for extraction and not retained on our servers after the response; medication thumbnails may remain in this browser's IndexedDB
Lab report images/PDFs and extracted lab values — uploaded to Google Gemini when you choose AI lab parsing, then the structured panel may be stored in your RLS-scoped profile data; the uploaded file is not retained by our application after the response
Wearable screenshots you upload — sent to our AI to extract visible metrics; not retained on our servers after the response
Extracted genetic markers (rsid + genotype + interpretation) for 678 targeted SNPs — stored in our RLS-scoped genomic_data table for authenticated users so DNA-informed findings can re-render
Authentication metadata (email, Supabase user id, plan tier) — required for accounts; managed by Supabase Auth
Anonymous product analytics (Vercel Analytics + Speed Insights) — page views, route timings, web-vital metrics; no health data, no profile content, no PII payloads

What We Never Collect

Your raw DNA file — it is parsed in your browser and never uploaded
A retained copy of your raw lab file — when you choose AI lab parsing, the file is sent transiently to Google Gemini for extraction, but our application does not retain the uploaded file after the response
Phone number or postal address
Location or IP-based geolocation data
Cross-site advertising cookies or device fingerprinting identifiers
Payment card details — when billing is enabled, payments are processed by Stripe and we never see card numbers
Data from third-party health apps or wearables except screenshots you choose to upload

Third-Party Services

Supabase (US-hosted) — managed Postgres + Auth. All user-scoped tables (profile_data, chat_messages, genomic_data) enforce row-level security. Encryption at rest is provided by the platform.
Google Generative AI (Gemini), our disclosed AI processor — receives the structured context needed for intake classification, stack analysis, diet/lifestyle guidance, lab synthesis, and Coach responses. This can include conditions, medications, lab values, reviewed genomic phenotypes, and free-text notes. For label, lab, and wearable extraction, the selected image or PDF bytes are sent transiently because OCR requires the document; do not upload a file containing information you do not want processed. No raw DNA files, nucleotide genotypes, profile names, or payment data are sent to Gemini. Google processes this data under the applicable Gemini API terms and retention controls.
Vercel — application hosting (HTTPS), plus Vercel Analytics and Speed Insights for anonymous traffic and performance metrics. We do not pass health data, profile content, or genomic findings into analytics events.
Upstash Redis — rate-limit counters keyed by user id; no profile content stored.
Stripe — payment processing for paid plans (when enabled). Stripe receives card data directly; we receive only a customer id and subscription status.
Resend — transactional email (account confirmations, password resets) when you have an account.

AI Data Processing Disclosure

When you calibrate a profile, scan a medication or supplement label, parse a lab report, classify a free-text condition, run an analysis, or use the AI Coach, the following may be transmitted to Google Gemini: medications, conditions, allergies, pregnancy status, biometric inputs, lab values or uploaded lab images/PDFs, supplement stack, reviewed genomic phenotypes, extracted label text, and free-text notes you type. DNA-aware surfaces receive reviewed phenotype summaries only — not nucleotide genotypes or raw DNA files — and respect the Hide DNA setting. Uploaded OCR documents are sent as selected; the app does not perform arbitrary visible-text redaction before Gemini processing. If you type genetic details into a message, that text is transmitted. We do not transmit billing data or your name.
AI outputs pass through our post-generation safety filter before being returned to you. Recommendations are educational; they are not medical advice and are not reviewed by a clinician.

Server Logs and Telemetry

We log request-level metadata (route, status, latency, pseudonymous user id, model name, token counts) to operate and debug the service. We do NOT log prompt content, AI response content, medication names, condition names, gene names, rsids, genotypes, or lab values into observability sinks.
Error reports use sanitized error codes and scope identifiers — never the raw row content that triggered the error.

How we handle genetic information

If you upload DNA data, we process the extracted SNP markers against reviewed static interpretations for screening context. GINA restricts employers and health insurers from using genetic information in certain decisions — we are not an employer or insurer. We do not share genetic data with employers or insurers. You can delete all genetic data at any time from your DNA settings; deletion also wipes DNA-derived blobs (diet plan, lifestyle protocol, genomic supplements) from your profile.

Your Rights

Access — request a copy of all data we store about you
Correct — edit your profile data directly in the app at any time
Delete — wipe your account and all server-stored rows from your account settings
Export — download your analysis history as PDF or JSON
California (CCPA) and Washington (My Health My Data Act) residents may have additional rights, including the right to opt out of any data processing not strictly necessary to deliver the service. Contact privacy@titrate.app to exercise these rights.

Last updated: August 2026

Run my analysis

titrate

What We Collect

Intake profile: first name, birth year, biological sex, dietary protocol, health goals — kept in browser local storage; mirrored to RLS-scoped Supabase profile_data rows when you sign in and cloud sync is enabled

Health context: current medications, known conditions, allergies, pregnancy status, lifestyle flags (alcohol, smoking, nicotine, stress, sleep window if you enter one), optional surgeries/injuries, optional peptide protocols, and lab panels you upload or enter — same storage path as the intake profile

Intake drafts: a short-lived copy of an unfinished calibration form in browser local storage (cleared on save)

Current supplement stack and analysis results — local storage by default, mirrored to profile_data on cloud sync

AI Coach conversations — stored in our RLS-scoped chat_messages table for authenticated users so history persists across sessions

Supplement and medication label photos — sent to our AI for extraction and not retained on our servers after the response; medication thumbnails may remain in this browser's IndexedDB

Lab report images/PDFs and extracted lab values — uploaded to Google Gemini when you choose AI lab parsing, then the structured panel may be stored in your RLS-scoped profile data; the uploaded file is not retained by our application after the response

Wearable screenshots you upload — sent to our AI to extract visible metrics; not retained on our servers after the response

Extracted genetic markers (rsid + genotype + interpretation) for 678 targeted SNPs — stored in our RLS-scoped genomic_data table for authenticated users so DNA-informed findings can re-render

Authentication metadata (email, Supabase user id, plan tier) — required for accounts; managed by Supabase Auth

Anonymous product analytics (Vercel Analytics + Speed Insights) — page views, route timings, web-vital metrics; no health data, no profile content, no PII payloads

What We Never Collect

Your raw DNA file — it is parsed in your browser and never uploaded

A retained copy of your raw lab file — when you choose AI lab parsing, the file is sent transiently to Google Gemini for extraction, but our application does not retain the uploaded file after the response

Phone number or postal address

Location or IP-based geolocation data

Cross-site advertising cookies or device fingerprinting identifiers

Payment card details — when billing is enabled, payments are processed by Stripe and we never see card numbers

Data from third-party health apps or wearables except screenshots you choose to upload

Third-Party Services

Supabase (US-hosted) — managed Postgres + Auth. All user-scoped tables (profile_data, chat_messages, genomic_data) enforce row-level security. Encryption at rest is provided by the platform.

Google Generative AI (Gemini), our disclosed AI processor — receives the structured context needed for intake classification, stack analysis, diet/lifestyle guidance, lab synthesis, and Coach responses. This can include conditions, medications, lab values, reviewed genomic phenotypes, and free-text notes. For label, lab, and wearable extraction, the selected image or PDF bytes are sent transiently because OCR requires the document; do not upload a file containing information you do not want processed. No raw DNA files, nucleotide genotypes, profile names, or payment data are sent to Gemini. Google processes this data under the applicable Gemini API terms and retention controls.

Vercel — application hosting (HTTPS), plus Vercel Analytics and Speed Insights for anonymous traffic and performance metrics. We do not pass health data, profile content, or genomic findings into analytics events.

Upstash Redis — rate-limit counters keyed by user id; no profile content stored.

Stripe — payment processing for paid plans (when enabled). Stripe receives card data directly; we receive only a customer id and subscription status.

Resend — transactional email (account confirmations, password resets) when you have an account.

AI Data Processing Disclosure

When you calibrate a profile, scan a medication or supplement label, parse a lab report, classify a free-text condition, run an analysis, or use the AI Coach, the following may be transmitted to Google Gemini: medications, conditions, allergies, pregnancy status, biometric inputs, lab values or uploaded lab images/PDFs, supplement stack, reviewed genomic phenotypes, extracted label text, and free-text notes you type. DNA-aware surfaces receive reviewed phenotype summaries only — not nucleotide genotypes or raw DNA files — and respect the Hide DNA setting. Uploaded OCR documents are sent as selected; the app does not perform arbitrary visible-text redaction before Gemini processing. If you type genetic details into a message, that text is transmitted. We do not transmit billing data or your name.

AI outputs pass through our post-generation safety filter before being returned to you. Recommendations are educational; they are not medical advice and are not reviewed by a clinician.

Server Logs and Telemetry

We log request-level metadata (route, status, latency, pseudonymous user id, model name, token counts) to operate and debug the service. We do NOT log prompt content, AI response content, medication names, condition names, gene names, rsids, genotypes, or lab values into observability sinks.

Error reports use sanitized error codes and scope identifiers — never the raw row content that triggered the error.

How we handle genetic information

If you upload DNA data, we process the extracted SNP markers against reviewed static interpretations for screening context. GINA restricts employers and health insurers from using genetic information in certain decisions — we are not an employer or insurer. We do not share genetic data with employers or insurers. You can delete all genetic data at any time from your DNA settings; deletion also wipes DNA-derived blobs (diet plan, lifestyle protocol, genomic supplements) from your profile.

Your Rights

Access — request a copy of all data we store about you

Correct — edit your profile data directly in the app at any time

Delete — wipe your account and all server-stored rows from your account settings

Export — download your analysis history as PDF or JSON

California (CCPA) and Washington (My Health My Data Act) residents may have additional rights, including the right to opt out of any data processing not strictly necessary to deliver the service. Contact privacy@titrate.app to exercise these rights.