Privacy Policy — MyHealth
Version (policy_version): 3.30 Last updated: November 16, 2026 Effective: November 16, 2026. Changes (3.30, 2026-11-16): This update triggers re-acceptance (the acceptance screen reappears); the authorizations you already gave still stand. (1) The age-based screening reminders no longer exist; in their place there is a reference page, the same for everyone, with the official source of each item, and the AI reading does not mention screening tests absent from your record (Section 4). (2) The emergency card may list medications you choose (Section 3.2). (3) Items you type by hand also have their substance identified by the AI (the item's name and dose), and the item's page shows the lab results in your record linked to it, with no assessment (Section 6.5). (4) The AI analysis starts to receive four computed associations between readings from your device — two means, the number of days and the period, nothing stored (Section 6.1). No new category of data is collected and there is no new recipient. Changes (3.29, 2026-11-16): New notices, all described in Section 12-A — no new health data is collected, there is no new recipient and the legal basis does not change. This update triggers re-consent (the acceptance screen reappears). (1) "Any new test?" — whoever has already sent tests may receive, some months after the last upload, the question whether there is a new one. (2) The food diary now has two notices, and the sentence "the food diary does not generate notifications" no longer holds: an invitation to choose the goal (at most two, for whoever opened Nutrition without choosing one) and a meal reminder that comes off and exists only if you turn it on. (3) The come-back invitation gains a fourth wording, used only when it is true: "There is something new since your last visit — your portrait has been updated." All have fixed text, with no health data in the body. The Terms of Use describe, in this same version, the subscription's free trial period (Terms, Section 12.11). Changes (3.28, 2026-11-16): No change to this Policy — it moves up a number together with the Terms of Use, because the accepted version is a single one for both documents. This version's change is in the Terms (the welcome courtesy goes from about 10 to about 40 pages, Sections 12.1 and 12.10). If you have not yet accepted version 3.27, its changes, described right below, also apply. Changes (3.27, 2026-11-15): Notifications — fewer notices per day and new notices, all described in Section 12-A. No new health data is collected, there is no new recipient, and the legal basis does not change. (1) One minor notice per day: the summaries of sleep, glucose, activity, symptoms, a lab marker's evolution and the weekly crossover, and the "Daily headline", now go out at most once a day; when two or more were due on the same day, they arrive gathered into one, "Your summary for today". For 48 hours after an exam enters your record, the minor notices about exams stay silent. (2) Appointments: the eve reminder now says, in the same notification, that the material to take along is ready (with the counts only if you turned on the numbers in alerts), and the separate notice at 6 PM on the eve no longer exists; the day after an appointment of yours, the app may ask "How was your visit?", with a fixed, neutral text. (3) "Time to leave" rings at the time computed for leaving, even inside the quiet-hours window, like the dose reminders. (4) Glucose: with the numbers turned on, they enter the day's summary only when read from 6 PM on. (5) Three new notices inside the "Daily headline" (same switch): "Your notifications" (a reminder that some notice types come turned off, without saying which), "Your month" (the month's portrait is ready, on days 1 to 7) and "Vaccination calendar" (it points to a general reminder the app already shows — never a booster recommendation, an individual deadline, a vaccine name or a date; at most once every 90 days). (6) Last day of a treatment with an end date: on the day an item of your routine with an end date you entered comes to its end, a neutral notice — never the item's name or the dose, and with no advice at all. (7) Three new server notices, with fixed text and no health data: an upload waiting for pages; a subscription that was not renewed or that ended; and a family sharing that started (invitation accepted) or ended. The closed list of remote notices goes from eleven to fourteen cases. All of them are turned off in Profile › Notifications, except the account notices with no separate switch, which Section 12-A names; notices about minor and managed profiles stay generic. (8) Meal reading by the AI (Section 6.13): a reading may gather up to four photos and a short note of yours; only the main photo is kept with the meal; and the AI may ask one question when it cannot see what changes the estimate.
Changes (3.26, 2026-11-14): MyHealth now works only with the analysis by artificial intelligence. The service we offer is the reading and organizing of your health record by AI; using the app without AI has been discontinued. This update triggers re-acceptance (the acceptance screen appears again). (1) Two acceptances of their own (§4, §5, §6.1 and §9.1; Terms §1.2, §2.1, §8.1 and §8.4): the AI analysis and the international transfer to the United States are now requested as two separate acceptances, never pre-ticked, and are a condition for using the app. You are not required to agree; without agreeing, the app does not work. (2) Accounts that already existed with the AI off (new §5.1; Terms §17): until January 13, 2027 nothing changes; after that, the account stays in read mode, where you view and export everything, until you agree. No account is deleted because of this change. (3) Turning the AI off (§5; Terms §16.1) leads to that same read mode, with export and deletion always available. (4) Wording precision (§4, §6.1 and §9.1): in the documents you upload, covering your name, tax ID, email and phone before they go to the AI is done on your device and may not reach all of them; the United States has no adequacy decision from the Brazilian authority. (5) Where the app is offered (§2): the list of countries was narrowed. (6) Apple Health clinical records (§3.2): the import, which is optional and only takes place with your authorization on Apple Health's sheet, applies to accounts in the United States and now also to accounts in Canada; the text no longer describes it as a feature that is still inactive.
Changes (3.25, 2026-11-05): This version brings a new feature — the Nutrition tab — and describes it in full, and it corrects, in your favor, several points of the previous text. This update triggers re-acceptance (the acceptance screen reappears). (1) Food diary (§3.2): you can log your meals (time, meal of the day, how it was logged), the items with their portion and estimated calories and nutrients, mark a day as complete, set — only you — a personal calorie goal, and choose the "no numbers" mode. It is health data, stored in Brazil, visible only to you: it is not part of family sharing, it cannot be accessed by a Manager or by someone with read-only access, and it does not exist on dependent profiles. It is included in your export and deleted with your account. To log without a photo, you can search for the food in tables that come inside the app (TACO, the USDA's FoodData Central and the Canadian Nutrient File), and the search happens on your device. (2) AI meal reading, by photo or by text description — optional, with its own consent ("Read meals with AI (photo or description)", food_photo_ai, off by default and outside "Accept and continue"; §6.13): if you turn it on, the photo you take or choose is reduced, has its location removed, faces blurred, and your own name, ID, email and phone covered when the device recognizes them (other text, including other people's data, is not covered) on your device, and only then does it — or the description you type or dictate — go to our AI provider (Anthropic, USA — the same one as always), only to estimate foods and portions. The protected copy of the photo is kept with the meal you save, visible only to you; the text is not kept. Anthropic generally retains them for about 30 days, unless retention is required by law or for abuse prevention. (3) Energy expenditure (§3.2 and Section 8): we now name the active and resting energy the app already reads from Apple Health; without them, we show an estimated expenditure based on your weight, height, age and sex, always labeled as estimated. (4) AI (§6.1 and §6.13): weekly averages of the complete days of your diary go into the health-record analysis and the chat — never a meal, the name of a food, the photo or your goal, and only for people who have accepted this version. Logging a meal does not trigger a new analysis. If you share your health record, whoever has access does not see the diary, but can read the analysis, which may cite those averages. (5) Usage events (§3.5): we record that you logged a meal, marked a day as complete or saved a goal — never the food, the amount or the value. (6) Microphone (§3.6): to dictate a meal description, the app uses the microphone only when you tap "Speak", and the transcription happens on your device — the audio is neither kept nor sent. (7) The lock screen and numbers in notifications depend on you again (Sections 4 and 12-A): the four lock-screen details (medication name and dose, vaccine detail, appointment detail and "time to leave") and the numbers from your data in summaries (sleep, glucose and time in range, activity, weekly and monthly summaries) are off by default; each one appears only when you turn it on, and that choice is recorded as its own consent (LGPD Art. 11, I), which you can turn off at any time, with immediate effect. We also correct what we said about "time to leave": to calculate the route, your current location and the appointment address go to Apple Maps (an Apple service), never to us. (8) Clinical processing with its own request (Section 5): the consent for us to organize your health record is now requested prominently, separate from accepting the Terms, not pre-ticked, and it can be revoked in Profile › Privacy — revoking it deletes the account right away, after the warnings and the offer to export, and only the data the law requires us to keep remains (Section 5). (9) An invitation to move (Section 12-A): after a few days with far fewer steps than your usual, the app may invite you for a walk — a notice with none of your numbers, which you can turn off in Profile › Notifications. (10) Where MyHealth is not offered (Section 2): Russia, Belarus, Yemen, Kosovo, Afghanistan, Hong Kong, Macao, Myanmar and Venezuela, because our AI provider does not serve those places; and using MyHealth in Crimea, Donetsk, Kherson, Luhansk and Zaporizhzhia is not permitted. (11) Daily copy of your files (Section 12): we declare the daily backup copy of your files and what happens to it when you delete a file or your account. (12) Providers (Section 9): the list now includes Vercel (internal operations console) and Google Workspace (support and DPO mailboxes), with the contract status of each. (13) Wording corrections: the consent legal bases now cite the right article (LGPD Art. 7, I and Art. 11, I); the incident clause now states the deadlines (in Brazil, 3 business days); Section 15 gains the rights to anonymization/blocking and to information about not consenting, the list of other countries' authorities, the exact description of what the export contains and of the automated decisions; the new Section 15-B gathers what applies in Canada; the forensic index keeps IP addresses for 6 months; and an own account requires 18 years or the age of majority of the country you enter, if higher. The Terms also change (the "AI readings" join the plan with a stated limit).
Changes (3.24, 2026-10-18): Wording precision — the Policy now quotes, word for word, the "Your analysis was updated" notice (Section 12-A, case (a)), which our server sends when a new analysis can be compared with the previous one. The body says only how many changes there were ("1 change since the last one — tap to see what changed.", "N changes since the last one — tap to see what changed." or "Nothing new since the last one — tap to check.") — never the name of a test, a marker or an analysis item —, and the notice about a profile under your care stays generic. It is the same analysis-ready notice, turned off in the same place, in Profile › Notifications — with no new purpose and no change of legal basis. No new health data and no new recipient.
Changes (3.23, 2026-10-01): Wording precision — the Policy describes in more detail what the app already does, with no new purpose and no change of legal basis. (1) In the invitation to come back (Section 12-A), the timing examples now include around two days for those who have not sent anything yet — the same neutral invitation, turned off in the same place, in Profile › Notifications. (2) In usage events (Section 3.5), we make explicit that the screens recorded include the pages of the upload tutorial and whether you skipped or finished it — screen names only, never health content. No new health data and no new recipient.
Changes (3.22, 2026-10-01): Adjustments to notifications, all toward more control and more protection. (1) The test name no longer appears in evolution summaries by default: the notice says "one of your tests", and the name only appears if you turn on "Show the test name in the notice" in Profile › Notifications (Section 12-A). (2) When you sign out, this device's notification token is unlinked right away — the device stops receiving your account's notices —, and a token not renewed for 180 days is deleted (Sections 3.4 and 12.1). (3) Section 12-A now lists every notice our server sends: besides the seven already described, the watch or ring connection interrupted notice, the document that could not be read notice, the account notices about the guardianship of a minor and, under the existing "Something new in your data" option (off by default), the association observed over time between a marker and one of your medications — all with no health data in the text. (4) Dose reminders ring at the time you chose, even inside the quiet-hours window. (5) Usage events now also record which type of notice you tapped to open the app (only the category). No new health data and no new recipient.
Changes (3.21, 2026-09-30): The four lock-screen detail exceptions now come ON by default (Section 12-A), by founder directive (sole Controller/DPO): "by default, all notifications come enabled; it is up to you to turn off what you don't want." They are: medication name and dose, vaccine name and dose, appointment detail (professional, time, and the short address you entered), and the "time to leave" alert. Until now each required you to turn it on; now each comes on and can be turned off individually, at any time and with immediate effect, in Profile › Notifications — when you turn one off, already-scheduled reminders return to neutral right away. What does NOT change: the content limits stay exactly the same — never the purpose, the drug class, the condition treated, the specialty, the reason for the visit, a diagnosis, or any clinical or urgency judgment; minor and managed profiles remain entirely excluded; everything stays 100% on your device, set per device, and never travels over remote push. "Time to leave" additionally still requires the iOS location permission — coming on only means the alert is armed: without the permission, which your iPhone asks for the first time, no travel is computed. Change of legal basis: since there is no longer an act of activation to record, these four exceptions stop running under their own separate, highlighted consent and move to the performance of the service you configured, with easy, granular opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)) — the underlying health data (your medications, your vaccines, your schedule) remains processed under the clinical consent you already gave (LGPD Art. 11, I; GDPR Art. 9(2)(a)), exactly as has been the case since version 3.12 for the personalized summaries that show your own numbers in the notice body. You can turn all four off in under a minute, and we recommend reviewing them if your iPhone is often visible to other people: the lock screen can be seen by anyone nearby and read aloud by Siri. iOS also lets you hide previews in Settings › Notifications › Show Previews. In this same version, the live "today's doses" card (Live Activity/Dynamic Island) no longer exists — a notification that stays permanently on screen has become an exception, reserved for the day of the appointment, in the last hour before it. Transparency about the gap: app version 1.0.7, released on 2026-09-29, already shipped these four options on before this text was published — this version of the Policy closes that gap and describes what the app does. This version also adds a seventh case of remote push (Section 12-A, item g): when we release a new version of the app, we may send one service notice, with fixed text, no health data and no promotion, at most once per version. The delivery token, the limits (one interruptive notice per day, quiet hours) and the legal basis (legitimate interest) are the same as for the other notices. Finally, Section 12.3 now describes what we keep when you delete a workout imported from a device: only the identifier the source uses, so it does not come back on the next sync — nothing of the workout's content. Changes (3.20, 2026-09-03): This version describes a measurement the app already offered on screen and that the Policy did not describe. To find out where the app stalls or confuses people, we record which screens you open and at which step an upload stopped — never health content. These events are linked to your account (which is why they are declared separately from de-identified telemetry), in internal processing, with no analytics SDK, no third-party tracker and no advertising, for up to 12 months. Basis: legitimate interest (LGPD Art. 7, IX; GDPR Art. 6(1)(f)), with objection in one tap at Profile › Privacy & consents › "Help improve the app". No new health data, no new recipient, no new subprocessor. This update triggers re-acceptance (the acceptance screen reappears). Changes (3.19, 2026-08-10): This version discloses an external lookup that already existed and was not described. When you add a healthcare professional with your device in the United States region, the app offers a lookup in NPPES — the public provider registry maintained by the US government (CMS). That lookup sends CMS only the name you typed: none of your data, no health data, no identifier — and it happens only when you trigger it. This is an information fix, not a processing change: nothing started leaving your device because of this version. No new data is collected, no new purpose, no new subprocessor (CMS does not process our data — it receives a search term). This update triggers re-acceptance (the acceptance screen reappears). Changes (3.18, 2026-08-08): This version brings one optional addition that expands what you can do, and no other change. Until now, your menstrual cycle was part of the record analysis, but the chat did not receive it — so questions like "does my sleep change around my period?" went unanswered. There is now a "Talk about my cycle in the chat" option (Profile › Privacy), under its own separate consent (cycle_ai_chat), off by default and outside "Accept and continue": until you turn it on, nothing changes. If you turn it on, the assistant can see your most recent cycle entries when answering (a smaller window than the one used for analysis, by data minimization); when you turn it off, sending stops on the next turn — and nothing needs to be deleted, because no new data was stored because of this option. This supersedes what the version 3.10 note said about the chat not receiving cycle data. Not available to minors or managed profiles. The app still does not predict fertility or ovulation and does not diagnose. No new data is collected (it is the same cycle you already log), no new subprocessor, no new international transfer. Basis: LGPD Art. 7, I + Art. 11, I; GDPR Art. 6(1)(a) + 9(2)(a); Washington MHMDA (per-category consent). This update triggers re-acceptance (the acceptance screen reappears). Changes (3.17, 2026-08-08): This version brings one optional addition and no other change to how we handle your data. Up to 3.16 we did not store the trace (waveform) of your watch's electrocardiogram — only the classification and metadata. A new option appears, "Store my ECG trace" (Profile › Privacy), which starts off: while it is off, nothing changes. If you turn it on, we import and store the trace so you can take it to your doctor — and, even when on, the trace is never interpreted by us, never sent to the artificial intelligence, never altered, does not enter family sharing or notifications, and turning it off deletes the traces already imported. We ask for a separate authorisation because the Apple Health permission does not distinguish "see the classification" from "store the trace". No new subprocessor, no new international transfer. The Terms also changed in this version (liability cap, §14.3).
Changes (3.16, 2026-08-01): This version describes what already happened and changes nothing about how we handle your data: no new data, no new purpose, no new subprocessor, no change of legal basis. The Policy gains §12.3, on deleting a specific exam from your health record — the two options the app offers and the difference between them, what goes immediately, what remains on purpose (the appointment you have already attended and the symptom you have already confirmed), how the AI analysis stops resting on the removed exam, and what we keep of the act: a receipt with counts only, never the title or the content. The former §12.3 and following were renumbered.
Changes (3.15, 2026-07-25): This version amends the Terms of Use (§12.1) and changes nothing about how we handle your data. We removed from the contract the monetary amounts quoted "for reference" for the subscription and the add-on packs. Why: MyHealth's price varies by country — the App Store sets its own amount for each market where the app is sold — so a contract quoting a fixed amount, even as a reference, is wrong for most readers and goes stale when the price changes; one of the quoted amounts was in fact below what the App Store charged. The Terms now state what has always applied in practice and still applies: the prices and quotas in force are always those displayed at the time of purchase. The quotas are unchanged (40 pages and 12 interactions per month; 480 and 144 per year; packs of 50/150 pages and 20/50 interactions) — what you are entitled to use is exactly the same. No new data, no new subprocessor, no new transfer. Changes (3.14, 2026-07-25): A stress transparency round — three points: one new, one in your favor, and one honest correction of our earlier text. (A) Your ring's stress index is now shown TO YOU (§3.2 and Sections 4, 6.8 and 8): in the "Today's readiness" card, on the Routine tab, next to your readiness, we show the label Oura itself publishes for the day (restful / normal / stressful), exactly as the brand publishes it and always with the date it refers to — no translation into a scale of ours, no severity color, no severity ordering of ours, and no calculation of ours: MyHealth never computes a "stress index" from your signals. This is not new data: collection already happens under the consent you granted when you connected Oura (revocable), and "stress" has been listed among the daily scores we declare we collect since version 3.9 — what was missing was declaring that we give that data back to you, on screen. Everything that already applied still applies: this index is NEVER sent to the AI (the exclusion is applied in the database query itself, in both the analysis and the chat, and reaches the stress sub-score embedded in Oura's resilience "contributors" — it is not merely an instruction to the model), never enters the PDF Health Report, never becomes a notification and never appears on a dependent's or a minor's profile. Legal basis unchanged, no new purpose: performing the service you signed up for (seeing your own organized data) over sensitive data already consented to (LGPD Art. 7, V and Art. 11, II, "a"; GDPR Art. 6(1)(b) and Art. 9(2)(a)); the change is one of transparency (LGPD Art. 6, VI and Art. 9; GDPR Art. 5(1)(a) and Art. 12–13). No new data, no new subprocessor, no new international transfer. (B) A new control: "What appears in the app" (§3.2 and Sections 4 and 5): in Profile › Privacy & consents you can now turn off the display of sensitive categories, one by one — Ring stress, Menstrual cycle and Mental health — effective on tap and across all your devices. Read carefully what this switch does and what it does NOT do: it hides that content from the app's screens, for you — and that is all. It does not disconnect your ring or Apple Health, does not withdraw consent, does not delete data, does not stop collection and does not change what the AI receives; collection and use are still governed by your consent. We only offer the switch for a category you actually have on that profile; it does not exist on a dependent's profile or in read-only access; and when you hide Menstrual cycle, it also stops being offered in the PDF Report (the PDF goes to third parties — offering to send data you chose not to see would be the opposite of what you asked for). It is extra control for you, with no new legal basis: minimization and privacy by default (LGPD Art. 6, III; GDPR Art. 5(1)(c) and Art. 25(2)). (C) Correction: the daily check-in's "Stress" axis IS sent to the AI analysis — and our text said it was not (§3.2 and Sections 6.1, 6.8 and 9). The "How are you today?" check-in has evolved: where there used to be a single mood answer, there are now four axes that you yourself answer on three levels — energy, mood, stress and (only when the app does not receive sleep from your wearable) sleep. The stress axis is your own self-report and is part of the context sent to the AI, only as a weekly average, under the Clinical processing, AI processing and International transfer consents you already granted, with a hard instruction to the model: a descriptive reading of what you reported, never a diagnosis of anxiety, depression or a "stress disorder", never treated as a clinical instrument, never treatment advice. Our earlier text, written before the check-in gained axes, said that "point-in-time stress… stays out of the AI" and described the check-in as being mood only — a reasonable reader would conclude that no self-reported stress reaches the AI, and one does. We corrected the affected paragraphs to say plainly what goes and what does not: the check-in axis goes (weekly average, three levels); the sensitive Health Diary entries (alcohol and stress/evening context, under their own consent) do not, the ring's stress index does not, and the GAD-7/PHQ-9 questionnaires do not. Legal basis — the same one already operating, now described correctly: specific and prominent consent for sensitive data (LGPD Art. 7, I and Art. 11, I; GDPR Art. 6(1)(a) and Art. 9(2)(a)) + international transfer (LGPD Art. 33; GDPR Art. 44–49); for Washington (USA) residents, the per-purpose consent under MHMDA, reaffirmed over the corrected text. That is why this version asks you to accept again: because the earlier description was incomplete on a special-category point, we ask you to confirm you have read the corrected Policy, so that your consent record points to the right text. This update triggers re-consent (the acceptance screen reappears). Also in this version (Section 13): we now record the install source when you download the app after seeing one of our App Store ads (Apple Search Ads / AdServices) — campaign data, no IDFA, no iOS tracking permission (ATT) and no third party: it is Apple reporting on our own campaign to our own server. It exists so we can tell which ads bring people who actually use the app. Legal basis: legitimate interest (LGPD Art. 7, IX; GDPR Art. 6(1)(f)).
Changes (3.13, 2026-07-25): The come-back invitation may now also be delivered by remote push (Section 12-A). The neutral invitation to return to the app after a stretch without use already existed and keeps the same purpose, the same trigger and the same legal basis: what triggers it is still only the time since you last opened the app — an app-usage signal, never a reading or inference about your health. What changes is only the delivery method: it used to be assembled exclusively on your device (a local notification); now it may also be sent from our server (remote push, APNs). Why: a local notification is only scheduled when the app is opened — so someone who went a long time without opening it, or switched devices, simply never received the invitation. The body stays identical and neutral: no health data, no number, no comparison, no judgment, no urgency and no blame (e.g., "Your data misses you — the portrait is still here, just as you left it."). The cap of one interruptive notice per day, your quiet-hours window, the cancellation as soon as you open the app, and the individual toggle in Profile › Notifications all still apply. Dependent and managed profiles remain excluded. Remote delivery uses the same technical delivery token already described in Section 3.4 — no new data is collected and no new subprocessor is involved. Legal basis unchanged: performing the service/legitimate interest, with easy opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)). This update triggers re-consent (the acceptance screen reappears).
Changes (3.12, 2026-07-19): Personalized notifications with your own data (Section 12-A). By founder directive (sole Controller/DPO, 2026-07-19), MyHealth notifications may now include, in the body, a summary of your own health data — for example, the duration and efficiency of last night's sleep (and deep sleep) and how it compares to your own average; your daily glucose average and time in range (descriptive, never an alarm or clinical threshold); your activity versus your average and milestones reached; how one of your lab markers changed over time — the marker name only appears if you turn on "Show the test name in the notice" in Profile › Notifications (off by default since version 3.22, and only for the device where you turned it on); without it, the notice just says "one of your tests"; a weekly or monthly summary with real numbers; and the analysis-ready notice (a push about your own record) may name the analysis theme/panel, in your language. Previously the body was kept generic (no health values). This is a change in how data you already share is DISPLAYED to you, on your own device — not a new data category collected, and not new sharing with third parties. Four controls: (a) iOS hides previews on the lock screen until you unlock the device (default "Show Previews: When Unlocked"; you can also choose "Never"), so a glance at a locked phone does not reveal the content; (b) each category has its own toggle in Profile › Notifications — the non-sensitive personalized summaries are on by default and each can be turned off (granular opt-out); (c) they are for you, the adult account holder, on your device only — minor and managed profiles never carry health data in the notice body; (d) the notices stay descriptive and factual — never a diagnosis, a medical judgment or opinion, a cause, an efficacy claim, or urgency. Sensitive domains (mental health, cycle/reproductive, substance, medication adherence) stay off by default and would only ever appear in a notification if you had both opted into that data category (the dedicated consent that enables it — e.g., the Health Diary, Mental health, cycle) and turned on that category's notification toggle; today, mental-health and cycle/reproductive content remain entirely out of any notification, and medication notices never frame a missed or late dose (adherence memory, never surveillance). Legal basis: for the personalized service notices derived from your own data and delivered to your own device, performance of the service you configured, with granular opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)); for the sensitive (special-category) ones, explicit consent (LGPD Art. 11, I; GDPR Art. 9(2)(a); Washington MHMDA). This update triggers re-acceptance (the acceptance screen reappears). Changes (3.11, 2026-07-19): Two Apple Health-related additions, published together — a minor bump, with re-acceptance. (A) Observed medication adherence (§3.2, Sections 4, 6, and 9; requires iOS 26 or later): if you log that you took a medication dose in Apple Health, MyHealth can import only the doses marked as taken into your record, matched to a medication you have already registered in the app (we never create a new medication from Apple Health). Only a factual aggregate goes to the AI — how many days, within a 30-day window, had a dose logged — never a percentage, never a judgment, never a causal claim. There is no surveillance: the app never sends a "missed dose" or "forgotten dose" notification — the absence of a log is never treated as a failure. This import uses the clinical-processing and AI consents you have already granted (it is a new source for a routine medication data point you already share, not a new category); unavailable to minors and managed profiles. (B) Clinical Records (United States only) — honest conditional note (§3.2, Section 8, and Sections 4, 6, and 9): we have built, and will make available once Apple grants the required authorization (an external process, outside our control, that can take weeks), the read-only import of your own structured clinical records from Apple Health (via FHIR) — lab results (matched via the international LOINC standard), immunizations, medications, conditions/diagnoses already recorded by clinicians, procedures, and allergies — directly into your record, with the same protections as any other data of yours. Free-text clinical notes and insurance/coverage records are never imported. Available only for US accounts; until Apple grants the authorization, the feature stays invisible. No new subprocessor and no new international transfer in either addition. This update triggers re-acceptance (the acceptance screen reappears). Changes (3.10, 2026-07-19): Two new optional, special-category areas (mental health and a reproductive complement), each under its own separate consent — a dedicated bump, with re-acceptance. (A) Mental health from Apple Health (§3.2, Sections 4, 6, and 9): if you log your mood (State of Mind) or answer well-being questionnaires (GAD-7 for anxiety, PHQ-9 for depression) in Apple Health, you may bring them into your record only by turning on a dedicated, separate consent ("Mental health from Apple Health," mind_import, off by default, outside "Accept and continue"). We keep only the daily mood average (a −1 to +1 score; we discard the item-by-item emotions and associations) and, for the questionnaires, only the total score and Apple Health's own classification (we discard the question-by-question answers). This data lives in your record, with a home in the Journal and the "Mental health" system — never on the home screen. Only the weekly mood trend (average and number of days) goes to the AI, descriptively, and only if you have also enabled the Health Diary (daily_journal_ai) — a double consent. The GAD-7/PHQ-9 questionnaires and the ring's stress index are NEVER sent to the AI. No mental-health content appears in notifications. Unavailable to minors and managed profiles. When you revoke, we delete everything (mood and questionnaires). Basis: LGPD Art. 7, I + Art. 11, I; GDPR Art. 6(1)(a) + 9(2)(a); Washington MHMDA (per-category consent); requires iOS 18+. (B) Cycle/reproductive complement (§3.2 and Sections 6.10 and 9): the contraceptive (in use) and lactation states can now contextualize the educational reading of your labs (they shift reference ranges, as pregnancy and menopause already did). They follow exactly the same design as pregnancy: they stay only on your device (Keychain, outside iCloud and backups), are never written to any table of ours nor synced, and go to the AI only transiently, at the moment you run the analysis, to calibrate the reading — they are not stored by us and the AI does not record them as a condition. In addition, cycle deviations from Apple Health (infrequent/irregular cycles, persistent intermenstrual bleeding, prolonged periods) appear as descriptive findings within cycle tracking (under the cycle opt-in you already control), always suggesting a conversation with your gynecologist, without alarm. As already applies to the cycle, the AI chat does not receive cycle data, and none of this becomes a notification. The app still does not import the Apple Health "pregnancy test" and does not import sexual activity. Basis: LGPD Art. 7, I + Art. 11, I + Art. 33; GDPR Art. 6(1)(a) + 9(2)(a) + 44–49; Washington MHMDA. No new subprocessor and no new international transfer. This update triggers re-acceptance (the acceptance screen reappears). Changes (3.9, 2026-07-19): A transparency update (a minor bump, with re-acceptance — anyone who already accepted 3.8 simply confirms they have read this update): we enumerate the new Apple Health and wearable data categories we now import, all under the consents you already granted (clinical + AI + international transfer) — no new subprocessor, no new international transfer. (1) New device/Apple Health data (§3.2): a possible sleep-apnea event and high sound-exposure alerts; home spirometry (FVC/FEV₁/peak flow) and inhaler use; the Oura ring's hypnogram and ideal sleep window; symptoms imported from Apple Health; nutrition data (water, caffeine, energy, macro- and micronutrients); gait (asymmetry, support, step length, stair speed); audiogram (it becomes an audiometry exam in your health record, with no file upload); eyeglass/lens prescription (display only); insulin and alcoholic beverages (display only, never sent to the AI); the ring's vascular age, pulse-wave velocity, and temperature deviation; and standing time, stairs climbed, effort, wheelchair pushes, and the activity's intensity/quality. (2) Oura ring annotations (§3.2 and Section 8) — a correction and clarification: the free text (custom name and comment) is discarded at import and never gets stored; we keep only the standardized category code (e.g., "coffee", "alcohol"), which — aggregated by week and never as free text — may be part of the context sent to the AI when you keep the Health Diary (daily_journal) on. (3) Retention (Section 12.1): we detail that the condensation of daily wearable series (weekly summaries after 13 months; monthly after 36 months) covers the continuous activity, sleep, and environment metrics and the daily continuous-glucose-monitor aggregates — but never manually recorded measurements, point clinical measurements (weight, capillary glucose, blood pressure), nor insulin, alcohol, spirometry, and inhaler use. (4) The nightly sleep reminder may cite the ideal window suggested by Oura, always attributed to Oura (the brand's recommendation, never our advice). (5) We now store a pseudonymous identifier of your WHOOP profile (just a number, never a name or email) to receive real-time update/deletion notices (Section 9). Legal bases indicated in each section. This update triggers re-acceptance (the acceptance screen reappears): anyone who already accepted 3.8 simply confirms they have read it — there is no new mandatory affirmative consent (no new special category, no new subprocessor, no new international transfer). Changes (3.8, 2026-07-18): Consolidated round with six changes. (1) Educational, age-based screening reminders (Section 4): we now use your date of birth and sex at birth — data you already provided at sign-up — to show, as an in-app card (never as a notification), educational reminders about health screenings that population guidelines commonly suggest for your age group; they are generated on your device, by fixed age/sex rules — without using your test results, conditions, or any individual risk assessment —, dismissible one by one and can be turned off. (2) Care team in the analysis (Section 6.11): the context we send to the AI when analyzing your record now includes the name and specialty (and, when you provide them, the institution and the reason) of your Care Team professionals — never phone, email, address, or registration number —, as already happened in chat. (3) Continuous glucose monitor (CGM) glucose (§3.2 and Sections 6 and 8): continuous-monitor days imported from Apple Health are stored only as daily aggregates — mean, minimum, maximum, variability (CV), and the percentage of the day within the 70–180 mg/dL range of the industry display standard (AGP) — and the raw continuous readings are never stored by us; spot/capillary measurements continue as normal measurements; only the aggregates enter the AI context. (4) Oura ring annotations (§3.2 and Section 8): we import the annotations you record in the Oura app (type, custom name, and a free-text comment) under the maximum protection of sensitive data — visible only to you, never sent to the AI, and always deleted when you disconnect Oura; they require an additional Oura permission ("tag" scope): older connections need to be reconnected. (5) AI-generated educational library (Section 6.12): the generic educational content shown in the app may be generated by AI (Anthropic) in a population-level way — one text per topic and language, the same for everyone; the generation receives no data of yours, and the choice of what to show happens on your device. (6) Condensation of wearable series (Section 12.1): raw daily wearable metric series may be condensed after 13 months into weekly summaries (minimum/mean/maximum/count) and, after 36 months, into monthly summaries — a minimization policy; manually entered measurements and clinical measurements (weight, glucose, blood pressure) are never condensed. Legal bases indicated in each section. Triggers re-consent for everyone. Changes (3.7, 2026-07-18): New optional feature for adult female account holders — Pregnancy state (§3.2, the Section 4 table, and Sections 6.10 and 9). You declare only your trimester (not pregnant / 1st / 2nd / 3rd / postpartum, with "prefer not to say"); never the date of your last menstrual period (LMP) nor the estimated due date (EDD). The state stays only on your device (Keychain, outside iCloud Keychain and backups), is never written to any table of ours and never synced, expires in about 40 weeks, and is erasable in one tap. It goes to the AI (Anthropic, USA) only transiently, in the request body, when YOU run an analysis or the chat, to calibrate the reading of your labs by the reference ranges specific to pregnancy and lactation — it is not stored by us, and the AI never records it as a condition, alert, or diagnosis. Unavailable to minors and managed profiles. Specific, prominent consent (pregnancy-state-1.0), separate from the clinical consent, covering the international transfer under the DPA/SCC in effect; revocable in Profile › Privacy. Also in this version: the app stopped importing and storing "pregnancy tests" from Apple Health (§3.2 and Section 8) — the mention was removed. Legal basis: LGPD Art. 7, I + Art. 11, I + Art. 33; GDPR Art. 6(1)(a) + 9(2)(a) + 44–49. Triggers re-consent for everyone. Changes (3.6, 2026-07-18): Adjustments to reminders and notices (Section 12-A), with no new data collection: (1) the invitation to come back to the app after a stretch without use (for example, around one and three weeks) now belongs to the neutral service reminders (group 1, pre-enabled) rather than the inference-based group — because what triggers it is only the time since you last opened the app (an app-usage signal, not a reading about your health); the body is neutral, with no health data and no blame, and the reminder remains toggleable in Profile › Notifications. (2) In the Question of the Day (under the "Daily headline", optional), the notice body may become the question itself when it comes from a closed list of everyday, non-sensitive questions (coffee, energy, hydration, a change in routine, how your body responded to yesterday's workout in a generic way) — fixed phrases, the same for everyone, with none of your data, value, or judgment; sensitive questions (alcohol, night context, stress), symptom questions, or ones that would involve medication/appointments or an inference about your data are never shown in full. (3) The analysis-ready notice may state how many exams were organized (a count), never the name or value of any of them; plus new neutral wording in existing reminders. Legal basis for the service items: performing the service/legitimate interest (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)); for the inference-based notices: specific consent (LGPD Art. 7, I and Art. 11, I; GDPR Art. 6(1)(a) and Art. 9(2)(a)). Triggers re-consent for everyone. Changes (3.5, 2026-07-17): New optional agenda feature (Section 12-A) — and the first feature in the app that uses your location: with "Alert me when it's time to leave" on, on the day of an appointment that has a time and address, the app estimates your travel time (via Apple Maps, on your device) and alerts you "Time to leave" so you arrive on time. Location is requested only when you turn the option on (iOS "While Using the App" permission), used 100% on your device for the calculation, and never stored, never sent to our servers, and never sent to the AI. Opt-in per device, off by default, revocable in the app or in your iPhone Settings; dependent and managed profiles are excluded; the calculation and the alert are 100% on your device. Legal basis: specific, explicit consent (LGPD Art. 7, I and Art. 11, I; GDPR Art. 6(1)(a) and Art. 9(2)(a)). Triggers re-consent for everyone. Changes (3.4, 2026-07-17): New optional exception to the neutral body of agenda reminders (Section 12-A): the adult account holder may enable, for their own appointments and follow-ups, showing on the lock screen the professional, the time, and a short address they entered themselves (with a map of the destination) — never the specialty, the reason, or a diagnosis. Opt-in per device, off by default, revocable with immediate effect; dependent and managed profiles are excluded; 100% on your device (nothing travels over push). Legal basis: specific, explicit consent (LGPD Art. 7, I and Art. 11, I; GDPR Art. 6(1)(a) and Art. 9(2)(a)). Triggers re-consent for everyone. Changes (3.1, 2026-07-16): AI-assisted support is now active (to draft and translate replies). For logged-in users, it runs only under a new, dedicated, unbundled consent — "Share my support messages with AI assistance" (support_ai_share) — separate from the general AI Processing consent, off by default, refusable on its own (the paid product works fully without it), together with the existing International transfer consent (intl_transfer); a human reviews every draft/translation before it is sent, the support text is best-effort minimized before sending (not de-identification, not a guarantee of complete removal), and your health record is never sent. For people who write to support without an account, it is consent-first: no message goes to AI until the sender grants two separate consents (to process the message, and to transfer it to Anthropic (Claude), in the United States); otherwise a human replies with no AI. The transfer is covered by our existing DPA + EU SCC with Anthropic — the same terms governing record analysis, extraction, and chat — with no new subprocessor. Triggers in-app re-consent. Changes (3.0, 2026-07-15): New optional exception to the neutral notice body (Section 12-A): with the "Daily headline" on, the adult account holder may include, in notices derived from their own data, a small detail of the data — e.g., minutes left to their activity goal, or that they slept above their usual (no "below" variant exists). Closed list of phrases — never a diagnosis, lab value, judgment, or urgency. Opt-in per device, off by default, revocable with immediate effect; dependents/managed profiles are excluded. Also in this version: new closed-list domain headlines (sleep, activity goal, new lab result, partial week, consistency), an appointment-eve notice with the prep summary ready, and a technical sensor-quiet notice. Legal basis: specific, explicit consent (LGPD Art. 7, I and Art. 11, I; GDPR Art. 6(1)(a) and Art. 9(2)(a)). Triggers re-consent for everyone.
In short (read this first)
MyHealth is an iPhone app that helps you organize your own health record, with an artificial intelligence (AI) assistant that reads the documents and photos you upload to extract and fill in records (which you confirm before saving) and offers a supportive educational reading. You bring together your lab results, conditions, medications, vaccines, appointments, measurements, and documents in a single place, and the app builds a timeline of your health to prepare you for the conversation with your doctor.
The most important points:
- Who you are is kept separate from your health data. Your name, email, phone, and identification document (such as your tax ID) are stored in an encrypted vault (authenticated field-level encryption — AEAD — deterministic, using the pgsodium library, AES-256) and are decrypted only under your own identity, by a secure function. The clinical tables refer to you only by a code (pseudonym).
- Your data stays in Brazil. The database is hosted in the São Paulo region (
sa-east-1). - The AI receives the clinical content of your health record — without our sending your direct identifiers. The AI analysis is MyHealth's service: to use the app you authorize, in two acceptances of their own, the AI analysis and the transfer to the United States. You are not required to agree; without agreeing, the app does not work. It may include lab results, medications, symptoms, sleep and wearable metrics, your device's events, lifestyle habits you declare (smoking, alcohol, activity, sleep), and menstrual cycle records, plus your sex and age. From your food diary, the AI receives weekly averages of the complete days. Only the chat — which you alone read — also receives the calorie goal you set, the average time, per week, of the first and the last meal logged and the names of the foods that repeat the most. A meal, a portion or the photo never go. A meal's photo or description goes to the AI only if you turn on that separate option; the description is not kept, and the protected copy of the photo is kept only with the meal you save, visible only to you. Name, tax ID, email, and phone are kept encrypted in a separate vault and are not sent to the AI. Your data does not train models. This processing involves an international transfer to the United States (Anthropic). See Sections 6 and 9.
- The account is for people 18 or older — or of the age of majority of the country you enter at sign-up, if higher. Minors are only included as a profile managed by an adult guardian (Section 11).
- The AI features are paid and consume your usage quota (analyzed pages and AI Chat prompts); AI meal readings are included in your plan, with a daily or weekly limit shown in the app, and logging a meal by hand is always free. There is an initial free courtesy, a subscription that renews the quota each cycle, and add-on packs that do not expire. Purchases are processed by Apple (App Store); a minor's AI use is charged to the guardian. See Section 9 and the Terms.
- You're in charge. You can access, correct, export (in the standard health format FHIR R4 and as PDF), revoke consents, and delete your account whenever you want.
- MyHealth is NOT a doctor and is not marketed as a medical device. It does not diagnose and does not prescribe. The readings and the AI assistant's responses are educational — you must always confirm with your doctor. To help you prepare for your appointment, the educational reading may explain the meaning and context of your findings (the mechanism, what clinical practice generally investigates, and what is worth bringing to your specialist), but it remains educational information: it never defines your diagnosis, your management, your work-up, or your treatment — that is your doctor's decision.
- Vaccination reminder (minor profiles). For a dependent minor's profile, the educational reading may, based on the recommended immunization schedule (WHO / your country's reference) and the vaccines you have recorded, informatively flag that a vaccine may be pending. It is only an educational reminder to the guardian: the absence of a record in the app does NOT mean the vaccine was not given (it may have been administered elsewhere), it is not a demand nor an individual immunization recommendation, and it must be confirmed on the vaccination card, with the pediatrician, or at the immunization service.
The full text below details all of this and describes your legal rights.
1. Who we are (the Controller) and the DPO
The party responsible for processing your personal data ("Controller" under the LGPD; "Controller" under the GDPR) is:
BAS AI — BAS ARTIFICIAL INTELLIGENCE LTDA
CNPJ: 64.106.409/0001-70
Website: www.bas-ai.com
Address: Rua Gomes de Carvalho, 911, Vila Olímpia, São Paulo/SP, ZIP 04547-003, Brazil
In this document, "MyHealth", "we", or "the app" refer to this Controller.
Data Protection Officer (DPO)
For any privacy and data protection matter, contact our Officer (LGPD Art. 41 / Data Protection Officer, GDPR Art. 37):
Email: dpo@bas-ai.com
Officer's name: Guilherme Kaschny Bastian
Mailing address: Rua Gomes de Carvalho, 911, Vila Olímpia, São Paulo/SP, ZIP 04547-003, Brazil
We adopt the GDPR standard as our global baseline of protection (the most protective standard, applied to all users), even though the service is not offered in the European Union/EEA, the United Kingdom, Switzerland, Turkey or the United Arab Emirates.
2. To whom this Policy applies
This Policy applies to everyone who uses the MyHealth app. The app is multi-language (Portuguese, English, and Spanish) and is offered in the list of countries set out below.
Where the law of your country is more protective, it prevails. We treat the LGPD (Law No. 13.709/2018, Brazil) and the GDPR (Regulation (EU) 2016/679) as our minimum standard of protection everywhere, applied to all users. The app is offered in a list of countries: Brazil, the United States, Canada, Mexico, Argentina, Colombia, Chile, Peru, Uruguay, Ecuador, Costa Rica, Panama, Paraguay, Bolivia, the Dominican Republic, Guatemala, New Zealand, Singapore, India, South Africa, Australia, Japan, South Korea, Angola, Mozambique and Cabo Verde. It is not offered in the European Union/EEA, the United Kingdom, Switzerland, Turkey or the United Arab Emirates, nor in the places listed in the paragraph below. Whoever already had the app in a country that left the list can keep using it, but no longer receives updates through that country's store.
Where MyHealth is not offered. MyHealth is not offered, and the AI features do not work, in Russia, Belarus, Yemen, Kosovo, Afghanistan, Hong Kong, Macao, Myanmar and Venezuela, because our AI provider does not serve those places: the app is not distributed there and our server refuses AI calls linked to them (by the country of your profile, of the account holder, and of the App Store storefront of your most recent purchase). Using MyHealth in the regions of Crimea, Donetsk, Kherson, Luhansk and Zaporizhzhia is also not permitted.
Users in the United States: US-specific supplementary disclosures — the California Privacy Notice (CCPA/CPRA) and the US Consumer Health Data Privacy Policy (Washington, Nevada and Connecticut) — form part of this Policy as supplementary documents, published at https://www.bas-ai.com/myhealth/legal and prevailing, for residents of those jurisdictions, where they are more specific.
Residents of Nevada (SB 370, NRS 603A.400 et seq.) and Connecticut (CTDPA, CGS §42-515 et seq.): the consumer health data we collect, the purposes, the sources, with whom we share it and how to exercise your rights (access, deletion, withdrawal of consent and appeal) are in the US Consumer Health Data Notice (https://www.bas-ai.com/myhealth/legal/us-washington-chd), which also applies to you. We do not sell health data and we do not use geofencing.
Children and adolescents: self-registration is intended for people 18 or older — or of the age of majority of the country you enter at sign-up, if higher. Data of minors may only be included by a legal guardian, who manages the dependent's profile (see Section 11).
3. What data we collect
We collect only what is necessary for the app to work (the minimization principle). Below is what we collect and where it is stored.
3.1 Identity data (PII) — encrypted in a vault
The following data identifies you directly and is stored in an identity vault (identity_vault), encrypted field by field with authenticated (AEAD), deterministic encryption (the pgsodium library, AES-256), physically separated from the clinical tables. It is decrypted only by a secure function, under your own identity:
- Name (or display name);
- Email;
- Phone;
- Identification document (for example, the CPF/tax ID) — optional, used to redact your documents before they go to the AI. Do not enter national identifiers whose collection your country's law restricts, such as the My Number (Japan), the resident registration number (South Korea) or the Aadhaar (India).
The clinical tables do not contain this data — they refer to you only by a profile code (pseudonym). In the pseudonymized profile we keep only the clinical-demographic minimum needed to interpret the data correctly (for example, biological sex and date of birth/age, important for lab reference ranges).
3.2 Health / sensitive data
This is sensitive personal data (health) and receives maximum protection. In the United States, BAS AI is not a HIPAA "covered entity" or "business associate"; your health data is protected by what this Policy describes and by the applicable state and federal laws (for example, the FTC Act and the Health Breach Notification Rule). We collect, as you record or import it:
- Lab results and laboratory markers (values, units, reference ranges, dates);
- Conditions and body systems ("head to toe" line);
- Medications (item, dose, indication, period, prescriber, active/inactive status);
- Allergies and intolerances (substance, category, reaction, severity);
- Vaccines;
- Appointments / encounters;
- Vital signs and bioimpedance — weight, body fat percentage, lean mass, circumferences, blood glucose, blood pressure, heart rate, saturation, temperature;
- Continuous glucose monitor (CGM) glucose — daily aggregates only. If you import glucose from Apple Health, the app distinguishes, day by day, the spot measurement (for example, a capillary reading or one you typed in — stored as a normal measurement, with date and time) from a continuous monitor (CGM) day, which produces hundreds of readings: on days identified as continuous-monitor days, we store only five daily aggregates — mean, minimum, maximum, variability (CV), and the percentage of the day within the 70–180 mg/dL range (the range of the industry display standard, the AGP report) — and the raw continuous readings are never stored by us (they are summarized in memory, on your own device, at import time). These aggregates are a factual display of an industry standard — they are not an individual target and not a judgment about your glucose control (see the Medical Notice);
- Symptoms and complaints;
- Physical activity and energy expenditure (the day's active and resting energy, when Apple Health has them — see the "Food diary" subsection below and Section 8);
- Documents and reports (PDFs, photos, and text files — lab results, prescriptions, reports, records you submit);
- Family history of health;
- Care team (professionals, area, institution, reason, optional professional contact and address);
- Card / emergency information (blood type, allergies, emergency contact). Besides living in your account, these fields are mirrored on your own device, in the iOS Keychain (
WhenUnlockedThisDeviceOnlyprotection, which keeps them out of iCloud Keychain and out of backups), so the card stays visible even without internet — which is precisely when it tends to be consulted. It is the same information you already entered, stored only to be shown to you: it is not new data, it is not sent anywhere, and it is not shared. You can also choose medications in use to appear on the card: nothing goes on it by itself — only what you tick appears, with the name and dose as you entered them, never the indication, the prescriber or anything generated by the AI. The chosen list travels with the card's mirror on your device, so it shows without internet, and the card tells whoever reads it that the list was entered by you, was not verified and may be incomplete. This is a screen made to be shown to third parties: tick only what you want someone holding your device to be able to read. This local copy is erased when you sign out and when you delete your account, along with the other data on this device; - Notes, questions, and messages that you write in the app (including the chat with the AI assistant and the messages you send to our support through the app), to the extent they contain health data.
- Device events — events that your device records: ECG classification (sinus rhythm / atrial fibrillation / inconclusive) with the average heart rate, irregular rhythm and high or low heart rate notifications, atrial fibrillation burden, fall detection, and — when your device offers them — possible-hypertension notifications, low-cardio-fitness notifications, possible sleep-apnea events, and high sound-exposure alerts (environment and headphones). We store the event's classification and metadata. Regulated device events (apnea, sound exposure) are shown exactly as the device classifies them, never reinterpreted by us. The electrocardiogram trace (the waveform) has its own rule — see just below.
Electrocardiogram trace (waveform) — optional, only if you turn it on
Up to version 3.16 of this Policy, we did not store your ECG trace: only the classification and the metadata. That changes in this version, and it changes only for those who turn the feature on.
If — and only if — you turn on "Store my ECG trace" (Profile › Privacy), we begin importing from Apple Health, alongside the classification, the trace of the exam: the sequence of voltage measurements your watch recorded. The option starts off; while it is off, nothing changes.
Why we offer it. The trace is what your doctor reads. The classification says "sinus rhythm" or "atrial fibrillation"; the trace is the exam. Storing it lets you take it to your appointment, including an older trace, without depending on still having the same device.
What we do NOT do with it:
- We do not interpret it. No rule, threshold or label of ours. We do not measure intervals, do not detect beats, do not classify rhythm, do not say whether it is normal. The classification shown beside it is Apple's, attributed to Apple.
- We do not send it to the artificial intelligence. Never — not in the analysis, not in the chat, not summarised or excerpted. The trace is stored outside the tables that feed the AI, so that no path exists by which it could reach it.
- We do not alter it. No filtering, no smoothing, no resampling that changes the waveform.
- It does not leave Brazil (São Paulo,
sa-east-1), it does not enter family sharing, notifications, the lock screen, the app's search or our team's internal console, and it is never stored in the profile of a dependent minor.
For how long. As long as your account exists and you want it — an older exam matters because it allows comparison. The control is yours and it is granular: on the event's record you can delete only the trace and keep the entry (classification, heart rate and date). Turning the option off deletes the traces already imported. When you disconnect Apple Health, the traces are deleted by default. The trace is never summarised or condensed over time.
Why we ask for a separate authorisation. Because the permission you already gave Apple Health does not distinguish "see the classification" from "store the trace" — it is a single authorisation, and it is Apple's, not ours. Data like this does not enter your health record riding on an authorisation given for something else. Turning it off does not disconnect Apple Health.
- Your wearable's annotations (category code only). — if you connect an Oura ring, we import the annotations you record yourself in the Oura app (for example: coffee, alcohol, symptom, medication, travel). The free text of those annotations — the custom name and the comment you may have written, which could mention, for example, mental health or substance use — is discarded at the moment of import and never gets stored by us (it does not touch your health record, our records, or our logs). We keep only the standardized category code of the annotation (the "type": coffee, alcohol, etc.), which stays visible only to you (it does not appear in family sharing) and is deleted when you disconnect the wearable. This standardized code — aggregated by week and never as free text — may be part of the context sent to the AI when, and only when, you keep the Health Diary (
daily_journal) on; without that consent, it is not sent to the AI. Importing the annotations requires an additional Oura permission ("tag" scope): older connections need to be reconnected. - More Apple Health and wearable data you choose to import — when available on your device and you import it: detailed activity (standing time, stairs climbed, physical effort, movement intensity and, for wheelchair users, pushes and distance — read as activity, never as a condition); average sound exposure from the environment and headphones (in decibels); detailed sleep (phase profile/hypnogram and the ideal sleep window suggested by Oura); respiratory function (home spirometry — FVC, FEV₁, and peak flow — and the number of inhaler uses); nutrition data (water, caffeine, energy, and macro/micronutrients, when you use a counting app that writes to Apple Health — read-only: MyHealth does not write your meals to Apple Health); gait (asymmetry, double support, step length, and speed going up/down stairs); audiogram (an Apple Health hearing test becomes an audiometry exam in your health record, with no file upload); eyeglass/lens prescription (display only, outside the AI); insulin (daily totals) and alcoholic beverages (daily count), kept display only and never sent to the AI; and the Oura ring's estimates of vascular age, pulse-wave velocity, and temperature deviation. All are health data with the same maximum protection and, except for the items marked "display only", are part of the AI context under your consent — always in a descriptive/educational way, never as a diagnosis, target, or treatment.
- Observed medication adherence (Apple Health, iOS 26 or later). If your device is on iOS 26 or later and you log in Apple Health that you took a medication dose, MyHealth can import only the doses marked as taken, matched to a medication you have already registered in the app (we never create a new medication from this import). This is adherence memory for you, never surveillance: the absence of a log is never treated as a "missed dose", and the app never sends a missed-dose notification. When you authorize AI Processing (Section 6), the AI receives only the factual aggregate — how many days, within a 30-day window, had a dose logged — never a percentage, never a judgment, never a causal claim with another data point of yours. Unavailable on minors' and managed profiles (manual entry by a guardian remains allowed).
- Clinical Records — United States and Canada. For accounts in the United States and in Canada — the countries where Apple offers Health Records on iPhone and where the app is offered — and only if you authorize it on Apple Health's own permission sheet, the app performs the read-only import of your own structured clinical records from Apple Health, received in the international FHIR standard from your healthcare providers: lab results (matched to our catalog via the LOINC code), immunizations, medications, conditions/diagnoses already recorded by a clinician, procedures, and allergies — each integrated into the corresponding section of your record, with the same protections as any other data of yours. We never import free-text clinical notes or insurance/coverage data. You choose, on Apple's sheet, which categories to share, and you can withdraw that authorization at any time in the device's Settings. Outside those two countries, the feature does not appear in the app.
- Menstrual cycle and reproductive health — menstrual flow, intermenstrual bleeding, ovulation tests, and cervical mucus quality, when you record or import them. Under the same cycle opt-in (the Apple Health read permission), the app may also import the descriptive cycle-pattern findings that Apple Health itself classifies — infrequent cycles, irregular cycles, persistent intermenstrual bleeding, and prolonged menstrual periods —, kept only as the presence of the finding, verbatim (no grade and no interpretation of our own). These findings are part of the analysis context in a descriptive way ("persistent irregularities are worth discussing with your gynecologist", without alarming) and only go to the chat if you turn on the "Talk about my cycle in the chat" option (off by default; see the version 3.18 Changes and the Section 4 table). Correlated signals, such as basal body temperature, may be imported as vital signs. If you are female and 40 years old or older, the app may, optionally, ask your phase in relation to menopause (still menstruating, in transition, or already in menopause — with the option not to answer); this information is self-declared by you, not imported from Apple Health, and helps the AI better interpret your hormones (for example, FSH, LH, and estradiol). We do not import sexual activity records. This is sensitive data with the same maximum protection as the rest of the health data.
- Pregnancy state (optional, only on your device). If you are an adult female account holder (your own profile, 18 or older, sex assigned female at birth), the app may, optionally, ask your pregnancy stage — only the trimester (not pregnant / 1st / 2nd / 3rd trimester / postpartum), with the option "prefer not to say" (which erases the entry). For this feature we collect only that trimester enum — never the date of your last menstrual period (LMP) nor the estimated due date (EDD), never a date. This state is kept only on your device, in the iOS Keychain (
WhenUnlockedThisDeviceOnlyprotection, which keeps it out of iCloud Keychain and backups), per profile: it is never written to any table of ours (Supabase), never added to your lifestyle habits (lifestyle_facts), and never synced; it expires on its own in about 40 weeks and is erasable at any time, in one tap (turning the feature off erases the data from the Keychain), in Profile › Privacy. Only when you run an analysis (or the chat) with the feature on is this state sent at that moment, in the request body, in memory, to our AI provider (Anthropic, United States — Sections 6 and 9), solely to calibrate the reading of your labs by the reference ranges specific to pregnancy and lactation, and it is not stored by us (Anthropic keeps the request for its own contractual limit, as a rule ~30 days — Section 6.2). Automatic/proactive analyses and large-record analyses do not receive this state — it accompanies only the analysis you trigger. The AI never writes "pregnant", "expecting", or "breastfeeding" as a condition, alert, problem-list item, or diagnosis in your health record (model instruction + deterministic server-side output filtering, with a regression test). Unavailable on minors' and managed profiles (blocked in the app and on the server). It depends on your specific, prominent consent (pregnancy-state-1.0), separate from the general clinical consent, which covers the international transfer to Anthropic/USA under the DPA/SCC in effect and is revocable in Profile › Privacy. This is not medical advice — your obstetrician follows your pregnancy. This feature uses only the trimester you declare and does not derive from any menstruation records you may import from Apple Health (handled in the item above). The same state is also read on your device to limit the calorie goal of the food diary (see "Food diary" below) — that use sends it nowhere. - Contraceptive state (optional, only on your device). If you are an adult female account holder (your own profile, 18 or older, sex assigned female at birth), the app may, optionally, ask whether you use a contraceptive method and which type (hormonal or non-hormonal), with the option "prefer not to say" (which erases the entry). Just like the pregnancy state, this state follows exactly the same design: it is kept only on your device, in the iOS Keychain (
WhenUnlockedThisDeviceOnlyprotection, which keeps it out of iCloud Keychain and backups), per profile — it is never written to any table of ours (Supabase), never added to your lifestyle habits (lifestyle_facts), and never synced; it expires on its own (in about 24 months) and is erasable at any time, in one tap (turning the feature off erases the data from the Keychain), in Profile › Privacy. Only when you run an analysis (or the chat) with the feature on is this state sent at that moment, in the request body, in memory, to our AI provider (Anthropic, United States — Sections 6 and 9), solely to calibrate the reading of your labs by the reference ranges specific to contraceptive use (for example, the effect of hormones on some markers), and it is not stored by us (Anthropic keeps the request for its own contractual limit, as a rule ~30 days — Section 6.2). Automatic/proactive analyses and large-record analyses do not receive this state — it accompanies only the analysis you trigger. The AI never writes your contraceptive use as a condition, alert, problem-list item, or diagnosis in your health record. Unavailable on minors' and managed profiles (blocked in the app and on the server). It depends on your specific, prominent consent (contraceptive-state-1.0), separate from the general clinical consent and from the pregnancy state, which covers the international transfer to Anthropic/USA under the DPA/SCC in effect and is revocable in Profile › Privacy. The lactation / postpartum state is handled by the "postpartum" stage of the pregnancy state (item above), under the same on-device design. This is not medical advice — your doctor follows your reproductive health. - Lifestyle habits you provide — data you declare, optionally, in the app's cards: smoking (and cigarettes-per-week range), alcohol consumption (and drinks-per-week range), physical activity level, your perception of your sleep, and your dietary pattern (no restriction, vegetarian, or vegan — with the option not to answer). When you authorize AI Processing (Section 6), these habits are part of the context sent to the AI, along with the year you provided them — so the educational reading can weigh whether a habit declared long ago still reflects your routine (the dietary pattern contextualizes, for example, the reading of B12 and iron, always descriptively, never as a diet or supplement recommendation).
Daily records of sensitive habits (special category). Beyond what you submit, the app may ask, occasionally and optionally, about habits that devices do not measure: a day's alcohol drinks (substance-use data) and what shaped a shorter night — including the options "Stress" (mental-health data) and "Alcohol". Because they involve a substance and a mental state, we treat these records as sensitive / special-category personal data. This is different from the weekly range of smoking/alcohol you declare at registration (the "Lifestyle habits you provide" item, above), which is part of the AI context when you authorize it: here we mean the daily, point-in-time records, which stay on your device and in your health record and are not sent to the AI.
We only collect them after YOUR specific and prominent consent (the daily_journal purpose, which you turn on in Profile › Privacy & consents), separate from accepting the Terms and from the general clinical consent. It is OFF by default — nothing is recorded until you turn it on —, it is blocked on the server until the consent exists, and it is UNAVAILABLE on minors' profiles and managed profiles (blocked in the app and on the server). Declining it does not reduce any other feature of the app.
Well-being check-in distinction (energy, mood, stress and sleep). The "How are you today?" check-in is handled separately, as health data under the general clinical consent (it does not fall into the sensitive-habit category above). It has four axes that you yourself answer, each on three levels (1 = worse · 2 = average · 3 = better): energy, mood, stress and — only when the app does not receive sleep from your wearable — sleep. Like the rest of the health record, these axes may be part of the context sent to the AI under that same clinical consent (together with AI Processing and International Transfer), only as a weekly average per axis — never a single day's answer, never free text. This includes the stress axis, and we want to be explicit: it is your own self-report, of low granularity (three levels), aggregated by week, sent so that the educational reading can cross how you feel with your sleep, your activity and your lab results — always descriptive. The AI is instructed hard: never diagnose anxiety, depression or a "stress disorder", never treat this axis as a clinical instrument, never advise treatment. What does NOT go to the AI, and still does not: entries in the sensitive Health Diary (alcohol doses and stress/evening context, under the separate consent described above) — dated sensitive self-observation entries, more stigmatizing, which is why they have their own consent; your ring's stress index (Oura); and the GAD-7/PHQ-9 questionnaires from Apple Health. The distinction in one line: the check-in axis is an answer of yours, on three levels, that the analysis reads as the week's average; the sensitive Diary is a daily record of substance use and evening context that stays between you and your health record.
What changed in this description (3.14). Up to version 3.13 this paragraph said that "point-in-time stress" stayed out of the AI and described the check-in as being mood only — text written before the check-in gained its own axes. A reasonable reader would conclude that no self-reported stress reached the AI, and the check-in axis did, as a weekly average. The text above is the correct description; the correction is one of the reasons for the re-acceptance in version 3.14.
Other non-sensitive daily contexts. Occasionally and optionally, the app may also ask about lifestyle and wellness contexts that devices don't measure — for example coffee/caffeine, energy levels, hydration, how your workout felt (light/normal/hard), and routine changes during the week (e.g., travel, a new workout, changes in diet or sleep). Like the mood check-in, these are health data under the general clinical consent and are stored in your health record. When you authorize AI Processing and International Transfer (Sections 6 and 9), these contexts are included in the context sent to our AI provider (Anthropic, USA — Section 9) only in weekly aggregated form, as day counts — for example, "low hydration on 3 days of the week" or "3+ coffees on 2 days"; for routine changes, only the category you reported that week (e.g., "travel") — never the individual daily entry, never free text, limited to recent weeks. The sole purpose is to correlate, in an educational and descriptive way, your habits with your sleep, activity, and exam data — never diagnosis or treatment. Entries in the sensitive health diary (alcohol and stress/evening context) are not included: they remain outside the context sent to the AI and under their own separate consent, and any future AI use of them would require new explicit consent.
Your ring's stress index: you see it, the AI does not. If you connect an Oura ring, the daily scores we import (Section 8) include the day's stress index. We show it to you in the "Today's readiness" card, on the Routine tab, in the most conservative way possible: we display the label Oura itself publishes for that day (for example, restful, normal or stressful), exactly as the brand publishes it, always with the date it refers to — no translation into a scale of ours, no severity color, no severity ordering, and no calculation of ours: MyHealth never computes a "stress index" from your physiological signals. This index is never sent to our AI provider — not in the analysis, not in the chat, and not inside Oura's resilience sub-scores (the exclusion is applied in the database query itself, not merely as an instruction to the model) —, never enters the PDF Health Report you hand to third parties, never becomes a notification and never appears on a dependent's or a minor's profile. Collection of this index happens under the consent you granted when you connected Oura, revocable at any time (Section 8).
"What appears in the app" — hiding from the screen is different from withdrawing consent. In Profile › Privacy & consents there is a card called "What appears in the app", with one switch per sensitive category you actually have on that profile: Ring stress (your ring's index), Menstrual cycle and Mental health. Turning one off hides that content from the app's screens — and that is all —, with immediate effect and across all your devices (the choice travels with you, not with the device). To leave no doubt: hiding does not disconnect your ring or Apple Health, does not withdraw any consent, does not delete any data, does not stop collection and does not change what our AI provider receives. Collection and use are governed by your consent — the two controls sit on the same screen on purpose, but they are different controls with different effects: if what you want is to stop collection or use, use consent withdrawal (Section 5) or disconnect the source (Section 8). When you hide Menstrual cycle, it also stops being offered in the PDF Health Report — the PDF goes to third parties, and offering to send data you chose not to see would be the opposite of what you asked for. This control does not exist on a dependent's profile or in read-only access. The Ring stress switch hides the line with the ring's index; the "Stress" axis of the check-in (which is your self-report, not the ring's reading) and Oura's Resilience index remain visible — which is why the label names the ring.
Food diary and meal photos — adult account holder only
In the Nutrition tab you can keep a food diary. We store, as you log it: each meal (time, meal of the day — breakfast, lunch, snack or dinner — and how it was logged: by photo, by text description or by hand); the items of each meal, with name, portion (for example, "2 tablespoons") and estimated calories, protein, carbohydrates, fat and fiber — and, when the food table or the reading provides them, estimated sodium, potassium, iron, calcium, magnesium, cholesterol, saturated fat, sugars, caffeine and vitamin K, and alcohol only if you have turned on the Sensitive health journal consent (daily_journal) — the server discards it without that consent and deletes it from your meals if you turn it off; when an item came from an AI reading, what the AI suggested, kept with the item; the model and version of the reading used; the "day complete" mark; a personal calorie goal, optional and set only by you; and your choice of the "no numbers" mode (turning off "Show numbers"), which hides calories from the screens.
They are estimates. The calories and nutrients of a meal — especially from a photo — can be quite wrong; that is why nothing is saved without your review, and you can edit or delete any meal, unmark a complete day and remove the goal whenever you want (in Diary preferences, which stay at hand in the "no numbers" mode too; in that mode, logging by hand does not ask for calories).
Days that count toward the balance. A day counts toward the balance and the averages when you mark it as complete or, for a day that has passed, when it has two or more meals; today counts only when you mark it. Days with fewer entries are shown as a partial log.
Who sees it. The diary is yours only. It is not part of family sharing (Section 7), it cannot be accessed by a Manager you have named (§7.2) or by someone with read-only access to your health record, and it does not exist on dependent profiles — it is a feature exclusive to the adult account holder (the barrier is enforced in the database, not only on screen). It is stored in Brazil (São Paulo, sa-east-1), like the rest of the health record.
Energy expenditure. To show the day's balance, the app uses the total expenditure that Apple Health records (the sum of your device's active and resting energy). When it does not exist — for example, without a watch —, the app shows an estimated expenditure, calculated on your device from the weight, height, age and sex assigned at birth you have already recorded (Mifflin–St Jeor equation) plus the active energy, when available, and always labeled "estimated". Without that data, we show no estimate. The day's intake is the one from your diary or, if it is higher and the day is not marked complete, the one another app wrote to Apple Health — never the sum of both.
AI meal reading — photo or description (optional, its own consent). Logging by photo or by text description requires a separate consent — "Read meals with AI (photo or description)" (food_photo_ai) —, off by default and outside "Accept and continue", in addition to the AI processing and International transfer consents. The camera is requested by the iPhone only when you tap "Open camera"; the gallery uses the system picker, which gives the app only the photo you choose, with no access to your library. Before anything is sent, on your device, the photo is reduced (about 1,024 pixels), loses its location metadata, has faces blurred and your own name, CPF/ID, email and phone covered when the device recognizes them in the photo — for example, your name or ID on a delivery label; other text, including other people's data, is not covered. This protection is best-effort: it can fail on difficult photos, so photograph only the plate — avoid people and documents. The photo stays with the meal; the text does not: when you save a meal read from a photo, the protected copy (the same reduced, location-free copy that went to the AI — never the camera original) is kept with the meal, on your device and in our storage in Brazil, so that you can review it and not lose it when you change devices. It is visible only to you: it is not part of family sharing, it cannot be accessed by a Manager or by someone with read-only access, and it never goes to any AI again. Deleting the meal deletes its photos from our storage within minutes, and deleting the account deletes all of them; their copy in the daily backup copy of files is deleted within about 2 hours afterwards (Section 12.2). The photos of a reading you do not save are not kept. The description and the text corrections are not kept; what remains of them is what you confirmed in the review. So as not to read or charge the same photo twice, your device keeps the estimate received and a code of the photo (never the photo) for up to 24 hours (protected and outside backups), and deletes them when you save the meal, when the period ends (as soon as the app notices it has expired), when you sign out or when the account is deleted. Where it goes and Anthropic's retention are in Section 6.13. Text descriptions and corrections you type or dictate (for example, "it was whole wheat", "it was fried") go to the AI under the same consent, for the same purpose.
Logging by hand sends nothing to the AI, uses no reading and is always free.
Food search. To log without a photo, you can search for the food in tables that come inside the app — TACO (the Brazilian Food Composition Table, NEPA/UNICAMP) with the IBGE household measures (POF 2008-2009), FoodData Central (USDA, United States) and the Canadian Nutrient File (Health Canada), with names in Portuguese, English and Spanish. The search happens on your device: what you type is sent to no one. When an item comes from a table, we keep the food's code in that table with it. You can mark foods as favorites; we keep only the codes of those foods, together with your goal.
Without internet. If you save a meal without a connection, it is kept on your iPhone, protected and outside the iCloud backup, with the notice "waiting to send", and it is sent as soon as there is internet — and then deleted from the device. A meal the server refuses stays marked on the device until you discard it. When you sign out or delete the account, unsent meals and stored estimates are deleted from this device.
Export. Meals and their items are included in the FHIR export; the Health Report PDF carries a summary of the last 4 weeks of the diary (estimated averages, without meals or foods). The goal, the complete days, the favorites and the meal photos are not in those files: you see them in the app, and the meal photos are delivered, on request to the DPO, within 15 days (Section 15).
When this data refers to a minor in your care, the same protections apply (see Section 11).
3.3 Locality and language (optional, in clear text)
Optionally, to adapt the experience and prepare future features (such as recommending professionals by city), we may store country, state/province, city, and the preferred language. We do not collect a full address, latitude/longitude, or precise location. These locality fields are kept in clear text because the "city" granularity is not, in itself, sensitive data, and they are protected by the same access rules as your account. When you authorize AI Processing (Section 6), your profile's country is part of the context sent to the AI, only to regionalize, in an educational way, emergency guidance and vaccination-calendar guidance (state/province and city are not sent to the AI).
3.4 Account, session, and security data
- Account and authentication: technical account identifiers and session tokens, to keep you securely signed in; two-factor authentication (MFA/2FA via TOTP), when enabled by you.
- Account number (
account_ref): a short pseudonymous identifier of 8 random, non-sequential digits, generated by us (not collected from you), shown in your Profile and used by support to locate your account — including when you use "Hide My Email" in Sign in with Apple. It is erased upon account deletion. - Notifications (push): when you turn on notifications, we store a technical token that your device generates, used only to deliver the app's notices (e.g., when your analysis is ready). It is a delivery identifier — it is not used for tracking, does not train AI, and is not shared with third parties (it only travels through Apple's push service). You control this in the iOS notification permission and in the Notifications button inside the app, and the notice's content is generic, with no health data. One type of notice — "Something new in your data" (optional, off by default) — is triggered when your data (e.g., sleep, resting heart rate, variability) records a new finding; even so, the content stays generic and with no health data whatsoever (the data never travels in the push, and never suggests abnormality or urgency), at most one per day, and never for minors' profiles. When you sign out, this device's token is unlinked from your account right away; and a token your device has not renewed for 180 days (the app renews it every time it opens) is deleted.
- Access and audit logs (
access_log): metadata about who accessed what and when (action, table, origin, source IP address) — metadata only, never the clinical content. We keep the access IP address for security, auditing, and fraud prevention (and, in Brazil, to meet the retention floor of the Internet Civil Framework, Law 12.965/2014, Art. 15). **We also log the technical identifier of your browser/app (user-agent) on synchronous accesses (exam upload, AI chat, and access ping), for the same purpose and the same period. The recent access IP also forms part of the minimum forensic index** that survives account deletion (see 12.2). - Consent records (
consent_events): which purpose you authorized, the legal basis, the Policy version, and the moment — in an immutable way (see Section 5). - AI usage and billing: we record metadata of the use of the AI features (function, model, number of tokens) and your usage-quota balance and consumption (pages, prompts and AI meal readings) and add-on packs, to operate billing and prevent abuse. To count meal readings and not charge them twice, we keep, per reading: an attempt code, the quota day, the outcome (delivered, not food, failed), how many corrections were used, the AI usage record (model, tokens, cost) and an irreversible fingerprint of what was sent, which serves only to recognize the same attempt; per day, how many readings were not charged; and, if the estimate's note goes through our clinical-language check, the record of that check — never what you ate, the photo or the text. These records do not contain the analyzed health content.
3.5 De-identified usage data
We collect minimal stability and diagnostics data (telemetry) — crashes, errors, performance — in a de-identified way and without any health content, to keep the app safe and working (see Section 13). This is internal processing: we do not use analytics SDKs or third-party tracking. As a self-limited minimization measure, we retain this telemetry for up to about 12 months (see Sections 12 and 13).
Usage and navigation events (linked to your account, and you can turn them off). To find out where the app stalls or confuses people, we record which screens you open — including the pages of the upload tutorial and whether you skipped or finished it —, at which step an upload stopped, that you logged a meal (and, when you log it without a photo, whether it was by hand, through the food-table search or by repeating an earlier one), marked a day as complete or saved a goal — never the food, the amount, the calories or the goal value — and, when you open the app by tapping a notice, which type of notice it was (only the category, never the notice content) — for example, "opened Upload test and closed before saving". Unlike the telemetry in the paragraph above, these events are linked to your account — which is why we declare them separately instead of calling them de-identified. We record nothing from your health content: no test, no marker, no condition, and nothing you write. This is internal processing: it stays with us, we use no analytics SDK and no third-party tracker, and it is not advertising. Retention: up to 12 months. Basis: legitimate interest (LGPD Art. 7, IX; GDPR Art. 6(1)(f)); you may object at any time in Profile › Privacy & consents › "Help improve the app" — the switch takes effect on tap, and the app works the same.
3.6 What we DO NOT collect / DO NOT do
- We do not sell your data.
- We do not run targeted advertising based on your health, nor do we use third-party trackers that see your health data.
- We do not collect precise location or phone contacts. (The only feature that uses your location is the optional "time to leave" alert, which sends it to Apple Maps, never to us — Section 12-A.) The camera and gallery are accessed only at the exact moment you decide to upload a document or photograph a meal (just-in-time permission: the iPhone asks for the camera only when you tap "Open camera"; in the gallery, the system picker gives the app only the photo you choose).
- Microphone, only to dictate a meal. The app uses the microphone and the iPhone's speech recognition only when you tap "Speak" to dictate a meal description — both permissions are requested on that first tap, never before. The transcription happens on your device (the app does not fall back to Apple's servers; if your device has no on-device recognition for the app's language, it says so and suggests the keyboard's microphone). The audio is neither kept nor sent: only the text you then send goes to the AI, like a typed description (§3.2). If you dictate with the iOS keyboard's microphone, iOS itself transcribes, under Apple's rules.
4. Purposes and legal bases
Every processing activity has a legal basis. Because we process sensitive health data, we are especially rigorous: each sensitive purpose is recorded in our consent record with the corresponding legal basis and Policy version.
| Purpose | What it is | Legal basis — LGPD | Legal basis — GDPR |
|---|---|---|---|
Clinical processing (clinical_processing) | Organize your documents, structure values, build the health record's timeline and trends — including the food diary (§3.2) and the decision to send to your device the notices that start from your own data (Section 12-A). Requested prominently, separate from accepting the Terms, and revocable — revoking it deletes the account (Section 5) | Primary basis: Art. 7, I and Art. 11, I (specific and prominent consent for sensitive data). Subsidiary basis (only for security, integrity, compliance with a legal obligation, and operating deletion): Art. 11, II, "a" (legal obligation), "d" (regular exercise of rights) and "g" (fraud prevention and the data subject's security). We do not invoke health protection (Art. 11, II, "f") | Primary basis: Art. 6(1)(a) + Art. 9(2)(a) (explicit consent for health data). Subsidiary basis (security, integrity, legal obligation, and deletion): Art. 6(1)(c) and (f). We do not invoke Art. 9(2)(h): Art. 9(3) would require a health professional bound by confidentiality in the flow, and there is no doctor in the loop |
AI processing (ai_processing) | Send the pseudonymized clinical content (without direct identifiers) to the AI (Anthropic) to read the documents and photos you upload and from them extract and fill in records (lab results, medications, vaccines, measurements, professionals — which you confirm before saving), structure the health record, and generate a supportive educational reading (assistant, never diagnostic — see Section 6) | Art. 7, I and Art. 11, I (specific and prominent consent), disclosed as a condition of the service (Art. 9, § 3) | Art. 6(1)(a) + Art. 9(2)(a) |
| Progress reports and follow-up decisions | Record, in your health record, your own reports about the evolution of a tracked item (report text, keep/close decision, date, and version of the confirmed text), in an immutable trail, and send them to the AI as context marked as your report (see Section 6.9). Operates under the already-active consents (clinical_processing + ai_processing/intl_transfer) — it is not a new consent | Art. 7, I and Art. 11, I (same consent as the clinical core) | Art. 6(1)(a) + Art. 9(2)(a) |
Sensitive health journal (daily_journal) | Collect your daily sensitive self-observation records — alcohol (substance) and stress/what shaped the night (mental health) — as dated points that make up your time series (§3.2). Opt-in, off by default, blocked on the server until the consent exists, unavailable on minors' profiles. These records are not sent to the AI (see Section 6) | Art. 7, I and Art. 11, I (specific and prominent consent for sensitive data) | Art. 6(1)(a) + Art. 9(2)(a) (explicit consent for a special category) |
Pregnancy state (pregnancy-state-1.0) | Keep, only on your device (Keychain, outside iCloud and backups), the trimester you declare (adult female account holder), and send it transiently to the AI (Anthropic, USA) only when YOU trigger an analysis or the chat, to calibrate the reading of your labs by pregnancy/lactation ranges. On-device, never written to any table of ours nor to lifestyle_facts, not synced; expires ~40 weeks; erasable in one tap; unavailable to minors/managed profiles; never written as a condition/diagnosis (see §3.2 and Sections 6.10 and 9) | Art. 7, I and Art. 11, I (specific and prominent consent) + Art. 33 (international transfer) | Art. 6(1)(a) + Art. 9(2)(a) (explicit consent) + Art. 44–49 (transfer) |
Contraceptive state (contraceptive-state-1.0) | Keep, only on your device (Keychain, outside iCloud and backups), whether you use a contraceptive method and the type (hormonal/non-hormonal) you declare (adult female account holder), and send it transiently to the AI (Anthropic, USA) only when YOU trigger an analysis or the chat, to calibrate the reading of your labs by contraceptive-use ranges. On-device, never written to any table of ours nor to lifestyle_facts, not synced; expires ~24 months; erasable in one tap; unavailable to minors/managed profiles; never written as a condition/diagnosis (see §3.2 and Sections 6.10 and 9) | Art. 7, I and Art. 11, I (specific and prominent consent) + Art. 33 (international transfer) | Art. 6(1)(a) + Art. 9(2)(a) (explicit consent) + Art. 44–49 (transfer) |
Talk about my cycle in the chat (cycle_ai_chat) | Send your most recent cycle entries (a smaller window than the analysis one) to the chat assistant, when YOU ask, so it can answer questions about your cycle. Off by default and outside "Accept and continue"; not available to minors or managed profiles; never becomes a notification; the app still does not predict fertility/ovulation and does not diagnose. Turning it off stops sending on the next turn — nothing needs to be deleted, because no new data is stored because of this option (see the version 3.18 Changes) | Art. 7, I and Art. 11, I (specific and prominent consent) | Art. 6(1)(a) + Art. 9(2)(a) (explicit consent) |
| Food diary (Nutrition tab) | Store the meals, items and estimated nutrients that you log and review, the "day complete" mark, the personal goal that only you set and the "no numbers" mode; show the day's balance with the measured (Apple Health) or estimated expenditure (weight, height, age and sex already recorded). Adult account holder only; outside family sharing, the Manager and dependents (§3.2). Runs under the Clinical processing consent, requested prominently and revocable (Section 5) | Art. 7, I and Art. 11, I (consent of the clinical core) | Art. 6(1)(a) + Art. 9(2)(a) |
AI meal reading, by photo or by text description (food_photo_ai) | Send the photo — reduced, without location, with faces blurred and your own name, ID, email and phone covered when recognized on the device —, or the description/correction you type or dictate, to the AI (Anthropic, USA) only to estimate foods and portions, which you review before saving. Off by default and outside "Accept and continue"; also requires ai_processing and intl_transfer; we do not keep the text, and the protected copy of the photo is kept only with the saved meal, visible only to you (§3.2); Anthropic generally retains them for about 30 days, unless retention is required by law or for abuse prevention (§6.13) | Art. 7, I and Art. 11, I (specific and prominent consent) + Art. 33, VIII (international transfer with specific consent) | Art. 6(1)(a) + Art. 9(2)(a) + Art. 46(2)(c) (standard contractual clauses/IDTA) |
International transfer (intl_transfer) | Send the clinical content to Anthropic, in the United States, for the AI analysis (see Section 9). We do not send your name, tax ID, email or phone; in the documents you upload, the app tries to cover them before sending, and some may get through. It is requested in an acceptance of its own and is a condition of the service. | Art. 7, I; Art. 11, I; Art. 33 (international transfer) | Art. 6(1)(a) + Art. 9(2)(a); Art. 44–49 |
Family sharing (family_sharing) | You authorize a family member to read your health record, in a revocable way (see Section 7) | Art. 7, I and Art. 11, I (consent) | Art. 6(1)(a) + Art. 9(2)(a) |
| Data of minors in your care | Organize a dependent's health record | Art. 14 (best interest of the child/adolescent; consent of at least one parent or legal guardian) | Art. 8 + Art. 9(2)(a), exercised by the legal guardian |
Age attestation (age_attestation) | You declare you are 18+ — or of the age of majority of the country you enter, if higher; registration below that age is blocked and the attestation is recorded immutably, with the server's date/time | Art. 14 + Law 15.211/2025 (Digital ECA) | Art. 8 |
| Security, fraud prevention, and audit | Access logs, defense against attacks, compliance with legal record-keeping obligations | Art. 7, II (compliance with a legal obligation — Marco Civil, art. 15) and, when the record touches sensitive data, Art. 11, II, "a" and "g"; Art. 7, IX and Art. 10 (legitimate interest, limited) only for what is not sensitive data | Art. 6(1)(c) (legal obligation) and Art. 6(1)(f) (legitimate interest) |
| App notifications — delivery token | Store a technical delivery token (push/APNs) and send generic, no-health-data notices (e.g., "your analysis is ready"); operational consent via the iOS notification permission | Art. 7, IX (legitimate interest) | Art. 6(1)(f) (legitimate interest) |
| SENSITIVE-domain notices (optional — notices derived from a sensitive domain: mental health, cycle/reproductive, substance, medication adherence) | Decide when to send, or include a detail, from a sensitive domain of your data. These run under their own consent, off by default (see Section 12-A), never legitimate interest | Art. 11, I (specific, highlighted consent) | Art. 9(2)(a) (explicit consent) + Art. 6(1)(a) |
| Lock-screen detail (medication name and dose, vaccine detail, appointment detail, "time to leave") — off by default since version 3.25, each one turned on by you | Display, in the reminder for a service you already configured, the echo of what you yourself recorded — never the purpose, the drug class, the condition treated, the specialty, or the reason for the visit. Minor and managed profiles are excluded; set per device and never sent over push. Through 3.20 these ran under their own consent; in versions 3.21 to 3.24 they came on; since 3.25 they are off again and each one appears only when you turn it on — that choice is recorded as its own consent, revocable at any time, with immediate effect (see Section 12-A) | Art. 11, I (specific and prominent consent, collected when you turn each detail on) | Art. 9(2)(a) + Art. 6(1)(a) (explicit consent, collected when you turn each detail on). The location for "time to leave" also remains under the iOS permission |
| SERVICE reminders and summaries of your data (medication/dose, wellbeing check-in, weekly check-in, schedule eve, stock refill, suggested follow-up, come-back invitation after a stretch without using the app; and the summaries of your health data outside the especially sensitive domains — mental health, cycle/reproductive, substance and medication adherence: sleep, glucose and time in range, activity, a marker's evolution, the weekly/monthly summary, and the "Daily headline") | Deliver, on your device, a neutral (no health data in the text) reminder of the service you set up or a descriptive summary of your own data (never a diagnosis, judgment, cause, efficacy claim, or urgency). The numbers from your data in the notice body are off by default and appear only if you turn on "Numbers from your data in alerts"; the name of a test appears only if you turn on "Show the test name in the alert" — each recorded as its own consent. Without them, summaries arrive with a sentence that carries no number. The reminders are pre-enabled once you allow notifications on iOS and can be disabled per type/category in Profile › Notifications (see Section 12-A) | Health data (sensitive): Art. 11, I — within the Clinical processing consent, which includes sending to your device notices that start from your own data; the numbers and the test name in the notice, under their own consent (Art. 11, I). The delivery decision and the token follow Art. 7, V and IX | Art. 9(2)(a) + Art. 6(1)(a) for the health data and for the numbers and test name in the notice; the delivery decision and the token, Art. 6(1)(b)/(f) |
| An invitation to move (optional notice, on by default) | Decide, from your steps, exercise minutes and workouts, whether to send to your device a neutral invitation to take a walk, with none of your numbers in the text — on your device or, if you have not opened the app in 48 hours, as a push from our server (Section 12-A). Account holder only, on their own profile; never for minors, managed profiles or read-only access. Can be turned off in Profile › Notifications › "An invitation to move" | Art. 11, I (consent of the clinical core) | Art. 9(2)(a) + Art. 6(1)(a) |
| Technical telemetry / stability | Crash diagnostics, without health data, in internal processing (no analytics SDK or third-party tracking) | Art. 7, IX (legitimate interest), with self-limited minimization (Art. 6, III) | Art. 6(1)(f) (legitimate interest) |
| Usage and navigation events | Finding where the app stalls or confuses — screens opened, the step at which an upload stopped and that a meal, a complete day or a goal was logged (never the content) —, without health content, linked to the account, in internal processing | Art. 7, IX (legitimate interest), with objection in one tap (Art. 18, § 2) | Art. 6(1)(f) (legitimate interest), with the right to object (Art. 21) |
| Account, subscription, and packs | Maintain the account and process subscriptions and AI usage packs (measured in pages and prompts; AI meal readings are included in the plan, with a stated limit). A minor's AI consumption is charged to the guardian | Art. 7, V | Art. 6(1)(b) |
| Support and assistance | Receive and reply to the messages you send through the app's support channel (free text that may contain health data you include). AI-assisted drafting/translation of the reply runs only under the dedicated, unbundled "Share my support messages with AI assistance" consent (support_ai_share) — separate from the general AI Processing consent — together with International transfer (intl_transfer), with a human reviewing before sending (see Section 6.7) | Art. 7, V (performance of the contract) + Art. 11, I (consent for any health data you include, and the dedicated support_ai_share consent for AI-assisted drafting/translation); retention: the body of the messages in a closed support case is erased after 180 days (replaced by [removed]); the record of the support case remains as long as the account exists, and everything is erased when you delete your account | Art. 6(1)(b) + Art. 9(2)(a) |
| Pseudonymized research (opt-in at deletion) | Pseudonymized research cohort (only sex, age range, and year, in random cohorts, without profile_id, without free text, and without an exact date) that you may authorize at the moment of deleting your account (see Section 12) | Art. 11, I (specific consent, collected at the time of deletion) — BAS AI is not a research body (Art. 5, XVIII), so we do not invoke Art. 11, II, "c" or Art. 16, II; pseudonymized data, not irreversibly anonymous data | Art. 6(1)(a) + Art. 9(2)(a) (explicit consent); cf. Art. 9(2)(j) (research purposes) |
Legal basis of the clinical core — clarification. The primary basis for processing your health record is your specific and prominent consent (LGPD Art. 11, I / GDPR Art. 9(2)(a)), requested prominently, separate from accepting the Terms (Section 5), consistent with the "sovereign health record" positioning: you authorize, and you may revoke. We reserve a subsidiary basis only for what consent does not cover — information security, data integrity, compliance with a legal obligation, and the very operation of account deletion —, supported by LGPD Art. 11, II, "a", "d" and "g" and by GDPR Art. 6(1)(c) and (f). We do not adopt the health protection ground (LGPD Art. 11, II, "f" / GDPR Art. 9(2)(h)): under the GDPR, Art. 9(3) conditions this ground on the presence, in the flow, of a health professional bound by a duty of confidentiality, and there is no doctor in the loop of MyHealth.
Screenings by age — reference page. In Health › Education, the app shows a reference page with what Brazil's health authorities (the Ministry of Health and INCA, the National Cancer Institute) publish about screening tests, with the name of the body, the document, the date and a link to the official source. The page is the same for everyone: we do not use your age, your sex, your test results or your history to build it, and it generates no reminders and no notifications. It is reference content, not medical advice — whether and when to have a test is a decision for you and your doctor. When you tap "See the official source", your browser opens the body's website; none of your data is sent in that address. The age-based screening reminders that existed up to version 3.29 no longer exist, and the AI reading does not mention screening tests that do not appear in your record.
5. Consent and how to revoke it
When you authorize a sensitive purpose, that consent is:
- Free — you are not required to authorize the processing of your health data. The AI analysis is the service MyHealth offers: whoever prefers not to authorize does not use the app, and can sign out or delete the account on that very screen, with no insistence;
- Informed — we explain the purpose on the spot, in plain language;
- Specific and prominent — the clinical processing of your health record is requested prominently, separate from accepting the Terms, and is not pre-ticked: only your tap grants it, at sign-up and whenever we ask for a new acceptance; the AI analysis and the international transfer to the United States are two separate acceptances, each with its own text and its own tap, never pre-ticked, at sign-up, when we ask for a new acceptance and when an account turns the AI on;
- Condition of the service — clinical processing is necessary for the app to work (LGPD Art. 9, § 3): without it there is no health record to organize. You can revoke it at any time in Profile › Privacy. Since there is no health record without it, revoking it means deleting the account: before you confirm, the app explains clearly what will happen and offers to export your data; once you confirm, the account and the health record are deleted right away, as in Section 12.2 — for clinical processing there is no paused or read-only state (the read mode described further on in this item applies only to the AI analysis and the transfer). Only the data the law requires us to keep remains, for the minimum periods in Section 12.1 (the tax records of people who made a purchase, the access logs under Marco Civil art. 15, the minimum forensic index and the consent records). The AI analysis and the transfer to the United States are also a condition of the service (LGPD Art. 9, § 3): what MyHealth offers is the reading and organizing of your health record by AI. You can withdraw either one at any time in Profile › Privacy, as easily as you gave it. When you withdraw, nothing else is sent to the AI and your account goes into read mode: you keep viewing and exporting everything you organized, and stop logging, syncing and receiving analyses until you authorize again. We do not delete the account for this; deleting is always your decision. The optional authorizations (sensitive journal, cycle in the chat, meal reading, AI-assisted support and so on) can be withdrawn with no effect on the rest of the app.
Our system only executes an operation if the corresponding consent is active. For example: if you do not authorize "AI Processing", the app does not send anything to the AI — this check happens automatically, on the server (the has_active_consent function), on every operation. International transfer: it is an acceptance of its own. The server sends content to the AI only when both — AI analysis and transfer — are active; with either one missing, or revoked, nothing is sent.
How the record works: each authorization or revocation is recorded as an immutable event in our consent record (consent_events), with the purpose, the legal basis, the language, and the Policy version in effect. Revoking does not erase the consent history — it records a new event that halts future processing of that purpose.
Revocation does not make unlawful processing already lawfully carried out, but it halts the future use of that purpose. You do not lose access to the health record you had already organized: for the AI analysis and the transfer, it stays in read mode, as described above.
Sensitive health journal. The daily sensitive collection (alcohol, stress/what shaped the night) has its own consent (daily_journal), off by default: nothing is recorded until you turn it on, and the server blocks writes of these items without the consent active. You may withdraw at any time, just as easily, in Profile › Privacy & consents. When you withdraw: (1) we immediately stop collecting new records; and (2) we delete the alcohol/stress records already collected in those categories.
Hiding ≠ withdrawing. On the same screen as the consents there is a card called "What appears in the app" (§3.2), which hides from the screens the ring's stress, the menstrual cycle or mental health. It is a display preference: it does not withdraw consent, does not stop collection, does not delete data and does not change what the AI receives. To stop the processing, use the withdrawal described in this Section; to cut off the source, disconnect the wearable or remove the permission in Apple Health (Section 8). The two controls sit side by side on purpose — and the screen says, in those words, what each one does.
AI meal reading (photo or description). Meal reading has its own consent (food_photo_ai), off by default and outside "Accept and continue": while it is off, no meal photo or description leaves your device, and the button appears as an invitation, never as an error. You can turn it off at any time, with one tap, on the photo screen itself or in Profile › Privacy & consent. Turning it off stops photo and text readings. Meals already saved — and the photos kept with them — stay in your diary, visible only to you: they are what you reviewed and confirmed, and you can delete any meal (and its photos) whenever you want; they also leave our storage and the daily backup copy within about 2 hours. Text descriptions were never kept. Logging by hand keeps working without this consent.
Details and numbers in notifications. Each lock-screen detail (medication name and dose, vaccine detail, appointment detail, "time to leave"), the numbers from your data in summaries and the name of a test in a notice have their own switch, off by default, in Profile › Notifications. Turning one on records your consent for that use; turning it off revokes it, with immediate effect — notices already scheduled go back to being neutral (Section 12-A).
5.1 Accounts that already existed with the AI off
Until November 14, 2026 it was possible to use MyHealth with the AI off. For accounts created before that date that are in that state:
- Until January 13, 2027, nothing changes. You keep using the app as you do today, and nothing is sent to the AI. The app tells you about the change when it opens, at most once a week, and we also tell you by email.
- From January 13, 2027, the account stays in read mode until you authorize the AI analysis and the transfer: you view and export everything you stored; logging, syncing and receiving analyses are unavailable, and the collection of new data (including from Apple Health and wearables) stops.
- No account is deleted because of this change. You can export your data and delete the account at any time, in Profile › Privacy.
6. How Artificial Intelligence (AI) processes your data
AI is a central piece of MyHealth (assistant and extraction of data from documents), so we explain it with full transparency. Our AI provider is Anthropic, which acts as a subprocessor.
6.1 The AI receives the clinical content of your health record, without your direct identifiers
- The content sent to the AI is the user's own and is processed only upon your two acceptances — the AI analysis (
ai_processing) and the transfer to the United States (intl_transfer) —, which are a condition of the service (Section 5). - The clinical content we send to the AI, without sending your direct identifiers (name, tax ID, email, phone) — replaced by sex, age, and your year of birth (without day/month) and, when available, by your country (only to regionalize, in an educational way, emergency guidance and vaccination-calendar guidance — never the city or precise location) — and without your emergency contacts — may include: lab markers and trends, measurements and bioimpedance, medications, vaccines, allergies, symptoms, appointments and notes, family history, physical activity, sleep data and wearable scores, device events (ECG classification, irregular rhythm, fall, possible hypertension signs, low cardio fitness), menstrual cycle and reproductive data (including the menopause phase, when you provide it), lifestyle habits you provide (smoking and years of use, alcohol, activity, and sleep), the non-sensitive daily contexts in weekly aggregated form (coffee/caffeine, energy levels, hydration, and workout perception, as day counts, and the week's routine-change category — never the individual daily entry, never free text; see §3.2), the weekly averages of the complete days of your food diary (estimated calories, carbohydrates, protein, fat and fiber, and — when Apple Health does not have the day's value — estimated sodium, potassium, iron, calcium, magnesium, cholesterol, sugars and caffeine; never alcohol) and how many days of each week you completed — never a meal, a portion or the photo; your calorie goal, the weekly average time of the meals logged and the names of the foods that repeat the most go only to your chat, as described in Section 6.13; and the averages, only if you have accepted version 3.25 of this Policy or a later one (§3.2 and 6.13) —, the blood type and the observations from your emergency card, and the document itself (photo/PDF) when you request AI extraction — before sending, the app attempts to cover (redact), directly on your device, your name, tax ID, email, and phone number printed on the document, and you can cover areas manually; the original file remains intact in your health record and the version sent to the AI is the redacted one, when generated. This automatic redaction is best-effort: it may fail on low-quality photos or handwriting and is not a guarantee of complete removal. We do not send the contacts from your emergency card (name, phone, relationship). Free-text notes written by you or by professionals may, occasionally, contain names — which is why we recommend not entering identifying data in text fields. In the chat with the assistant, the context may additionally include the conversation history itself and the location and the professional recorded in your appointments — items that do not enter the longitudinal analysis of the health record.
- Web search exists in the assistant chat, for general clinical knowledge, and in meal reading, only when you tap "Search the web" for a packaged product whose nutrition table did not show (§6.13). In the chat, we instruct the model to use only generic clinical terms; for meals, only the product type and the brand — in both cases without your values, dates, age, names, or identifiers. This protection is applied by instructing the model and not by an infallible technical filter; the search is run by Anthropic's infrastructure. The health-record analysis and document-extraction functions do not perform web search.
Computed associations between readings from your device. For four pairs of readings that come from your watch, ring or phone — sleep and next-morning resting heart rate; steps and sleep; time in daylight and sleep; steps and next-morning heart-rate variability — our server checks, in your own data, whether the two readings tended to vary together over a period, by the same test the app already runs on your device in "Your patterns". When a pair passes the test, the AI analysis receives two means, the number of days and the period — never each day's values. The result is not stored: it is recomputed at each analysis and discarded. Readings you declare (coffee, alcohol, mood, symptoms, meals), the menstrual cycle and weight are not part of this; the chat does not receive this block; no notice derives from it. The reading describes what "tended to" happen in your data — it is not a cause, a prediction, a diagnosis or a target. Your authorization of AI analysis covers it; no new data is collected and there is no new recipient.
6.2 We DO NOT use your data to train AI
- Under Anthropic's commercial terms, your data (inputs and outputs) is not used to train or improve models and is retained for a limited period and then deleted (as a rule, within 30 days), except for retention required by law or to prevent abuse. This relationship is supported by a DPA + SCC (Modules 2/3, UK IDTA, Swiss addendum) in effect through Anthropic's Commercial Terms.
6.3 Technical safeguards
- Traffic with the AI uses an encrypted (TLS) connection.
- We apply safeguards against prompt injection and minimization of the content sent.
- The AI does not make automated decisions about you within the meaning of GDPR Art. 22 / LGPD Art. 20: it organizes and describes, it does not decide, diagnose, or prescribe. A document's extraction is saved only after you review it; the educational reading and the points of attention are generated automatically, have no legal effect and come marked as content to confirm with your doctor — and you can request a review of any reading (Section 15).
- The AI does not detect, monitor, or diagnose the risk of suicide, self-harm, or psychiatric crisis, and does not alert anyone on your behalf. If you are in crisis, seek immediate help (in Brazil, CVV 188, 24h, free; outside Brazil, the national prevention line). See Section 3.5 of the Terms of Use.
6.4 Open standards and vocabularies (LOINC® / UCUM)
So that the same test coming from different laboratories (with different names, abbreviations, and languages) is recognized as a single parameter and produces a coherent timeline, MyHealth normalizes markers using the open vocabulary LOINC® (Logical Observation Identifiers Names and Codes) and standardizes units of measure based on UCUM. These standards are licensed reference content embedded in the app — they work like a dictionary and receive none of your personal data (Regenstrief Institute is not a sub-processor and nothing from your record is sent to it).
This product includes content from LOINC® (loinc.org). LOINC is copyright © 1995–2024, Regenstrief Institute, Inc. and the LOINC Committee, and is available at no cost under the LOINC license (loinc.org/license). LOINC® is a registered trademark of Regenstrief Institute, Inc.
6.5 Organizing medications and supplements (derived data, AI-assisted)
To organize your record, the AI may produce, from the medications and supplements you log, a derived organizational datum: the decomposed active ingredients (a compounded formula is split into its label ingredients) and a general category; the canonical vaccine, the disease prevented, and the dose in the series (consolidating the same vaccine under different names); and the normalized allergen and its class. This datum is generated from what you already provided (we collect nothing new from you) — both from items read from a document and from those you type by hand (in that case we send the AI only the item's name and dose, under the conditions of Sections 6.1–6.3 and only with AI analysis authorized). It serves to show, on the item's page, the substance identified and the lab results in your own record linked to it — only the ones you already have, with the value and date as they are in the report. The app does not assess that value in relation to the item, does not suggest tests you do not have, and does not explain what the medication is for; for that, read the package leaflet and ask your doctor. It is educational and AI-assisted — you can review and correct it, and it is not a clinical classification, a prescription, or interaction checking (see the Medical Notice, item 5.2). AI processing details follow Sections 6.1–6.3.
6.6 Document awaiting available quota/usage
When billing is active and you do not have enough available quota or usage at the moment of upload, a document already redacted (after the on-device redaction described in 6.1) may be stored, without analysis, until subscription quota or an add-on pack becomes available — and is then analyzed automatically. The document waits in your own health record, under the same security and access protections as your account; nothing is sent to the AI while the AI Processing consent (ai_processing) is not active and there is no available usage.
6.7 AI-assisted support
When you contact our support and an agent uses AI assistance to draft or translate the reply, the text of your support conversation — which may contain health data you write — may be sent to our AI provider (Anthropic (Claude), United States) only to prepare a draft reply or translate it, which a human agent always reviews before it is sent. The support AI never receives your health record (prontuário) — only the text of your support message.
For logged-in users (in-app support, Profile › Support). This happens only when you grant a new, dedicated consent — "Share my support messages with AI assistance" (support_ai_share), which is separate from, and additional to, the general AI Processing consent (ai_processing): it has its own request, is off by default, and can be refused or withdrawn on its own without affecting anything else — the paid product works fully if you decline. AI-assisted support runs only while both this consent and your International transfer (intl_transfer) consent are active; if either is off, an agent replies without any AI. Before your support text is sent, the app makes a best-effort attempt to minimize identifiers in it — this is not de-identification and not a guarantee of complete removal, so please still avoid including unnecessary data (name, ID document, contacts) in your support messages.
For people who write to support without a MyHealth account (external senders). We do not send your message to AI without your own consent. When you email support, you first receive an email asking for two separate consents: (1) to process your message to prepare a reply, and (2) to transfer it to Anthropic (Claude), in the United States — with a link to our Consumer Health Data Privacy Policy. Only after you grant both does the AI draft or translate a reply for your ticket, which a human reviews before it is sent. If you do not consent, a human replies to you with no AI involved.
Safeguards. The transfer to Anthropic (United States) is covered by our existing Data Processing Agreement and EU Standard Contractual Clauses (SCC) with Anthropic — the same terms that govern record analysis, document extraction, and chat, and that apply to all data we submit to Anthropic's API. Contractual non-training applies. Retention follows Anthropic's own contractual limit (as a rule about 30 days, subject to legal or abuse-prevention exceptions) — this is Anthropic's limit, not a deletion date we guarantee. This adds no new subprocessor: Anthropic is already listed in Section 9.
6.8 Stress and the AI: what goes and what doesn't
The Sensitive Health Journal is NOT sent to the artificial intelligence. Your alcohol and stress/what-shaped-the-night records (the Diary's own consent) stay on your device and in your health record and are not part of the context sent to our AI provider (Anthropic, United States). Any future use of these records by the AI would require a separate, explicit consent ("include my daily records in the AI analysis"), which does not exist in this version. This differs from the non-sensitive daily contexts (coffee/caffeine, energy levels, hydration, workout perception, and routine changes), which are part of the AI context only in weekly aggregated form — day counts and the routine-change category — as described in §3.2.
Your ring's stress index is also NOT sent to the AI. Oura's stress score is excluded in the database query itself, in both the health-record analysis and the chat (a single exclusion list serves both surfaces), and the exclusion also reaches the stress sub-score embedded in Oura's resilience "contributors" — the barrier does not depend on the AI obeying an instruction. It also does not enter the PDF Health Report (§3.2). The same applies to Apple Health's GAD-7/PHQ-9 questionnaires.
What IS sent: the well-being check-in's "stress" axis, as a weekly average. The "How are you today?" check-in — which you answer on three levels, across the energy, mood, stress and (only without wearable sleep) sleep axes — is part of the analysis context under the Clinical processing, AI processing and International transfer consents, only as a weekly average per axis, so that the educational reading can cross how you feel with your sleep, your activity and your lab results. It goes descriptive, with a hard instruction to the model: never a diagnosis of anxiety, depression or a "stress disorder", never a clinical instrument, never treatment advice. Up to version 3.13 this section did not say this — it said only that "point-in-time stress" stayed out of the AI, text that predates the check-in's axes. This is the correct description, and it is one of the reasons for the re-acceptance in version 3.14.
All of this is also different from the non-sensitive daily contexts (coffee/caffeine, energy, hydration, workout perception and routine changes), which go into the AI context only aggregated by week — day counts and the routine-change category —, as described in §3.2.
6.9 Progress reports and follow-up decisions
When you record the evolution of a tracked item as your own report (Terms, Section 9.7), we store in your health record the report text, the decision (keep or close follow-up), the date, and the version of the text you confirmed, in an immutable trail (correcting = a new entry). These reports become part of the context sent to the AI explicitly marked as a patient report — the AI is instructed to treat them as a report ("you reported that…"), never as a documented clinical fact, and it is technically prevented (server-side validation, not just an instruction) from closing or superseding an item based on a report without your express decision. All of this operates under the already-active Clinical Processing, AI Processing, and International Transfer consents; the copy sent to the AI follows the same identifier-redaction pipeline as the rest of your record.
Minimization: to record a report, professionals' names are optional — the report works equally well without identifying who made the assessment; we recommend including only what is necessary.
Export and deletion: reports and decisions are part of your health record — they are included in the export and erased upon account deletion, through the same dual-track process of Section 12.
Minors: on minors' profiles, entries are made by the legal guardian, in representation, and the entry identifies the guardian who made it; relevant closures are communicated to the other guardians linked to the profile.
6.10 Pregnancy and contraceptive state (transient, never recorded by the AI)
When you keep the pregnancy state on (§3.2) and trigger an analysis or the chat, the trimester you declared is attached to the body of that request, in memory, only so the AI can calibrate the reading of your labs by the reference ranges specific to pregnancy and lactation. It is not persisted by us in any table, and the AI is instructed — with deterministic server-side output filtering as a backstop (with a regression test) — to never record "pregnant", "expecting", or "breastfeeding" as a condition, alert, problem-list item, summary, or diagnosis in your health record. Automatic/proactive analyses and the large-record (batch) path do not receive this state — it accompanies only the analysis you start. The transfer to Anthropic (United States) is governed by the DPA/SCC already in effect (Section 9), under the pregnancy-state-1.0 consent (which covers the international transfer), and Anthropic retains the request for its own contractual limit (as a rule ~30 days — Section 6.2); we do not store this state.
The contraceptive state (§3.2), when you keep it on, follows the same transient design: it stays only on your device (Keychain, expires in ~24 months) and is attached to the request body, in memory, only when you trigger an analysis or the chat, under the contraceptive-state-1.0 consent (which covers the international transfer). It is not persisted by us in any table, does not go to automatic/proactive analyses nor to the large-record path, and the AI is instructed to never write it as a condition, alert, or diagnosis in your health record. The lactation / postpartum state is the "postpartum" stage of the pregnancy state, under the same treatment above.
6.11 Care team in the analysis context
If you add professionals to your Care Team (for example, the doctor who already follows you), those professionals' name and specialty — and, when you provide them, the institution and the reason for the follow-up — become part of the context we send to the AI when it analyzes your health record, so that the educational guidance can point to the professional you already registered (for example, "worth taking this to your cardiologist already on file") instead of a generic suggestion. We never send the professional's contact details (phone, email, or address) or registration number to the AI; those fields stay only in your record. This is the same handling that already happens when you chat with the AI. The legal basis and international transfer are the same as for the rest of the AI processing described in this section.
6.12 AI-generated educational library (generic, population-level content)
Beyond the personalized reading, the app shows a library of educational content about markers, measurements, and conditions (for example, "what ferritin is" or "what a value above the range usually means"). This content may be generated by AI — by the same provider (Anthropic) and with the same provenance as Sections 6.1–6.3 — but in a generic, population-level way: each text is produced once per topic and language and is the same for every user of that topic. The generation receives no data of yours: the AI receives only the abstract coordinate of the topic (the marker/measurement/condition name from our catalog and generic direction, range, and population-group categories) — never your value, your result, your dates, or any identifier. Personalization happens only in the selection: the app uses your data, on your device, solely to choose which generic texts from the library are relevant to show you. The content itself is not an individual analysis of your case — it is population-level educational material, available regardless of the AI Processing consent (which governs the personalized reading), and subject to the same non-diagnosis rule as the rest of the app (see the Medical Notice).
6.13 AI meal reading (photo or description)
What goes, what for and for how long. Only with the food_photo_ai consent ("Read meals with AI (photo or description)") turned on (§3.2 and Section 5), and only when you take or choose the photo or write (or dictate) the description, we send to our AI provider (Anthropic, United States — Section 9): in a photo reading, only the reduced, protected copy of the photo (without location, faces blurred and your own name, ID, email and phone covered when the device recognizes them; other text, including other people's data, is not covered — best-effort), the meal of the day you chose (breakfast, lunch, snack or dinner) and the language of the reply; in a description reading, the text you wrote or dictated, with the meal of the day and the language; in a correction, the text of the correction and the list of items in the proposal — or, if a packaged product's nutrition table did not show, a photo of the table that you take (with the same protection) or your "Search the web" request: the AI then looks up the official table using only the product type and the brand (Section 6.1). Never your account identifiers, never any other data from your health record. The purpose is one only: to estimate which foods, in which portions and the approximate calories and nutrients (including sodium, sugars and caffeine when they can be estimated, and the alcohol of an alcoholic drink only if your Sensitive health journal consent is on — without it, the alcohol estimate does not even leave our server), so that you can review, correct and only then save. Anthropic does not receive the photo again after the reading; we keep the protected copy only with the meal you save, visible only to you (§3.2); the text is not kept. Anthropic does not use them to train models and generally retains them for about 30 days, unless retention is required by law or for abuse prevention — a period that is Anthropic's, not a deletion guaranteed by us (Section 6.2). There is no new subprocessor for this feature. Basis of the transfer: Brazil — specific consent (LGPD art. 33, VIII); you can request a copy of the safeguards from the DPO. Turning the consent off stops photo and text readings.
More than one photo, a note and the AI's question (since version 3.27). A photo reading may gather up to four photos of the same meal (another angle, the food cut open, the package label) and a short note you type or dictate ("Anything the photo doesn't show?"); all of it goes together to the provider, only to estimate foods and portions, under the same consent. We keep with the meal you save only the main photo; the other photos and the note are not stored by us (the provider retains them for the period described above). When something that changes the estimate cannot be seen — the filling, the kind of milk —, the AI may ask one question, with a few ready answers, only about the food, its preparation or the quantity; the answer you tap is sent as one of that reading's corrections. Answering is optional.
Your food diary and the AI. The health-record analysis and the chat receive from the diary weekly averages of the complete days (Section 6.1), including that of saturated fat, and read them as estimates. Only the chat — your conversation with the AI, which always stays with you only (Section 7) — also receives: the calorie goal you set yourself; the average time, per week, at which the first and the last meal of the day were logged — never the times of a single day, and only for weeks with at least three complete days; and the names of the ten foods that repeated the most in the last 28 days, with how many times each appeared. The health-record analysis does not receive the goal, the times or the food names, because its text can be read by whoever you allow to see your health record; for the same reason, they are not included in a question asked from a card in the app, whose answer is kept with the card. A meal, a portion, the photo or a single day never go, to the analysis or to the chat. In the chat, the AI uses this data as context: it does not judge or propose a goal, does not suggest when to eat and does not classify foods. The saturated-fat average, the goal, the times and the food names are sent only for people who have accepted version 3.26 of this Policy or a later one; the other averages, for people who accepted 3.25 or later. Logging a meal does not trigger a new analysis. If you share your health record, whoever has access sees neither the diary nor your chat, but can read the analysis, which may cite the averages.
What the AI is instructed not to do here. The AI is instructed not to build a meal plan, not to tell you what you "should" eat, not to promise weight loss, not to suggest an insulin dose from carbohydrates and not to identify or diagnose an eating disorder — even so, it can make mistakes. The estimates are approximate and the readings are educational and descriptive (Section 16).
7. Family sharing (opt-in, read-only, revocable)
MyHealth lets you share your health record with a family member, in a controlled way:
- It is opt-in: nothing is shared unless you initiate and authorize it (
family_sharing). - Access is read-only and to the entire health record (all or nothing — it is not possible to share only parts), except what always stays with you only: the ECG trace, your Oura ring's annotation codes, the food diary of the Nutrition tab (§3.2), the AI readings you have not yet reviewed and saved, and your conversations with the AI (the chat): the family member can view, but cannot edit or delete.
- The link is created by a single-use invitation code, which expires in 7 days if not used.
- You can revoke the link at any time, ending the access.
The family member must also be a user of the app. This sharing is between you and the person you choose — it is not sharing with third parties or for commercial purposes.
7.1 Item-by-item sharing of hereditary conditions
In addition to the read-only link above, you may choose, item by item, to offer health conditions tracked in your record (for example, a diagnosis and its year of onset) to linked family members, so they can add them to their own family history. How it works:
- Double authorization: the item is only offered if you enable it, and it is only incorporated if your family member expressly accepts it, item by item (never in bulk).
- Minimization locked in code: only the condition, the period (year of onset), and the status are transmitted — never exams, documents, values, medications, free text, attachments, or routine. The database rejects any content beyond these fields.
- Permanence notice: at the moment you enable each item, we show the named item, who can receive it, and the notice that, if you deactivate it later, what a family member has already accepted remains in their record. We log your consent (who, when, and the version of the text displayed).
- Permanence rule (ex nunc revocation): revocation takes effect from that moment on and does not affect incorporations already accepted by your family members, which become health data of their respective subjects (family history) — as if they had noted it from memory. Deactivation immediately removes the offer for all linked family members, in one tap, free of charge and with no justification required.
- Deletion by the recipient: the family member may delete the incorporated item at any time, and it is included in the family member's own data export and erasure.
- De-identification upon the source's erasure: if the source requests erasure of their data or deletes their account, we remove from the family member's record every reference to the source's identity and account, keeping only the degree of kinship, condition, and period (LGPD art. 18, VI; GDPR art. 17).
- Minors: minors' profiles do not participate as a source by their own decision; the management of minors' data follows the legal-guardian mechanism.
Legal basis: processing based on your specific, highlighted consent (LGPD art. 11, I; GDPR art. 9(2)(a)) and, where applicable, upon a valid authorization under the My Health My Data Act (Washington/USA). The incorporated item is treated as sensitive data of the recipient themselves throughout the pipeline (including AI, export, and erasure), under the recipient's own active consents.
7.2 Manager authorized by you (delegation by an adult)
Upon your specific, highlighted consent (LGPD art. 7, I and art. 11, I; GDPR art. 9(2)(a); for Washington/USA residents, the separate consent required by the MHMDA), an adult you designate (the "Manager") may access and record data in your health record. How this processing works:
- Consent on your device, with reinforced identity: the authorization can only be granted by you, on your device, after reinforced identity confirmation; we log who consented, when, and the version of the text displayed.
- Legal basis: your consent, revocable at any time with immediate effect, in one tap, free of charge and without justification; the Manager only learns that the link changed, never the reason. 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).
- Strictly personal acts technically blocked: the Manager cannot change your consents, delete your account, create/change/remove sharing or links, change your credentials, make purchases on your behalf, or bulk-export your record — the block on consents, account deletion, links, and credentials is enforced server-side (database access rules); the block on purchases and bulk export is enforced technically in the app.
- Audit trail: we keep an immutable authorship record of everything the Manager creates or edits in your record and show it to you, plus an in-app summary of their activity, which the Manager cannot turn off. These records are retained for the same period as the health record.
- Ownership: what the Manager records is your data and remains in your record after revocation, under your consents and rights (access, export, erasure).
- Food diary outside management: the Manager does not see or log meals, goals or the "day complete" mark in your diary — it is yours only (§3.2).
- Chat outside management: the Manager does not see your conversations with the AI or chat with the AI on your profile — the chat is yours only.
- Minors: minors' profiles cannot appoint a Manager; the management of minors' data follows exclusively the legal-guardian mechanism.
8. Apple Health (HealthKit)
MyHealth lets you import measurements from Apple Health (HealthKit) — weight, height, body composition, blood glucose, blood pressure, heart rate, saturation, and temperature, plus day-to-day metrics when your device offers them, such as active energy and resting energy (added together, they make up the day's total expenditure — resting energy is not stored separately), sleep breathing disturbances, time in daylight, and mindfulness sessions — and, when you authorize them in the iOS permissions, also menstrual cycle and reproductive health data (menstrual flow, intermenstrual bleeding, ovulation tests, cervical mucus quality) into your health record. We do not import sexual activity records.
Continuous glucose monitor (CGM) glucose — daily aggregates only. When importing glucose from Apple Health, days with a continuous glucose monitor (hundreds of readings) are summarized on your own device and stored only as daily aggregates — mean, minimum, maximum, variability (CV), and the percentage of the day within the 70–180 mg/dL range of the industry display standard (AGP); the raw continuous readings are never stored by us. Spot measurements (capillary/manual) continue to be stored as normal measurements, with date and time (see §3.2).
Cycle patterns (its own opt-in, off by default). If you turn it on in Profile › Privacy, the app can show your logged cycle days alongside your charts (sleep, heart) and observe local, descriptive patterns (for example, how your sleep behaves on logged menstruation days). It is a composition, on your device, of data you already see: none of it becomes a notification, nothing is sent to the AI beyond what you already authorized, and the app never calculates or predicts fertility/ovulation. Unavailable on dependents' profiles; revocable at any time (the pattern simply stops being shown).
Medication adherence (iOS 26 or later). See the summary in §3.2 — the app can import, from Apple Health, medication doses marked as taken, matched to a medication you have already registered; it is adherence memory for you, never surveillance, and never generates a missed- or forgotten-dose notification.
Clinical Records (United States and Canada). See the summary in §3.2 — the read-only import of your structured clinical records (lab results, immunizations, medications, conditions, procedures, and allergies) via FHIR is available for accounts in the United States and in Canada and only takes place with your authorization on Apple Health's permission sheet; outside those countries, the feature does not appear in the app.
- The import is optional and happens only with your explicit authorization, granted in the iOS permissions. Access is read-only — MyHealth does not write data to Apple Health.
- Data coming from Apple Health is used exclusively to enrich your own health record within the app.
- In compliance with Apple App Store Guideline 5.1.3, Apple Health data is NEVER used for marketing/advertising, is NEVER shared with third parties for advertising purposes or data mining, and is NEVER used to train AI models.
Connecting smart bands and rings (Oura and WHOOP)
In addition to Apple Health, you may, optionally and revocably, connect third-party wearables, with specific consent per provider (wearable_sync_oura, wearable_sync_whoop):
- Oura Ring: sleep and sleep stages, daily scores (sleep, readiness, activity, stress, resilience), temperature deviation, steps, calories, distance, sedentary time, SpO2, sleep breathing disturbance index, VO2max, cardiovascular age, workouts and meditation sessions, and the annotations you record in the Oura app (enhanced tags): the free text (custom name, comment) is discarded on import — we do not store it; we keep only the standardized category code, which — aggregated by week, never as free text — may enter the AI context when you keep the Health Diary (
daily_journal) active, is visible only to you, and is deleted on disconnect (see Section 3.2). For annotations, Oura requires an additional permission ("tag" scope): connections made before this version will only start syncing them after you reconnect Oura. The stress and resilience scores are categorical (a label for the day, not a number): we show you the label published by Oura, with the date it refers to, in the "Today's readiness" card on Routine — no calculation, no severity color and no ordering of ours —, and stress can be hidden from the screen in Profile › Privacy & consents ("What appears in the app", §3.2), without that disconnecting Oura or interrupting the sync. The stress score is never sent to the AI and never enters the PDF (Section 6.8). - WHOOP: recovery score, resting heart rate, heart rate variability (HRV), SpO2, skin temperature, strain, sleep, and workouts.
The authorization uses OAuth: the access tokens are encrypted (AES-256-GCM) on our server and are not accessible by the app. Oura operates in Finland (European Economic Area) and WHOOP in the United States; connecting these services involves an inbound international transfer, under the safeguards in Section 9.1. Oura and WHOOP act as data sources (independent controllers of their own platforms), not as our subprocessors, and do not receive data from your health record.
When you disconnect a wearable:
- WHOOP: to comply with the WHOOP API's terms of use and as a matter of the privacy standard we adopt, we request the revocation of access at WHOOP and permanently delete all data originating from WHOOP already synced (sleep, scores, measurements, activities, and events). We recommend exporting beforehand if you want to keep a copy.
- Oura / Apple Health: we revoke access and delete the encrypted tokens we hold. Data already synced remains in your health record, unless you request its deletion. Exception: Oura free-text annotations are always deleted when you disconnect, even if you choose to keep the other already-synced data.
Data imported from wearables and from Apple Health is always recorded in your own health record (account holder) and never in a dependent's profile, even if you are viewing a minor's profile.
9. Subprocessors and international transfers
We do not sell your data. To operate the service, we use a minimal set of vendors ("subprocessors"/"processors"), which process data only under our instructions, with confidentiality and security. Supabase (signed 2026-06-18), Anthropic (via Commercial Terms, 2026-06-17) and Resend (via EU-US DPF + SCC, 2026-06-17) have DPAs/SCCs in effect; for the others, the contract status is in their own row of the table.
| Subprocessor | What it does | What data it processes | Where | Safeguards |
|---|---|---|---|---|
| Supabase | Database (PostgreSQL), authentication, document storage, and edge functions | Pseudonymized clinical data; encrypted PII in the vault; encrypted documents; account metadata | São Paulo, Brazil (sa-east-1) | DPA in effect (signed 2026-06-18; Supabase Pte. Ltd) — includes EU SCCs + transfer safeguards (UK/Switzerland); SOC 2 Type 2 + ISO 27001 (Supabase provider certifications); daily database backups, on a short cycle set by Supabase (Section 12.2); 28-day log retention; encryption in transit (TLS) and at rest; additional field encryption under our key management; isolation via RLS; SCC for any transfers outside the EEA |
| Anthropic, PBC | Anthropic's AI models for health-record analysis, document extraction, chat, and generation of the generic educational library (for the latter, it receives only the abstract topic coordinate — never data of yours; see Section 6.12) | Pseudonymized clinical content (values, dates, notes, lifestyle habits, cycle, wearable aggregates — for continuous glucose monitoring, only the daily aggregates, never the raw readings —, the name and specialty (and, if provided, the 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 and never sent, and only their standardized category code — never free text, aggregated by week — may be sent when you keep the Health Diary (daily_journal) on — see §3.2) plus sex, age, country, and year of birth (without day/month) — without direct identifiers and without emergency contacts — and, in document analysis, the redacted copy of the image/PDF (best-effort on-device redaction of printed identifiers, when located) — transiently; if you turn on AI meal reading (food_photo_ai), the reduced, protected copy of the meal photo or the description/correction you type or dictate, only to estimate foods and portions (§6.13); and, when an agent uses AI-assisted drafting in support, the text of your support conversation (never the health record); and, when YOU trigger an analysis or the chat with the pregnancy state on, the self-declared trimester (enum) you consented to (pregnancy-state-1.0) — and, likewise, the self-declared contraceptive state (enum) you consented to (contraceptive-state-1.0), when on — transiently, only in the request body, never stored by us (§3.2 and 6.10) | United States (international transfer) | DPA in effect (via Anthropic's Commercial Terms, 2026-06-17) + SCC; contractual non-training; limited retention (~30 days); TLS |
| Resend | Sending transactional emails (access code/OTP and account notices) | Only your email address and the email body; no PHI / no health content | US / global | DPA in effect (2026-06-17) via EU-US DPF + SCC; TLS. For those who choose "Hide My Email" in Sign in with Apple, transactional emails are delivered through Apple's private relay (@privaterelay.appleid.com) and we do not see your real email |
| Vercel Inc. | Hosts the internal operations console, used only by authorized operators with two-step verification | Email and display name looked up during support, account metadata and the text of support messages; never the structured health record (the console only sees aggregated indicators of it) | Processing in São Paulo, Brazil (region gru1); a United States company | DPA being formalized; TLS |
| Google LLC (Google Workspace) | Support and DPO mailboxes (support@bas-ai.com and dpo@bas-ai.com): e-mails sent to support are received in our Google Workspace mailbox and copied into our support system (Supabase) | Your email address and the content of the e-mails you send us, which may contain health data if you write it | Google infrastructure, in the data region Google sets for the service | DPA being formalized; TLS |
| Apple (App Store / In-App Purchase / HealthKit / push) | Distribution, HealthKit, notifications, and payment processing for subscriptions and add-on packs as merchant of record | Purchase/receipt data; we do not receive your card data; no health content in the payment flow | US / global | App Store Terms; Guideline 5.1.3 |
Oura and WHOOP do not appear in this table: they are data sources that you connect (Section 8), acting as independent controllers of their own platforms, and not as our subprocessors. Apple acts as an independent controller for distribution, HealthKit, push, and payments. The DPAs and Standard Contractual Clauses (SCC) of Supabase, Anthropic and Resend are in effect; those of Vercel and Google are being formalized, as indicated in the "Safeguards" column. We maintain a public subprocessors page kept up to date at https://www.bas-ai.com/myhealth/legal/subprocessadores. We will give notice before adding a relevant new subprocessor.
9.1 International transfers
Your health record is stored in Brazil (São Paulo) — that is the rule. Transfers outside Brazil occur in a limited way and with your authorization (intl_transfer): in AI processing (Anthropic, United States — Section 6), in which we send the clinical content without your direct identifiers (in document extraction, the file itself — after a best-effort on-device automatic redaction that attempts to cover name, tax ID, email, and phone; identifiers not located may remain in the file; and, if you turn it on, a meal's photo or description, as described in §6.13); in the connection of wearables (Oura, in Finland/EEA; WHOOP, in the United States — Section 8); in sending transactional e-mails (Resend, United States); in the e-mails you send to support or the DPO (Google Workspace); in the internal operations console (Vercel, a United States company, with processing in São Paulo); and in distribution by Apple (United States). The United States has no adequacy decision from the Brazilian data protection authority: the protection of the content sent comes from the contract with Anthropic and from your own acceptance, and the risk is that the law there may not offer the same guarantees as the law of your country. When there is an international transfer, we adopt the required safeguards:
- LGPD (Art. 33): the transfer to Anthropic (USA) for AI processing rests on your specific and prominent consent, given in an acceptance of its own and separate from the other purposes (Art. 33, VIII — the
intl_transferpurpose); sending your e-mail to Resend (USA) for the account's transactional e-mails rests on Art. 33, IX, together with Art. 7, V (performance of the contract). The European Union Standard Contractual Clauses in our contracts apply to the GDPR and do not replace the standard clauses approved by the ANPD (Resolution CD/ANPD No. 19/2024), which we have not yet adopted. - GDPR (Art. 44–49): Standard Contractual Clauses (SCC) and/or other adequate guarantees for transfers outside the EEA, with a transfer impact assessment where applicable.
We may also disclose data when required by law (court order or competent authority), always limited to what is strictly necessary and, where legally permitted, notifying you.
9.2 Residents outside Brazil (including Asia-Pacific)
If you do not live in Brazil, storing your health record in São Paulo is itself an international transfer from your country. For each recipient: Supabase — Brazil, storage and operation of the app, continuously, for as long as the account exists; Anthropic — United States, AI, at each analysis, extraction, chat or meal reading, over an encrypted connection (TLS), with retention by Anthropic generally of about 30 days; Resend — United States, the account's transactional e-mails; Google Workspace — e-mails you send us; Vercel — internal operations console, with processing in São Paulo; Oura (Finland) and WHOOP (United States) — only as sources you connect (Section 8). Summary of the systems: in Brazil, the LGPD (Law 13.709/2018), enforced by the ANPD; in the United States, there is no general federal data protection law, and there are state laws (for example, California's and Washington's). On request to the DPO, we tell you the contractual measures adopted with each recipient.
- Japan: Brazil and the United States are not recognized by the PPC as having a level of protection equivalent to Japan's.
- South Korea: you can refuse the transfer to Anthropic by withdrawing, in Profile › Privacy, the acceptance of the International transfer or that of the AI analysis; without it, nothing else is sent to the AI and your account goes into read mode (Section 5). Storage in Brazil is a condition of the service.
- Countries that require local storage: if your country's law requires personal or health data to be stored in it, please note that your data is stored in Brazil and that we do not offer local storage.
10. Information security
The confidentiality of your health data is our number one control. The main measures:
- Separation between identity and clinical data: who you are (name, email, phone, document) stays in an encrypted vault (
identity_vault) with authenticated (AEAD), deterministic field-level encryption (pgsodium, AES-256), separated from the clinical tables, which refer to you only by a code. - Controlled decryption: PII is decrypted only by a secure function, under your own identity, with an audit record.
- Encryption at rest and in transit: encrypted database and storage; communications over TLS.
- Row-level access control (RLS) per verb: the database ensures that only you (or an authorized guardian/family member) access your data — and, for the ECG trace and the food diary, only you — and the read and write permissions are separated.
- Two-factor authentication (MFA/2FA via TOTP): available to strengthen access to your account.
- Versioned consents and an immutable audit record (access metadata only, never the clinical content).
- AI safeguards: removal of the direct identifiers (name, tax ID, email, phone) from the context sent, non-sending of the emergency card's contacts, content minimization, and protection against prompt injection.
External environment: we process data in Brazil (storage — LGPD) and in the United States (AI and e-mail — no general federal data protection law, with state laws); we assess those systems before transferring (Section 9.2).
We seek alignment with the best international practices for health information security. No system is 100% immune; that is why we maintain incident response plans (see Section 14).
11. Data of children and adolescents (minors)
The protection of children and adolescents follows the Statute of the Child and Adolescent (Law 8.069/1990), Law 15.211/2025 (Digital ECA), Art. 14 of the LGPD, and Art. 8 of the GDPR (EEA).
- Self-registration is intended for people 18 or older — and, in countries where the age of majority is above 18 (for example, South Korea, 19), for people who have reached the age of majority of the country you enter at sign-up. The app checks that age when you choose the country.
- The minor has no account or email of their own: they exist only as a managed profile within an adult guardian's account (the
managed_byfield), who declares this condition. - The profile may have more than one guardian: the primary guardian invites another adult by an invitation code with an expiration date. Each invitee receives a role: guardian (views and edits) or companion (read-only). Every authorization is verified on the server, on each operation.
- The consent relating to the minor is recorded identifying which adult granted it, observing the best interest of the child and adolescent (LGPD Art. 14).
- Paid AI features require the guardian role and are charged to the primary guardian (the profile's paying holder), regardless of which guardian triggered them; the usage record remains linked to the minor's profile for audit purposes.
- We apply the same maximum protection to this data (identity vault, RLS, AI non-training). We do not target advertising to minors. Wearable data never follows a minor's profile.
- The guardian may, at any time, export the dependent's data and, as the primary guardian, permanently delete the dependent's profile and all associated data (exams, documents, and records) — this deletion is permanent.
This age requirement refers to account ownership and is not to be confused with the GDPR's age of autonomous digital consent (Art. 8, between 13 and 16 years old depending on the country). Below that age, data processing only occurs through a profile managed by an adult guardian.
Users in the United States (COPPA): MyHealth is not directed to children, does not offer accounts to minors and does not collect data directly from children. A minor's profile is created and filled in exclusively by the adult guardian, the account holder, who consents to the processing when creating the profile and can export or delete it at any time.
Data provided by someone else. When data is provided by another person (for example, the guardian who registers a dependent), this Policy is the notice to the person that data is about.
Sensitive journal unavailable to minors. The daily sensitive collection (alcohol, stress) is not performed on minors' profiles or on profiles managed by a guardian — blocked on the client and on the server. It is a feature exclusive to adult account holders (18+). Under no circumstances do we collect alcohol/stress records from minors.
Food diary unavailable to minors. The Nutrition tab (food diary, personal goal and meal photo) does not exist on minors' profiles or on managed profiles: it is a feature exclusive to the adult account holder, with the barrier enforced in the database. We do not record meals, goals or meal photos of minors.
12. Retention and disposal
We adopt the minimization principle: we keep each category of data only for as long as needed for its purpose or required by law. Because MyHealth is offered in several countries, we apply the most protective standard among the applicable laws: by default, deletion erases your identity and health record, and retention is the exception, triggered only when a concrete law requires it or to enable fraud prevention and response to authorities. The only exception that survives deletion for every account is a minimum forensic index — search identifiers as irreversible codes (HMAC) + recent IPs, with no health data —, described in 12.2.
12.1 Retention periods
| Category | Period | Why |
|---|---|---|
| Health record and identity vault (clinical data + PII) | As long as your account exists; removed upon account deletion (see 12.2) | You keep the health record organized for as long as you want |
| Photo of a saved meal | As long as the meal exists. The protected copy stays with the meal, on the device and in our storage, for you only; deleting the meal deletes it from storage within minutes, deleting the account deletes all of them, and the daily backup copy of files deletes it within about 2 hours afterwards | Purpose (reviewing the logged meal; not losing it when changing devices) — the diary belongs to the account holder (§3.2) |
Meal description; photo of a reading not saved (only with food_photo_ai) | Not kept by us. The estimate received and a code of the photo stay on the device for up to 24 h (§3.2). The copy sent to Anthropic is retained generally for about 30 days, unless retention is required by law or for abuse prevention | Minimization (LGPD Art. 6, III; GDPR Art. 5(1)(c)); the period is Anthropic's, not a deletion period guaranteed by us |
| Record of meal readings (attempt code, outcome, daily counter, AI usage record — never the food, the photo or the text) | As long as the account exists; removed with the account | Billing and abuse prevention (§3.4) |
| Daily copy of files (documents, profile photos and meal photos) | As long as the original exists; deleted within about 2 hours after you delete the file or the account; old versions of a file you replaced, 90 days after they were replaced | Disaster recovery and security (LGPD Art. 46; for health content, the consent of the clinical core, Art. 11, I, and Art. 11, II, "g") |
| Daily wearable / Apple Health series (daily imported metrics — e.g., steps, SpO₂, walking heart rate, activity and environment, nutrition data, gait, and the daily continuous-glucose-monitor (CGM) aggregates; never manually recorded measurements, point clinical measurements — weight, capillary/spot glucose, blood pressure —, nor insulin, alcohol, spirometry, or inhaler use) | Daily detail for 13 months; after that, the daily points may be condensed into weekly summaries (minimum, mean, maximum, and count) and, once older than 36 months, into monthly summaries — a granularity exception to the row above: the history remains in your record as a summary | Minimization / storage limitation (LGPD Art. 6, III; GDPR Art. 5(1)(c) and (e)) — our own minimization policy, not a legal deadline |
Access / audit logs (access_log — date/time, source IP, action; never clinical content) | 6 months | Security and detection of fraud/abuse (a proportionate measure — legitimate interest, GDPR Art. 6(1)(f); LGPD Art. 7, IX). In Brazil, it also meets the floor of the Internet Civil Framework (Law 12.965/2014, Art. 15) for an application provider. The log (date/time + IP) is not health data and the IP is never used to infer a health condition |
| Minimum identity retained upon deletion (encrypted name + encrypted email + creation date + last access date) | Only where there was a transaction (subscription or packs purchased); for the tax period of your jurisdiction — determined by the App Store storefront where the purchase was made (Apple is the merchant of record and registers it); absent a purchase, by the country in your profile — (Brazil, United States, and other countries: 5 years; United Kingdom and Canada: 6 years; European Union: 10 years), with automatic purging at the end. For anyone who never transacted: none of this is retained — the identity is erased upon deletion | To comply with a tax/accounting obligation that arises only from a real transaction (Brazil: Tax Code (CTN), Arts. 173 and 174; United States: IRS rules; European Union: the Member State's period; United Kingdom: Limitation Act 1980 / HMRC; Canada: Income Tax Act s. 230). Without a transaction, there is no legal obligation that justifies keeping the identity |
| Billing and tax data (receipts, subscription and pack movements) | Tax period of the jurisdiction (Brazil: 5 years) — only for those who transacted | Tax periods (Brazil: Tax Code (CTN), Arts. 173 and 174; or the applicable local tax law) |
| De-identified technical telemetry | Up to about 12 months | Internal minimization policy (LGPD Art. 6, III) — not a legal period |
| Usage and navigation events | Up to 12 months | Internal minimization policy (LGPD Art. 6, III) — not a legal period; the purge runs daily |
| Notification delivery token (push) | Up to 180 days without renewal — the app renews it every time it opens; on sign-out, it is unlinked right away | Internal minimization policy (LGPD Art. 6, III) — not a legal period; the purge runs daily |
Consent records (consent_events, de-linked / pseudonymized from your profile upon deletion — the identifier is replaced by an HMAC code whose key is kept outside the database) | Kept as proof of lawfulness for the applicable limitation period | To prove lawfulness and the authorizations granted/revoked (accountability — GDPR Art. 5(2)/7(1); LGPD Art. 8/6, X) |
Minimum forensic index retained upon deletion (account_forensic_hold — search identifiers as an irreversible HMAC code — email, Sign in with Apple identifier, phone, national ID — + recent IPs; never readable name/email or clinical content) | The IP addresses: 6 months after deletion (Marco Civil, art. 15), unless an authority asks for longer retention. The irreversible codes (HMAC): for the limitation period of 5 years (Consumer Defense Code, art. 27; Brazil/US/others — 6 years United Kingdom/Canada; 10 years European Union); for minors' profiles, 1 year. Automatic purging at the end | Legitimate interest in fraud prevention and defense in proceedings (LGPD Art. 7, IX and Art. 10, with a recorded legitimate-interest assessment) and regular exercise of rights (Art. 7, VI); GDPR Art. 6(1)(f) and Art. 17(3)(e). Break-glass access restricted to the top responsible person, with a mandatory reason and immutable audit |
How identity is protected when retained: when there is a transaction and tax law requires retention, we keep the name and email encrypted (the same protection as the identity vault), in an isolated table, accessible only by the internal service (RLS, no user access), and we delete it automatically at the end of the period. We do not keep your email in readable text.
Retention of the sensitive journal. While the consent is active and the account exists, the Sensitive Health Journal records (alcohol, stress/what shaped the night) remain in your health record. When you withdraw the consent, they are deleted; when you delete the account, they follow the dual-track deletion (Section 12). There is no tax retention of this data.
Retention of the food diary. Meals, items, complete days and the goal stay in your health record for as long as the account exists (you can delete any of them at any time) and are not condensed over time; they leave with the account (12.2). There is no tax retention of this data.
12.2 Permanent account deletion (right to erasure — LGPD Art. 18, VI / GDPR Art. 17 / local equivalents)
Deletion is available directly in the app, under Profile › Privacy › Delete my account (an Apple requirement). Upon confirmation, we execute the permanent cascade removal — an immediate operation — of all of your clinical health record (lab results, conditions, medications, vaccines, documents, measurements, history, appointments, conversations with the AI, wearable data, food diary with the meal photos and personal goal) and of the files in storage, we revoke the wearable connections, and we close your access account.
Managed dependents and guardianship migration. Deleting your account also erases the data and files of the dependents you manage (minor profiles in your care). Before completing, if a minor has another guardian already linked, the app offers to migrate that minor's guardianship to the existing co-guardian — so the minor's profile survives with them, instead of being erased. If you choose not to migrate, the dependent's profile is removed together with your account. In any case, we never retain the minor's name or email for tax reasons (see below).
Backups exist at two levels. (1) Daily copy of your files (documents, profile photos and, when they exist, meal photos), kept in our private storage, on the same server, in São Paulo, to recover them in case of failure: when you delete a file — or the account —, its copy is deleted automatically within about 2 hours, because no file you send is kept by legal obligation; old versions of a file you replaced are deleted from the daily copy 90 days after they were replaced. (2) Database backups of our processor (Supabase), which may contain data already deleted for a short period and are overwritten on a short cycle set by our processor (Supabase) — well within the 6 months. The data processing agreements (DPAs) with Supabase and Anthropic govern the disposal of residual copies. (We do not claim "key destruction" or instant purging of the database backup.)
The deletion of your identity depends on whether or not you made a purchase:
- If you never made any purchase (subscription or packs): we also erase your name and your email (in readable text) upon deletion, and we do not create any fiscal identity record. Only the minimum forensic index described below survives (search identifiers as irreversible HMAC codes + recent IPs, with no health data), retained for fraud prevention and response to authorities — never your readable name or email.
- If you made at least one purchase: the tax/accounting law of your country requires us to keep the transaction record for a period (in Brazil, 5 years). For that, we keep a minimum accounting record and, where it is indispensable to link it to you, your encrypted name and email — isolated, accessible only upon a judicial request or that of a competent authority, and deleted automatically at the end of the legal period.
Deletion receipt (accountability — LGPD Art. 6, X): we can confirm the completion of the deletion upon request to the DPO. The deletion is not total — the minimum records below remain, by legal requirement.
Minimum forensic index that survives deletion (all accounts). At the moment of deletion, and for any account — including minors' profiles and deletions you perform yourself —, we keep a minimized forensic index, in an isolated, shielded table (no user access and no access by ordinary operations staff), containing at most: (a) irreversible codes (HMAC) of your search identifiers — email, Sign in with Apple identifier, phone, and national ID — which do not allow recovering the original value and serve only to confirm an exact match when an identifier is presented to us; (b) the IP addresses of your recent accesses; and (c) the pseudonymous account identifier (account_ref) and minimal retention metadata (creation/deletion dates, jurisdiction, and period). This index contains no health data, no readable name or email, and no content from your health record. It is pseudonymized data — it remains personal data (LGPD Art. 12 and 13); we do not invoke anonymization (Art. 16, IV). Purpose: fraud prevention and response to a request from a competent authority — for example, answering "which accounts were associated with this email, Apple ID, or IP" — within the period. Legal basis: legitimate interest in fraud prevention and defense in proceedings (LGPD Art. 7, IX and Art. 10, with a recorded legitimate-interest assessment) and regular exercise of rights (LGPD Art. 7, VI); GDPR Art. 6(1)(f) and Art. 17(3)(e). Period: the IP addresses are kept for 6 months after deletion (Marco Civil, art. 15), unless an authority asks for longer retention; the irreversible codes (HMAC) of the identifiers are kept for the limitation period of 5 years (Consumer Defense Code, art. 27) — 6 years United Kingdom/Canada; 10 years European Union —, with automatic purging at the end. Access: restricted, "break-glass" type, reserved for BAS AI's top responsible person (owner), always with a mandatory reason and an immutable (tamper-evident) record of each lookup; the key that generates the HMAC codes is kept in a vault (Vault), encrypted by a root key managed outside the database, and never exposed. Accounts deleted before this version took effect do not have this index.
What always remains after deletion, for any user:
- A minimum deletion record, without any personal data and with your identity replaced by an irreversible code (which does not allow re-identifying you), only to prove that the deletion occurred.
- The minimum forensic index (described above): search identifiers as irreversible codes (HMAC) + recent IPs, with no health data — the IPs for 6 months after deletion, unless an authority asks; the HMAC codes for the applicable limitation period (5 years in Brazil) —, for fraud prevention and response to authorities, under audited break-glass access.
- Access logs for the 6-month retention period (12.1), provided only upon a judicial request or that of a competent authority.
- Consent records de-linked from your profile (we replace the identifier with a pseudonymous code, separated by a key that is not kept in the database), kept only as proof of lawfulness for the limitation period. We treat this as pseudonymized data, not as irreversibly anonymous data.
- Optional — research: if, and only if, you authorize it at the moment of deletion, we keep your markers in a pseudonymized way — without a name, without a profile identifier (
profile_id), without free text, and without an exact date, keeping only sex, age range, and the year, in random cohorts. We treat this as pseudonymized data, and not as irreversibly anonymous data: re-identification is unlikely, but we do not declare it impossible. You may decline and still delete the account.
Dependent profiles (minors): when deleting a minor's profile, we never retain the minor's name or email for tax reasons — the tax obligation, if any, belongs to the paying guardian, not to the minor's profile. For the minor, erasure of the identity is the rule; only the minimum deletion record by irreversible code and the minimum forensic index (search identifiers as irreversible HMAC codes + recent IPs, with no health data of the minor) remain, retained for a reduced period, proportionate to the fraud-prevention purpose — 1 year, and the IPs at most 6 months (never the fiscal period, which does not apply to a minor who does not transact) —, subject to a proportionality assessment and to the best interests of the child, under the same audited break-glass access — and subject to DPO sign-off.
Users in jurisdictions with a reinforced right to deletion (e.g., Washington — My Health My Data Act): we treat the request as deletion of consumer health data — we erase the identity and all consumer health data (without invoking the tax period against anyone who did not transact), and the disposal of residual copies at the processors occurs within 6 months, in accordance with the respective data processing agreements (DPAs). The minimum forensic index above is not consumer health data: it holds only account identifiers as irreversible codes (HMAC) and IPs, for fraud prevention and response to authorities — a distinct purpose and category from the health data, which is erased.
12.3 Deleting an exam from your health record (right to erasure, item by item)
In addition to deleting the entire account (12.2), you can remove a specific exam at any time, on the document's own screen. The app offers two options, and the difference matters:
- "Delete only the document (keep data)" — the file and the exam record go, but the data that reading recorded (markers, measurements, medications, vaccines, professionals) remain in your health record and merely stop referencing the removed file. Useful when the data is correct and you simply no longer want to keep the file.
- "Delete test and the extracted data" — what that exam recorded goes as well. Two things remain on purpose, because they stopped being a reading of the file and became a fact of yours: the appointment you have already attended and the symptom you have already confirmed.
Under either option, the readings our AI had written from that exam are deleted, and the follow-ups that were born from it are closed — the follow-up entry remains, recorded as closed and with the reason, so that your history does not lose the thread.
What happens to the file and to the record. The exam record is deleted from the database immediately and in a single operation — the entry ceases to exist; it is not a "hidden" flag. The file is removed from storage: the app removes it immediately and, if that removal fails for any reason, the server repeats it on its own, in sweeps every 15 minutes, until it is done. The file name does not survive either: it is replaced by an irreversible code in our deletion record, because the name is chosen by you and can, on its own, reveal the finding; in the technical record of the daily file copy, it is replaced in the same way when the copy is deleted (within about 2 hours). (There is a distinct case: a document the app could not prepare may be deleted in a way that is reversible for a period — when that is the case, the screen itself says so in those words. The deletion described here, performed on the exam's screen, is permanent.)
The analysis of your health record stops resting on the removed exam. The next analysis is redone without the memory of the previous one: it rebuilds the conclusions from what the remaining record supports — otherwise, a finding from the deleted exam could be restated indefinitely. This rebuild is prioritized: removing an exam counts as a relevant change and enters the next sweep, which happens every few minutes; in exceptional situations (for example, when your plan's daily processing limit has already been reached) it may be postponed by a few hours. We record the moment the redone analysis is published.
Two honest caveats about that interval. First: until the new analysis is ready, the text of the previous analysis remains displayed, and it may still mention the removed exam — the file and the record, however, were gone from the very first moment. Second: if the rebuild returns no conclusions, we prefer to keep the previous reading rather than empty your health record; in that case it may reflect the removed exam until a later analysis replaces it. Earlier conversations with the assistant also remain in your conversation history until you delete them.
What remains, and why. We keep the act, never the content: the record that a removal occurred, when, who requested it, and which of the two options was chosen, with a receipt that keeps counts only — how many markers, medications, vaccines, measurements, professionals, appointments, and follow-ups were affected. We do not keep the title, the date, or any content of the removed exam, for the obvious reason that a title is already health data. This is what lets us explain the effect of the removal to you without retaining what you told us to delete (accountability — LGPD Art. 6, X; GDPR Art. 5(2)). If the exam was still being processed when you removed it, the working data from that preparation is discarded automatically within 24 hours — 30 days when the processing had ended in error, so that the failure can be investigated. The access logs — date/time, action and, when available, the IP address — never keep the exam's content and follow the period in Section 12.1.
Workouts imported from a device. When you delete a workout that came from Apple Health, Oura or WHOOP, we keep only the identifier the source uses for it, the name of the source and the time of deletion — nothing about the workout (no type, date or duration) — so that the next sync does not import it again. This record is removed together with your account.
Backups: the daily copy of the removed file is deleted within about 2 hours; the database backups follow the cycle of Section 12.2, and the data processing agreements govern the disposal of residual copies.
12.4 Death of the data subject
The LGPD and the GDPR protect living persons and, as a rule, do not reach the deceased (ANPD, Technical Note No. 3/2023; GDPR, Recital 27). Even so, a deceased person's health record involves personality rights that survive death (Civil Code, Art. 12, sole paragraph) and matters of succession.
- The heir does not inherit access to the content of the health record. The Superior Court of Justice (REsp 2.124.424/SP) treated health records as a non-transferable existential asset — tied to the person's intimacy, and not to their estate.
- For this reason, we do not carry out total deletion at the request of third parties (the access logs for 6 months and the tax records for 5 years still remain — 12.1), nor do we hand over the clinical content to heirs as if it were an inheritance.
- Requests related to the death of a data subject (for example, to cease processing, or measures provided for in Art. 12, sole paragraph, of the Civil Code by someone with standing) must be directed to our DPO (Section 1), upon proof of the death and of the standing of the requester. We assess each request in light of the applicable law.
12-A. Notifications and reminders (opt-in)
MyHealth may send reminders on your iPhone — about medication, a wellbeing check-in, a weekly check-in (optional, once a week — a neutral, fixed-text invitation to log what the app can't see on its own, such as activity, symptoms, or energy; it never carries health data or inference; you can turn it off whenever you like), your schedule (appointments/tests/follow-ups/vaccines), an invitation to come back to the app after a stretch without use, an invitation to move after a few days with far fewer steps than your usual, and a few server-side notices (when an analysis is ready, when one of your exams is updated, when a follow-up appointment is approaching, when support replies to your message, when we release a new version of the app, when an upload of yours is waiting for pages, when your subscription is not renewed or ends, when a family sharing of yours starts or ends, and — optional, off by default — when your data — e.g., sleep, resting heart rate — brings something new). Since version 3.12, these notices may also carry, in the body, a summary of your own health data (for example, last night's sleep and how it compares to your average, your glucose average and time in range, your activity and milestones, a lab marker's evolution, or a weekly/monthly summary) — always descriptive, on your own device, and disable-able category by category; since version 3.25, the numbers from your data appear in those summaries only if you turn on "Numbers from your data in alerts" (see "Personalized summaries of your data"). The food diary generates only the two notices described further on ("Food diary notices"), both of fixed text and with none of your data — never a notice with what you ate, calories or nutrients. Since version 3.27, the minor notices of a same day arrive gathered into one, "Your summary for today" (see "One minor notice per day"). Key points:
- Local notifications vs. remote push. Many notifications are LOCAL, scheduled on your own device (medication, wellbeing check-in, weekly check-in, and schedule reminders) — for those we use no push server. Others are delivered by remote push (Apple's APNs) because the event happens on the server, in fourteen cases: (a) an analysis is ready — when the new analysis can be compared with the previous one, the notice has a fixed title ("Your analysis was updated") and one of these bodies: "1 change since the last one — tap to see what changed.", "N changes since the last one — tap to see what changed." (N is the number of changes) or "Nothing new since the last one — tap to check.". The body carries only the count of changes (analysis items that appeared, went away or changed level), never the name of a test, a marker or an analysis item, a value, a direction or a judgment — what changed is shown only inside the app, on the card the tap opens. This text goes only to your own profile: the notice about a profile under your care stays generic ("The analysis of a profile under your care is ready — tap to review."), with no count and no name; (b) one of your exams was updated (a marker that was out of range received a new result); (c) a follow-up appointment is coming up; (d) support replied to your message; and (e) your data (e.g., sleep, resting heart rate) recorded something new (optional, off by default — "Something new in your data"; the body never suggests abnormality or urgency — under the same option, also an association observed over time between a marker and one of your medications, "Pattern over time", equally generic); and (f) you have gone a while without opening the app and we send the neutral come-back invitation (the same wording described later in this Section; the trigger is time without opening, a usage signal, never a reading about your health); and (g) we released a new version of the app and let you know it is available — a service notice with fixed text ("A new version of MyHealth is available. Update to keep using the app."), with no health data and no promotional content (it does not advertise features, offers, or plans), sent at most once per version, because older versions may stop working with our server; and (h) the connection with your watch or ring (Oura, WHOOP) stopped and needs to be redone — a service notice, with no health data, that you can turn off in Profile › Notifications; and (i) we could not read a document you sent — a fixed-text service notice ("We couldn't read an upload — tap to see what happened and try again"), with no file name and no health data, which follows the same option as the analysis-ready notice; and (j) account notices about the guardianship of a minor — when you become responsible for a dependent (because the other guardian deleted their account) and when a dependent of yours reaches the age to take over their own account —, service notices to the guardian, with no health data; and (k) the invitation to move, when you have not opened the app in 48 hours — our server reads your steps, exercise minutes and workouts to decide, with the same rule as the app, and sends the invitation at your workout time, with the fixed text "Time to move?" / "How about a walk today? A few minutes already count.", with none of your numbers (see "An invitation to move", below); and (l) an upload of yours is waiting for pages — when the reading of a document you sent is held for lack of available pages, a fixed-text service notice ("An upload is waiting for pages" / "The reading continues as soon as pages are available. Tap to see."), with no file name, no page count, no offer to buy and no health data, which follows the same option as the analysis-ready notice — the text is the same when the upload belongs to a profile under your care; and (m) account notices about your subscription — when the App Store tells us that the renewal charge was not completed ("Your subscription was not renewed" / "The App Store did not complete the charge this time. Tap to see your subscription.") or that the plan ended ("Your subscription has ended" / "The plan's pages and prompts no longer renew. What you have already sent stays in the app. Tap to see.") —, with no price, no offer and no health data, at most one per subscription per period, and never when you were the one who cancelled; and (n) account notices about family sharing — to whoever shares their record, when an invitation is accepted ("Family invitation accepted" / "Someone accepted your invitation and can now see your record, read-only. Tap to see it in Family."), and to each side that still has an account, when a sharing ends because the other side removed it or deleted their account ("A sharing has ended" / "A family link is no longer in effect. Tap to see it in Family.") —, naming nobody, with no relationship and no health data; a change in what an existing link allows to be seen does not generate a notice. The other remote service notices use a generic, fixed text, with no health data ("Support replied to you — tap to read"; "There's something new in your data — tap to see"), which you can turn off in Profile › Notifications. For remote push we store a technical delivery token from your device (see Section 3.4). Since version 3.12, the analysis-ready notice may name the analysis theme or panel that became ready (the health area organized), in your language; the other server notices (exam updated, follow-up appointment, support reply, "Something new in your data") remain generic, fixed text ("One of your exams was updated", "You have a follow-up appointment") — with no lab value, marker, or doctor name. Summaries with your own numbers (sleep, glucose, activity, a marker's evolution, the weekly/monthly summary) are local notifications, assembled on your own device (see "Personalized summaries of your data"). The token is a delivery identifier — it is not tracking, does not train AI, and is not shared with third parties beyond Apple's push service. To avoid bothering you, we cap this at one interruptive notice per day and respect your quiet-hours window (the dose reminders, which are local, ring at the time you chose to take them, even inside that window; since version 3.27, so does the "Time to leave" alert, which rings at the time computed for leaving); each category can be turned off separately in Profile › Notifications. The exceptions are the account and service notices with no separate switch: the new-version notice (g) — rare, at most one per released version —, the guardianship notices (j), the subscription notices (m) and the family-sharing notices (n). Like all the others, they only arrive if you allowed notifications in iOS — which you can revoke at any time in iPhone Settings.
- Nothing fires without your iOS permission. No notice — of any type — is delivered until you allow notifications at the iPhone system prompt. That iOS authorization is the master key: you grant it once, affirmatively, and can revoke it at any time in iOS Settings.
- How each type comes configured (two groups). After you allow notifications on iOS, the neutral SERVICE reminders — medication/dose reminder, wellbeing check-in, weekly check-in, and the schedule eve (plus the stock-refill and suggested-follow-up sub-reminders and, since version 3.27, the notice on the day after an appointment and the one on the last day of a treatment with an end date), plus the invitation to come back after a stretch without using the app — come pre-enabled, so the service you set up (the medications and appointments you entered) is useful from the start; each one can be turned off individually, at any time, in Profile › Notifications. These reminders have a fixed-text, neutral body, with no health data (the only caveat is the sentence about the material to take along on the eve of an appointment, whose counts appear only with your authorization — see "Appointment eve", below), and the decision to deliver them rests on performing the service you asked for and our legitimate interest in a health-tracking app you chose to use, always with easy, granular opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)); the underlying health data (your medications, your schedule, your in-notice replies) remains processed under your clinical consent already given (LGPD Art. 11, I; GDPR Art. 9(2)(a)). The summaries of your own data outside the especially sensitive domains — sleep, glucose, activity, symptoms, a lab marker's evolution, the weekly cross-summary and the weekly/monthly summaries, plus the "Daily headline" — come on by default and can be turned off individually in Profile › Notifications; since version 3.25, they arrive without numbers: the numbers from your data in the notice body appear only if you turn on "Numbers from your data in alerts", and the name of a test appears only if you turn on "Show the test name in the alert" — both come off, and turning them on records their own consent (LGPD Art. 11, I; GDPR Art. 9(2)(a)). The processing of your data to decide on and assemble these notices runs under your clinical consent (LGPD Art. 11, I; GDPR Art. 9(2)(a)); the delivery decision and the token follow Art. 7, V and IX (GDPR Art. 6(1)(b) and (f)). The sensitive domains (special category) — mental health, cycle/reproductive, substance (alcohol), and medication adherence — remain off by default and would only appear in a notification if you had both opted into that data category (the dedicated consent that enables it — e.g., the Health Diary, Mental health, cycle) and turned on that category's notification toggle (LGPD Art. 11, I; GDPR Art. 9(2)(a); Washington MHMDA); today, mental-health and cycle/reproductive content remain entirely out of any notification, and medication never frames a missed or late dose. The lock-screen details (medication name and dose, vaccine detail, appointment detail and "time to leave") come off. Each one appears only when you turn it on, and that choice is recorded as its own consent, which you can turn off at any time, with immediate effect (LGPD Art. 11, I; GDPR Art. 9(2)(a)). (In versions 3.21 to 3.24 they came on; from 3.25, a detail that was on only by that default is turned off once on this device, and the app offers it again with the consent request — a choice you made expressly is kept.) The content limits did not change — each item below describes what that notice may and may never say, and minor and managed profiles remain entirely excluded. "Time to leave" also depends on the iOS location permission, requested when you turn it on. You can turn everything off at any time (in the app or in iOS Settings). The live "today's doses" card no longer exists as of version 3.21. It showed, on the lock screen and in the Dynamic Island, the day's progress and the next moment, and stayed present while any dose was pending. It was removed by founder decision: a notification that stays permanently on screen has become an exception, and the exception is the day of the appointment, in the last hour before it (see the appointment item below). The dose reminder is exactly as it was — it appears at the time, is answered, and leaves the screen.
- Lock-screen content (what may and may never appear). A notification may carry, in the body, a summary of your own data — with the numbers only if you turn on "Numbers from your data in alerts" (off by default since version 3.25) — for example, your sleep duration/efficiency and how it compares to your average, your glucose average and time in range, your activity versus your average, the name of a lab marker and how it changed, or a weekly/monthly summary with real numbers (see "Personalized summaries of your data"). Even so, the notification never carries a diagnosis, a disease name, a medical judgment or opinion, a cause, an efficacy claim, or urgency, nor the AI summary; and the medication, vaccine, appointment, and location details follow the specific options described below — which, since version 3.25, come off and apply in your adult profile only when you turn each one on, with its own consent and immediate effect when turned off. All other clinical content stays inside the app only. The analysis-ready notice may state how many exams were organized (a count — for example, "3 exams") and name the analysis theme/panel, but never a marker's value. The Question of the Day may carry the question itself in the body when it comes from a closed list of everyday, non-sensitive questions (coffee, energy, hydration, a change in routine, and how your body responded to your workout — the last one in a generic form): these are fixed phrases, the same for everyone. Summaries and questions from sensitive domains (alcohol/substance, night context, stress/mental health, cycle/reproductive, medication adherence) and symptom ones appear only if you have opted into that category (see the sensitive-domains item above); otherwise, and on days when the question accompanies a complaint, the notice keeps its neutral text. Remember the lock screen can be seen by others and read aloud by Siri — that's why iOS lets you hide previews (Settings › Notifications › Show Previews: When Unlocked, or Never).
- Medication name on the lock screen (off by default since version 3.25; you turn it on, per device). With this option on, medication reminders display the name and dosage of the item in notifications ON THIS device — for example, "Losartan 50 mg · breakfast". The option comes OFF (version 3.25) and applies only once you turn it on — that choice is recorded as your consent —; it applies only to YOUR OWN medications, is set separately on each of your devices (turning it off on one iPhone does not turn it off on another), and can be turned off at any time, effective immediately — when off, already-scheduled reminders return to neutral right away. The text shows only what you entered — name, dose, and the moment/label — and NEVER the purpose, the drug class, the condition treated, interactions, or any clinical or urgency judgment. Because this displays HEALTH DATA on a surface others can see, that Siri can read aloud, and that can be mirrored to your other devices (Apple Watch, CarPlay, speakers, notification history), we recommend you review it if your iPhone is often visible to other people. You'll find it in Profile › Notifications and can additionally hide previews in Settings › Notifications › Show Previews: When Unlocked. Legal basis (since 3.25): your specific and prominent consent, collected when you turn the option on and revocable at any time (LGPD Art. 11, I; GDPR Art. 9(2)(a)). Reminders from DEPENDENT (minor) profiles and from MANAGED profiles NEVER show the name or dosage on the lock screen, even when this option is on — for them the notice stays generic ("Reminder for a dependent").
- Vaccine detail in the reminder (off by default since version 3.25; you turn it on — your own adult profile only). In Profile › Notifications, the option "Show the vaccine detail in the reminder" makes your vaccine reminders — and only those — show the vaccine name and dose on the lock screen (e.g., "Tomorrow: Influenza · annual dose"). Even when on, the reminder stays an echo of your own record (the name and dose you saved): it is never a booster recommendation, an individual due-date calculation ("overdue", "due in X"), or an urgency alert, and it never shows the doctor, the location, or the reason. No other notice changes — exams, analyses, medication, and appointments stay neutral. Because a vaccine name is health data (special category / sensitive data) and can reveal a sensitive context, and because the lock screen can be seen by others and read aloud by Siri, we recommend reviewing it if your iPhone is often visible to other people. It comes off (version 3.25): turning it on records your consent, and you can turn it off at any time, effective immediately; iOS still lets you hide previews. Legal basis (since 3.25): your specific and prominent consent, collected when you turn the option on (LGPD Art. 11, I; GDPR Art. 9(2)(a)). Minor and managed profiles are excluded: a dependent's vaccine reminder always stays generic ("Reminder for a dependent") and never exposes the vaccine name or the minor's name — in the child's best interest (LGPD Art. 14; GDPR Art. 8).
- Appointment detail in the reminder (off by default since version 3.25; you turn it on — your own adult profile only). In Profile › Notifications, the option "Appointment details in reminders" makes your appointment and follow-up reminders — and only those — show, on the lock screen, the professional, the time, and a short address that you entered yourself (for example, "Appointment with Dr. Silva · 2:30 PM · Av. Paulista, 1000"), together with a map of the destination (a static image of the address, generated by Apple's map service from the address you entered, without using your location). Even when on, the notice stays a factual echo of your own record: it never shows the specialty, the reason for the visit, or any diagnosis or clinical judgment, and it assembles the phrase only from the parts you filled in. No other notice changes — exams, analyses, medication, and vaccines stay neutral. Because this exposes health data on a surface others can see and that Siri can read aloud, we recommend reviewing it if your iPhone is often visible to other people. It comes off (version 3.25), is set separately on each device (local preference, not synced), turning it on records your consent, and it can be turned off at any time, effective immediately — legal basis (since 3.25): your specific and prominent consent, collected when you turn the option on (LGPD Art. 11, I; GDPR Art. 9(2)(a)) — and, when you turn it off, already-scheduled reminders return to neutral; iOS still lets you hide previews. Minor and managed profiles are excluded: a dependent's agenda reminder always stays generic and never exposes the professional, the location, or any of that person's data (LGPD Art. 14; GDPR Art. 8). None of it goes through our server — the professional, the time, and the address never travel over remote push; only the address goes to Apple's map service, to generate the map. With this option on, that same detail may also appear as a Live Activity on the lock screen and in the Dynamic Island, with a countdown to the time — under the same limits of content. Since version 3.21 this Live Activity exists only in the last hour before the appointment and ends within an hour after it (previously it opened as soon as the day turned): it is the only notification in the app that stays present on screen, and the short window is the reason it is the exception. Without this option, no Live Activity is created.
- "Time to leave" alert (off by default since version 3.25; you turn it on — your own adult profile only; uses your location). In Profile › Notifications, the option "Alert me when it's time to leave" makes it so that, on the day of an appointment or follow-up of yours that has a time and address, the app estimates your travel time to the place and sends, on your own device (a LOCAL notification, no sending server), a "time to leave" alert — for example, "Time to leave · Appointment at 2:30 PM" and "Leave by ~1:50 PM to arrive at 2:30 PM (current traffic)". To compute the route, this is the only app feature that uses your location: we request the iOS permission ("While Using the App") only when you turn this option on. To compute the route, the app sends to Apple's map service (Apple Maps) your current location and the appointment address, without your name or your MyHealth account, solely to estimate travel time. We do not receive, store, or send your location to the AI — in the app, it exists only in memory, at the moment of the calculation. Because the alert shows the appointment time on the lock screen — which others can see and Siri can read aloud — we recommend reviewing it if your iPhone is often visible to other people. It comes off (version 3.25), is set separately on each device, and turning it on records your consent — and it still depends on the iOS location permission, which your iPhone asks for the first time: without it, no travel is computed and no alert goes out. Legal basis (since 3.25): your specific and prominent consent, collected when you turn the option on (LGPD Art. 7, I and Art. 11, I; GDPR Art. 6(1)(a) and Art. 9(2)(a)), together with the iOS location permission. It can be turned off at any time here in the app or revoked in iPhone Settings › MyHealth › Location, effective immediately. Minor and managed profiles are excluded (LGPD Art. 14; GDPR Art. 8). None of this travels over remote push or goes through our server — the alert is assembled on your device, and only the route calculation uses Apple Maps. Since version 3.27, this alert rings at the time computed for leaving, even inside your quiet-hours window (like the dose reminders): before, the window could push it to after the time to leave.
- Personalized summaries of your data (on by default and disable-able; numbers only with your authorization; your own adult profile only). MyHealth may send, on your own device, notifications that carry in the body a summary of your own health data, so you can follow what you recorded without opening the app — for example: last night's sleep (duration, efficiency, deep sleep) and how it compares to your own average; your daily glucose average and time in range (a descriptive reading, never an alarm or a clinical threshold; since version 3.27, the glucose numbers enter the notice only when read from 6 PM on — a reading made earlier produces the notice without numbers); your activity versus your average and milestones you reached; how one of your lab markers changed over time — the marker name only appears if you turn on "Show the test name in the alert" in Profile › Notifications (off by default since version 3.22, and only for the device where you turned it on); without it, the notice just says "one of your tests"; your week's symptoms; the weekly cross-summary and a weekly or monthly summary with your real numbers. These summaries of your data outside the especially sensitive domains (mental health, cycle/reproductive, substance and medication adherence) come on by default and each category can be turned off individually in Profile › Notifications. The numbers, however, come off (since version 3.25): they appear in the notice body only if you turn on "Numbers from your data in alerts" in Profile › Notifications — one single switch, for all those summaries and for the "Daily headline" detail, set on this device and valid only for the notices of your own profile. Turning it on records its own consent (LGPD Art. 11, I; GDPR Art. 9(2)(a)); turning it off takes effect right away. Without it, each summary arrives with a sentence that carries no number — for example, "Your night summary is ready in the app." On a device where the numbers were on only by the old default, they are turned off once, and a choice you made expressly is kept. Four safeguards: (a) iOS hides previews on the lock screen until you unlock the device (default "Show Previews: When Unlocked"; you can also choose "Never" in Settings › Notifications), so a glance at a locked phone does not reveal the content; (b) each category has its own toggle and is disable-able at any time, effective immediately; (c) they are for you, the adult account holder, on your device only — minor and managed profiles never carry health data in the notice body; (d) the text is descriptive and factual — never a diagnosis, a medical judgment or opinion, a cause, an efficacy claim, or urgency. Sensitive domains (special category) — mental health (mood, questionnaires, stress), menstrual/reproductive, substance (alcohol), and medication adherence — stay off by default and would only generate a notification if you had already opted into that data category (the dedicated consent that enables it, such as the Health Diary, Mental health from Apple Health, or cycle tracking) and turned on that category's notification toggle; today, mental-health and cycle/reproductive content remain entirely out of any notification, and medication notices never frame a missed or late dose (they are adherence memory, never surveillance). Legal basis: the summaries are health data, processed under your Clinical processing consent (LGPD Art. 11, I; GDPR Art. 9(2)(a)); the numbers and the test name in the notice, under the own consent you give when turning them on (LGPD Art. 11, I; GDPR Art. 9(2)(a)); the sensitive (special-category) domains, under explicit consent for that category (LGPD Art. 11, I; GDPR Art. 9(2)(a); Washington MHMDA); the delivery decision and the token follow Art. 7, V and IX (GDPR Art. 6(1)(b) and (f)).
- Reply right from the notification. You can answer certain reminders in the notification itself (e.g., "Took all" / "So-so"). Those answers are health data (medication adherence, wellbeing) stored in your record with the same protection as your other health data; none of it appears on the lock screen.
- Minors and managed profiles: when the reminder is for a dependent's profile or for another person you manage, the notice on your device is always generic ("Reminder for a dependent") and never exposes that person's name, dosage, or any health data. The options to show a medication name or a vaccine detail on the lock screen apply only to your own records and never to those of dependents or managed profiles — this applies to vaccine reminders as well, which never display a dependent's vaccine name.
- Refill / low-stock reminder (a service reminder, alongside medication). If you record the quantity on hand of an item in your routine (a medication or supplement), the app can tell you, on your own device (a LOCAL notification, with no sending server), that an item in your routine is running low — so you can restock whenever you like. This is inventory logistics, computed on your device from data you already recorded (the quantity) and your dose schedule: we collect nothing new and it is not a clinical recommendation — it does not claim that running out is risky, suggests no abnormality, and does not tell you to restock urgently. The body is neutral, fixed text ("An item in your routine is running low. Tap to see which and plan the refill"): it never includes the item name, dose, quantity, or "days remaining" — the detail (which item, how much is left) stays inside the app only. It follows the same configuration as medication notifications (pre-enabled once you receive them, disable-able in Profile › Notifications) and fires only while those are active, with the same cap of one interruptive notice per day and the same quiet-hours window. Legal basis: performance of the service / legitimate interest for a neutral logistics reminder, with easy opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)); the underlying data under clinical consent (Art. 9(2)(a)), like the other medication reminders. On dependent profiles the minors rule applies: the notice on the guardian's device is generic ("Reminder for a dependent") and never reveals the minor's name, which item, or that it is a medication/supplement.
- Suggested follow-up reminder (a service reminder, alongside the schedule). When your health record holds a suggested follow-up from a professional (a follow-up date that you — or the reading of one of your documents — saved) and you have not yet scheduled the corresponding appointment, the app can send, on your own device (a LOCAL notification, with no sending server), a single notice that a suggested follow-up is coming up — so you can schedule it whenever you like. This is calendar organization, computed on your device from a date you already recorded: we collect nothing new and it is not a clinical recommendation — it asserts no urgency and suggests no abnormality. The body is neutral, fixed text ("A follow-up suggested at an appointment is coming up. See the details and secure your time in the app."): it never includes the doctor, the reason, the specialty, the date, or the fact that you have not scheduled it; the detail (which follow-up, when) stays inside the app only. It follows the same configuration as your calendar notifications (pre-enabled once you receive them, disable-able in Profile › Notifications), respects the cap of one interruptive notice per day and your quiet-hours window, and disappears as soon as you schedule the appointment. Dependent and managed profiles are excluded (it applies to your own profile only). Legal basis: performance of the service / legitimate interest for a neutral schedule reminder, with easy opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)).
- Invitation to come back after a stretch without using the app (a service reminder). If you go a while without opening the app (for example, around two days, for those who have not sent anything yet, and around one and three weeks), it can send a neutral invitation to come back whenever you like — on your own device (a LOCAL notification) or, when the local notice cannot be scheduled (for example, you went a long time without opening the app or switched devices), by remote push from our server, with the same neutral wording (for example, "Your data misses you — the portrait is still here, just as you left it." or "Nothing is lost: your history is saved and ready to pick up where you left off."; and, for someone who hasn't added anything yet to their record, an invitation to take the first step, such as "Your record is ready to begin — upload your first test whenever you like."). What triggers this reminder is only the time since you last opened the app — an app-usage signal (engagement metadata), not a reading or inference about your health: the notice never carries health data, a number, a comparison, a judgment, or blame, and the timer resets every time you open the app. It comes with the other service reminders (pre-enabled once you allow notifications; disable-able in Profile › Notifications, alongside the local reminders). Dependent and managed profiles are excluded (it applies to your own profile only). Legal basis: performance of the service / legitimate interest for a neutral come-back invitation, with easy opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)).
- An invitation to move (on by default, disable-able; account holder only, on their own profile). When your watch or ring records three days in a row with steps clearly below your usual — below 70% of your median over the last 30 days, with at least 10 days of history —, no exercise recorded on those days and nothing active today, the app may send a light invitation to take a walk: "Time to move?" / "How about a walk today? A few minutes already count.". The text is fixed and carries none of your numbers, no comparison, judgment or blame — it asserts nothing about you. A day with no data from the watch or ring does not count as an inactive day (missing data is not inactivity). It arrives at most once every 3 days: on your device (a LOCAL notification), at your workout time (6 PM if you have not set one), or — only if you have not opened the app in 48 hours — as a remote push from our server, at your local workout time; in that case, it is our server that reads your steps, exercise minutes and workouts to decide, with the same rule as the app. It follows the day's notice cap and your quiet-hours window. The switch "An invitation to move" (Profile › Notifications) comes on and, when turned off, also turns off the remote invitation. Never for minors' profiles, managed profiles or read-only access. Legal basis: processing your activity data to decide on sending runs under your Clinical processing consent (LGPD Art. 11, I; GDPR Art. 9(2)(a)). It is a wellbeing invitation, not a medical recommendation.
- One minor notice per day — "Your summary for today" (since version 3.27). The minor notices — the summaries of sleep, glucose, activity, symptoms, a lab marker's evolution and the weekly crossover, and the "Daily headline" — go through a single outbox on your device: on a same day, at most one minor notice is delivered. If only one was due, it arrives as always, with its own title, text and time. If two or more were due, they arrive gathered into a single notice, titled "Your summary for today", at the time of the first of them; the body lists the titles of the gathered notices — nothing beyond what each would already show on its own. Once the day's notice has gone out, no other minor notice goes out that day. An exam that just arrived: for 48 hours after a document enters your record, the minor notices about exams stay silent — that upload already had the analysis-ready notice and, when there is one, the analysis-updated notice. Not part of this gathering, and still arriving on their own: medication and dose reminders, the schedule, "Time to leave", the weekly summary and the server notices. Nothing new is collected: it is the same information, in fewer notices. To assemble the summary, the app keeps on the device itself the text of the notices that are due, in a protected file, outside the iCloud backup and deleted when you sign out. Each category keeps its own switch in Profile › Notifications, and these notices apply only to your own adult profile — minor and managed profiles remain excluded.
- Appointment eve: a single notice, with the material to take along (since version 3.27). The eve reminder of an appointment or follow-up now carries, in the same notification, a sentence about the material the app gathered for you to take along — and the separate notice that used to arrive at 6 PM on the eve no longer exists (one notice fewer about the same appointment). The sentence is "Your summary to take along is ready." or, only on your own profile and if you turned on "Numbers from your data in alerts", "I gathered N tests from the last 6 months and M medications in use to take along." — counts only (how many exam documents from the last six months and how many medications in use there are in your record), never the name of a test, a marker or a medication, nor a dose. The material itself appears only inside the app, on the appointment's screen. It is a LOCAL notification, assembled on your device, which follows the same setting as your schedule notifications (can be turned off in Profile › Notifications). In the schedule reminders of dependent and managed profiles the sentence does not appear — they stay generic.
- "How was your visit?" — the day after an appointment (since version 3.27; alongside the schedule). The day after an appointment of yours, at 10 AM (or at the first time outside your quiet-hours window), the app may send, on your own device (a LOCAL notification, no push server), an invitation to write down what was agreed: "How was your visit?" / "Write down what was agreed while it is fresh — it takes a minute.". The text is fixed and neutral: never the professional, the specialty, the reason or any data about the appointment. It is not sent for an appointment marked as not attended, nor for one you have already answered or silenced on the corresponding card in the app. It follows the same setting as your schedule notifications (can be turned off in Profile › Notifications). Dependent and managed profiles are excluded (it applies only to your own appointments). Legal basis: performance of the service / legitimate interest for a neutral schedule reminder, with easy opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)); the underlying data (your schedule) under the clinical consent (LGPD Art. 11, I; GDPR Art. 9(2)(a)).
- Last day of a treatment with an end date (since version 3.27; alongside medication). When an item of your routine (a medication or supplement) has an end date that you entered, the app may tell you, on your own device (a LOCAL notification, no push server), at 9 AM on that day (or at the first time outside your quiet-hours window), that today is the last day: "Last day of a treatment" / "Today is the last day of an item with an end date in your routine. Tap to see which." — or, when several end on the same day, a single notice: "Today is the last day of some items with an end date in your routine. Tap to see which.". It is an echo of the date you yourself entered: never the item's name, the dose or the reason, and no advice at all — the notice does not tell you to stop, to continue or to see anyone; whether a treatment ends on the date entered is a matter for whoever prescribed it. We collect nothing new. It follows the same setting as the medication notifications (can be turned off in Profile › Notifications) and is not part of the day's summary. On a dependent or managed profile the text is the same, neutral: never the person's name, the item's name or the dose. Legal basis: performance of the service / legitimate interest for a neutral reminder, with easy opt-out (LGPD Art. 7, V and IX; GDPR Art. 6(1)(b) and (f)); the underlying data under the clinical consent (LGPD Art. 11, I; GDPR Art. 9(2)(a)), like the other medication reminders.
- Three new notices inside the "Daily headline" (since version 3.27; your own adult profile only). The "Daily headline" gains three types, all with fixed text, no numbers and no health data in the body, under the same switch (Profile › Notifications) and subject, like every minor notice, to "One minor notice per day": (a) "Your notifications" — some notice types come turned off because turning them on is a consent of yours (see "How each type comes configured"); while there is one the app can still offer you, it may remind you of that, at most once every 60 days, with "Some of the app's notifications start turned off — see which ones make sense for you." or "Some notifications only you can turn on. They are in Profile › Notifications, and the choice is yours.". The notice does not say which are off and turns nothing on: the choice remains yours, on the screen. (b) "Your month" — on days 1 to 7 of each month, while the app shows the portrait of the month that closed, only once a month: "The month has closed — its portrait is ready in the app." or "Your last month, side by side with the one before. It is in the app.". (c) "Vaccination calendar" — only while the app already shows, inside it, a general vaccination calendar reminder (an educational reminder, which starts from generic reference intervals and from the dates of the vaccines you recorded — see "Recheck and update reminders", below), and at most once every 90 days: "There is a general vaccination calendar reminder in the app. It is worth checking with your doctor.". The notice only points to that reminder: it is never a booster recommendation nor an individual deadline ("overdue", "next in X"), and it never carries a vaccine name, a date or urgency — what the reminder says stays only inside the app. Minor and managed profiles are excluded from all three. Legal basis: the same as the "Daily headline" (see "How each type comes configured").
- "Any new test?" (since version 3.29; only for the account holder, on their own profile). If you have already sent at least one document and about four months have passed since the last upload, the app may ask, on your own device (a LOCAL notification, with no sending server), whether there is a new test: "Any new test?" / "No new test has come into the app for N months. If you had one, send it: it joins the analysis along with the earlier ones." (N is the number of months since your last upload). The body carries only that count of months — an app-usage fact, never the name of a test or of a marker, a value or a result — and it is not a recommendation to repeat a test: the app does not calculate when you should have a test; it only asks. After asking, it asks again only after about three months, and a new upload restarts the count. Tapping opens the document upload. It follows the "Invitation to complete" switch (Profile › Notifications), which comes on and you can turn off. Dependent and managed profiles are left out.
- Food diary notices (since version 3.29; only for the account holder, on their own profile). Until version 3.28 the food diary generated no notifications; it now generates two, both LOCAL (on your device, with no sending server), of fixed text and with none of your data — never what you ate, calories, nutrients, your goal or any judgment. (a) Invitation to choose the goal — if you opened the Nutrition tab and have not yet chosen a goal, the app may invite you: "Your eating goal" / "It takes a minute to choose your daily goal. With it, the diary shows how each day went." There are at most two, once only (the second, a week after the first); choosing the goal ends the invitation. It follows the "Invitation to complete" switch. (b) Meal reminder — it comes OFF and exists only if you turn it on in Profile › Notifications › "Food diary": with it on, at 8 pm (or at the first time outside your quiet hours) the app asks "Logged today's meals? A photo or a line of text is enough." — only on days when no meal has been logged. To decide whether to ask, the app checks, on your device, only whether any meal is logged that day — not its content. The reminder is scheduled for the following seven days each time you open the app; if you go a week without opening it, it stops by itself. You can turn it off whenever you like, with immediate effect. Your choice (on or off) is kept with the other notification preferences of your account.
- Come-back invitation — fourth wording (since version 3.29). The come-back invitation described above gains a wording, delivered in place of the generic one — at the same moments, with the same cap and under the same switch — only when it is true that your analysis was redone after you last opened the app: "There is something new since your last visit — your portrait has been updated." It says that something is new, never what: no health data, test name, count or judgment. To know whether it is true, our server compares dates it already kept (that of your last analysis and that of your last opening of the app) — nothing new is collected.
- Recheck and update reminders are educational and universal. Some reminders flag that it may be time to repeat a routine test, update a record (e.g., weight), or check a follow-up/device. They are based only on generic reference intervals (e.g., routine tests are usually repeated periodically) and on the dates of your own records — we collect nothing new, and the app does not compute an individual interval from your result. They are not an individual clinical recommendation: the right interval should be confirmed with your doctor.
13. Cookies, telemetry, and tracking
- Install source (Apple Search Ads / AdServices) — no IDFA and no cross-app tracking. When you download the app after seeing one of our App Store ads, Apple makes a temporary code available to the app for about 24 hours, which our server exchanges with Apple itself for campaign data: which campaign, ad group, keyword, country, and whether it was a new download or a redownload. We store this linked to your account so we can tell which ads bring people who actually use the app — and stop spending on the ones that don't. What does NOT happen: we do not use the IDFA, we do not ask for the iOS tracking permission (ATT), we do not combine this with data from other apps or websites, we do not share it with data brokers, and there is no third party involved — it is Apple reporting on our own campaign to our own server. Apple does not give us your name, email, or a device identifier. If the download did not come from an ad, the record simply says so ("organic"). Legal basis: legitimate interest in measuring the effectiveness of our own advertising, with no advertising profile (LGPD Art. 7, IX; GDPR Art. 6(1)(f)). The record is deleted along with your account and is included in your data export.
- Provider lookup in the US public registry (NPPES). If your device region is the United States, adding a healthcare professional offers a lookup in NPPES, the public provider registry maintained by the US government (CMS). When you use it, the app sends CMS only the name you typed — none of your data, no health data. The lookup is optional and happens only when you trigger it.
MyHealth is a native iPhone app (not a website), so it does not use browsing cookies in the traditional sense.
- De-identified technical telemetry: we collect minimal stability and diagnostics data (crashes, errors, performance), without health content, to keep the app safe and working. This is internal processing: we do not embed any analytics SDK or any third-party tracker. As a self-limited minimization measure, we keep this telemetry for up to about 12 months (see Section 12).
- Usage and navigation events: we record which screens you open, at which step an upload stopped and that a meal, a complete day or a goal was logged — never the content —, to find where the app stalls or confuses people. They stay linked to your account, without any health content, for up to 12 months, in internal processing — no analytics SDK, no third-party tracker and no advertising. Turn it off whenever you want in Profile › Privacy & consents › "Help improve the app".
- No third-party trackers with access to health data and no sale of data. We do not track across apps/sites for advertising purposes.
- App Store privacy labels: our App Store declarations reflect what is described here.
Today we do not use any third-party analytics or tracking tool; if that changes, we will update this Policy and the subprocessors page before activation, with a new notice — also reviewing the App Store privacy labels and the need (or not) for App Tracking Transparency (ATT).
14. Security incidents and notification
We maintain an incident response plan and record every incident involving personal data, including those not notified, for at least 5 years. If an incident may create relevant risk or harm to you:
- Brazil (LGPD Art. 48; Resolution CD/ANPD No. 15/2024): we notify the National Data Protection Agency (ANPD) and you, directly, within 3 (three) business days from when we learn that the incident affected personal data, in plain language, stating the nature of the incident and the category of data affected, the number of data subjects, the risks and possible consequences, the measures adopted and the recommendations for you to protect yourself. If it is not possible to notify each person, we will publish the notice in the app and on the website for at least 3 months.
- United States (FTC Health Breach Notification Rule, 16 CFR Part 318): as a vendor of personal health records, we notify you without unreasonable delay and within 60 calendar days of discovery at the latest — including in the case of an unauthorized disclosure — and we notify the FTC (and, when required, the media) within the rule's deadline; and we observe state deadlines (for example, 30 days in California).
- Canada: we report to the Office of the Privacy Commissioner of Canada and to you any breach that poses a real risk of significant harm, and we keep a record of every incident for 24 months; in Quebec, we report to the Commission d'accès à l'information and to the people affected when there is a risk of serious injury.
- GDPR (Art. 33–34): we will notify the competent supervisory authority, as a rule within 72 hours, and we will communicate to you when there is a high risk to your rights and freedoms.
- Other jurisdictions: when the law of the country where you live requires it, we will also notify the local authority within its deadlines — for example, the PPC (Japan), the PIPC (South Korea), the OAIC (Australia), the PDPC (Singapore), the Data Protection Board of India and the Privacy Commissioner (New Zealand) —, always following the shortest applicable deadline.
15. Your rights
You are the owner of your data and have rights guaranteed by the LGPD (Art. 18), the GDPR (Chapter III) and the data protection law of the country where you live — always whichever is more protective:
| Right | What it means | How to exercise it in MyHealth |
|---|---|---|
| Access / confirmation | To know what data we hold and obtain a copy (LGPD Art. 18, I–II; GDPR Art. 15) | View the full health record in the app; export it |
| Correction | To correct incomplete or wrong data (LGPD Art. 18, III; GDPR Art. 16) | You review and edit the data directly |
| Anonymization, blocking or deletion | To ask that unnecessary or excessive data, or data processed in breach of the law, be anonymized, blocked or deleted (LGPD Art. 18, IV) | Contact the DPO, or delete the item in the app |
| Deletion / erasure | To delete your data and account (LGPD Art. 18, VI; GDPR Art. 17) | Delete account / data in the app (see Section 12) |
| Portability | To take your data in a structured, interoperable format (LGPD Art. 18, V; GDPR Art. 20) | Export of your health record in FHIR R4 (labs, measurements, medications, conditions, allergies, vaccines, appointments, the food diary and the list of the documents you uploaded) and in PDF (Health Report); and of your account data in JSON (your conversations with the AI, consents, usage measurement and install source). The original files you uploaded open in the app and can be shared or saved one by one. Meal photos stay visible in your diary and are delivered, on request to the DPO, within 15 days. |
| Consent revocation | To withdraw an authorization (LGPD Art. 8, §5; GDPR Art. 7(3)) | Turn off a purpose (e.g., "AI Processing") in the settings (see Section 5) |
| Information on sharing | To know with whom we share (LGPD Art. 18, VII) | This Policy (Section 9) and the subprocessors page |
| Information about not consenting | To know what happens if you do not give an authorization (LGPD Art. 18, VIII). You may refuse the AI analysis and the transfer: the consequence is not being able to use the app (or, if you already have an account, staying in read mode), with no other penalty. | Each consent request says, on its own screen, what stops working without it (see Section 5); for the AI analysis and the transfer, on the acceptance screen and in Profile › Privacy |
| Objection / restriction | To object to a processing or request its restriction (LGPD Art. 18, §2; GDPR Art. 18 and 21) | Contact the DPO |
| Review of automated processing (LGPD Art. 20) | Document extraction is saved only after you review it; the educational reading and the points of attention are generated automatically by the AI, have no legal effect and decide nothing about you | You can ask the DPO for a review of any reading and for information about the criteria used (what the AI received and how the reading is produced); we respond within 15 days |
| View the access history | Transparency about who accessed what | Your access log is available |
| Petition to the authority (ANPD) | To petition against the controller before the national authority (LGPD Art. 18, §1) | Contact us (Section 1) and/or the ANPD — see "Complaints" below |
How to exercise: many rights are exercised directly in the app (review, export, delete, revoke consent). For the others, or if something does not work, write to our DPO (Section 1). We respond within the deadline of the law that applies to you — the shortest, when more than one applies (as a rule, up to 15 days under the LGPD; up to 30 days under the GDPR and similar laws; shorter deadlines, where your country's law sets them, prevail); grievances of residents of India are resolved within 90 days. Residents of India may nominate a trusted person to exercise their rights in the event of death or incapacity (DPDP Act, Section 14): that person's request, with the nomination, can be sent to the DPO (dpo@bas-ai.com).
Automated decisions (including for the purposes of Australia's APP 1.7 and section 12.1 of Quebec's law): computer programs decide, without human intervention, (a) blocking the registration of someone who declares an age below the one required for an own account (Section 11), based on the date of birth and the country entered; (b) enabling or blocking a feature according to the active consent and the region (Sections 2 and 5); (c) the consumption of your quota of pages, prompts and meal readings; and (d) recording that a dependent has reached the age of majority, based on the date of birth. The AI's educational reading decides nothing about you. To contest any of these decisions, contact the DPO.
Complaints: you can complain to the data protection authority of the country where you live — for example, the ANPD (Brazil, https://www.gov.br/anpd), the PPC (Japan, www.ppc.go.jp), the PIPC (South Korea, www.pipc.go.kr), the OAIC (Australia, www.oaic.gov.au), the Privacy Commissioner (New Zealand, www.privacy.org.nz), the PDPC (Singapore, www.pdpc.gov.sg), the Data Protection Board of India and the Information Regulator (South Africa); in Canada, see Section 15-B. We ask, however, that you talk to our DPO first — we want to resolve it directly with you.
15-B. Users in Canada (PIPEDA and, in Quebec, Law 25)
You can access and correct your data, withdraw consent, obtain a copy in a structured, commonly used format (FHIR R4 — section 27 of Quebec's law) and ask that the dissemination of a piece of data stop (section 28.1). The person in charge of the protection of personal information is Guilherme Kaschny Bastian (dpo@bas-ai.com). Your data stays in Brazil (São Paulo) and, with your consent, part of it goes to Anthropic in the United States (Sections 6 and 9). The AI's reading is educational and is not a decision about you; even so, you can ask for a human to review it and submit observations (section 12.1). We respond within 30 days. If you are not satisfied, you can complain to the Office of the Privacy Commissioner of Canada (https://www.priv.gc.ca) or, in Quebec, to the Commission d'accès à l'information (https://www.cai.gouv.qc.ca).
16. MyHealth is NOT a medical service
- MyHealth is a tool for organizing and educating about your own health, which prepares you for the appointment with health professionals and offers a supportive educational reading by AI.
- It does NOT diagnose, does NOT prescribe treatment, and does NOT replace the assessment of a doctor or qualified health professional.
- The readings and the AI assistant's responses serve to bring questions and information to your doctor — you must always confirm with your doctor before any decision.
- The food diary is self-logging with estimates: it is not a meal plan or a dietary prescription, it does not provide individualized nutritional assistance, counseling or education (activities reserved to nutritionists — Brazilian Law 8.234/1991, art. 3), it does not replace a nutritionist or a doctor, it does not identify or diagnose eating disorders and it must not be used to calculate an insulin dose. The limits the app applies to the personal goal (a minimum floor and refusing a goal below expenditure in certain situations) are the app's safety rules, not medical guidance or an intake recommendation.
- MyHealth is designed as an educational and organizing tool, and is not marketed as a medical device; it has no registration or notification with ANVISA, and it has not been evaluated, registered or cleared by the FDA (USA), Health Canada or any other health authority. It is intended to organize your data and offer an educational reading, and not to diagnose, treat, prevent or clinically monitor diseases. The regulatory classification of software depends on its purpose and on each country's law; if your country's health authority takes a different view, do not use it for diagnosis, screening or monitoring.
- In an emergency, seek medical care immediately — do not use the app for that.
17. Changes to this Policy and versioning
We may update this Policy to reflect changes in the app, in vendors, or in the law. The Policy has a version (policy_version):
- The app collects your acceptance at registration, tied to the version in effect;
- We update the version and the date at the top when there is a change;
- We notify you in the app and/or by email; and, when the change requires it, we will ask for a NEW acceptance — the app requires a new acceptance when the version changes — recording it immutably in our consent record.
The version history is published at https://www.bas-ai.com/myhealth/legal/versoes; each accepted version remains archived.
18. Contact us
Questions, requests, or complaints about your data:
- Officer/DPO: dpo@bas-ai.com
- In-app support: Profile › Support — the channel for usage questions, technical issues, and requests about your account.
- Account number: you can find it under Profile; give it to support so we can locate your account faster (including if you use "Hide My Email" in Sign in with Apple).
- Controller: BAS ARTIFICIAL INTELLIGENCE LTDA — CNPJ 64.106.409/0001-70 — www.bas-ai.com — Rua Gomes de Carvalho, 911, Vila Olímpia, São Paulo/SP, ZIP 04547-003, Brazil
- Subprocessors page: https://www.bas-ai.com/myhealth/legal/subprocessadores
MyHealth — your health record, sovereign and private. This Policy was drafted in Portuguese and translated into English and Spanish. In case of divergence between versions, the interpretation most favorable to you prevails; where there is no difference in favorability, the Portuguese prevails, unless your country's law requires otherwise.