Privacy Policy

1. Overview

macro ("we", "our", or "us") respects your privacy. This policy explains what information is collected when you use the app, how we use it, and the choices available to you. Most of the nutrition data you create stays on your device. We also collect anonymous product analytics to understand how macro is used and to improve the experience.

2. Information We Collect

2.1 Data stored on your device

By default, meals, goals, recipes, weight entries, and other content you create in macro are stored locally on your device. We do not receive a copy of that content unless you explicitly use a feature that sends data to us or a service provider (described below).

2.2 Product analytics (PostHog)

We use PostHog, a product analytics service hosted in the United States, to collect usage information about how people interact with macro. Analytics events are not linked to your name, email address, or Apple or Google account. Each install is identified by a random device identifier. If you sign in to macro Cloud, we may also associate events with your account identifier so usage stays connected across devices — without attaching your email or display name to those events.

Depending on how you use the app, analytics may include:

• Screens and features you open (for example Home, Progress, Profile, paywalls, onboarding, and settings)
• Actions you take (for example starting or completing meal logging, changing goals, enabling reminders, or attempting a purchase or restore)
• Meal logging context, such as which logging mode was used (photo, describe, manual, recent, or recipes), how many ingredients were logged, and whether you clarified a meal
• Optional meal-logging prompts you type (describe text, manual ingredient text, and clarify text), capped in length
• Aggregated nutrition figures associated with those events, such as calorie totals or macro totals for a logged meal or daily summary — not meal photos, barcodes, or meal display names
• Profile and onboarding details that help us understand the product (for example gender, activity level, weight, height, goal weight, and birthday) when you complete onboarding or update related settings
• Subscription and paywall interactions (for example viewing a paywall, starting checkout, or completing restore)
• App and device context needed to interpret usage, such as app version, operating system, device type, language or locale, and general session timing

We do not send meal photos, barcodes, recipe text, health data from Apple Health or Health Connect, or your email address to PostHog. Analytics is used to improve macro, not to sell your data or to show third-party advertising.

2.3 Feature processing (AI and barcode lookup)

To provide app features, meal photos or meal descriptions that you submit, recipe images or recipe webpage content from links you choose to import, and barcode values you scan may be sent to third-party APIs for processing. When you import a recipe from a link, our servers may fetch that public URL to extract recipe text or images for AI processing.

2.4 macro Cloud (optional)

If you choose to enable macro Cloud (our optional backup and sync subscription), we additionally process: the email address associated with your Apple or Google sign-in, an account identifier, your subscription status, and a backup of your in-app data (such as meals, weight logs, recipes, goals, and settings). Meal photos are not included in cloud backups. Your email and sign-in provider details are not sent to PostHog; only the account identifier may be used as described in section 2.2.

2.5 Payments

We do not collect or store raw payment card information. In-app purchases and subscriptions are processed by the App Store or Google Play.

3. How We Use Data

Submitted meal photos or descriptions are processed through the Gemini API to estimate calories and macros. Recipe images you upload and recipe content fetched from links you import are also processed through Gemini to draft a personal recipe (name, servings, and ingredients). Scanned barcodes are sent to the Open Food Facts API to retrieve product nutrition data.

We use anonymous product analytics to measure feature adoption, diagnose crashes and performance issues, understand which logging flows work best, evaluate paywall and onboarding effectiveness, and prioritize improvements. Analytics does not give us access to modify or delete the meals stored on your device.

If you enable macro Cloud, we use your account information and backup data only to authenticate you, store your backup, sync it across your devices, and verify your subscription status.

4. Data Sharing

We do not sell your personal data. We share information only with service providers that help us operate macro, including:

• PostHog (anonymous product analytics, United States)
• Gemini API (meal estimation and recipe import)
• Open Food Facts API (barcode lookup)
• Supabase (authentication, cloud backup storage, and recipe link import processing)
• RevenueCat (subscription management)
• Apple or Google (sign-in and billing, when you use them)

Each provider processes data under its own privacy policy and only for the purposes described in this policy.

5. Data Retention

Meal photos, meal descriptions, recipe import images or fetched recipe page content, and barcode values are sent to third-party providers only to return the requested result and are not stored by us after processing is complete (except the recipe fields you save on your device, which may include an optional source URL for your reference). Data saved in the app is stored on your device and remains until you delete it or uninstall the app.

Analytics events, including optional meal-logging prompts, are retained in PostHog for up to one year, after which they are deleted or aggregated. Third-party services (such as Gemini API, Open Food Facts, and PostHog) may apply their own retention schedules to data they process on our behalf.

You can delete your account and all associated cloud data at any time from within the app (Profile → Cloud Backup → Delete Account) or from our account deletion page, which removes your backup, account, and subscription records from our systems.

You can also request deletion of any data we control by emailing support@downloadmacro.com. We will confirm and complete deletion within 30 days. Because analytics identifiers are not email addresses, we may need additional information you provide (such as an approximate date and app version) to locate a specific device's events.

6. Your Choices

macro requires product analytics to help us maintain and improve the app. If you do not want anonymous analytics collected, please do not use macro. You can email support@downloadmacro.com to ask us to stop future analytics from your device where technically feasible. Uninstalling the app stops further analytics collection from that device.

7. macro Cloud (optional backup & sync)

macro Cloud is an optional, subscription-based feature. It is off by default, and the core app works without it. When you turn it on, you sign in with Apple or Google and your in-app data is backed up to our hosting provider (Supabase) so it can be restored and synced across your devices. Your subscription is managed by the App Store or Google Play through RevenueCat. Cancelling your subscription stops future syncing; deleting your account removes your cloud data.

8. Product Scope

macro provides meal and nutrition tracking features, including AI-based macro estimation from meal photos or descriptions, AI-assisted recipe import from images or links for personal use, and barcode lookup via Open Food Facts. macro does not provide AI-assisted coaching tools.

9. Apple Health & Health Connect (optional)

If you enable burned-calorie syncing, macro reads calorie burn summaries from Apple Health or Health Connect on your device to show burn totals in the app and to adjust Calories left compared to logged meals. We do not send this health data to PostHog, use it for advertising, or sell it, and macro does not write health data back to Apple Health or Health Connect.

10. Children

macro is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us information, contact us and we will take appropriate steps to delete it.

11. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the effective date at the top of this page. Continued use of macro after an update means you accept the revised policy.

12. Contact

If you have privacy questions, email us using the button below.