App Privacy Notice
Last updated: 4 October 2026
Who is responsible for your information
MyBodyPath Limited, Irish company number 823059, provides MyBodyPath and is responsible for the processing described in this notice. Our registered address is 111 Brocan Wood, Monasterevin, County Kildare, W34 CH92, Ireland. Contact privacy@mybodypath.app about privacy and data-rights requests. For account or product support, contact support@mybodypath.app.
This notice covers the MyBodyPath app and its connected account services. The website has a separate notice. The app helps you record food, movement and personal habits; it is a general wellbeing and record-keeping service.
Information used by the app
| Information | Use and source |
|---|---|
| Profile and personal records | The age, height, weight, goals and planning preferences you provide; your food, water, body, activity and workout records; and related images you choose. The app displays your records, calculations and summaries. These records can reveal health information. |
| Connected health information | The categories you permit Apple Health or Health Connect to supply for the selected feature. Current declarations include steps, walking/running distance, exercise time, heart rate, weight and body fat; support differs by platform and device. |
| Workout location and motion | Device readings during a workout you start, including while the screen is locked where tracking is supported, to record route, distance and pace. |
| Account and sign-in information | Account identifiers, verified sign-in details, account state and security/session information supplied by you and the chosen sign-in provider. A Google profile image may be retrieved for your local profile. |
| Selected account preferences | Measurement/display units and Food Region if you turn on preferences sync. Theme and language remain device settings. |
| Service and support information | Technical connection/request information, account-support and deletion status, consent/authorization evidence where collected, and information you separately choose to send with a support request. |
Records on your device and account connection
Your profile, Diary, body and weight records, workouts, and private meal, progress and profile photos are stored locally. Signing in does not automatically upload, merge or restore this history. Choosing Keep this profile explicitly connects the existing local profile to the verified account on that device. Another account cannot silently take over that profile. Signing out locks the retained account profile; the same verified owner can reopen it.
Preferences sync is optional and limited to the selected preferences above. It does not sync the full Diary, workout history or private photos.
You can separately export an encrypted account backup containing selected profile, saved-record and workout data and product images. Private meal, progress and profile photos are excluded. You choose the destination and protect the recovery code. Restoring requires the code and the same verified account, replaces the destination profile after confirmation, and leaves preferences sync off. Copies you save or send to another device, person or service are outside automatic cloud-account deletion.
Local storage and encryption reduce exposure; they do not make a device, exported file or account immune to loss or misuse. Keep your device, sign-in method and recovery code secure.
Choices before optional features
Camera and photo access is used when you choose to take or select an image. The current app has no configured remote meal-recognition service. Selecting a private image does not by itself authorize a recognition upload. Before any new upload service is offered, its recipient, data and purpose will be explained and a separate choice provided.
You choose whether to connect supported health categories. Device health settings let you revoke permission for future reads. That permission is separate from health-data consent and does not itself remove records already saved in the app.
You choose whether to allow location/motion for a selected outdoor workout. Disabling location affects location-based tracking. Displaying an online map requests tiles for the viewed area; the map provider receives that area and connection information. The saved full workout route is not uploaded by the tile request.
Terms acceptance, acknowledgement of this notice, an operating-system permission and a health-data consent are separate actions. When consent is the basis for a purpose, we explain the information and purpose before asking for it. Optional choices are not preselected. You may decline an optional feature without agreeing to unrelated processing.
Purposes and legal bases
We use account and service information to provide and secure the account services you request. For a valid service contract, processing objectively necessary to provide that service uses the contractual-necessity basis. Proportionate account security, abuse prevention and handling service requests use our legitimate interests, subject to the required balancing of your rights, with particular care for children. Specific legal obligations may require limited processing.
Where the service uses consent for a purpose, including a consent-based minor account purpose or optional preferences sync, the appropriate person makes a separate choice and can withdraw it. We do not treat acceptance of all the Terms as consent to every use of information.
For purposes using health information on the basis of consent, we ask for a specific explicit consent covering those health records and their display, calculation or summary purpose. That is separate from the ordinary Article 6 basis and supplies the Article 9 explicit-consent condition where required. We do not use a healthcare-treatment exemption merely because this is a wellbeing app. The valid decision-maker for a teen depends on the applicable purpose and capacity rules, as explained below.
Services that receive information
| Service | Information and role in the current app |
|---|---|
| Supabase | Account authentication, state, optional preferences, account security and deletion. Account identifiers, verified sign-in details, selected preferences and necessary technical information. Both the account database and the separate deletion-evidence database currently use Frankfurt, Germany, eu-central-1. |
| GitHub | A private repository holds encrypted, limited account-deletion evidence used to prevent a deleted account reappearing after recovery. This is not a Diary, workout or photo backup. GitHub also processes repository/account and connection metadata. |
| Google and Apple | The sign-in method you choose verifies identity and exchanges the information needed for that sign-in. A Google image may be retrieved for the local profile. Device health access remains governed by your separate permissions. |
| Resend | Transactional service emails and the recipient/delivery information needed to send them. Email processing can involve the United States. |
| Open Food Facts and its image hosts | A barcode or search text you submit, image requests and technical connection information for product lookup. The full Diary is not uploaded by that lookup. |
| OpenStreetMap tile service | Viewed map-area tile requests and technical connection information when an online map is displayed. |
Restricted support tools expose account-support status, rather than the contents of your private Diary, body, health, location or photo records. If you separately send a support attachment, screenshot, recording or backup, you disclose its contents by that action. Send only what is needed to resolve the issue.
We do not sell personal information or share it for cross-context behavioural advertising. The app's selected features do not authorize an advertising tracker or optional third-party sharing of your private health records. Technical account, map and lookup information can still indicate app use, health interests or an area; “private records stay local” does not mean no information reaches a service.
International processing
The Frankfurt database locations do not mean every support operation, email, provider log, subprocessor or recovery copy is processed exclusively in Germany or the EEA. Sign-in, email and recovery services may process information in other countries, including the United States. Encryption of deletion evidence does not remove international-transfer responsibilities.
Applicable transfers require the relevant legal protection, such as a valid adequacy arrangement for the recipient and processing, or appropriate contractual safeguards and associated protections. Contact privacy@mybodypath.app for the arrangements applicable to your information and how to obtain a copy. We do not use a general optional-feature checkbox as consent to every international transfer.
Retention and deletion
You control your local records through the app's record-removal and local-profile controls. Cloud-account deletion and local-profile removal are separate.
The current operational target is to complete an accepted live-cloud account deletion within 24 hours; completed request receipts remain available for 30 days. Outages, failed execution or a recovery hold can delay completion, and the app must continue to show the request as pending until completion is verified. These targets do not promise physical erasure of all recovery copies within 24 hours.
Limited deletion evidence and its required keys are retained while a recoverable copy could restore the deleted account. Deletion must be reapplied before a recovered service reopens. A fixed erasure date for every provider recovery copy is not currently established.
Security, diagnostic, support and consent/authorization evidence is retained only for its justified service, security, accountability or legal-claims purpose. There is currently no verified automatic maximum for all provider logs, support records or consent records. The planned 30-day audit and 14-day diagnostics targets are not enforced maximums; detailed security-audit pruning is not currently enabled. We assess retention and erasure against the relevant legal obligations and your rights rather than treating indefinite retention as a permitted default.
Your rights and requests
Subject to applicable conditions, you can request access, correction, deletion, restriction or portability, object to processing, and withdraw consent. Withdrawal does not invalidate earlier lawful processing; it stops future processing relying on that consent and can affect the related feature. We assess whether records must be erased or retained on another independently justified basis and explain that result. Revoking an OS permission, withdrawing consent and deleting an account are different controls.
Contact privacy@mybodypath.app. We use proportionate verification to protect your records. An authorized representative may act where the relevant rules permit; a parent does not automatically own or receive unrestricted access to a teen's data. We explain a refusal, any applicable appeal and the relevant deadline. We do not penalize you for exercising privacy rights.
You can complain to the Irish Data Protection Commission or another competent authority. UK users can contact the ICO; Swiss users can contact the FDPIC.
Teen privacy and participation
MyBodyPath's minimum product age is 13. Ages 13–17 receive food/activity logging and healthy-habit support, without automatic adult calorie-deficit targets, aggressive dieting, fasting plans or weight-loss deadlines. Age and territory checks are separate from app-store content ratings.
For consent-based online-service processing, local digital-consent thresholds differ, and the applicable law for the service must also be considered. Health-data consent and agreement to service terms require their own authority/capacity assessment. We explain when a parent or guardian must act, verify their authority proportionately, and also explain the choice to the teen. We do not interpret a child's “my parent agrees” box as verified guardian authority or give a guardian automatic access to private entries.
Teen-directed choices are requested when an applicable age transition changes who may consent. Moving into the adult product experience does not silently enable preferences sync, private-record uploads, advertising or new health purposes.
Regional information
The EU/EEA GDPR protections relevant to MyBodyPath's Irish establishment apply alongside additional applicable local protections. UK users also have the applicable UK GDPR rights. Swiss information is subject to the applicable Federal Act on Data Protection, including rights of information, access and correction and the relevant remedies concerning processing.
US residents should also read the separately linked Consumer Health Privacy Notice. Where applicable, state rights include confirmation/access, correction, deletion, portability, limits or choices concerning sensitive information, authorized-agent requests and appeal of a refusal. California's “sharing” for cross-context behavioural advertising has a particular legal meaning. We do not sell information or perform that advertising sharing; there is no sale opt-in hidden in these Terms or privacy choices. Local law controls any additional right and its conditions.
Changes
We explain material changes before they take effect where required and request a new choice if a new purpose needs consent. A future cloud-sync, recognition, payment or AI provider will be disclosed before that processing is enabled; this notice does not authorize it in advance.