Revora Consumer Health Data Privacy Notice

Version: v1.0.2.4 Effective date: 2026-06-13 Last updated: 2026-06-13


Scope of this notice

This Consumer Health Data Privacy Notice describes how Revora, Inc. ("Revora," "we," "us," or "our") processes consumer health data as that term is defined under applicable US state laws. This notice applies to residents of:

If you are a resident of one of these states, this notice supplements our main Privacy Notice and describes the additional protections, disclosures, and rights that apply to consumer health data under your state's law. In the event of a conflict between the main Privacy Notice and this Consumer Health Data Privacy Notice, this Consumer Health Data Privacy Notice applies to the extent it is consistent with applicable US state law.

If you are a resident of a state not listed above, the disclosures and rights in this notice may not apply to you, but the rights described in our main Privacy Notice §15 and §24 do apply.

This notice is published as a separate and distinct document, linked from our website homepage and from the main Privacy Notice, in compliance with the "separate and distinct link" requirement under MHMDA RCW 19.373 and corresponding requirements under Nevada SB-370 and Connecticut CTDPA.

This notice does not apply to any consumer health data we process on behalf of an enterprise customer (for example, an employer-sponsored wellness program). Revora has no enterprise customers at v1.0; if that changes, this notice will be updated.


1. Categories of consumer health data we collect

For the purposes of this notice, "consumer health data" (CHD) means personal information that identifies your past, present, or future physical or mental health status, as defined under applicable state law. Revora collects the following categories of consumer health data:

We do not collect:

If we collect any of the above categories in the future, we will update this notice and seek explicit consent where required.


2. Categories of sources of consumer health data

We collect consumer health data from the following categories of sources:

We do not buy consumer health data about you from data brokers, marketing data providers, or any third-party data source. We do not receive consumer health data about you from healthcare providers, laboratories (other than a lab report you yourself upload), insurance companies, or employers.


3. Purpose of consumer health data collection and use

We use consumer health data only for the purposes described below:

We do not use consumer health data for:


4. Categories of consumer health data we share, sell, or disclose

We do not sell consumer health data. We do not share consumer health data for monetary or other valuable consideration with any third party.

We share consumer health data only with sub-processors that operate the Service on our behalf, as described in §5. We do not share consumer health data with employers, insurance companies, public databases, third-party advertisers, or any party offering insurance or benefits.

We may disclose consumer health data when:


5. Categories of third parties and named affiliates that receive consumer health data

The third parties listed below are the sub-processors that receive consumer health data as part of operating the Revora Service. Each is bound by a signed Data Processing Agreement that requires them to process your data only as we instruct, to keep it secure, and to delete it when we ask. The full sub-processor list is in our main Privacy Notice §10; the entries below are the ones that handle consumer health data specifically.

The "Contact" column provides direct contact mechanisms for each sub-processor, as required by the Washington My Health My Data Act (RCW 19.373) and corresponding statutes — you have the right to contact each recipient regarding consumer health data they have received from us.

Sub-processor Role Consumer health data received Region Contact
Supabase Inc. Primary database All consumer health data (bloodwork, biomarker, protocol state, member context, adherence, audit log) United States (us-east-1) privacy@supabase.com; https://supabase.com/privacy
Anthropic, PBC (via AWS Bedrock) AI model API Bloodwork results and member context (de-identified at API call boundary), for narrative explanations of deterministic protocol outputs ("why this is in your protocol"), cycle-outcome narratives, conversational protocol assistance, summary-email content, and free-text medication and supplement extraction — explanatory prose around deterministic protocol logic. Does NOT make protocol decisions — those are made by Revora's deterministic engine. United States (AWS us-east-1) privacy@anthropic.com; https://www.anthropic.com/legal/privacy
Microsoft Corporation (Azure OpenAI Service + Azure App Service) AI model API + application hosting (i) Azure OpenAI: bloodwork results and member context (de-identified at API call boundary), for case-study content and fallback narrative — explanatory prose around deterministic protocol logic; does NOT make protocol decisions. (ii) Azure App Service: all consumer health data in transit (account, bloodwork, protocol, adherence, communications) — production hosting per ADR-0047. United States (Azure East US; both services) https://aka.ms/privacyresponse; Microsoft EU DPO, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, D18 P521, Ireland
Google LLC (Google Cloud / Vertex AI) AI model API Bloodwork PDF content (de-identified at API call boundary), for bloodwork PDF parsing — explanatory prose around deterministic protocol logic does not apply here; this provider returns structured parse data rather than narrative. Does NOT make protocol decisions, interpret biomarkers, or generate recommendations. Global (multi-region; processing location determined by Google) — preview-generation Gemini parser model is served via Vertex's global endpoint only Google Cloud Data Processing Addendum incorporating EU Standard Contractual Clauses + UK International Data Transfer Addendum; https://policies.google.com/privacy; https://cloud.google.com/terms/data-processing-addendum
Resend Inc. (Resend Inc. for inbound bloodwork email) Receives bloodwork PDFs attached to email and routes them to our ingestion pipeline Bloodwork data in email attachments United States privacy@resend.com; https://resend.com/legal/privacy-policy; DPA at https://resend.com/legal/dpa
Google LLC (Google Workspace / Gmail support inbox) Stores member inquiries sent to privacy@revoraapp.com and other support addresses Communications data; may contain consumer health data when members include health-related details (for example, a member emailing about their bloodwork or a privacy rights request that references their health information) Not contractually committed at current subscription tier; Google operates per global DPA. Revisit at Enterprise Plus upgrade. https://policies.google.com/privacy; Google Workspace Data Processing Amendment at https://workspace.google.com/terms/dpa_terms.html

Sub-processors that do NOT receive consumer health data (listed for completeness, full details in the main Privacy Notice §10):

Affiliates. Revora has no corporate affiliates as of the effective date of this notice.


6. MHMDA-required disclosure chart

This chart provides the disclosure required by Washington's My Health My Data Act, Nevada SB-370, and Connecticut Data Privacy Act for consumer health data.

Consumer health data we collect Source Purpose of collection and use Categories of third parties with whom shared
Bloodwork and biomarker readings Self-reported (you upload your lab report) Service delivery (protocol generation); audit-logged interpretations; aggregated/de-identified service improvement Sub-processors only (Supabase, AI providers — Anthropic/Microsoft/Google, Resend Inc. for inbound bloodwork email); we do not share with any other third parties
Health-related self-reported information (medications, conditions, goals, lifestyle) Self-reported (during onboarding and as you use the Service) Service delivery (protocol generation, member-context-aware recommendations); audit-logged interpretations Sub-processors only (Supabase, AI providers — Anthropic/Microsoft/Google); we do not share with any other third parties
Inferred and derived health-related data (responder profiles, expected response windows) Generated by Revora from sources above Service delivery (improving protocol generation specificity); audit-logged interpretations Sub-processors only (Supabase, AI providers); we do not share with any other third parties
Protocol and adherence data Generated by Revora; updated based on your in-app interactions Service delivery (cycle management, re-test coordination, adherence tracking); audit-logged interpretations; aggregated/de-identified service improvement Sub-processors only (Supabase); we do not share with any other third parties
Audit and event logs on protocol interpretations Generated by Revora protocol engine (deterministic stack-assembly events written to event_log; LLM-assisted narrative records written to audit_log) Internal record-keeping for member transparency, advisor review, and regulatory inquiries; logs are part of your record and are exportable per main Privacy Notice §16. Coverage of every recommendation-generation surface is being completed as part of v1.x audit hardening. Sub-processors only (Supabase); we do not share with any other third parties

7. Your rights regarding consumer health data

If you are a resident of Washington, Nevada, or Connecticut, you have the following rights regarding consumer health data under your state's law. These rights supplement (and in some cases overlap with) the rights described in our main Privacy Notice §15.

7.1 Rights for Washington residents (My Health My Data Act, RCW 19.373)

7.2 Rights for Nevada residents (Nevada SB-370)

Nevada residents have substantially the same rights as Washington residents under Nevada SB-370, with the following procedural notes:

7.3 Rights for Connecticut residents (Connecticut Data Privacy Act)

Connecticut residents have the following rights under CTDPA with respect to consumer health data:


8. How to exercise your rights

To exercise any right described in this notice, please contact us:

Email: privacy@revoraapp.com

When contacting us, please include:

If you do not have a Revora account but believe we have collected consumer health data about you, please describe the basis of your request so we can verify your identity and respond appropriately.

Verification. Before processing a request, we may need to verify your identity. We will typically verify identity by confirming information already on file with us — your account email, recent activity, or similar. If you do not have an account with us, we may request additional information for verification, used only for that purpose.

Authorized agents. You may designate an authorized agent to submit a request on your behalf. We may require verification of the agent's authorization (a signed permission form or power of attorney) and may also separately verify your identity to confirm the agent's authority.

Timeline. We will confirm receipt of your request within 10 business days. We will respond to your request within 30 days of receipt; complex requests may be extended once for an additional 30 days, with notice within the original 30-day window. (Note: the response window for Connecticut and Nevada residents is up to 45 days under state law; we apply our 30-day window as a member-favorable standard.)

Fee. We do not charge a fee for processing requests under this notice, except where a request is excessive, repetitive, or manifestly unfounded under applicable law. If we determine a fee applies, we will tell you why and provide a cost estimate before completing the request.

Declining to provide information. Some consumer health data is essential to providing the Service (most notably, bloodwork and biomarker readings — without those, we cannot generate your protocol). If you decline to provide essential data, or if you withdraw consent for essential data, we may not be able to continue providing the Service, and we will notify you of this consequence.


9. How to appeal a denial

If we deny a request you've made under this notice, you have the right to appeal. Submit your appeal by email to privacy@revoraapp.com with the subject line "Privacy Rights Appeal" and a description of the request that was denied and your basis for appeal.

We will respond to appeals within the following timelines:

If your appeal is denied, you may file a complaint with your state Attorney General:


10. Versioning and changes

We publish a plain-language version history here so you can see what's changed and when. Every published version is also available on request from privacy@revoraapp.com.

Version Date What changed
v1.0.2.4 2026-06-13 Removed an internal placeholder row from this changelog. Fixed a visual issue where long URLs in the sub-processor table didn't wrap correctly within the page's reading-mode width. No substantive disclosure changes.
v1.0.2.3 2026-06-13 Rewrote this version history for public readability (the prior text was dense with internal terminology). Applied Revora's brand typography, color palette, and reading-mode spacing to how this notice is displayed on our website. No substantive disclosure changes.
v1.0.2.2 2026-06-12 Removed some internal drafting notes that had inadvertently been included at the bottom of this notice. Sub-processor disclosures unchanged. (The main Privacy Notice received a parallel update adding a sub-section on how Revora handles Google user data when you sign in with Google.)
v1.0.2.1 2026-06-11 Corrected the disclosed processing region for the Google Vertex AI parser (used to extract data from uploaded bloodwork PDFs) from "United States" to "Global". The Gemini model we use is in fact served only via Google's global endpoint, which routes inference to any of Google's data center regions worldwide. The transfer is governed by Google Cloud's Data Processing Addendum incorporating EU Standard Contractual Clauses and the UK International Data Transfer Addendum. Mirrors the parallel main-notice correction.
v1.0.2 2026-06-11 Updated the sub-processor list to reflect cookieless analytics (PostHog) and Revora's deterministic protocol engine (with AI used only in supporting roles). Updated the Microsoft Corporation row to reflect that Microsoft Azure now also provides our production application hosting. Mirrors the parallel main-notice update.
v1.0.1 2026-05-29 Updated the sub-processor list (removed Sentry; PostHog now handles both product analytics and error tracking). Added Washington / Nevada / Connecticut Consumer Health Data classification for allergies, medical conditions, and family medical history collected at onboarding. Corrected the disclosed support inbox region. Corrected the contact email domain.

We may update this notice from time to time. The "Last Updated" date at the top reflects when we last changed it. Material changes — for example, changes to the categories of consumer health data we collect, new third-party recipients of consumer health data, or new purposes for which we use consumer health data — will be communicated to affected members at least 30 days before the change takes effect, by email and through an in-app notification.


Return to Revora