MyFitLife Privacy Statement
Last updated: July 28, 2026
MyFitLife is a meal tracking and nutrition coaching app operated by IHP Technology LLC. This privacy policy explains what information the app collects, how it is used, and the choices available to users.
Information We Collect
Depending on how you use MyFitLife, we may collect:
- Account information such as email address and authentication identifiers.
- Food logs, saved meals, recent meals, recipes, shopping lists, hydration logs, macro goals, dietary preferences, fasting schedules and history, saved supplement labels and taken logs, weight or progress history, MyFit Score values, and profile settings you enter.
- Meal photos, selected images, generated recipe images, or food and supplement barcode scans you submit for app features.
- AI coach questions, generated responses, recipe prompts, food search queries, and related usage metadata needed to provide, secure, and improve app features.
- Technical information such as app errors, request timing, device or browser context, authentication state, quota state, and service logs needed for security, reliability, and abuse prevention.
- If you accept optional analytics on the public website, Google Analytics may receive pseudonymous page-view, browser/device, referral, and approximate location data to help us understand public-site usage. You can decline this analytics collection.
- Connected-app information such as the OAuth client, scopes you approve, token and consent status, and security events needed to operate or revoke an integration.
- Subscription lifecycle information such as app-store purchase or transaction identifiers, product and entitlement status, purchase and expiration dates, and renewal, cancellation, refund, or billing-issue status. MyFitLife does not receive your full payment card number from Apple, Google, or RevenueCat.
How We Use Information
We use information to:
- Provide meal logging, hydration and fasting tracking, supplement-label and taken-log features, nutrition planning, progress tracking, shopping list, recipe, and AI coaching features.
- Authenticate users and protect user-scoped app data.
- Provide connected-app features that you authorize through OAuth consent.
- Analyze meal photos, food search queries, recipes, and coach prompts when you request those features.
- Receive and respond to support requests that you choose to submit.
- Confirm Premium access, restore purchases, synchronize subscription status, and administer MyFitLife Family memberships.
- Maintain app security, diagnose errors, prevent abuse, enforce quotas, and improve reliability.
- Comply with legal, safety, and platform requirements.
Service Providers
MyFitLife uses service providers to operate the app, including Google Firebase for authentication, Firestore data storage, and Firebase Storage; Google Cloud services for backend hosting, job processing, and AI processing; Google Vertex AI and Gemini; Google Analytics for optional public-site measurement; Apple App Store and Google Play for subscription purchase and account management; RevenueCat for purchase validation, entitlement access, and subscription lifecycle synchronization; Stytch for connected-app OAuth authorization and token management; OpenAI when you direct MyFitLife to provide data to Codex; Open Food Facts; USDA food data services; and ERPNext/Frappe Helpdesk for support ticket handling when you submit a support request. These providers process information only as needed to support app functionality, security, reliability, and support operations.
Subscriptions and Billing
Apple or Google processes subscription payments through the store account you use. RevenueCat helps MyFitLife validate store purchases and synchronize Premium entitlement, renewal, expiration, cancellation, refund, and billing-issue status. MyFitLife may receive store purchase or transaction identifiers and subscription product and status details, but does not receive or store your full payment card number.
Codex and Connected Apps
Connecting MyFitLife to Codex is optional. The consent screen identifies the app and requested scopes before access is granted. The initial integration is read-only and can provide only the MyFitLife account goals and preferences, one requested nutrition day, recent progress check-ins, and grocery-list items covered by the scopes you approve.
When you ask Codex to use a MyFitLife tool, the requested tool output is sent to OpenAI to complete your request and is then handled under the terms and privacy choices that apply to your OpenAI account. MyFitLife does not send your password, payment-card data, support tickets, photos, coach conversations, or unrestricted profile record through these connected-app tools.
Photos, Camera, and AI Features
MyFitLife may request camera or photo library access when you choose to scan a food or supplement barcode, attach a food image, or analyze a meal photo. These features are optional. Nutrition estimates generated by AI or food databases may be inaccurate and should be reviewed before relying on them.
Health and Nutrition Information
MyFitLife is a general food logging, fasting, supplement tracking, and nutrition coaching tool. It is not medical advice, a medical device, or a replacement for professional medical care. Consult a qualified professional before making medical or diet changes based on app information. See the MyFitLife Health Disclaimer for more detail.
Data Sharing
We do not sell personal information. We may share information with service providers that operate app infrastructure, when required by law, to protect rights and security, or with your direction.
Support requests may be routed to IHP Technology LLC's helpdesk system with the details you submit, your account contact email if available, app version, platform, support category, and an internal user or case identifier. MyFitLife does not automatically attach nutrition logs, coach history, progress data, receipts, passwords, payment card numbers, or medical records to support tickets.
Data Security
We use Firebase Authentication, owner-scoped database and storage rules, HTTPS, backend authorization checks, OAuth scopes, short-lived access tokens, service identity controls, rate limits, and operational monitoring to help protect user data. No system can guarantee absolute security.
Data Retention and Deletion
We keep information while needed to provide the app, meet legal requirements, resolve disputes, and maintain security. Signed-in users can delete their full account in the app from More, Settings, Privacy & Safety, Delete Account.
Deleting an account revokes its Stytch connected-app grants and active connected-app tokens before MyFitLife account data and sign-in access are deleted. You may also revoke a connection from the connected app where that option is available or contact support.
To prevent delayed billing events from recreating deleted access, MyFitLife retains a one-way hashed account-deletion marker and deletion timestamp. This marker does not contain the account UID, email, profile, nutrition data, connected-app tokens, or billing details.
Support tickets and related correspondence may be retained separately when needed to resolve a request, maintain security, or satisfy legal and operational obligations.
Children
MyFitLife is not intended for children under 13. If we learn that we collected personal information from a child under 13, we will take appropriate steps to delete it.
Changes to This Policy
We may update this policy from time to time. Updates will be posted on this page with a new last-updated date.
Contact
For privacy questions, contact IHP Technology LLC at support@ihptechnology.com.
