Privacy Policy

1. Who is responsible for your data

My Health Engineer ("MHE", "we") is the data controller. My Health Engineer is the registered business name (Companies Registration Office no. 768945) of Keith Young, a sole trader based in Ireland, trading as My Health Engineer. Contact for any privacy matter: support@myhealthengineer.com.

2. The data we collect

Depending on how you use MHE, we hold:

• Account details: name, email, password (hashed) or Google or Apple sign-in, and security data (sessions, two-factor settings). If you sign in with Apple and choose Hide My Email, we hold the relay address Apple gives us, and our emails reach you through Apple.
• Health information you give us when you set up (special category, Article 9): date of birth, biological sex, height, body-fat where you provide it, medical conditions and medication flags you choose to share, pregnancy or breastfeeding status where you tell us, your stated health concerns, your sleep and fasting windows, your daily water target if you set one, and two optional facts if you answer them during plan setup: how you usually log workouts, and how most of your food is made. Wherever you pick an "Other" option, we store exactly what you typed. If you choose the cycle-phase refeed schedule, we also hold the cycle details you enter for it: last period start date, cycle length, and whether your cycle is regular. This is the core of how MHE personalises and keeps your plan safe.
• Health information you log as you go (special category, Article 9): your trackers, check-ins and reviews over time, which cover weight and the tape measurements you choose to log (waist, hips, upper arm and thigh), what you eat against your targets (calories, protein, carbohydrates, fibre), the food diary itself where you use it (the specific foods and portions you log against each meal, including foods you name yourself, with their nutrition figures recorded as they stood when you logged them, and a photo of the meal if you choose to add one), water and electrolytes, blood ketones, sleep hours and quality (your nightly sleep rating, and where you choose to add detail, how many times you woke, roughly how long you were awake, and what woke you, picked from a fixed list), bedtime and wake time, stress, energy, hunger and cravings, symptoms you tick (for example headaches, dizziness, fatigue, cramps, muscle soreness or digestive changes), workout sessions down to individual sets, habit streaks, and your weekly review answers (how the week went, what felt difficult, and any figures you type into the review, such as a weigh-in or average steps). Your daily check-ins ask for numbers, ratings and fixed-option answers. The morning and evening check-ins also have one optional notes box, up to 1,000 characters, for anything that explains your numbers. We store what you type there with that day's check-in. The box says your coach can read it. Today that means our admin team (Keith, MHE's founder), who read the last 28 days of notes in the staff coaching view. They see your notes under your member code, not your name, unless you are a coaching client (section 3). You can leave it empty, and you can clear a note at any time. Please keep other people's details out of it. It also includes the sleep and stress self-checks you fill in when you set up a plan and every couple of weeks after: how long you take to fall asleep, how often you wake and what wakes you, your usual bed and wake times, and how the last fortnight has felt. If one of those answers prompts us to suggest speaking to your doctor, we record that we showed you the prompt and whether you told us it is already being looked after. We never record what the diagnosis or the treatment is, and we do not ask. On the programs built around a clinical marker, it also includes readings you enter yourself on the Markers tab: blood pressure, HbA1c, fasting glucose, total cholesterol, LDL, HDL and triglycerides. We never receive results from a lab, a clinic or anyone else. We hold only what you type, and only for the markers your program tracks.
• Step counts from your phone, if you allow it (special category, Article 9): in the MHE phone app, and only if you give permission, we read your daily step count from Apple Health on an iPhone or Health Connect on Android. We read steps and nothing else. We only read, and we never write anything to your phone's health data. We store one total for each finished day. We never store today's count while it is still climbing, and we skip days with no steps. The app asks for access at the plan-setup step that asks for your usual daily steps. If you allow it, we read your last 14 days and fill in your average. You can change that number, and the step has a button to read from your phone again. If you say no, you type a figure to carry on. If your plan was set up before you had the phone app, your activity log has a "Connect your phone's steps" button that asks for access when you tap it. Your dashboard never asks. Once you have allowed access, we read your recent finished days when you open your dashboard, at most once every 6 hours. We also read your older step history once, a year at a time, back to 2010 at the earliest. If you stay away for more than a few weeks, we fill in the missed days when you come back. On Android, Health Connect only shares data from about 30 days before you first allowed access. If you also let the app read older data, we read your history again to pick it up. We use your steps to set your activity level, which sets your calorie and macro targets, and to show your weekly activity in your coaching reports and to your coach. We also chart them on your dashboard. Once your phone shares steps, anything you type is added on top, for a walk your phone missed. A day's total you typed before connecting stays if it's at least 500 steps above your phone's count for that day. Otherwise your phone's count replaces it. Apple Health and Health Connect keep this data on your phone. They may also back it up to your own iCloud or Google account, depending on your settings with Apple or Google. We read only from the store on your phone. We copy the daily totals from there to our own servers (section 4), and we send nothing back to your phone's health data or to Apple or Google. We never use step data for advertising, never sell it and never share it. You can turn off access at any time in your phone's Apple Health or Health Connect settings. That stops new reads. The steps we already stored stay in your account until you erase your daily logs or delete your account, and they are in your data export. The website does not read step data. We do not connect to any watch, ring or other wearable, and we read no other health data from your phone. We may offer more later, because a wearable can record things that are tedious to log by hand, such as heart rate, sleep stages or workouts. If we do, it will be your choice, off by default, one service at a time, and you will be able to disconnect it and delete what it sent us. We will tell you before any of that goes live rather than quietly widening what this policy covers.
• Plans and progress: your computed nutrition and training plans, weekly planner history, and any plan setup you started but didn't finish (we keep unfinished drafts so you can pick up where you left off).
• What we work out from your data (special category, Article 9): the app's own estimates learned from your logs, which cover your derived daily energy use and how confident the model is in it, the history of every calorie-target change we've proposed or applied (shown to you on your dashboard, with a revert option), and an internal flag raised when your results stay off-model despite good logging, which drives the "note on your results" guidance, and your weekly coaching reports. The app reads your week's logs and answers, picks one area to focus on, and writes the report from pre-written coaching text with your numbers filled in. Each report is kept so the next one can show your progress. We generate these rather than collect them, and we treat them with the same Article 9 care as health information you give us directly.
• Meal-planning data: saved recipes, custom foods, weekly meal plans, kitchen inventory, and any photos you choose to upload (e.g. against a custom food), stored on a private bucket scoped to your account only. When you save a food or a recipe ingredient our ingredient database does not carry, its name also goes onto a shared improvement list, together with the quantity or nutrition figures you supplied, so the database grows in the direction of real use. That list holds no link to your account and none of your written notes. The food name itself is the one thing on it you typed, so a name that contains personal details would sit on that list without a connection to you. It is best to name foods plainly. A food you save from a barcode scan, or a database food whose figures you edit, goes on the same list the same way, with the barcode, so the database can be corrected from it. The food database you search is compiled from public composition tables and Open Food Facts. Where each row comes from, and the licences, are on the Food Data Sources page.
• Membership and access: your program entitlements.
• Former community sign-ups: if you typed your email into our former online community's joining question between 27 August and 24 September 2026, we hold that email address, your name, the date you joined, and the wording of that question. We do not use it to send you marketing email.
• The tester programme, if you join it:the email you applied with, your phone type (Android or iPhone), and on Android the Google account email you use in the Play Store. We also hold the access code you entered, which tells us which group you came from. We record when you agreed to take part and the version of the wording you saw. We record whether you ticked the box for tester perks and offers, with the time and the wording version, and whether we have added you to our perks list. We keep the dates we sent you each programme email. Once you verify your email, we add a "tester" tag to your account. It records that you took part, and it stays after the programme ends so we can offer testers future perks. All of this is in your data export. If you applied but never created an account, ask us at support@myhealthengineer.com for a copy.
• Your answer about sharing your wins: whether you have said yes or no to MHE showing something you posted to other members inside MHE. We record your answer, the exact wording you saw, and where you answered. If you change your mind we keep the earlier answer too, so we can always show what you agreed to and when. This record holds no health information. Your answer makes no difference to your account or your plan either way.
• A record of anything of yours we have shared, and where: if you said yes and we then shared something of yours, we keep a short entry saying what it was, where we put it, which version of the permission applied, and the date. If you change your mind, this record is how we find everything we shared and take it down. It holds a short description written by us, never a copy of your health information.
• Your consent to store your health information: each time you give this consent (section 3), we add an entry to a record we never edit. The entry holds the version of the wording you saw, a fingerprint of that exact wording, where you gave it (the account setup step or the one-time consent screen), and when. We keep this record for as long as your account exists, and we delete it with your account. It is in your data export.
• Your member code: a random code, such as M-7K3QX, that our staff see in place of your name when they review member records (section 3). We do not build it from your account details, and we never show it on the admin screens that hold names and emails. We keep it for as long as your account exists. It is in your data export.
• Your agreement to our documents: which version of our Terms of Service, this Privacy Policy and our Medical Disclaimer you agreed to, where you agreed (the account setup step or the update screen) and when. When we make a material change to one of them, the app shows you what changed the next time you open it, and asks you to agree before you carry on. We keep this record for as long as your account exists, and we delete it with your account. It is in your data export.
• Technical and app-state data: IP address, device/browser, usage analytics (see section 7), and operational app state such as your reminder preferences, the record of reminders you've snoozed or skipped, the record of which set-up emails we have sent you about your membership, and any opt-out you've registered for those set-up emails.

This section describes categories with real examples rather than a field-by-field inventory. The exact record we hold about you at any moment is the export you can download from your account page (section 6): that shows what the app holds about you at that moment, and it is yours. Section 6 names the records that sit outside it.

3. Why we use it, and our lawful basis

• To deliver your programs and plans. Lawful basis: performance of our contract with you.
• To run the tester programme, if you join it. We use your application to give you free premium access to the app until 00:00 Dublin time on 1 January 2027, to add you to our Android test in Google Play if you use Android, and to send you programme emails. You get a welcome email with download steps as soon as you apply, short check-ins on day 3, day 7 and day 14 (the last one has a link to give feedback), and one email on 1 January 2027 to say your tester access has ended. We skip that last email if you are paying by then. On an iPhone you install the app through Apple's TestFlight with a public link. Apple sees your Apple ID there, and we send Apple nothing about you. Lawful basis: performance of our agreement with you (Article 6(1)(b)). The required tick on the form records that you agreed to take part. We do not rely on it as consent. You can unsubscribe from every programme email except the welcome, which answers your application. Once you create your account, the app asks for the same separate health-data consent as it asks every member (see below).
• To recognise testers after the programme.The "tester" tag on your account lets us offer testers future perks. Lawful basis: our legitimate interest in thanking the people who helped us test the app (Article 6(1)(f)). Perks by email go only to people who ticked the perks box. If you want the tag removed, ask us and we will delete it.
• To process your health information (every category marked Article 9 in section 2: what you give us at setup, what you log as you go, and what we work out from it) so plans are personalised and safety gates work. Lawful basis: your explicit consent (Article 9(2)(a)). You give it with its own tick on the account setup step. That tick is separate from agreeing to our Terms and this policy, and it starts unticked. It reads: "I consent to My Health Engineer storing and using my health information to build my plans and reports." The small print under it says the consent covers your measurements, check-ins, questionnaire answers and the notes you write. It covers your phone's step count only if you allow step access. It also says that our team reviews member records to check the advice is accurate and safe. We record each consent you give (section 2). We never treat continued use of MHE as consent. If you agreed to an earlier version that combined this consent with the Terms, you see a one-time screen that asks for the separate consent before you can use your plans. You can choose instead to download or delete your data from your account page, or to sign out. You can erase any part of this data from your account page at any time (section 6 says exactly what each erasure removes). Deleting your account withdraws your consent completely (see section 6).
• Quality review by our staff. Our admin team (today, Keith, MHE's founder) can open any member's records in a staff coaching view. They do this to check that the plans, targets and reports the app generates are accurate and safe. In that view you appear under a random member code, such as M-7K3QX, not under your name or email. Your age shows as a band, such as 35-39, not your date of birth. The dates you joined and started your program show as a month and year. Lawful basis: your explicit consent (Article 9(2)(a)), the same consent described above, whose small print names this review. A member code does not hide what you write yourself. If you put your name or other identifying details into a check-in note, staff will see them. In the coaching view, staff can see the name and email of a member who is not a coaching client only by choosing a reason first: a safety concern, a member asking for support, setting up a coaching client, or another reason they write down. The app records each reveal in the security audit log (section 5), with the staff member, the reason and any details they add, and it then shows that member's name and email for 15 minutes. Separately, our admin screens for membership and support list members by name and email. Those screens hold no health information and no member codes.
• To share a win you post with other members, if you say yes. Lawful basis: your explicit consent (Article 9(2)(a)), asked separately from everything else and never required. This is separate from the consent to store your health information. It covers one thing only: showing something you posted to other members inside MHE. The question sits in your account settings, unticked by default, and nothing is shared unless you go there and say yes. You can change your answer at any time. If you change your mind, we stop sharing and we take down anything we have already shared. Nothing of yours goes to the public or into an advert on the strength of this answer. That would be a separate conversation with you, about that specific thing, every time.
• To keep accounts and the service secure (sessions, two-factor, audit logging, and limits on how often anyone can try to sign in, sign up, download a data export or send the tester form). Lawful basis: legitimate interest in protecting your data and keeping the service available.
• To improve the product via analytics. Lawful basis: our legitimate interest in understanding how features are used so we can improve them (Article 6(1)(f)). These events are behavioural only and carry no health information, nothing is stored on your device, and you can switch analytics off at any time from your account settings (see section 7).
• To decide what the recipe library and ingredient database add next. Lawful basis: our legitimate interest in improving the product (Article 6(1)(f)). Two inputs feed this: the anonymous improvement list described in section 2, and a periodic internal review of the recipes and foods members create, which tells us what people actually want to cook and track. That review is read-only, done by us and never by a third party, and what comes out of it is new curated content for everyone. Nothing that comes out of it identifies you or reuses your content.
• To send you marketing email, if you said yes to it. You can say yes on the tester programme form, which has an optional box, unticked to start, that reads "Email me tester perks and offers". Lawful basis: your consent (Article 6(1)(a)), given by ticking that box. We record your answer, the date, and the version of the wording you saw. You can withdraw at any time using the unsubscribe link in any marketing email, or by writing to support@myhealthengineer.com. Your answer either way has no effect on your membership or your tester access. Marketing email goes only to addresses with a yes on record, never to the wider member list. We run the marketing list in Brevo (section 4).
• To keep a record of who joined our former online community. Lawful basis: our legitimate interest in knowing who took part in it, for example to answer questions from former members (Article 6(1)(f)). Its joining question made members type an email address, so we do not treat that as a yes to marketing, and we do not email these addresses. We delete the record by 30 September 2027, or sooner if you ask.
• To publish aggregate outcome statistics. We may publish group figures such as "members who finished lost an average of X", including averages of clinical markers such as HbA1c or cholesterol. Any published figure is computed across at least 30 members, with no subgroup below 30, so nothing we publish can identify you. Nothing has been published yet.
• Coaching. If you take coaching with us, your coach can see the information you have entered in the app (your profile, plan, planner, logs, diary, training, assessments and reports) for the purpose of coaching you. That includes any notes you add to a check-in and any step counts your phone sends us. That may be on a call, or as a written review of what you have logged, sent to your Reports page without a call. Because coaching you is the service you bought, you appear in the staff coaching view under your name and email, not a member code. Lawful basis: the coaching agreement, and your explicit consent to store and use your health information (described above). Only our admin team can open members' records in the coaching view. Every time they open a member's records there, the app writes the time, the staff member, the account and the section to the security audit log described in section 5, and the database refuses any edit or deletion of that log, apart from removing the link to your account when you delete it. The Coaching terms say what coaching is and what you can do.

4. Who processes your data, and where

We use a small set of processors. Your database sits in the EU. Each line below says where the provider is and, for a provider outside the EU, the safeguard that covers the transfer, or that none is in place. For one provider this is still being confirmed.

• Supabase: primary database and file storage. EU (Frankfurt).
• Vercel: application hosting. US/global edge, SCCs.
• Google:optional sign-in (email, name, avatar). If you join the tester programme on Android, Google also gets your Play Store email. We add it to our tester list in the Google Play Console, or you join our Google Group "MHE Android testers" yourself. Google needs it to let you install the test version. US, adequacy framework / SCCs.
• Apple: optional sign-in (email, which can be a relay address, and name). When you delete your account, we ask Apple to end the sign-in link. US, adequacy framework / SCCs.
• Resend: transactional and service email, including the welcome email when your membership opens app access and the tester programme emails. US, SCCs and the EU-U.S. Data Privacy Framework.
• Brevo: our marketing email platform and the list that runs it. It holds the people who said yes to marketing (section 3). For each of them it holds your email address, your consent answer and its date, and whether our emails reached you, were opened or were clicked. It also holds the sign-ups from our former online community: the email typed into its joining question, the name and the date, plus a marketing setting our old sign-up tool wrote, which we do not treat as a yes. We never send marketing email to those addresses. If you said yes on the tester form, it also holds a tester flag and the version of the wording you saw. EU (France).
• PostHog: product analytics. EU (Frankfurt).
• Sentry: error and performance monitoring, so we find out when something breaks before you have to tell us. It receives technical diagnostic data: the error itself, the page or route it happened on, timing, browser and device type. We never send it your health entries, your logs or your plan content. The page address can imply which programme you were using at the time, so we treat that as capable of revealing health information and it is covered by the same consent as the rest of your health data. EU (Germany).
• Our former online community platform: keeps the community, including the member list, members' posts and the answers to its joining questions, until we delete it. It is based in the US. We have no data processing agreement or standard contractual clauses in place with it.
• Google Sheets: holds the record of our former online community's sign-ups: the date, the name, the email typed into its joining question and the wording of that question, each marked so that we never email it. US, EU-U.S. Data Privacy Framework.
• Upstash: holds short-lived rate-limit counters so we can stop abuse. For data exports it counts requests against your account ID. For sign-in, sign-up and the tester form it counts requests against the IP address they come from. The counters hold request times and no content, and they expire within an hour. Region and DPA to confirm, see the Sub-Processor Register.
• Cloudflare Turnstile: checks that the person filling in the sign-up form is human, which stops bots using the form to send our emails to strangers. It sees the IP address and browser details of anyone who opens the sign-up page, and receives none of your account or health data. US. Transfer safeguard and DPA to confirm, see the Sub-Processor Register.

We never sell your data, and we never share special-category health information for advertising.

5. How long we keep it

We treat your account as a longitudinal health record across life stages, so we keep it for as long as your consent stands. We intend to ask you to re-affirm or revoke consent every 24 months, starting 24 months after your consent was given. That reminder is not built yet, and the first one cannot fall due before 2028. That includes two operational records worth naming because you might not expect them: unfinished plan-setup drafts are kept so you can resume where you left off, and the record of reminders you've snoozed or skipped is kept so your reminders behave correctly. Neither currently expires on its own. Setup drafts are removed when you erase your plans and drafts or delete your account. The reminder record is removed when you delete your account. We keep the record of your health-data consent, the record of your agreement to our documents and your member code for as long as your account exists, and we delete all three with your account.

When you delete your account, your data is removed. The deletion cascades across all your records, including uploaded files in storage, and we also instruct our analytics processor to erase the events tied to your account ID. Four things deliberately survive, and we would rather name them than have you find them. First, the security audit trail: its entries keep the email they were keyed by with the account link removed (including the record of the deletion itself) so we can show what happened and reconcile past access against our membership roster. This is retained personal data, not anonymised data, and it is the reason section 6's deletion right is described as reaching everything except this trail. Since 24 September 2026, the entries the app writes when staff open your records in the coaching view no longer hold your email. Entries written before that date still hold it, and entries from before that date for opening a member's page also hold the account ID. Like the rest of the trail, we have not set a date to delete them. Second, only if you had said yes to sharing and we had actually shared something: the entry saying what we shared, where, and the email it belonged to. Deleting your account counts as changing your mind, so anything of yours still shared is flagged for take-down at the same time. We keep the entry itself because it is how we find and remove whatever is still out there. Third, food names you contributed to the anonymous ingredient improvement list stay on it, because nothing on that list links to you (see section 2). Fourth, if you opted out of our set-up emails: the opt-out itself stays on the suppression list, because honouring an opt-out means remembering it, and any record of a set-up email sent to your address before your account existed stays keyed to that address the same way. To be precise about what "surviving" means: the link to your account is removed in every case (apart from the older coaching-view entries described above, which also hold the account ID), but the first two records and the email opt-out keep your email: that is retained personal data, held for the accountability purposes described, not anonymised data.

For marketing email: If you said yes, your address stays on the marketing list while your consent stands. If you unsubscribe or withdraw, we stop sending and suppress the address so it cannot be mailed again, and we keep the log of the consent itself (the answer you gave, its date and the question wording) and of the withdrawal, because we have to be able to show that history. For the tester form, a no is recorded once and that address never receives marketing email.

For the tester programme: your tester access ends at 00:00 Dublin time on 1 January 2027. On 31 January 2027 we delete the whole programme record: your application details, the group you came from, your agreement and perks choices, any unsubscribe from programme emails, and the dates we sent them. We delete it sooner if you delete your account or ask us to remove you from the programme. The access codes we give each group hold no member data, and we delete them on the same date. The "tester" tag stays on your account until you delete the account or ask us to remove it. If you applied but never verified your email, the tag never joins an account, and we delete it on 31 January 2027. If you ticked the perks box, your place on the perks list follows the marketing email rules above. By 31 January 2027 we also delete our Google Group for Android testers and our tester list in the Google Play Console. What Google keeps after that falls under Google's own privacy policy.

6. Your rights

Under GDPR you can, at any time:

• Access and export your data: download a complete JSON copy from your account page (Articles 15 and 20). The download holds everything the app keeps about you, apart from the narrow security material named in section 8. Some records sit outside the app, so they are not in it: the former community sign-up record in section 2, what our email platform holds about you, and your posts, member profile and joining answers on our former online community. Ask us at support@myhealthengineer.com and we will send you a copy.
• Correct your data: edit your profile in-app (Article 16).
• Delete your account and data permanently from your account page (Article 17). Deletion reaches everything except the small set of surviving records named in section 5. If you joined the tester programme, you can also ask us at support@myhealthengineer.com to remove you from it at any time, and we delete your programme record. Removing you also ends your tester access.
• Withdraw consent for health-data processing at any time (Article 7). Deleting your account withdraws it completely and ends all processing of your health information. Short of that, your account page lets you erase each health-data category on its own: your setup health profile, your daily logs, your exercise logs, your journals, your plans, or the estimates we derived. Erasing a category deletes that data, and some erasures reach further. Erasing your setup health profile also erases your plans and the estimates we derived. Erasing your daily logs also erases the estimates we derived. The estimates we derived include your weekly reports, your weekly review answers, and any coach reports and coach notes about you. Erasing your exercise logs or your journals also erases your weekly reports, your weekly review answers and any coach reports about you, because they are built from that data. Erasing your plans and drafts erases that category only. After you erase your setup health profile, the app asks for your date of birth and height again before you can carry on. Anything you log after an erasure is stored as normal, until you erase it or delete your account.
• Object to analytics (switch it off in your account settings and we stop immediately) and object to or restrict our other processing (Articles 18 and 21). That includes the tester tag, which we delete if you ask.
• Complain to the Irish Data Protection Commission (dataprotection.ie), your supervisory authority.

7. Cookies and analytics

We use an essential session cookie to keep you signed in. For product analytics we use PostHog, run in cookieless mode, to understand how features are used. Nothing is stored on your device for analytics: no analytics cookie, no local storage, no persistent tracking identifier. You are already signed in when you use MHE, so we have no need to tag your browser to recognise you.

We rely on legitimate interest for analytics (Article 6(1)(f)) rather than consent. The processing is limited to behavioural events on our own service, stays inside the EU, is never shared with third parties, and is never used for advertising, profiling, or automated decisions about you. We do not send your health values (conditions, medications, metrics) to analytics, and we deliberately do not record which health conditions or knowledge topics you read about, so an analytics event can never reveal your health status. You can switch analytics off at any time from your account settings and we stop immediately, on every device you sign in from.

8. Security

Your data is held on EU infrastructure, encrypted in transit, with passwords hashed and optional two-factor authentication. We exclude security-sensitive material (password hashes, two-factor secrets and backup codes, sign-in and OAuth tokens, short-lived verification tokens) from data exports so a downloaded copy can't be used to compromise your account. Beyond that named security material and the anonymous ingredient improvement list (section 2, which holds no link to you), the export contains everything the app holds about you. Section 6 names the records outside the app that we send on request.

9. Children

MHE is for adults aged 16 and over, matching the Irish digital age of consent. Date of birth is required during onboarding and under-16 dates are refused, both on the form and by the server behind it. We do not knowingly collect data from anyone under 16. If we learn an account belongs to someone under 16, we close it and delete the data. The tester form asks you to confirm you are 16 or older, and the account you then create asks for your date of birth as usual.

10. Changes and contact

We'll update this page when our processing changes, with the "Last updated" date reflecting the most recent revision, and flag material changes in-app. Questions or requests: support@myhealthengineer.com. See also our Terms of Service.