Privacy Policy
Effective Date: 18 November 2026
Last Updated: 18 November 2026
1. Introduction
Welcome to Health3 (“we,” “us,” or “our”). Your privacy is important to us. This Privacy Policy explains how we collect, use, disclose, and safeguard your personal data when you use our mobile application (the “App”), our website at health3.app (the “Website”), and related services. By using these services, you acknowledge the practices described in this policy.
Note on HIPAA applicability: Health3 is a consumer wellness application and is not a “Covered Entity” or “Business Associate” under U.S. HIPAA, because we do not provide medical services, bill health plans, or engage with insurers. We instead protect your health information under GDPR, UK GDPR, CCPA/CPRA, and relevant state privacy laws.
2. Data Controller Information
- Company Name: Health3 AG
- Address: Wiesenstrasse 10A, 8952 Schlieren, Switzerland
- Email: privacy@health3.app
EU and UK Representatives (Article 27)
Health3 AG is based in Switzerland, outside the EU/EEA and the UK. Under Article 27 of the EU GDPR and the UK GDPR we have appointed representatives that you and data protection authorities can contact about how your personal data is handled:
- EU representative: Prighter EU Rep GmbH, Schellinggasse 3/10, 1010 Vienna, Austria.
- UK representative: Prighter Ltd, 20 Mortlake High Street, London SW14 8JN, United Kingdom.
You can contact the relevant representative about any data protection matter concerning your personal data.
3. Types of Data Collected
Within the app, we collect the following types of personal data:
- Health Biomarker Data: Results of blood and other lab tests that you add to the App: by uploading a lab report (PDF or photo), entering values by hand, or, on iOS, importing lab results from Apple Health. Where a lab report or an Apple Health record shows a reference range next to a result, we store that range with the result.
- Apple Health (iOS only, optional): With your permission, the App reads the lab results stored in Apple Health, only to import them into Health3. It writes nothing to Apple Health. Data from Apple Health is never used for advertising and never sold.
- Content you create in the App: lifestyle journal entries, your answers to insight check-ins (for example “Tried it” or “Not for me”) and your ratings of insight cards.
- Personal Identification Information: Email address, display name, year of birth, gender, and a profile photo and cover photo if you add them, as shared by you by specifying profile details within the App. We also store the language you choose for the App. If you sign in with Apple or Google, we receive your email address from them (with Apple, this can be a relay address that hides your own) and, with Google, the basic profile details Google sends with the sign-in, such as your name.
- Records of your choices: When you agree on the consent screen described in Section 5, we store the time, your language setting, the text you agreed to and whether you opened this policy from that screen. We also store whether insights are on or off for your account.
- Data added before you create an account: During onboarding the App works with a temporary account without an email address. Results you add at that stage can be stored under it. When you sign up, the temporary account becomes your account. Temporary accounts that are not used for 30 days are deleted automatically.
- App and Website Analytics (only if you opt in): Analytics is off by default. Only when you enable analytics under Settings → Analytics in the App, or accept analytics cookies on the Website, do we use PostHog to collect pseudonymous product events from the App and Website, such as screens or pages opened, buttons or product flows used, app or website version, platform, browser category, locale, approximate location derived from the network request, subscription platform and coarse subscription state. Some events carry coarse ranges in place of exact numbers, for example that a report has 6 to 20 results, that 1 to 5 of them are outside the reference range, or that a score lies between 61 and 80. When you open a biomarker page in the free preview, or start adding a first value from a biomarker page, the event names that biomarker, not your values. Error reports contain the type of error and the places in our code where it happened; they do not contain the error message. On the Website, PostHog also records page views and clicks automatically. You can withdraw consent at any time in the same place, which stops future collection; in the App, this also clears the analytics identifier on that device.
For an authenticated account, events use the Health3 account UUID as a pseudonymous identifier so activity can be grouped across sessions and platforms. Consented sessions that are not associated with an authenticated account use a generated analytics identifier. We do not send your name or email as an analytics property and we do not use advertising identifiers or cross-site advertising tracking.
We never record your screen. Analytics events do not contain your lab values, reference ranges, journal entries, the text of your lab reports or your support messages. As described in Section 18, sanitized unsupported biomarker names and units may be counted separately in a privacy-minimized aggregate after analytics consent; exact unsupported names and units are not sent to PostHog. PostHog processes this data on EU infrastructure in Frankfurt. Analytics events remain available only for the event-retention period included in our PostHog service plan and are then removed. When you delete your Health3 account, we ask PostHog to delete the analytics profile and events linked to it. You can also ask us to delete them at any time. - Apple Ads Attribution (iOS only): When you open the App on iOS, it passes Apple’s ad attribution token to RevenueCat. RevenueCat uses this token to learn from Apple whether the App was installed through one of our Apple Ads campaigns and, if so, which campaign, ad group and search keyword. This does not use the advertising identifier (IDFA), and the App does not ask for tracking permission. We use this information only to measure our own advertising.
On our website, we collect the following types of data:
- Personal Data: When you interact with our website, we may collect personal information such as your name, email address, and any other information you provide voluntarily.
- Essential Website Logs: Our hosting and security providers process request metadata such as IP address, browser and operating-system category, requested path, timestamp, and security signals as necessary to deliver and protect the Website. These operational logs are separate from optional PostHog product analytics.
- Files loaded from other servers: Pages of the Website load fonts from Google Fonts and some images from our Supabase storage. The App can load fonts from Google Fonts, a few illustrations from Unsplash and some images from a second Supabase project in the United States that holds no user data. Each of these servers receives your IP address and basic browser or device details with the request.
- Links to the App Store and Google Play: Store links on the Website carry a label that names the page or campaign you came from, so that Apple and Google can show us how many installs came from which page. The label names a page or campaign, not you.
- Cookies and Local Storage: On health3.app we use strictly necessary browser storage for security and to remember your consent choice. Optional analytics cookies (PostHog and Google Analytics 4) are set only after you accept them; you can change this choice at any time under Cookie Settings on health3.app.
- Analytics Data (with your consent): If you accept analytics cookies on health3.app, we use PostHog and Google Analytics 4 (Google LLC) to measure website visits. Both remain disabled until you opt in, and you can change this choice at any time under Cookie Settings on health3.app.
4. Purpose of Data Processing
We process your data for the following purposes:
- Providing Services: To deliver the App’s functionalities, including tracking and analyzing health metrics, we process the biomarker data you share with us.
- Personalization: To customize your experience and provide tailored content. To provide the most accurate and relevant information in the area of reference ranges, we use your personal identifying information about year of birth and gender in order to show you the reference range relevant to you.
- Insights (optional): To create general wellness insight cards from your biomarker values (see Section 6). In the current version of the App, a new account has insights off until you turn them on, and you can turn them off again at any time under Settings → Insights. Accounts created before this choice was introduced, or with an earlier version of the App, have insights on until you turn them off there. Insight cards are not medical advice and are not used to make decisions about you.
- Communication: To send you updates (including in-app or push notifications about new features or health insights, with your consent) and to respond to inquiries.
- Compliance: To comply with legal obligations and protect our legal rights.
- Subscription Administration: To create and manage subscriptions, reconcile payment status, prevent duplicate subscriptions, provide billing support, prevent fraud, and maintain transaction records required by law.
- Advertising Measurement (iOS only): To measure whether our Apple Ads campaigns lead to installs and subscriptions, as described in Section 3.
- App Maintenance: To help us address any technical issues with the App and its operations, we process pseudonymized usage data.
- Website Management:
- To provide, operate, and maintain our website and services.
- To improve, personalize, and expand our website.
- To understand and analyze how you use our website.
Lawful Bases for Processing (GDPR / UK GDPR Art. 6 & 9):
- Consent: For health data and insights, given in the ways described in Section 5; for analytics, given when you turn it on.
- Contractual Necessity: To perform our services under the Terms and Conditions (e.g., login, data display).
- Legal Obligation: Where retention or disclosure is required by law (e.g., tax, record-keeping).
- Legitimate Interests: For security, fraud prevention, service improvement, and measuring our own advertising (with safeguards and right to object).
5. Consent Management
- Obtaining Consent: How you agree depends on how you add data:
- Lab report upload: before your first upload, the App shows a consent screen and continues only if you agree. If your account already holds results that you typed in or imported, the upload starts without this screen.
- Manual entry: you type the values yourself and decide what to enter.
- Apple Health (iOS): you agree in Apple Health’s own permission screens, where you choose which lab records to share with Health3. You can withdraw this in Apple Health at any time.
- Insights: in the current version of the App, you turn insights on yourself. In earlier versions, insights were part of the lab report consent screen.
- Analytics: off until you turn it on.
- Withdrawing Consent:
- For analytics: open the App, go to Settings → Analytics, and switch the toggle off. Capture stops immediately and the analytics SDK's local cache (pseudonymous identifier and queued events) is cleared. On the Website, open Cookie Settings and switch analytics off.
- For insights: in the current version of the App, go to Settings → Insights and switch the toggle off. From then on your values are no longer used for insights, no new cards appear and your existing cards are hidden. Existing cards are deleted when you delete your account. Earlier versions of the App have no such switch; update the App to use it.
- For Apple Health: stop sharing in Apple Health. Results already imported stay in Health3 until you delete them or your account.
- For all other processing: you may withdraw consent by deleting your account from within the App's profile screen, or by contacting us at privacy@health3.app.
6. Data Sharing and Disclosure
We may share your personal data with:
- Service Providers: Third-party companies that assist us in operating the App and providing services to you. These service providers act on our behalf under a Data Processing Agreement, are bound by confidentiality, and only use your data for the purposes we have described. The service providers we currently use for the App and the Website (processors, unless stated otherwise):
- Supabase (Supabase Inc.): primary database, authentication, file storage. Hosts: account data, biomarkers, lab values and reference ranges, journal entries, insight cards, profile fields and photos, consent records. Region: Switzerland (Zurich), for all accounts.
- Amazon Web Services (AWS): reading lab reports and creating insight cards, both with AI models that AWS runs in the EU. AWS does not use this data to train AI models. Region: EU, for all accounts.
- Reading lab reports: the uploaded file is converted to text in Frankfurt, Germany, and deleted after processing. An AI model in the EU picks out the biomarker rows from that text. The matching to the Health3 catalog that follows is described under Anthropic below. The result is kept at AWS with your account ID for 48 hours so that the App can fetch it; it then expires and AWS deletes it, usually within a few days. To find reference ranges printed on the report, a second step keeps a copy of the file until it has read it, normally for a few minutes; a storage rule deletes anything left after one day. The text recognised from a report can stay retrievable at AWS for up to 7 days. Technical logs of the reading (job and account IDs, counts, error codes and biomarker names our catalog did not recognise) are kept for 180 days.
- Insight cards (only if insights are on): receives biomarker names, values and units, the month of each test and how often each biomarker was measured, plus earlier cards with your ratings, your check-in answers and the theme and step of your insights journey. It receives no name, email or other identifier, so AWS cannot link them to you.
- Anthropic (Anthropic PBC): matching the biomarker names and units found on a lab report to the Health3 catalog. This is the only step that uses Anthropic’s own service. Receives: for each biomarker, its name, the label as printed, the value and the unit, in small batches together with our catalog. It receives no name, no account, job or document identifier and no file. Anthropic cannot link these entries to you. Region: United States.
- DeepL (DeepL SE): translation of insight cards into the language of your App, only if insights are on. Receives: only the text of the card, without your name or any identifier. DeepL states that texts sent through its paid service are not stored permanently and are not used to improve its services. Region: DeepL is based in Germany and states that content may be processed in different regions.
- RevenueCat (RevenueCat Inc.): subscription state management and, on iOS, Apple Ads attribution. Hosts: subscription tier, entitlement state, pseudonymized purchase events and, on iOS, the Apple Ads campaign, ad group and keyword through which the App was installed. Region: United States.
- PostHog (PostHog Inc.): consent-controlled pseudonymous product analytics for the App and Website. Hosts: the events described in Section 3 with the pseudonymous analytics identifier. No session recordings. Region: EU (Frankfurt).
- Google Analytics 4 (Google LLC): measurement of visits to health3.app, only if you accept analytics cookies. Hosts: pseudonymous visit statistics (pages viewed, feedback buttons used, device and browser category, approximate location, traffic source). Region: Google global infrastructure, which may include the United States.
- Firebase Cloud Messaging (Google LLC): push notifications. Hosts: device push token, notification payloads. Region: Google global infrastructure. Versions of the App for iPhone before 1.20.0 also contain Google’s Firebase Analytics component. Through it they send Google basic usage events (such as first open and sessions) with an app instance ID, app and device details and an approximate location. From version 1.20.0 the component is switched off. On 13 November 2026 we also deleted the App’s data streams in Google Analytics, so Google Analytics no longer processes what earlier versions still send. What was recorded before that is deleted as described in Section 8.
- Crisp Chat (Crisp IM SAS): in-App customer support chat and optional in-App feedback. Hosts: messages you send in the support chat and feedback you choose to send in the App (for example why you turned off renewal or why you are deleting your account), each with your account email and display name, or with your account ID if the account has no email. Region: EU (Netherlands and Germany, backups in Ireland).
- Resend (Plus Five Five, Inc.): sending account emails, such as one-time login codes and password resets. Receives: your email address and the content of these emails. Region: United States, where Resend stores this data; the emails themselves are sent from Ireland.
- Proton Mail (Proton AG): our company mailboxes, not part of the App. Hosts: emails you send to us and our replies. Region: Switzerland, Germany and Norway.
- Netlify (Netlify, Inc.): hosting of health3.app, including the how-to videos the App plays and a short technical page that the App loads when you start using it without an account, create an account, sign in or change your password. Receives: IP address and request details when you visit the Website, play a video or the App loads that page. Region: global network, which may include the United States.
- Apple App Store / Google Play Store: app distribution, in-app purchase processing, crash reporting and, if you choose it, sign-in with your Apple or Google account. Apple and Google act as independent controllers for app distribution and purchases under their own privacy policies. Hosts: crash logs, in-app purchase receipts. Region: Apple / Google global infrastructure.
- Legal Requirements: Government authorities or law enforcement if required by law.
The data is never sold to third-parties or shared for any commercial purpose. The data is not provided to third parties in any other fashion and for any other purpose than is detailed within the scope of this privacy policy.
The App shows no ads. Apart from the Apple Ads attribution described in Section 3, which only measures our own campaigns and is not used to target ads at you, we do not pass your data to advertising networks. We do not sell your personal or health data to anyone.
International Data Transfers:
- Your health data is stored in Switzerland (Zurich), whatever country your account is in. When you upload a lab report, the file is converted to text in Frankfurt, Germany, and deleted after processing; the AI model that reads the text runs in the EU. Switzerland and the EU recognize each other's level of data protection as adequate, so no further safeguard is needed for these transfers. If insights are on, insight cards are generated at AWS in the EU from biomarker values without any identifier. To match biomarker names and units to our catalog, we send only the name, printed label, value and unit of each biomarker to Anthropic in the United States, without your name, any account or document identifier, or the lab file. Anthropic cannot link these entries to you and does not use them to train its models. These entries do not identify you. Our agreement with Anthropic nevertheless includes Standard Contractual Clauses.
- Supplementary data is handled as follows:
- App and Website analytics (only if you opt in): processed by PostHog on EU infrastructure in Frankfurt. For EEA and Swiss accounts this means no extra-EU transfer occurs for product analytics. Website visit statistics on health3.app (only if you accept analytics cookies) are also processed by Google Analytics 4 (Google LLC), which may transfer them to the United States under the Data Privacy Framework or, where it does not apply, Standard Contractual Clauses.
- Cross-platform messaging (push notifications, crash reporting, in-app purchase receipts) is processed by Apple, Google, and Firebase on their respective global infrastructure under their own privacy commitments.
7. Data Security Measures
We implement the following security measures:
- Encryption: Data encryption in transit and at rest using industry-standard protocols.
- Access Controls: Restricted access to personal data to authorized personnel only.
8. Data Retention Policy
- Retention Period: We retain your personal data as long as your account is active or as needed to provide services. Specific retention windows:
- Account data and health content (biomarkers and reference ranges, journal entries, insight cards, ratings and check-in answers, profile fields and photos, consent records): for the lifetime of the account.
- Temporary onboarding accounts (before sign-up): deleted automatically after 30 days without use.
- Lab report reading at AWS: the uploaded file is deleted after processing. The result is kept for 48 hours and then expires. The text recognised from a report can stay retrievable at AWS for up to 7 days. Technical logs are kept for 180 days.
- App and Website analytics events (only created if you opt in): retained for the event-retention period included in our PostHog service plan and then removed. You can request earlier deletion at any time.
- Error reports (only created if you opt in to analytics): retained for the same period as analytics events. Crash reports that Apple and Google collect through their platforms are retained under their own policies.
- Website visit statistics in Google Analytics 4 (only if you accept analytics cookies), and the usage events that versions of the App for iPhone before 1.20.0 sent to Firebase Analytics: kept at user and event level for 2 months and then deleted in Google’s next monthly cleanup. Summary reports without identifiers may be kept longer.
- Apple Ads attribution data (iOS only): kept with your subscription records at RevenueCat for as long as we keep those records.
- Subscription records at RevenueCat: linked to your account ID, not to your name or email. They are not deleted automatically when you delete your account, because we keep them as transaction records. Ask us and we delete what the law does not require us to keep.
- In-App support chat history and feedback (Crisp): deleted in a yearly cleanup once the last message is more than 24 months old, or earlier if you ask us. Deleting your account does not delete them automatically; ask us and we delete them within 30 days.
- Deletion: Upon your request or account deletion, we delete or anonymize personal data within 30 days unless retention is required by law. Support chat history, feedback and subscription records are handled as described above. Copies in our database provider’s routine backups are removed when those backups expire. When you delete your account in the App, we also ask PostHog to delete the analytics profile and events linked to it. The App also resets the local analytics identity so future events cannot be linked to the deleted account.
9. User Rights
Under the GDPR, UK GDPR and FADP, you have the following rights:
- Right of Access: You may obtain confirmation of whether your data is being processed and obtain access to your personal data.
- Right to Rectification: You may request modification of any inaccurate or incomplete personal data.
- Right to Erasure (“Right to be Forgotten”): You may request deletion of your personal data. If you have created an account, you can delete it at any time using the App’s account settings. This will remove your personal data from our active systems (except for data we may need to retain to comply with legal obligations or for legitimate safety reasons). You may also request account deletion by contacting us at privacy@health3.app.
- Right to Restrict Processing: You may request limitation of the processing of your personal data.
- Right to Data Portability: You may ask to receive your personal data in a structured, commonly used format.
- Right to Object: You have the right to object to processing based on legitimate interests.
- Right Not to Be Subject to Automated Decision-Making: You have the right not to be subjected to decisions based solely on automated processing, including profiling, that produce legal effects concerning you or similarly significantly affect you.
- Right to complain to an authority: You have the right to complain to a data protection authority about our collection and use of your Personal Data. For more information, please contact your local data protection authority in the European Economic Area (EEA), United Kingdom, United States of America or in Switzerland (such an authority is, for example, the Information Commissioner’s Office in the UK).
- If you are located in the United States, please note there is no single privacy supervisory authority. You may consider reaching out to a relevant consumer protection agency, such as the Federal Trade Commission or your state’s Attorney General, for guidance or to lodge a complaint.
To exercise these rights, either use the functionalities offered through the App (e.g. account and data deletion), or contact us at privacy@health3.app.
10. Cookies and Similar Tracking Technologies
While our App does not use cookies in the traditional web browser sense, we employ similar technologies to collect information and improve your experience. These technologies support the App’s functionality and personalization and, only if you opt in, product analytics. On iOS, they also support the measurement of our own Apple Ads campaigns, as described below.
Types of Tracking Technologies Used:
- Local Storage: Data stored locally on your device to enhance App functionality, such as user preferences, settings, walkthrough completion state, and offline content. We do not use cookies inside the App.
- Pseudonymous identifier (only if you opt in to analytics): when you enable analytics in Settings → Analytics, we attach your Health3 user ID to analytics events so that your activity can be grouped across sessions and devices. The identifier is stored locally on your device and inside the analytics processor's data store. Disabling the analytics toggle clears the identifier locally and stops further capture. This identifier is not an advertising ID and is not used for cross-app or cross-website tracking.
- Apple Ads attribution token (iOS only): as described in Section 3, the App passes Apple’s attribution token to RevenueCat so that we can measure our own Apple Ads campaigns. The token is not an advertising identifier and is not used to track you across other companies’ apps or websites.
- Website: the Website uses browser storage and, only if you accept them, analytics cookies, as described in section 3.
Purpose of Using Tracking Technologies:
- App Functionality: To enable core features of the App, such as remembering your login status and preferences.
- Advertising Measurement (iOS only): To measure whether our Apple Ads campaigns lead to installs and subscriptions.
11. Children’s Privacy
- Age Limitation: The App is not intended for individuals under the age of 18.
- Data Deletion: If we become aware that we have collected personal data from a child under 18, we will take steps to delete that information.
12. Automated Decision-Making
- No Automated Decisions: We do not engage in automated decision-making that produces legal effects concerning you or similarly significantly affects you.
13. Third-Party Links
Our website may contain links to third-party websites that are not operated by us. We are not responsible for the privacy practices of these sites, and we encourage you to review their privacy policies.
14. Changes to the Privacy Policy
We may update this Privacy Policy periodically. We will tell you about changes by a notice within the App or by an email to the address associated with your account. The Effective Date at the top of this policy shows when the current version took effect.
15. Contact Information
For questions or concerns regarding this Privacy Policy, please contact us:
- Email: privacy@health3.app
- Address: Health3 AG, Wiesenstrasse 10A, 8952 Schlieren, Switzerland
16. Right to Lodge a Complaint
If you believe your data protection rights have been violated, you have the right to file a complaint with:
- In the EEA: Your local data protection supervisory authority.
- In Switzerland: The Federal Data Protection and Information Commissioner (FDPIC).
- In the United Kingdom: The Information Commissioner’s Office (ICO).
- In the United States of America: If you are located in the United States, please note there is no single privacy supervisory authority. You may consider reaching out to a relevant consumer protection agency, such as the Federal Trade Commission or your state’s Attorney General, for guidance or to lodge a complaint.
17. Additional Notices for U.S. Residents (State-Specific Privacy Rights)
Under CCPA/CPRA and laws in Colorado, Virginia, Connecticut, Utah, Washington, Nevada:
- We do not sell or share your personal or health data for advertising.
- You have rights to access, delete, correct, and port your data; to opt-out of any sale/sharing (none exist); and to non-discrimination.
- Section 17.1 lists the categories of personal information we collect. We do not sell or share your personal information, so there is nothing to opt out of.
- Washington’s My Health My Data Act & Nevada SB 370: express consent required for health data (see Section 5), plus notice and deletion rights.
17.1 CCPA Category Disclosure
Identifiers
- Examples: Email address, IP address, device identifiers, display name, pseudonymous Health3 user ID
- Source: Provided directly by you; from Apple or Google if you sign in with them; automatically collected via App & website
- Purpose of Collection: Account creation & login; security & fraud prevention; communication; pseudonymous product analytics (only if you opt in); measurement of our own Apple Ads campaigns (iOS)
- Disclosed for Business Purpose to: AWS and Supabase (hosting), RevenueCat (subscription state; Apple Ads attribution on iOS), Apple & Google (push notifications, crash reporting), Crisp (in-App support chat and feedback), PostHog (App and Website analytics, only if opted in), Google LLC (Google Analytics 4 on health3.app, only if you accept analytics cookies), Resend (account emails), Netlify (website and video hosting)
- Sold: No
- Shared: No
Personal Information (Customer Records)
- Examples: Name, profile photo and cover photo (if provided)
- Source: Provided directly by you (e.g., profile, email or support chat)
- Purpose of Collection: Customer support; communication
- Disclosed for Business Purpose to: Supabase (storage), Proton (our mailboxes), Resend (account emails), Crisp (in-App support chat and feedback)
- Sold: No
- Shared: No
Internet or Network Activity
- Examples: Screens or pages opened in the App or Website, buttons or product flows used, app or website version, platform, browser category, locale, coarse subscription state, approximate location derived from the request, technical error reports; on iOS, the Apple Ads campaign, ad group and keyword through which the App was installed
- Source: Generated by your interaction with the App or Website, only when you opt in to analytics; on iOS, the Apple Ads attribution is provided by Apple through RevenueCat, also if you have not opted in to analytics
- Purpose of Collection: Product analytics to understand which features are used and where the App can be improved, and measurement of visits to health3.app; measurement of our own Apple Ads campaigns (iOS)
- Disclosed for Business Purpose to: PostHog Inc. (EU); Google LLC (Google Analytics 4 on health3.app, only if you accept analytics cookies); RevenueCat Inc. (Apple Ads attribution on iOS)
- Sold: No
- Shared: No
Protected Classification Characteristics
- Examples: Year of birth (age), gender
- Source: Provided directly by you in profile
- Purpose of Collection: Personalization of reference ranges
- Disclosed for Business Purpose to: Supabase (storage)
- Sold: No
- Shared: No
Sensitive Personal Information
- Examples: Health biomarker data including reference ranges, hashed password
- Source: Provided directly by you (lab report upload, manual entry, import from Apple Health on iOS, account setup)
- Purpose of Collection: Core service delivery (health tracking & insights); authentication
- Disclosed for Business Purpose to: Supabase (secure storage), AWS (processing), Anthropic (biomarker name, printed label, value and unit only, without identity), DeepL (insight card text only)
- Sold: No
- Shared: No
18. Privacy-Minimized Biomarker Coverage Analytics
If you enable optional product analytics and the parser cannot match a biomarker or unit, Health3 may submit only the sanitized biomarker name and unit to a separate aggregate counter so we can add missing compatibility. This counter does not receive a laboratory value, reference range, test or report date, report identifier, provider, account identifier, device identifier, session identifier, advertising identifier, or PostHog identifier. Exact unsupported names and units are not sent to PostHog.
The authenticated request is used only to prevent unauthenticated abuse; the account identifier is not stored in or returned by the aggregate. Each installation locally avoids resubmitting the same name and unit, the database retains only the combined name-and-unit total and first/last calendar month, and combinations not seen for 24 months are removed the next time the counter receives an entry. Turning analytics off stops these submissions immediately.