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 back up, 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 (photos 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 processing.

2.4 Backup and sync (macro Lifetime and subscriptions)

If you have macro Lifetime or an existing Pro, Plus, or Cloud subscription and sign in with Apple or Google, we additionally process: the email address associated with that sign-in, an account identifier, your purchase or subscription status, and a backup of your in-app data (such as meals, weight logs, recipes, goals, and settings). With Lifetime, macro may also keep this backup under an anonymous account identifier before you sign in, so your data can be restored later. 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 a third-party AI service to estimate calories and macros. Recipe images you upload and recipe content fetched from links you import are also processed through that service 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 use backup, we use your account information and backup data only to authenticate you, store your backup, sync it across your devices, and verify your purchase or 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 (product analytics, United States)
• Meta (Facebook) — install and campaign measurement on iOS and Android. On iOS, the App Tracking Transparency prompt controls access to the advertising identifier. We do not send meal photos, health readings, or body measurements to Meta.
• A third-party AI service (meal estimation and recipe import)
• Open Food Facts API (barcode lookup)
• Supabase (authentication, cloud backup storage, coach and friend sharing, and recipe link import processing)
• RevenueCat (purchase and 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. We do not sell your personal data. Meta measurement helps us understand which ads brought people to macro; it is not used to show you third-party ads inside the app.

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 (including the AI service described above, 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 → Backup → Delete Account) or from our account deletion page, which removes your backup, account, subscription records, shared coach/friend data, and stored photos from our systems. When you delete your account, we also request deletion of the PostHog analytics profile tied to that account identifier.

Meta and the app stores may retain limited attribution or billing records under their own policies after you delete your macro account; we do not control those retention schedules. Store subscriptions must be cancelled in the App Store or Google Play.

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 when you never signed in.

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. Backup & sync

macro Lifetime and existing Pro, Plus, and Cloud subscriptions include backup and sync. When you sign in with Apple or Google, your in-app data is backed up to our hosting provider (Supabase) so it can be restored and synced across your devices. Purchases and subscriptions are managed by the App Store or Google Play through RevenueCat. Cancelling a subscription stops future syncing; deleting your account removes your cloud data.

8. Product Scope

macro provides meal and nutrition tracking features, including macro estimation from meal photos or descriptions, recipe import from images or links for personal use, and barcode lookup via Open Food Facts. With macro Lifetime or an active subscription you can also connect with coaches and friends (Buddies): open their invite link and accept in the app. After you accept, they can see your shared meal log, weight entries, targets, finished fasts, workouts, and daily Health summaries (such as steps, sleep, and active calories) once backup syncs. New meal, weight, workout, and fast photos you add after sharing can be included; older photos that were only on your phone stay on your device unless you re-share them. Buddies may also exchange messages and chat media. If you choose to sync contacts, macro reads email addresses in your contacts and checks which of them already have an account. We do not keep that contact list. A friend request shows up in Chats where it can be accepted or declined. You can skip contact sync. Backup must stay on for sharing to work. You can stop sharing anytime from Account & Backup or your coach/friend management screens.

9. Apple Health & Health Connect (optional)

If you enable Health syncing, macro reads calorie burn, steps, and sleep from Apple Health or Health Connect to show burn totals and adjust Calories left. If you accept a coach or friend invite, daily step, sleep, and related Health summaries can be shared with that person through backup. Meals you log are saved there with their calories and macros. We do not send this health data to PostHog or Meta, use it for advertising, or sell it.

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.