mealplan.fit App — Privacy Policy

This policy covers the mealplan.fit consumer mobile app for Android and iOS — the one you use to log meals, track habits, upload lab reports, and chat with our AI coach. If you're a dietitian using the web platform, please see our practitioner privacy policy instead.

We've kept this page intentionally short. If anything is unclear, email support@mealplan.fit and we'll fix it.

1. Who we are

mealplan.fit is operated by mealplan.fit Technologies, registered in India. Reach us at support@mealplan.fit.

2. What we collect

• Phone number — used to sign you in (Firebase phone OTP).
• Profile basics — first name, date of birth, gender, height, weight, activity level, dietary preference, primary health goal. You enter these during setup; you can edit them on the Me → Your profile screen.
• Health & fitness profile — likes, dislikes, allergies, medical conditions, medications, cooking context, goals, and freeform notes. These can be added by you on the profile screen, or proposed by the AI coach during chat (you tap Apply to save).
• Meal logs — meals you record (typed, captured by camera, or picked from suggestions): name, time, estimated macros, optional photo.
• Habit logs — water glasses, weight readings, activity sessions, mood entries, flare/symptom entries, fasts.
• Health Connect data (Android — optional) — if you choose to connect Health Connect, we read your steps, active calories burned, total calories burned, sleep duration, resting heart rate, and weight to show your daily activity and progress alongside your meals. Access is read-only, limited to those data types, and only happens after you grant it in the Health Connect permission sheet. See section 2b for full details.
• Lab reports — when you upload a PDF or photo of a lab report, we extract the markers (HbA1c, lipids, thyroid, vitamins, etc.) and your name as printed on the report. The original file is processed transiently and not retained.
• AI coach conversations — your messages and the coach's replies, so the conversation has memory across turns. Plus a small daily token-usage counter so we can apply fair-use limits.
• AI-generated meal plans — when you ask for a plan, the suggested meals + macros are saved so the app can show them and the coach can reference them.
• Coach proposals — short-lived records (24h TTL) of plan-edit, meal-log, or profile-update suggestions the AI made and is waiting for you to tap Apply or Skip on.
• Reminders you ask the coach to set (medicine, meals, check-ins).
• Device basics — app version, OS version, language, push notification token (if you enable notifications).

We do not collect: contacts, location, SMS, calendar, full photo library, microphone audio, biometric identifiers (fingerprint / face), or anything for advertising. Health & fitness readings (steps, sleep, heart rate, etc.) are only accessed via Health Connect, with your explicit consent — see section 2b.

2a. Device permissions we ask for

• Camera — only when you tap "take a photo" to log a meal or upload a lab report. The photo is sent to our servers for processing (meal recognition or lab marker extraction); the original image is not retained beyond extraction.
• Notifications — only if you accept the prompt. Used to send reminders you've set up (e.g. "take Metformin at 10pm") and occasional coach nudges. You can revoke from Android Settings any time.
• Biometric / device unlock — used by Android to encrypt your auth token in the device keychain (via expo-secure-store). We never see your fingerprint or face data; Android handles it locally.

We do not request: microphone, location, contacts, SMS, calendar, or background activity.

2b. Health Connect (Android health & fitness data)

mealplan.fit can connect to Health Connect on Android to read your health and fitness data. This connection is entirely optional — the app works without it, and we only read data after you explicitly grant permission in the Health Connect permission sheet.

• What we read (read-only): Steps, Active Calories Burned, Total Calories Burned, Sleep, Heart Rate, and Weight. We request read access only — the app never writes, edits, or deletes data in Health Connect.
• Why: to show your daily activity, sleep, and weight trends alongside your meals and goals, and to help the AI coach give context-aware suggestions. We only use this data to power features you see in the app.
• How it's stored: a daily summary (e.g. total steps, sleep minutes, resting heart rate, latest weight) is saved to your account under the same encryption and access controls as the rest of your data. We do not store the raw, per-sample records.
• Sharing: we do not sell or share Health Connect data with third parties, and we do not use it for advertising or any purpose other than the features described above. It is never transferred to data brokers.
• Revoking access: you can disconnect at any time in Android Settings → Health Connect → App permissions. Once revoked, we stop reading new data immediately. To delete summaries we've already stored, delete your account (Me → Delete account) or email support@mealplan.fit.

Our use of information received from Health Connect adheres to the Google Play Health Connect Permissions policy, including the Limited Use requirements.

3. How we use it

• Generate your AI meal plans and coach replies.
• Show you trends, adherence, and patterns across your logs and lab reports.
• If you link with a dietitian, share the relevant data with them so they can support you.
• Operate the service (auth, hosting, fixing bugs we find in logs).

We do not sell your data, share it for advertising, or use it to train third-party AI models.

4. Who we share with

• Google (Firebase Auth, Firestore, App Hosting) — auth, database, hosting. Data is encrypted at rest on Google's infrastructure.
• Google Gemini API — for AI plan generation, meal parsing, coach replies, and lab-report extraction. Inputs are not used to train Google's models per their API terms. Processing may occur on Google infrastructure outside your country (typically United States); Google's data-protection terms apply.
• Razorpay or Google Play Billing — only if you subscribe; they handle payment, we never see your card details.
• Your linked dietitian — if and only if you explicitly link to one. They see logs, lab reports, and goals; they do not see AI-coach chat content.

5. Where it's stored

Data is stored in Google Firestore — Mumbai region for users in India and Sydney for users in Australia. Files in transit use TLS 1.2+; data at rest is encrypted by Google.

6. How long we keep it

As long as your account is active. If you delete your account (see below), all of your personal data is removed within 30 days; most of it is removed immediately. We keep a minimal audit log of the deletion itself for 6 months in case of disputes.

8. Children

The app is not intended for users under 18. If you believe a minor has signed up, email us and we'll delete the account.

9. Updates to this policy

If we change anything material, we'll notify you in-app before the change takes effect. The "Last updated" date at the top of this page reflects the current version.

10. Contact

Questions, complaints, or requests: support@mealplan.fit.