Skip to content

MyHealth — US Consumer Health Data Privacy Policy (Washington, Nevada, Connecticut)

Required by the Washington My Health My Data Act (MHMDA), RCW chapter 19.373 (RCW 19.373.020 / .030 / .040); also the consumer health data notice for Nevada (SB 370, NRS 603A.400 et seq.) and the Connecticut Data Privacy Act (CTDPA, CGS §42-515 et seq.) — see Sections 9-A and 9-B.

Version (policy_version): 3.26 · Effective: November 14, 2026
This is a standalone Consumer Health Data Privacy Policy. Until version 3.15 it was titled "Washington Consumer Health Data Privacy Policy"; its address (https://www.bas-ai.com/myhealth/legal/us-washington-chd) is unchanged. It supplements, and is read together with, our general Privacy Policy and our Subprocessors page. Where this policy and the general Privacy Policy differ for consumer health data covered by the MHMDA, this policy controls for that data.

1. Who this policy is for

This policy applies to "consumer health data" as defined by the Washington My Health My Data Act when it relates to a "consumer" under that Act — that is, a natural person who is a Washington State resident, or a natural person whose consumer health data is collected in Washington — and who is acting in an individual or household capacity (not in an employment context).

It also applies, with the same content, to Nevada residents whose consumer health data we collect (Nevada SB 370, NRS 603A.400 et seq.) and to Connecticut residents whose "consumer health data" and other sensitive data we process (CTDPA, CGS §42-515 et seq.). Where this policy says "Washington consumer", read it as also covering Nevada and Connecticut consumers, with the state-specific additions in Sections 9-A and 9-B.

Under the MHMDA, consumer health data means personal information that is linked or reasonably linkable to a consumer and that identifies the consumer's past, present, or future physical or mental health status — including health conditions, diagnoses, treatments, medications, vaccinations, bodily functions, vital signs, symptoms, diagnostic testing, reproductive or sexual health information, and any data that identifies a consumer seeking health care services.

Important position. Because MyHealth is a health application, we treat the fact that a person has a MyHealth account — and the identifiers tied to it (name, email, and the account number we assign) — as consumer health data when that person is a Washington consumer. This affects how we handle deletion (see Section 8). Upon deletion we do not retain these identifiers in readable form: what survives is only an irreversible HMAC code (a one-way cryptographic transformation) of your search identifiers, kept in a minimal forensic security index held apart from any health record and containing no health data — and because it is not readable and is retained solely for security and fraud prevention, we do not treat it as the consumer health data subject to your deletion right (see Section 8).

This policy does not change rights you may have under our general Privacy Policy or under other laws.


2. Who we are

The entity responsible for the MyHealth app is:

BAS ARTIFICIAL INTELLIGENCE LTDA ("BAS AI", "MyHealth", "we", "us")
Tax ID (CNPJ): 64.106.409/0001-70
Address: Rua Gomes de Carvalho, 911, Vila Olímpia, São Paulo/SP, ZIP 04547-003, Brazil
Website: www.bas-ai.com

Data Protection Officer (Encarregado): Guilherme Bastian.

Privacy contact for consumer health data requests: dpo@bas-ai.com.


3. The categories of consumer health data we collect

We collect consumer health data only that you provide or authorize — there is no background or passive collection of health data. Depending on how you use MyHealth, the categories may include:

We do not collect your phone contacts, and we do not receive precise geolocation (the only feature that uses it is the optional "Time to leave" alert above, which sends it to Apple Maps, never to us) or microphone audio (dictation is transcribed on your device). We do not use third-party trackers or analytics SDKs.


4. How we collect consumer health data

We collect consumer health data only with your consent for a specified purpose, or as strictly necessary to provide the product or service you have requested (RCW 19.373.030).

Consent for the sensitive health journal — separate collection authorization. The daily alcohol/stress journal is consumer health data and is not necessary to provide the core product, so we obtain your separate, specific consent BEFORE collecting it (purpose daily_journal), presented separately from our Terms and from the general clinical consent, off by default, and revocable at any time. Our server refuses to write this data unless the consent is active. This section does not apply to minors' profiles, where the sensitive journal is unavailable.

These sensitive-journal entries (alcohol, stress/night context) are not shared with our AI provider. This differs from the non-sensitive daily contexts (coffee/caffeine, energy levels, hydration, workout perception, routine changes), which — under your active AI-processing and international-transfer consents — are shared with our AI provider only in weekly aggregated form (day counts and the routine-change category, never the individual daily entry, never free text). We do not sell consumer health data and do not seek a "valid authorization" to sell.

You may access/confirm, delete, and withdraw consent at any time (RCW 19.373.040). Withdrawing consent stops collection and deletes these entries.


5. Why we collect it (purposes) and how it is used

We use consumer health data to:

We do not use consumer health data for targeted advertising, and we do not use it to train AI models.


6. The categories of sources from which we collect consumer health data


7. Sharing: categories of consumer health data shared, and with whom

We do not sell consumer health data, and we do not seek any "valid authorization" to sell it (RCW 19.373.070 / .110). We do not share consumer health data for advertising, marketing, or behavioral targeting.

We share consumer health data only with a minimal set of processors ("vendors"), each under a binding data processing agreement that limits them to processing data on our documented instructions (RCW 19.373.060), and only as necessary to provide the service you requested or as you separately consent. We do not have corporate affiliates that receive your consumer health data.

Processor (third party)Role / purposeCategories of consumer health data sharedLocationKey safeguards
Supabase (Supabase Pte. Ltd)Database, authentication, document storage, and server functions that run the appPseudonymized clinical data, including the food diary; account identifiers (name, contact email, phone, national document) held encrypted in a separate vault; uploaded documents and the protected photos of saved meals; the daily copy of files; the text of your support messages; usage events; account metadataSão Paulo, Brazil (sa-east-1)DPA in effect (signed 2026-06-18, includes EU Standard Contractual Clauses and safeguards); encryption in transit and at rest; additional authenticated field-level encryption (AES-256 via pgsodium) of vaulted identifiers; row-level isolation; database point-in-time backups (about 7 days)
Anthropic, PBC (Claude API)AI analysis of your record, extraction of data from documents, the chat assistant, and — only with your consent — AI-assisted drafting/translation of support replies (see Section 5)Pseudonymized clinical content (values, dates, notes, lifestyle habits, cycle, wearable aggregates — for continuous glucose monitoring, only the daily aggregates, never raw readings —, the name and specialty (and, if provided, institution and reason) of your Care Team professionals — never their contact details or registration number —, and non-sensitive daily contexts in weekly aggregated form — day counts and routine-change categories, never the individual daily entry; the free text of your wearable annotations is discarded at import and never stored or shared, and only their standardized category code — never free text, aggregated by week — may be shared when you keep the sensitive Health Diary (daily_journal) on) plus your sex, age, country, and year of birth (without day/month) — no direct identifiers in the structured clinical content, and no emergency contacts (uploaded document copies are only best-effort redacted, so a direct identifier may remain — see "On redaction before AI processing" below). For document analysis, the redacted copy of the uploaded image/PDF, handled transiently. For AI-assisted support (Section 5), the content of the support thread as written (which may include health information you typed) — for logged-in users only under the dedicated support_ai_share consent plus your international-transfer consent and after best-effort identifier minimization; for people who email without an account only after they grant the two separate consents we request; never your clinical record; plus your self-reported pregnancy status (a trimester enum) — transient, shared only at the moment you run an analysis or send a chat message, only when your pregnancy-state-1.0 consent is active, and never stored by us (used solely to calibrate the reading of your labs for pregnancy/lactation ranges; automatic/proactive and large-record batch analyses never include it); your recent cycle entries in the chat only while cycle_ai_chat is on; weekly averages of the complete days of your food diary and, in your own chat only, the calorie goal you set, the weekly average time of the meals logged and the names of the foods that repeat the most (never a meal, a portion, or a photo); and, only while food_photo_ai is on, the protected copy of a meal photo or the meal description or correction you type or dictate, with the meal slot and language — never account identifiers or other record dataUnited States (international transfer under SCC)Commercial Terms + Standard Contractual Clauses in effect (2026-06-17) — a single agreement covering record analysis, extraction, chat, and AI-assisted support drafting/translation, which governs all data we submit to Anthropic's API and is not scoped by use case (no support-specific agreement is required); contractual non-training (your data is not used to train or improve models); limited retention we require by contract — Anthropic's contractual rule is deletion within about 30 days, except where retention is required by law or for abuse prevention (this is Anthropic's term, not a MyHealth-guaranteed deletion date, and is not zero-retention); TLS
ResendSending transactional emails (one-time access codes and account notices)No health content — only your email address and the email's textUS / globalDPA in effect (2026-06-17); EU-US Data Privacy Framework + SCC; TLS
Vercel (Vercel Inc.)Hosting the internal operations console, used only by authorized operators with MFATransiently: the email and display name looked up during support, account metadata, and the text of support messages (which may contain health information you typed); never the structured health recordProcessing in São Paulo, Brazil (gru1); US companyDPA and SCC being formalized (not yet signed); least-privilege database role; operator audit trail; TLS
Google (Google LLC — Google Workspace)Our support and DPO mailboxes (support@ / dpo@bas-ai.com); support emails received there are copied into our support system (Supabase) as ticketsThe sender and the content of the emails you send us, which may contain health information if you write itGoogle cloud (may involve the US)Google Workspace Data Processing Amendment and SCC being formalized (no acceptance recorded); TLS; mailbox access restricted to our team

On redaction before AI processing. Before clinical content is sent to Anthropic, we replace your direct identifiers with sex, age, country, and year of birth (without day/month), used only to regionalize educational guidance. For uploaded documents, the app attempts an on-device, best-effort redaction (covering) of four of your identifiers — name, national document (CPF), email, and phone — and the redacted copy is the one sent; the original file stays intact in your record. This redaction is best-effort and is not de-identification: it is directed only at your own four identifiers, and when the redaction process runs but finds nothing to cover (for example, because your identity vault is empty), the original may proceed to the AI. We do not represent that identifiers are guaranteed to be removed.

How support messages are handled (not a document-redaction path). The best-effort redaction described above applies to documents you upload. Support handling is different and is described in Section 5. AI-assisted drafting/translation of support replies is active, but only with consent and never using your clinical record. For logged-in users, it runs only under a new, dedicated, unbundled consent (support_ai_share) — separate from and independently refusable of the general AI-processing consent, off by default — together with your international-transfer consent; before the thread is sent, its text is minimized by best-effort identifier removal (not de-identification), so it may still include health information you chose to type. For people who email support without an account, nothing goes to the AI until they grant, in response to our request, two separate consents (to process the message and to transfer it to Anthropic in the United States); if they decline, a person replies with no AI. A human reviews every draft or translation before it is sent, your clinical record is never sent for this purpose, and no new processor is involved — the transfer is covered by the existing Anthropic DPA/SCC that governs all data we submit to Anthropic's API (see the Anthropic row above).

Apple processes your subscription and in-app purchases as merchant of record; no health content is in the payment flow. If you turn on the "Time to leave" alert, your iPhone sends Apple Maps your current location and the appointment address you typed, to estimate travel time; we do not receive them (Section 3). Cloudflare is not in our email path: our domain's mail goes to Google Workspace. Apple Health, Oura, and WHOOP are sources you connect, not recipients — they do not receive data from your health record.

Reproductive data — no sale, no share, no advertising. We never sell or share your reproductive or pregnancy data, and we do not seek any "valid authorization" to sell it (RCW 19.373.070 / .110). Your self-reported pregnancy status stays on your device (Section 3) and is transmitted to our AI provider only transiently, at the moment you run an analysis or send a chat message, solely to calibrate your lab reading — never for advertising, profiling, any secondary purpose, or a data broker, and never stored by us. It is available only on your own adult profile — not on minors' or managed profiles.

7.1 Sharing you direct between consumers: hereditary conditions with linked family members

MyHealth offers two consumer-directed sharing features, in which the recipient is a family member you choose (who must also be a user of the app) — not a vendor, affiliate, or advertiser:

For the hereditary-condition feature we obtain, before any sharing occurs, a valid authorization consistent with RCW 19.373.070: the authorization screen names the specific consumer health data shared (the named condition, year of onset, and status), the purpose (the recipient's family history), the recipient (your linked family members), and states that the authorization is revocable at any time, in one tap, free of charge and without justification — revocation immediately withdraws the offer from all linked family members. We keep a record of the authorization (who, when, and the version of the text displayed).

Permanence notice (shown at the moment you enable each item): an item a family member has already accepted becomes part of their family history, as their own record — deactivation does not delete it from their record; only they can remove it, and they may do so at any time. If you request deletion of your data or delete your account, we remove from the recipient's record every reference to your identity and account, keeping only the degree of kinship, condition, and period, which is consumer health data of the recipient themselves. Minors' profiles do not participate as a source by their own decision.

7.2 Data manager you authorize (consumer-directed delegation by an adult)

You may authorize another adult you choose (the "Manager" — who must also be a user of the app) to view your full health record and to register, edit, and upload documents on your behalf. This is consumer-directed sharing — the Manager is not a vendor, affiliate, or advertiser, and declares to act under your authorization, in your interest, in a personal, family, non-commercial context.

Before any access is granted we obtain the separate, distinct consent required by RCW 19.373.030(2), on your device, after reinforced identity confirmation: the consent screen names who the Manager is, the specific consumer health data covered (your full record), what the Manager can do (view; register, edit, and upload documents) and what the Manager can never do (change your consents, delete your account, manage sharing/links, change your credentials, make purchases, or bulk-export your record — the block on consents, account deletion, links, and credentials is enforced technically server-side; the block on purchases and bulk export is enforced technically in the app), and states that the authorization is revocable at any time, in one tap, free of charge and without justification, with immediate effect — revocation immediately ends the management powers; the read-only link remains until you also remove it (both options are shown side by side in the app). We keep a record of the consent (who, when, and the version of the text displayed), an immutable authorship trail of everything the Manager records (shown to you), and show you an in-app activity summary the Manager cannot turn off. What the Manager records is your consumer health data and remains in your record after revocation, under your rights (access, deletion, withdrawal of consent). Minors' profiles cannot appoint a Manager. The database also keeps two things outside a Manager's reach: your food diary (with its meal photos) and your conversations with the AI — a Manager neither sees them nor uses the chat on your profile.


8. Your rights as a Washington consumer (RCW 19.373.040)

If you are a Washington consumer, you have the right to:

No discrimination for exercising your rights (RCW 19.373.100). We will not discriminate against you for exercising any right under this policy — for example, by denying you goods or services, charging you a different price or rate, or providing a different level or quality of service — except to the limited extent that your consumer health data is strictly necessary to provide a product or service you have specifically requested and you have withdrawn or withheld consent for that data, in which case we may be unable to provide that specific feature.

How deletion works in MyHealth. You can delete your account directly in the app, in Profile › Privacy › Delete my account. On confirmation we permanently remove, in cascade, your encrypted identity vault and all clinical data (exams, conditions, medications, vaccines, documents, measurements, history, appointments, AI conversations, sleep, wearable scores, device events, lifestyle habits, medication-intake and check-in logs, the food diary and goal), your uploaded files and meal photos, your support tickets, your wearable connection data, and your AI usage/quota metadata — including the data of any dependents you manage — and we close your account. Where you manage a minor, deletion offers you the option to transfer guardianship of that minor to an existing co-guardian (so the minor's record survives with them) instead of deleting it.

For Washington consumers, we treat the identifiers tied to your health account (name, email, and the account number we assign) as consumer health data and delete them, in readable form, on your request — we do not keep them as text. Two categories of minimal, dissociated data may survive, neither treated as your consumer health data: (1) a minimal tax/accounting record for a consumer who actually completed a purchase, kept encrypted and dissociated from the health-account context and held solely to meet a legal accounting obligation; and (2) a minimal, pseudonymized forensic security index — described below — retained for every deleted account (including minors) solely for security and fraud prevention. Neither is used to infer your health status.

What remains after deletion is at most: (a) a de-linked, pseudonymized record of consent events (cryptographically dissociated from your identity), kept only to evidence that consent was given and withdrawn; (b) security/access logs kept for a short period (up to six months) that record metadata of access (time, action, source IP, and device user-agent) and never the clinical content — used only for security and fraud detection, never to infer your health status; and (c) a minimal, pseudonymized forensic security index that survives for every deleted account, containing at most (i) irreversible HMAC-SHA256 codes of your search identifiers (email, Apple ID, and, where collected, phone and national ID), computed with a dedicated secret ("pepper") guarded in a vault (Vault), encrypted by a root key managed outside the database and never exposed, so the code cannot be reversed to the original value; (ii) the recent IP addresses from your access log, in text; and (iii) your pseudonymous account number (account_ref) and minimal custody metadata (account creation/deletion dates, jurisdiction, retention term) — with no health data, no name, and no email in readable form. Because this index is not readable and is held apart from any health record solely to answer a lawful request from an authority and to establish, exercise, or defend legal claims and prevent fraud, we do not treat it as the consumer health data subject to your deletion right. It is retained for the prescriptive period applicable to the exercise or defense of legal claims and response to authorities — set by default to the same duration as the applicable tax-record term (about 5 years in Brazil, the United States, and most jurisdictions; 6 years in the UK and Canada; 10 years in the EU), a period we consider proportionate to that purpose, after which it is purged. Minors are included, but on a reduced term proportionate to the fraud-prevention purpose (never the tax term, which does not apply to a minor who does not transact), subject to a best-interest-of-the-child proportionality assessment and approval by our Data Protection Officer.


9. How to exercise your rights, and how to appeal

To make a request (confirm/access, delete, or withdraw consent), use either:

We take prompt steps to authenticate your request (to protect your data we may ask you to verify your identity or your control of the account). We respond within 45 days of receiving the request; if reasonably necessary, we may extend once by an additional 45 days and will tell you why within the first 45 days.

Authorized agents. You may use an authorized agent to make a request on your behalf; we may require proof of the agent's authority and verification of your identity.

Appeals. If we decline to act on your request, we will tell you why. You may appeal by replying to our decision or writing to dpo@bas-ai.com with the subject "Consumer health data appeal." We will respond to the appeal within a reasonable time — within 60 days for Connecticut consumers — and explain our decision. If your appeal is denied, you may contact the Washington State Office of the Attorney General (https://www.atg.wa.gov/file-complaint), or the Attorney General of your state (Sections 9-A and 9-B).


9-A. Nevada consumers (SB 370, NRS 603A.400 et seq.)

If you are a Nevada consumer, this policy is our consumer health data privacy policy for Nevada. In particular:

9-B. Connecticut consumers (CTDPA, CGS §42-515 et seq.)

If you are a Connecticut consumer, consumer health data and other sensitive data (such as data revealing a mental or physical health condition or diagnosis) are processed only with your consent — and, as the CTDPA requires, that consent is not the acceptance of our Terms: clinical processing and each optional purpose are asked separately (Section 4).


10. No sale; no targeted advertising

We do not sell consumer health data and do not seek valid authorization to sell it. We do not use consumer health data for targeted advertising, profiling for advertising, or sharing with data brokers. Sharing with the processors listed in Section 7, under contracts that limit them to our documented instructions, is processing — not a sale under the MHMDA. If this ever changes, we will update this policy and obtain any consent or authorization the law requires before doing so.


11. Geofencing

We do not use geofences around health care facilities, and we do not use precise location to identify or track consumers seeking health services (RCW 19.373.090). The only feature that uses your precise location is the optional "Time to leave" alert, in which your iPhone sends your current location and the appointment address to Apple Maps to estimate travel time; we never receive or store it (Section 3).


12. Security

We protect consumer health data with encryption in transit and at rest, authenticated field-level encryption (AES-256 via pgsodium) of the identifiers held in a separate vault, strict row-level isolation between accounts, server-side enforcement of consent on every operation, access controls with security/access logging, and restriction of access to only the personnel and processors for whom it is necessary (RCW 19.373.050). No method of transmission or storage is perfectly secure, but we maintain technical and organizational measures appropriate to the sensitivity of health data.


13. Changes to this policy

We will not collect, use, or share categories of consumer health data, or use it for purposes, not described here without first updating this policy and, where required, obtaining your affirmative consent. Material changes will be posted here with a new version and effective date. A prominent link to this standalone Consumer Health Data Privacy Policy is published in the footer of our MyHealth homepage (www.bas-ai.com/myhealth), distinct from the general Privacy Policy link, as required by RCW 19.373.020(1)(b).

Changelog:


14. Contact