Privacy policy
Updated 7 November 2026
MM Nutrition is maintained by Hamza Imdad. For questions about your information, contact pitchppt@gmail.com. This notice describes the Android account edition and this information website.
Your account data
In the account edition, Supabase stores your diary, food and nutrition records, measurements, workouts, saved foods, goals and account settings. Settings can include AI-provider credentials you choose to save. Each signed-in account has its own data. The app sends changes when you save them while connected; it does not wait for a scheduled backup. Graphs and statistics are calculated from the same account data.
The app keeps a separate local cache for each account so screens remain responsive and offline changes can be retained. Offline changes upload when the app reconnects; they are not stored remotely until a save succeeds. Signing in loads the account data. Signing out hides that account's local cache. Authentication tokens remain protected on the device and are not included in account-data documents.
Connections use HTTPS and normal account access is restricted by database row-level security. This account database is not end-to-end encrypted with a separate diary password: service administrators can access stored account records to operate the service. A backup encryption password is not required for ordinary account saving and loading.
Google sign-in and email authentication
If you choose Google sign-in, Google provides basic identity information, which may include your name, email address, profile image and Google account identifier. Supabase processes this information to create and authenticate your app account. The app uses your account ID and email to identify your account and keep its data separate. It does not request Gmail, contacts, calendar or Google Drive permissions.
For email authentication, Supabase processes your email address and password. Verification codes and recovery messages are delivered through Brevo. Brevo processes the recipient address and delivery information to deliver that message. Sign-in codes are for authentication, not marketing. These providers also process technical information needed to operate their services, such as IP addresses and security logs.
File exports and older encrypted backups
You can keep a separate file export. Password-encrypted exports and encrypted backup revisions from older previews remain separate from the primary account database. Their encryption passwords cannot be recovered through sign-in. Keep an export before updating or replacing an existing local diary. If two devices have conflicting edits, the app asks which copy to use and keeps a protected local recovery copy before replacing data.
AI, food lookup and other optional services
If you configure and use an AI provider, the meal descriptions, images and other request content needed for that action are sent to the provider you selected. Provider terms, retention and any charges depend on that provider. Signing in to MM Nutrition does not provide a shared AI subscription. Food searches and barcode lookups may send search terms or barcodes to Open Food Facts. Exercise illustrations and catalogues may be downloaded from external hosting services.
Crash reporting is off by default in the Google Play edition and the F-Droid-based account build. If you enable it, Sentry can receive diagnostic events, device/app details and a support identifier; optional heartbeat reports can include AI-provider choice and record counts. Names, meal contents, photos and API keys are excluded from heartbeat payloads. App settings provide reporting controls. Requests routed through the project's reporting proxy are also processed by that proxy's host. Do not include passwords or private diary contents in support messages or diagnostic submissions.
Camera, microphone and speech input
Camera and microphone access are requested when you use the relevant capture features. Live dictation uses the Android speech-recognition service selected on your device; that service may process audio under its own settings and privacy terms. Dictated wording remains editable. Recorded audio or selected food images are sent to your configured AI service when you request an estimate. You review the result before saving a meal.
Optional ChatGPT connection
If you connect your account to ChatGPT, the connection can read the nutrition information you authorise. Nutrition management requires your separate permission. Where enabled, requested routine edits can be saved through that connection; deletion proposals require the separate website confirmations. You can revoke the connection. ChatGPT and its provider process information you request through their service under their own policies.
Retention, removal and your choices
Changes and deletions made in the signed-in app are saved to the account when connected. Clearing Android app storage or uninstalling removes local data but does not delete the Supabase account; signing in again loads saved account data. Unsaved offline changes can be lost if you clear local storage before they upload. Older encrypted backup revisions remain separate until removed.
To request access, correction or deletion of account data and older cloud-backup information, email pitchppt@gmail.com from the address associated with the account. Account ownership must be verified before a request is carried out. Do not send your encryption password, sign-in code or a diary export. Use the account-deletion request page or Account → Request account deletion in the Android app to begin a support request. The request itself does not delete data; support verifies ownership before carrying it out. You can also remove Google's authorisation from your Google Account; that alone does not delete the Supabase account or backups.
AI content reports
If you choose Report AI content, you can review and edit the text before sending it to MM Nutrition. Supabase stores the selected text, reason, optional note, app version, report reference, timestamp and a random installation reporting identifier used for rate limits. The report does not automatically attach your photo, recording, account identity or full diary. Report text may contain personal or health information if you include it. Do not include passwords, API keys or sign-in codes. Reports are available to the developer for review and quality improvement; they are separate from optional crash diagnostics and are not used to train an MM Nutrition model. There is no automatic report-expiry promise. Contact pitchppt@gmail.com with your report reference to request access or deletion, subject to verification. Infrastructure providers may retain technical logs under their own policies.
Service providers and international processing
Google, Supabase, Brevo and any optional provider you use process data under their own terms and privacy notices. Infrastructure may process data in countries other than your own. The app's configured services and this policy should be reviewed before a public release.
This website and changes
These static information pages do not add analytics, advertising trackers or sign-in cookies. GitHub Pages hosts this website. GitHub logs visitors' IP addresses for security purposes. This notice will be updated when the app's data practices change.
Optional ChatGPT connection
This policy also covers the MM Nutrition ChatGPT bridge and connection/review webpage. Supabase authenticates your MM account and stores consent, connection permissions, proposed changes and execution receipts. Your MM password is sent to Supabase Auth. The ChatGPT tools do not receive passwords, provider keys, photos, recordings or app security settings.
At your request, synced meals, food names, portions, dates, nutrients and dated goals are shared with ChatGPT. If you enable nutrition management, allowlisted nutrition profile fields, dated weights and saved foods/recipes can also be shared and requested changes can update your MM account. These records may reveal information about your diet and body. Information returned to ChatGPT becomes part of your conversation under your OpenAI data settings. This connection does not create a second diary or start background conversations.
Read-only access is the default. Management is optional. Ordinary changes require website review unless you separately enable saves after values are shown in chat. Single meal or saved-food deletion always requires three website confirmations. You can change permissions or revoke access at MM connections. Revocation prevents subsequent bridge access; it does not erase your MM diary or previous ChatGPT conversations.
Proposed changes may contain the nutrition data being changed. Approval expires after ten minutes; expiry is not physical erasure. When a later proposal is created for that owner, the backend removes expired unfinished proposals and proposal records older than 30 days. Records can remain longer without a later proposal; no scheduled erasure deadline is promised. Permission/consent records and infrastructure backups or logs can remain subject to provider operation and retention. Contact support for an ownership-verified access or removal request; no fixed completion or backup-erasure deadline is stated here.
Vercel hosts the public MCP gateway, routing delegated access tokens and requested tool inputs/results to the protected Supabase bridge. The gateway source does not log request bodies or create a separate diary, and responses are not cached; Vercel can process technical information under its own policies. Framer hosts the separate MM dashboard and connection/review webpage, which loads Framer analytics code. Supabase, Framer and OpenAI may process technical information and data internationally under their own policies and settings. These providers’ exact technical-log and backup retention periods have not been independently verified by MM. The bridge itself does not call an external AI provider or include a separate advertising SDK. The absence of an SDK is not a claim that infrastructure providers keep no logs.