Privacy Policy

1. Information we handle

• Account and sign-in: email address, account ID, registration/login credentials, verification and password-reset codes, Google or Apple sign-in tokens, and access/refresh tokens. Apple sign-in may use a private relay email address. Session tokens and account identity are stored using the device's secure storage.
• Health and fitness information you enter: age, gender, height, body type, activity level, weight history, target weight, intended weekly weight change, calorie and macronutrient goals, water goals, and scheduled goals. We derive estimates such as BMI, calorie needs, weight trends and progress reports.
• Food and hydration records: foods, nutrition values, portions, units, dates, meal periods, water entries, planned meals, recipes, meal templates, favourites, recent foods and shopping lists. Product searches, barcodes, custom products, edit suggestions and reports are also processed.
• Photos and audio you submit: food or nutrition-label photos taken in the app or selected from your library, and recordings of spoken meal descriptions. Audio uploads include format and duration; scan requests include language, request identifiers and quota usage. These uploads are sent to our server for recognition, rather than processed entirely on your device. Barcode scanning reads the code on-device and sends the code for lookup; it does not send a continuous camera feed.
• Purchases: product and transaction identifiers, store receipts or purchase tokens, subscription status, expiry, trial eligibility, entitlements and promotion/affiliate codes. Apple and Google handle payment details; the app does not request your payment card number.
• Notifications: push registration tokens, account association, platform, language, time zone and reminder preferences/times, for delivery and background synchronisation.
• Technical and usage information: app and OS versions, device characteristics, installation/app-instance identifiers, sessions, screens, feature interactions, error types/codes, stack traces and diagnostic context. Network services receive connection information, including IP addresses.

2. Purposes and analytics

We use account and tracking information to authenticate you, calculate goals, maintain your diary, synchronise devices, generate reports and adaptive calorie suggestions, recognise submitted meals, deliver requested reminders, verify purchases, provide exports, moderate submitted products and respond to support requests.

Firebase Analytics and Crashlytics collect usage and diagnostics in release builds to measure features and investigate errors. Analytics events include onboarding answers and profile properties such as gender, goal, activity level and body type, as well as actions involving meals and weight. Installation identifiers are pseudonymous, and should not be understood as guaranteeing anonymity. Firebase SDKs may also collect an Android advertising identifier when available and enabled by their configuration.

The app currently has no in-app analytics consent switch. For questions about analytics, objections or requests concerning your information, contact support. Device permissions described below control camera, microphone and notifications; they do not disable analytics.

3. Permissions and optional uploads

• Camera: barcode scanning and photos of food or nutrition labels.
• Photos: access to images you choose for food or label recognition.
• Microphone: recording a meal description when you use voice input.
• Notifications: optional reminders, scan-limit updates and weekly reports.
• Network/background access: API requests, purchase verification and synchronisation.

You can refuse or revoke camera, photo, microphone and notification access in device settings. You can use manual food entry instead of photo or voice recognition. Submit only content needed to describe your food, and avoid including other people or unrelated personal information. The app has no HealthKit or Health Connect integration and does not request contacts or precise device location.

4. Recipients and sharing

• Macro Tracker's backend and infrastructure: account, diary, profile, recognition requests and synchronisation data needed to operate the service.
• Google/Firebase: Google sign-in, Analytics, Crashlytics, Cloud Messaging and Remote Config process identity tokens, usage/diagnostic information, installation identifiers, push tokens and technical configuration data. See Firebase privacy information and Google's Privacy Policy.
• Apple: Sign in with Apple, App Store billing and push delivery handle authentication, transaction and device registration information. See Apple's Privacy Policy.
• RevenueCat, when configured: subscription verification, restoration and attribution use an anonymous or account-linked app user ID, purchase records and an affiliate/promotion attribute. See RevenueCat's Privacy Policy.
• Google Gemini: our backend sends submitted food and nutrition-label photos, meal-description audio and the instructions needed to interpret them to Google Gemini to generate food and nutrition estimates. Google receives this content for AI processing. See Gemini API data-use terms and Google's Privacy Policy. The service uses the paid Gemini API through a Google Cloud project with active billing. Under Google's Paid Services terms, submitted content and responses are not used to improve Google's products or models. Google may retain prompts and responses for a limited period for abuse prevention, security and legal obligations. Our own non-storage of uploads does not guarantee zero retention by Google.
• Your chosen recipients: when you export and share an Excel file, its contents become available to the trainer, app or other recipient you select.

Products you explicitly submit as public may be reviewed by moderators and made available in the shared food catalogue. Do not put personal information in public product names or descriptions. Your personal diary is not a public feed.

We do not sell your personal information. The app does not display third-party advertisements. Service providers must protect information to a standard consistent with this policy and applicable law, and use it only for the permitted service purposes. Information may also be disclosed where legally required or necessary to address fraud or security incidents.

5. Storage, security and retention

Your account, profile and diary are stored on our servers while your account is active. The app also keeps an on-device SQLite cache and pending synchronisation records, plus preferences and locally saved shopping-list state. Local account caches and session credentials are cleared during the app's account-deletion/logout flow. A voice recording is temporarily written on-device and the app attempts to remove that temporary file after reading or cancelling it; photos may remain in temporary storage managed by the app or operating system.

Macro Tracker does not retain submitted photos or audio on its servers after processing; they are used to fulfil the recognition request. The resulting food and nutrition entries may remain in your diary until you delete them or your account. This does not remove temporary on-device files described above or override Google Gemini's own retention rules. Analytics, crash reports and store purchase records are separately subject to the relevant provider's retention settings and applicable legal obligations.

Deleting your account removes your account, profile and private tracking records from Macro Tracker's backend. Products you created in the global food catalogue remain available after account deletion, together with their existing creator identifier or account association. This means account deletion does not erase every account-linked record. Do not include personal information in public product entries. Contact support to request erasure of the retained creator association or personal information in public entries. Deletion of Macro Tracker records does not itself cancel store subscriptions or guarantee immediate deletion of records independently retained by Apple, Google, Firebase or RevenueCat; contact support about deletion requests involving those providers.

The production API uses HTTPS; session credentials use platform secure storage. No transmission or storage system is completely secure. Our providers may process data outside your country; applicable transfer safeguards are required where relevant.

7. Your choices and rights

You can edit your profile and goals and remove diary entries in the app. The trainer Excel export is a Premium feature; you can request access to or a copy of your personal data through support without purchasing Premium. Depending on your jurisdiction, you may have rights of access, correction, deletion, portability, restriction, objection and withdrawal of consent. Contact support to exercise them or ask which legal basis applies to processing. Withdrawing consent does not affect processing that was lawful before withdrawal. You may also complain to your local data protection authority.

8. Adults only

Macro Tracker is intended for adults aged 18 or older. Its nutritional estimates are designed for adults. If you believe a person under 18 has supplied personal data, contact support so the account and data can be investigated and removed.

9. Website services

These web pages load fonts from Google Fonts and a scrolling library from unpkg. Those providers receive ordinary web-request information, including IP address and browser information. The website host also receives connection information needed to serve the pages.