PRIVACY POLICY

Your information and MyHealthPrep.

Effective date: 23 October 2026.

MyHealthPrep operates the service under the name MyHealthPrep. This policy describes its website and mobile app. Contact legal@myhealthprep.com about privacy or a data request. Features and recipients depend on what you use and the app version available to you.

Information used to run the app

We process account identifiers, email and sign-in information to create and secure accounts. If you provide them, we store profile details and body measurements, goals, nutrition targets, meals, recipes, shopping lists, workouts, progress entries, and uploaded media to provide the features you use. We also process device and app information needed for security, synchronization, troubleshooting, and support. Your device can hold sessions, drafts, pending changes, and cached account data.

Support requests may include your contact details, message, and attachments you choose to send. Technical details and a limited local diagnostic excerpt are optional in the app’s bug-report flow. Please remove unrelated personal information from messages, images, and screenshots.

Food, recipes, voice, and outside services

Supabase provides account, database, and file-storage infrastructure. Food searches and barcode lookups may query Open Food Facts. If you use AI food or recipe features, the submitted food text, speech transcript, recipe content, or image may go to outside AI services. Depending on the feature, requests can go directly to DeepSeek or through OpenRouter. Configured OpenRouter recipe routes include providers serving Alibaba Qwen, Xiaomi MiMo, and OpenAI models; the provider selected for a request can vary. These inputs may themselves contain personal information. Ordinary food-parsing requests do not automatically attach your stored weight, profile, email, or account identifier. Recipe screenshot imports use signed image links whose storage path can include your account identifier.

Voice recognition uses your device’s speech service and may involve its provider; the resulting text can be sent through the same food-processing path as typed input. The app does not currently connect to Apple Health or Google Health Connect. We do not promise that an AI provider does not retain inputs or use them for training; those practices depend on the provider and configuration in effect. Avoid putting passwords, sign-in codes, payment details, or unrelated sensitive information in AI inputs.

Native purchase features are still being integrated and tested. If enabled, the relevant app store processes payment, and RevenueCat may receive an app account identifier and purchase or entitlement information to manage access. This site has no purchase, signup, waitlist, or analytics form. It serves its fonts and images locally. Cloudflare hosts the site and may run browser security checks that process connection and browser signals and set a security cookie. Opening an email link uses your email service, which processes the message so we can receive and answer it.

How information is used and shared

We use information to provide requested features, maintain accounts and synchronization, answer support requests, prevent abuse, diagnose failures, and meet applicable obligations. We share the information needed for those purposes with the infrastructure and feature providers described above, with an app store or billing provider when purchases are enabled, and when legally required. Acceptance of this policy does not replace any separate permission required for device access or sharing. Device permissions can be changed in system settings; withdrawing one stops future use of that permission but does not erase information already submitted.

Retention and deletion

Account-linked profile, meal, recipe, workout, progress, and upload records are used while the account and relevant feature exist. You can edit or remove many entries in the app. A saved meal-history entry may still contain recipe details after a recipe is removed. Uploaded recipe screenshots and unfinished imports can remain in account storage beyond extraction. Device caches, drafts, pending changes, cloud records, support messages, provider logs, and backups have separate lifecycles; uninstalling the app does not delete a cloud account.

When an account deletion request is accepted, the deletion process removes the account and its associated app records. Limited information may remain where needed for security, fraud prevention, accounting, dispute handling, or a legal obligation. Restricted recovery backups may continue to hold earlier copies until they expire. Information already sent to an outside service can follow that provider’s own retention rules. Maximum retention periods for backups, screenshots, support records, and provider logs differ and are not yet published. Contact us for the status of a particular deletion or retained record.

To request account deletion, use the in-app steps or the email request route. We verify ownership before acting on an email request. To ask about access, correction, deletion, or another applicable privacy right, contact legal@myhealthprep.com. The rights available and any lawful exceptions depend on your location and circumstances.

Security and updates

We use account authentication and access controls to protect stored information, but no service can guarantee absolute security. We may update this page as features, providers, and retention practices are confirmed or changed; the date above shows this version. Questions can be sent to legal@myhealthprep.com.