Privacy Policy · myfitplan

Your privacy is important to us. This policy explains how we collect, use, share, retain, and protect your information when you use the myfitplan website or mobile app.

1. Information we collect

We collect information you provide during the use of our service, including:

Account and contact information, such as your name and email address
Sign-in data via Sign in with Apple or Google Sign-In (name, email, profile picture), depending on which method you choose
Onboarding, nutrition, and self-reported health information, including age, sex, height, weight, body measurements, activity level, goals, dietary preferences, allergies and intolerances, pregnancy or breastfeeding status, and medical conditions or medications entered in free-text fields
Coaching chat messages you write
Meal logs, check-in answers, progress photos, meal photos, and barcodes you choose to submit
Product analytics and telemetry, including interaction events, a persistent internal user identifier, and crash or error data. Mobile session replay is currently disabled in production; web replay is described below
Purchase and subscription status, processed through the Apple App Store or Google Play
Device identifiers

2. How we use your information

The collected information is used to:

Generate and adjust your personalized nutrition and training plans
Provide coaching responses, meal-photo and barcode analysis, and quick calorie estimates
Save and display your progress history
Send re-engagement communications based on your journey
Analyze product usage, diagnose errors, and improve service and AI-response quality

AI processing is used only to provide nutrition-plan, meal-analysis, and coaching features. myfitplan does not use submitted material to train its own AI models. We do not sell health data or use it for advertising, marketing, profiling for ads, or data mining.

3. Data sharing

We do not sell your personal data. We disclose only the data needed to the following service providers. We require providers that access personal data to protect it consistently with this policy and applicable law:

Convex (mobile app) — Data: account records, health and nutrition inputs, plans, check-ins, meal logs, chat records, subscription status, device push tokens, and uploaded photos. Purpose: host the mobile backend, files, and application data.
Supabase (website) — Data: website account and authentication information, plans, progress records, survey responses, waitlist records, and website files. Purpose: host the website backend, database, authentication, and storage.
OpenAI (mobile app and website) — Data: health and nutrition inputs needed for the requested feature, coaching messages, and meal photos submitted for analysis. Purpose: generate and adjust nutrition plans, analyze meals, answer coaching requests, and provide calorie estimates—not advertising or marketing. Models currently include gpt-5.6, gpt-5-mini, gpt-4o, and gpt-4o-mini. OpenAI may retain abuse-monitoring logs for up to 30 days, subject to its stated legal and safety exceptions.
PostHog (mobile app and website) — Data: product-analytics events, internal user identifiers, device and interaction data, errors, and—on mobile AI flows—prompts and completions captured for LLM observability, which can include health inputs, coaching messages, submitted meal images, and generated responses. Purpose: analytics, debugging, feature flags, and AI quality review. Mobile session replay is disabled in the current production configuration; if enabled later, text inputs, images, sensitive views, and chat bubbles are masked. PostHog session replay is not enabled on the website.
Sentry (website) — Data: account identifier, crash and error diagnostics, logs, performance traces, and web session replay. Purpose: diagnose failures and improve reliability. Production web replay is sampled for 10% of sessions and sessions containing an error; Sentry's replay masking controls apply.
RevenueCat (mobile only) — Data: purchase and subscription data. Purpose: process and manage mobile billing and subscription status.
Clerk (mobile app) — Data: account, sign-in, authentication, and session information. Purpose: authenticate users, secure sessions, and manage mobile accounts.
Apple and Google (mobile app) — Data: sign-in information, purchases, subscription history, device and push-notification tokens, as applicable. Purpose: authentication, in-app purchases, subscription management, and delivery of notifications.
Expo Push Service (mobile app) — Data: Expo push token and notification payload. Purpose: deliver transactional push notifications requested in the app.
IPinfo (mobile app) — Data: the IP address received by our backend. Purpose: derive and save a country code for regional defaults and compliance.
Open Food Facts (mobile app) — Data: the barcode you scan, without your account identifier. Purpose: retrieve public product and nutrition information.
Stripe (website) — Data: payment, billing, customer, and subscription information. Purpose: process and manage website purchases and subscriptions.
Resend and Loops (website) — Data: email address, name, locale, and messaging status. Purpose: send transactional or requested lifecycle emails and manage contact preferences.
Vercel (website) — Data: network request information, including IP address, device/browser data, and operational logs. Purpose: host, secure, and deliver the website.

OpenAI references: API data-usage policy · Data Processing Addendum

4. Authentication and security

We support secure sign-in through Sign in with Apple and Google Sign-In. Access to your data is protected using industry-standard security practices, including encryption in transit and at rest and secure session tokens.

5. Your rights

Under applicable privacy laws, including Brazil's LGPD, you can:

Confirm whether we process your data and request access to it
Request correction, portability, or a copy of your personal data
Delete your account and associated data at any time, subject to legally required retention
Withdraw consent or object to processing where applicable
Revoke myfitplan's access granted through Sign in with Apple or Google Sign-In

Before myfitplan first sends any of your data for AI processing, the mobile app asks for your explicit agreement on a dedicated screen that names the providers, the data sent, and the purpose. You can review that consent at any time in the mobile app at Profile → Privacy & data → AI processing, which shows the date you agreed and the way to withdraw. To withdraw consent to future AI processing, delete your account, either from that screen or at Profile → Danger Zone → Delete account. There is no separate AI-processing toggle. Deletion stops myfitplan from sending new data for AI processing. For any privacy request, or if you cannot access the app, contact support@myfitplan.ai.

If you signed in with Apple, you can revoke myfitplan's access in your Apple ID settings here

If you signed in with Google, you can revoke myfitplan's access in your Google Account permissions here

6. Data retention

We retain your personal data while your account remains active. The following rules apply when you delete it:

When mobile account deletion is confirmed, myfitplan immediately deletes the Clerk authentication user and purges the account’s data from active Convex tables and stored photos. The mobile account cannot be recovered.
A minimal deletion tombstone containing only the mobile authentication identifier and deletion timestamp remains for 30 days to prevent replay of previously issued authentication tokens, then is automatically deleted.
myfitplan’s immediate deletion is separate from OpenAI’s API retention. OpenAI may retain API inputs and outputs in abuse-monitoring logs for up to 30 days, subject to its stated legal and safety exceptions. This is not an account-recovery period.

7. Storage

Your data is stored using secure, industry-standard cloud infrastructure, in compliance with modern data protection practices.

8. Contact

For questions, requests, or data deletion, send an email to: support@myfitplan.ai