Macropass Privacy Policy

Last updated: October 4, 2026

Macropass is operated by Geometry Lab L.L.C-FZ ("Macropass", "we", "us", or "our"). This Privacy Policy explains what information Macropass collects, how it is used, how it is stored, and how you can contact us about your data.

Contact: support@macropass.app

Data Controller and Representatives

The data controller for Macropass is Geometry Lab L.L.C-FZ, Licence No. 2651608.01, Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, United Arab Emirates.

We have appointed Prighter Group with its local partners as our privacy representative for the European Union and the United Kingdom:

• EU Representative (Art. 27 GDPR): Prighter EU Rep GmbH, Schellinggasse 3/10, 1010 Vienna, Austria.
• UK Representative (Art. 27 UK GDPR): Prighter Ltd, 20 Mortlake High Street, London, SW14 8JN, United Kingdom.

Visit <https://app.prighter.com/portal/geometry> to exercise your privacy rights or contact our representatives directly.

What Macropass Does

Macropass is an AI-native calorie and macro tracker. You can log meals in the app by text, photo, or voice. Completed estimates save to your diary automatically and remain available for review and correction. Voice transcripts are reviewed before estimation. You can also choose to connect an AI assistant such as Claude or ChatGPT to Macropass. The assistant can log, read, update, delete, summarize, and search your Macropass meal and nutrition data when you ask it to do so. Connecting an assistant is optional.

Macropass is not a medical device and does not provide medical advice, diagnosis, or treatment.

Information We Collect

We collect the information needed to operate Macropass:

• Account information: your sign-in provider identifier and, when available, your email address.
• Authentication information: records needed to verify your sign-in, maintain your session, and manage the AI assistants you authorize to access Macropass.
• Food and nutrition data: meal names, timestamps, calories, macros, fiber, sugar, notes, itemized meal details, source client, goals, and optional weekday goal schedules.
• Optional workout data: daily active-calorie totals, their dates, and an identifier for the device supplying the totals, when you enable workout-calorie adjustments through Apple Health or Health Connect.
• Onboarding profile data: the age, sex, height, weight, activity, diet, training, goals, target weight, pace, plan, and reminder information you provide so the app can restore onboarding and personalize your account across devices. If you answer the optional question about how you found Macropass, we also save that choice with your onboarding profile.
• Meal photos and voice notes: if you log a meal by photo or by voice, we collect the image(s) or audio clip you submit. We use them to estimate the meal's nutrition (see How Information Is Shared) and attach them to that meal entry. For meals saved to your account, photos and audio are stored in our infrastructure until you delete the meal or your account. Photos have embedded device metadata, including GPS location and EXIF, removed before they leave your device. If you enable saving meal photos to Photos, a copy of photos taken with the in-app camera is saved to your device’s Photos library, subject to your Photos permissions. This separate copy is not uploaded to us again. Deleting the meal in Macropass does not delete that copy; you can remove it from your Photos library.
• Operational information: request metadata needed for security, abuse prevention, rate limiting, troubleshooting, and service reliability.
• Product-usage information: we record non-identifying product events (for example: signing in, connecting an AI client, that a meal was logged, and subscription status changes) in anonymized form or tied to a pseudonymous account identifier, as described under Analytics and Legal Basis, to understand how Macropass is used and to improve it. This usage information does not include your meal names, notes, food descriptions, or dietary content. Nutrition, body, goal, and other onboarding answer values are not sent to product analytics, even as ranges. The only onboarding answer included is your optional choice of where you heard about Macropass, such as an app store, Instagram, TikTok, or a friend. Subject to your analytics consent or opt-out choice, we use this answer, or the fact that you skipped the question, to understand how people find Macropass.
• Apple Ads attribution information (iOS app only): the attribution token that Apple's AdServices framework gives the app and, if you installed Macropass from an Apple Ads advertisement, the campaign, ad group, search keyword, and ad that led to the install. RevenueCat stores it with the same pseudonymous account identifier it uses for your subscription. It includes no advertising identifier (IDFA). We collect it only for a signed-in account outside the EEA, the UK, and Switzerland, and collection follows your product-analytics choice, as described under Analytics and Legal Basis. Each time you sign out or delete your account while the app is running and collection has started, the app can send the token again for the device's signed-out state before the app next starts. RevenueCat stores the resulting attribution under a separate random identifier that is not linked to the account you signed out of or deleted.
• Google Play install attribution information (Android app installed from Google Play only): if you installed Macropass from a Google Ads advertisement or from a link we tagged, the information Google Play gives the app about that install: the ad click identifier, or the link's source, campaign, keyword, and ad content. RevenueCat stores it with the same pseudonymous account identifier it uses for your subscription. It includes no advertising identifier. The app reads it once per installation, only for a signed-in account outside the EEA, the UK, and Switzerland, and reading it follows your product-analytics choice, as described under Analytics and Legal Basis. Installs from Galaxy Store, and installs that did not come from an ad or a tagged link, record nothing.
• Support information: anything you choose to send when contacting us for help.

Macropass does not collect Claude memory, Claude chat history, conversation summaries, or files uploaded to Claude. Macropass only receives the data sent to its MCP tools or app endpoints.

Health and Nutrition Data

Meal logs, calories, macros, goals, body weight, workout-calorie totals, and related notes may reveal information about your diet, wellness habits, or health. We treat this as sensitive personal data. Macropass stores it so the app and your authorized AI clients can show your food log, nutrition totals, history, summaries, and goals.

Lawful basis (EEA/UK/Switzerland). Where this data qualifies as a special category of personal data under Article 9 of the GDPR (data concerning health), we process it only on the basis of your explicit consent (Article 9(2)(a)). You give consent for AI meal estimation through a dedicated screen shown before your first meal is ever sent for AI estimation, separate from accepting these Terms. You can withdraw this consent at any time in You → Privacy & Data → AI nutrition processing. Withdrawal immediately stops AI estimation. If you later try to estimate a meal, Macropass asks for your consent again before processing resumes. The separate choices and withdrawal controls for optional platform health integrations are described below. You can also delete your account to erase the server-side records described below. Outside the EEA/UK/ Switzerland, we process this data as necessary to provide the service you requested.

Do not use Macropass for medical emergencies or as a substitute for professional medical, nutrition, or dietetic advice.

Apple Health

Macropass offers an optional Apple Health integration that is off by default. You can choose to connect it during onboarding or in You → Preferences → Apple Health. Apple then asks you to grant access to specific data types. Importing or exporting health data requires a signed-in Macropass account.

• We write to Apple Health: the meals you log (energy and the protein, carbohydrate, fat, fiber, and sugar amounts) and your weigh-ins (body weight).
• We read from Apple Health: body-weight entries so weigh-ins recorded by your scale or other apps appear in your Macropass weight history. When you also enable workout-calorie adjustments, we read workouts and their active energy to calculate daily workout-calorie totals on your device, as described below. We do not read nutrition data, workout routes, or heart-rate data.

Apple Health data is governed by Apple's privacy protections and the permissions you grant on your device. We use it for weight and nutrition synchronization and optional workout-calorie adjustments, never for advertising or product analytics. You can turn the integration off in You → Preferences → Apple Health or revoke individual permissions in the Health app. Turning it off stops further synchronization; records already written to Apple Health remain there until you remove them in the Health app.

Health Connect on Android

Macropass offers an optional Health Connect integration that is off by default. You can choose to connect it during onboarding or in Settings → Privacy & Data → Health Connect. Importing or exporting health data requires a signed-in Macropass account. Android asks you to grant these permissions:

• Read weight: Macropass reads body-weight records created by your scale or other apps during the previous 30 days. Imported weights are added to your Macropass account so they appear in your weight history across signed-in devices.
• Read exercise and active calories burned: when you also enable workout-calorie adjustments, Macropass reads exercise sessions and active-energy records to calculate daily workout-calorie totals on your device, as described below.
• Write weight: Macropass writes weigh-ins that you save in the app to Health Connect.
• Write nutrition: Macropass writes meals that you save in the app, including the meal name, energy, protein, carbohydrate, fat, fiber, and sugar amounts, to Health Connect.

Macropass does not read nutrition records, exercise routes, or heart-rate data from Health Connect. We use Health Connect data for weight and nutrition synchronization and optional workout-calorie adjustments, never for advertising or product analytics.

You can turn the integration off in Macropass or remove individual permissions in Android's Health Connect settings. Turning it off stops further reading and writing. Records already written to Health Connect remain there until you remove them through Health Connect. Deleting a meal or weigh-in in Macropass asks Health Connect to delete the corresponding record created by Macropass. Deleting your Macropass account removes its server-side copies but does not remove records remaining in Health Connect or records created by other apps.

Workout-Calorie Adjustments

Adding workout calories to your daily goal is a separate, optional choice. With this choice enabled and the relevant health permissions granted, Macropass calculates active calories from available workout records for the most recent 30 days. It accounts for overlapping records on your device to avoid counting the same workout energy twice.

Macropass sends only each date's total active calories and a device source identifier to your signed-in account. These totals and your adjustment preference are stored with your goals in our database. They are used to adjust your daily calorie goal and to separate workout energy from the baseline used by adaptive calorie planning. Raw workout records, routes, and heart-rate data are not uploaded. Workout data is not sent to our AI-estimation or analytics providers.

You can change the workout-calorie choice in You → Preferences. Turning it off stops further workout-calorie imports and their addition to your daily goal; it does not erase totals already stored with your account. Those totals follow the account retention and backup rules below and are deleted with your account.

Analytics and Legal Basis

We use first-party, privacy-preserving product analytics (PostHog, hosted in the EU) to understand how Macropass is used so we can improve it. We do not use cookies or device-storage tracking for analytics, we do not use analytics for advertising, and we do not track you across other apps or websites. Your dietary and health content is never shared with our analytics provider.

In Germany and Austria, we ask for your consent on first launch before any product-usage analytics is collected, and you can change your choice at any time in You → Privacy & Data. If you do not consent, no usage analytics is collected about you; if you do consent, your events are recorded in an anonymized form that is not linked to a stable identifier. Everywhere else in the EEA, the UK, and Switzerland, this same anonymized, non-identifying analytics is on by default under our legitimate interest in operating and improving Macropass (GDPR Article 6(1)(f) where applicable), and you can opt out at any time on the same screen or by contacting support@macropass.app. Outside the EEA/UK/Switzerland, non-identifying analytics tied to a pseudonymous identifier is on by default under the same legitimate interest, with the same opt-out. When you delete your account, your analytics records are queued for deletion with our analytics provider. Crash and performance diagnostics (Apple MetricKit) are always on, contain no personal content, and are not affected by this choice. On Android, equivalent crash, ANR, and performance diagnostics may be processed through Android system diagnostics and Google Play Vitals. These diagnostics do not include your meal content.

Apple Ads attribution in the iOS app (see Information We Collect) is separate from product analytics. It is on by default under our legitimate interest in measuring our own advertising, and we collect it only for a signed-in account, apart from the case described under Information We Collect. We do not collect it if your device region or your App Store country is in the EEA, the UK, or Switzerland, or if either is unknown. Your product-analytics choice in You → Privacy & Data also applies to it: while product analytics is off, it is not collected, and turning product analytics off stops its collection from the next time the app starts.

Google Play install attribution in the Android app (see Information We Collect) follows the same rules. It is on by default under our legitimate interest in measuring our own advertising, the app reads it only for a signed-in account, and it does not read it if your device region or your Google Play country is in the EEA, the UK, or Switzerland, or if either is unknown. While product analytics is off in You → Privacy & Data, it is not read.

How We Use Information

We use your information to:

• Create and maintain your Macropass account.
• Authenticate you and your authorized AI clients.
• Store and display your meals, nutrition totals, goals, trends, history, and connected clients.
• Apply optional workout-calorie adjustments to your daily goals and adaptive calorie planning.
• Let authorized AI clients perform actions you request through Macropass tools.
• Send email verification codes when you choose email sign-in.
• Prevent abuse, enforce rate limits, secure the service, and debug failures.
• Measure and improve activation, onboarding, the AI-connection flow, reliability, and conversion, using non-identifying product-usage analytics.
• Measure which of our Apple Ads campaigns and search keywords lead to installs and subscriptions, for signed-in accounts in the iOS app outside the EEA, the UK, and Switzerland.
• Measure which of our Google Ads campaigns and tagged links lead to installs and subscriptions, for signed-in accounts in the Android app from Google Play outside the EEA, the UK, and Switzerland.
• Respond to support, privacy, or legal requests.

We do not sell your personal information. Macropass does not serve advertisements, use an advertising identifier (IDFA on iOS or the advertising ID on Android), or track you across other companies' apps or websites. We use Apple Ads attribution and Google Play install attribution, described above, only to measure our own advertising campaigns.

How Information Is Shared

We share information only as needed to operate the service:

• Cloudflare provides the hosting, data storage, processing, and security services needed to operate Macropass.
• Apple may process information when you use Sign in with Apple.
• Google may process your provider identifier and account details when you use Sign in with Google. On Android, Google also operates Google Play purchase and distribution services, Health Connect system services, and Google Play Vitals. Health Connect access is limited to the permissions and purposes described above. We do not send meal content to Google Play Vitals.
• Samsung processes purchases and subscriptions made through Galaxy Store under Samsung's terms and privacy policy. Galaxy Store handles the payment; Macropass uses RevenueCat to validate the purchase and determine subscription access.
• Resend may process your email address to send verification codes if you use email sign-in.
• RevenueCat provides subscription management and purchase validation. When you start a subscription through the Apple App Store, Google Play, or Samsung Galaxy Store, RevenueCat processes your purchase and subscription status tied to a pseudonymous account identifier. We do NOT send RevenueCat your meal content, food descriptions, notes, or email address. RevenueCat acts as a data processor on our behalf. In the iOS app, for a signed-in account outside the EEA, the UK, and Switzerland, RevenueCat receives the attribution token that Apple's AdServices framework gives the app and sends it to Apple. If you installed Macropass from an Apple Ads advertisement, Apple returns the campaign, ad group, search keyword, and ad that led to the install, and RevenueCat stores them with the same pseudonymous identifier so we can measure our Apple Ads campaigns. This uses no advertising identifier (IDFA) and involves no tracking across other companies' apps or websites. Attribution is not collected while product analytics is off, and turning product analytics off stops it from the next time the app starts. In the Android app installed from Google Play, for a signed-in account outside the EEA, the UK, and Switzerland, the app reads the install information Google Play provides once per installation. If you installed Macropass from a Google Ads advertisement or a link we tagged, the app sends RevenueCat the ad click identifier, or the link's source, campaign, keyword, and ad content, and RevenueCat stores them with the same pseudonymous identifier so we can measure our own campaigns. This uses no advertising identifier and involves no tracking across other companies' apps or websites. It is not read while product analytics is off.
• PostHog provides product analytics. We send PostHog non-identifying usage events (such as sign-in, AI-client connection, meal-logged, and subscription status) in anonymized form or tied to a pseudonymous identifier, as described under Analytics and Legal Basis. We do NOT send PostHog your meal content, food descriptions, notes, email address, or nutrition values or ranges. PostHog processes this data on our behalf as a data processor, hosted in the European Union (Frankfurt, Germany).
• OpenAI provides the AI that estimates a meal's nutrition. When you log a meal by typing, photo, or voice, we send OpenAI your meal description and any meal photo (with device location and EXIF metadata removed) so it can return an estimated nutritional breakdown for you to review. Voice notes are transcribed within our own infrastructure (Cloudflare AI) and are NOT sent to OpenAI as audio; only the resulting text is. Under OpenAI's API terms this input is not used to train OpenAI's models, and OpenAI acts as a data processor on our behalf. We do not send OpenAI your email, account identifiers, or analytics.
• AI clients you choose to connect, such as Claude or ChatGPT, may send requests to Macropass and receive the Macropass data needed to answer your request. Their use of your prompts and AI conversations is governed by their own policies.
• We may disclose information if required by law, to protect rights and safety, or to investigate abuse or security issues.

Data Storage and Retention

Macropass keeps your account, onboarding profile, meal, nutrition, goal, workout-calorie, sign-in, and connected-assistant information for as long as needed to provide the service or until you request deletion, subject to legal, security, and backup retention needs.

RevenueCat keeps your subscription records and any Apple Ads or Google Play install attribution for as long as your account exists. When you delete your Macropass account, we ask RevenueCat to delete its customer record for that account, including your purchase history and that attribution. Attribution stored under a separate random identifier, as described under Information We Collect, carries no account identifier or email address. We cannot find it later from your account, and it is not deleted with the account you signed out of or deleted. It remains in our RevenueCat records for as long as we use RevenueCat. If you then sign in to an account that RevenueCat has no record of, RevenueCat merges it into that account, and it follows that account's retention and deletion.

Verification codes and temporary sign-in and security records expire automatically. Some session records are renewed while you continue using the service.

Daily encrypted service backups are kept for about 35 days. Deleted accounts are not restored when we recover a backup.

International Transfers

Macropass is operated from the United Arab Emirates. Some service providers process data in the European Union, the United Kingdom, the United States, or other countries where they operate. Access by our UAE-based controller to data hosted in Europe can itself be an international transfer.

Where European or UK transfer rules apply, we rely on the provider's applicable data-processing terms and transfer safeguards, including the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum or another lawful UK transfer mechanism as applicable. We also reduce transfer risk by collecting only the data needed, encrypting data in transit, restricting access, limiting retention of temporary records, and removing IP addresses from product analytics. You can contact us or our European or UK representative for more information about the safeguards that apply to your data.

Security

Macropass encrypts data in transit and uses access controls, sign-in verification, and abuse-prevention measures to help protect your account and information. You can revoke access for an AI assistant you have connected.

No internet service can be guaranteed perfectly secure. If you believe Macropass has a security issue, contact support@macropass.app.

Your Choices and Rights

You can revoke an authorized AI client from Macropass. You can also contact us to request access, correction, export, or deletion of your Macropass data.

Deleting your Macropass account does not cancel an Apple App Store, Google Play, or Samsung Galaxy Store subscription. Cancel separately in the store account that purchased it. See the account-deletion instructions.

If you are in a jurisdiction with privacy rights, such as the European Economic Area, the United Kingdom, Switzerland, California, or another region with applicable privacy law, you may have additional rights regarding your personal information. Contact us at support@macropass.app to exercise those rights.

Right to object (EEA, UK, Switzerland). You can object at any time, on grounds relating to your particular situation, to processing based on our legitimate interests, such as product analytics. Contact us at support@macropass.app to object. You can also turn off product analytics, as described under Analytics and Legal Basis.

Right to complain (EEA, UK, Switzerland). You can lodge a complaint with a data-protection supervisory authority, in particular where you live or work or where you believe an infringement took place. In the United Kingdom this is the Information Commissioner's Office (ICO), and in Switzerland the Federal Data Protection and Information Commissioner (FDPIC).

Your California Privacy Rights (CCPA/CPRA)

If you are a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act ("CCPA/CPRA"), gives you the following rights regarding the personal information Macropass holds about you. Macropass extends these rights to all users, regardless of location.

• Right to know and access. You can request the categories and specific pieces of personal information we have collected about you, the categories of sources, the business purpose for collecting it, and the categories of third parties (service providers) with whom we share it. You can obtain a portable copy of your Macropass data at any time from within the app or by contacting us. The categories we collect are described in "Information We Collect" above (account information, authentication information, food and nutrition data, optional workout data, onboarding profile data, meal photos and voice notes, operational information, product-usage information, Apple Ads and Google Play install attribution information, and support information).
• Right to delete. You can request deletion of your personal information. You can delete your account and all associated data directly from within the Macropass app, which permanently purges your account, meals, goals, and all connected-client tokens and grants, and asks RevenueCat to delete its subscription and attribution records for your account. You may also contact us to request deletion.
• Right to correct. You can request correction of inaccurate personal information we hold about you.
• Right to non-discrimination. We will not discriminate against you for exercising any of your privacy rights.

Do Not Sell or Share My Personal Information

Macropass does not sell your personal information, and does not share it for cross-context behavioral advertising, as those terms are defined under the CCPA/CPRA. Macropass does not serve advertisements, does not use an advertising identifier (IDFA or the Android advertising ID) or track you across other companies' apps or websites, and does not exchange your personal information for money or other valuable consideration. Because we do not sell or share personal information, there is no "Do Not Sell or Share My Personal Information" action you need to take. This practice applies to all users by default, including in the prior twelve months.

We do disclose personal information to our service providers (Cloudflare for hosting, data storage, and security; Resend for email verification codes; RevenueCat for subscription management and ad attribution; PostHog for product analytics; and OpenAI for meal nutrition estimates), to Apple, Google, and Samsung for the sign-in, store, and platform services you use with Macropass (Sign in with Apple, Sign in with Google, Google Play, Health Connect, Google Play Vitals, and Galaxy Store), and to the AI clients you choose to connect, solely to operate and improve the service, perform the actions you request, and measure our own Apple Ads and Google Ads campaigns, as described in "How Information Is Shared" above. For Apple Ads attribution, Apple resolves the attribution token and RevenueCat processes the result as our service provider. These are not sales or shares for cross-context behavioral advertising; service providers are contractually limited to processing the information for Macropass's purposes.

Sensitive Personal Information

Your meal logs, calories, macros, goals, and related notes may constitute sensitive personal information because they can reveal information about your health. We use this information only to provide the Macropass service to you and to your authorized AI clients. We never use it to infer characteristics about you for any other purpose, and never for advertising. You may limit our use of sensitive personal information, but because we already use it only for these necessary service purposes, no further limitation is required.

How to Exercise Your Rights

To exercise any of these rights, use the in-app account deletion and data export features, revoke a connected AI client from within the app, or contact us at support@macropass.app. We will verify your request using your authenticated account or sign-in identifier before acting on it, and we do not require you to create an additional account to make a request. You may use an authorized agent to submit a request on your behalf, subject to reasonable verification.

Children

Macropass is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to Macropass, contact us so we can delete it.

Changes

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date above. Material changes will be reflected on this page.

Contact

Geometry Lab L.L.C-FZ · Licence No. 2651608.01

Email: support@macropass.app