Macromaxxing
Get the app
Menu
FeaturesRecipesCalculatorFAQ Support Download on the App Store

Privacy policy

Last updated: 26 October 2026

This policy covers the Macromaxxing app for iPhone and iPad and the macromaxxing.online website. It explains what we collect, why, who helps us, how long we keep it, and your rights.

In short

  • You don't need an account, name, email or password. The app gives you a random ID.
  • Your meals, weight, body stats and targets stay on your phone. We never see them.
  • Usage analytics is off unless you say yes. If you do, we see which screens and features you use, a few setup choices like your diet type, and how many meals you log. Never what you eat or your goal.
  • Crash reports are on, without your ID, and you can turn them off in Profile.
  • We never sell your data, and we don't use it for ads.
  • You can delete your account in the app. You can also ask us for a copy of your data, or complain to the Dutch data protection authority.

Who we are

Macromaxxing is made by Velvet Motion, a Dutch eenmanszaak registered with the Dutch Chamber of Commerce (KVK) under number 97514071. Velvet Motion is the controller of the personal data in this policy.

Velvet Motion
Kooilaan 182
2315 AX Leiden
The Netherlands
info.velvetmotion@gmail.com

Data stored on your phone

Your macro targets, onboarding answers, meal logs, saved recipes, planned meals, shopping checkmarks, cooking progress and progress history are stored on your phone. Onboarding may include your goal, formula baseline, age, height, weight, activity, protein and cooking preferences, and main challenge.

This data is not sent to Supabase or RevenueCat. If you turn on usage analytics, a few setup choices and a daily count of logged meals are sent to PostHog, as described under Usage analytics.

An unfinished setup draft is removed after seven days, or when you complete, skip, cancel or reset setup.

Some encryption keys and account-deletion keys are kept in the iPhone Keychain. These can survive uninstalling the app, so to erase everything, use Delete account & erase data before you uninstall.

Your anonymous ID

You don't need to give a name, email address, phone number or password. The app creates a random anonymous user ID through Supabase Auth. Supabase stores that ID and your session so the app can load recipes securely. A recipe request includes the recipe ID and an access token, but not your meal logs, targets or onboarding answers.

The same random ID is used as your RevenueCat ID so our server can check Premium access. If you turn on usage analytics, the same ID also links your analytics events in PostHog.

Purchases

If you subscribe to Premium, Apple handles the payment under your Apple ID. RevenueCat stores your purchase, renewal and subscription status, linked to your anonymous ID, so the app can unlock Premium and our recipe service can check it. We never receive your payment card details.

Usage analytics

Usage analytics is off until you say yes. The app asks once, during setup or the first time you open this version, and only if you're 16 or older. If you are, you can also turn on Help improve Macromaxxing in Profile > Privacy & legal.

When it's on, the app sends PostHog:

  • the screens you open and the features you use, from a fixed list of events;
  • your setup choices for activity level, diet type, meals per day, protein style and cooking time;
  • your unit and reminder settings;
  • whether you have Premium, a free trial or neither;
  • for each day you use the app: how many meals you logged.

Events are linked to your random anonymous ID and include the app version, device model, operating-system version, language, region and time zone. PostHog works out an approximate location (country and city) from your internet address when events arrive. Our PostHog project is set not to store the address itself.

Usage analytics never includes what you ate, recipe or food names, amounts, calories or macros, whether you reached your targets, your goal, your weight, height, age or gender, foods you avoid, your name, anything you type, photos, receipts or passwords. We don't use session replay, automatic tap capture, surveys, feature flags or advertising identifiers.

Crash reports

Crash reports are on unless you turn off Send crash reports in Profile > Privacy & legal.

If the app crashes or freezes, or a purchase, restore, paywall or sync fails, the app sends Sentry a technical report: the error and where in the app's code it happened, the app version, device model and operating-system version, the names of the last screens you opened, and a random installation ID. The app also tells Sentry when a session starts and ends, so we can count how often it crashes.

Crash reports are not linked to your user ID. They are not meant to contain your meals, weight, body numbers, name or anything you type, and the app removes such details it can recognize before sending. We tell Sentry not to store your internet address.

The website

When you visit macromaxxing.online, our host Netlify records your internet address, browser details and the pages you request in its server logs, as every website host does. This is needed to deliver the pages and protect the site.

If you choose "Allow analytics" on the cookie banner, the website counts visits and taps on download buttons with Umami Cloud. Umami doesn't use cookies. It uses your internet address briefly to make a visitor code and an approximate location, and doesn't store the address with the counts. If you choose "Essential only", nothing is counted. The banner stores that one choice in your browser.

Emailing us

When you email us, we receive your email address and whatever you choose to write, so we can answer you. Please don't send payment details, health information or other sensitive data.

Why we use your data

  • Running the app and your subscription (anonymous ID, recipe delivery, Premium checks through Supabase and RevenueCat): this is needed to provide the app you asked for (GDPR Article 6(1)(b)).
  • Usage analytics: only with your consent (Article 6(1)(a)). It leaves out your goal and whether you reached your targets, so it doesn't include health data. You can withdraw it at any time by turning off Help improve Macromaxxing. Withdrawing doesn't make earlier use unlawful.
  • Crash reports: our legitimate interest in keeping the app working and fixing bugs (Article 6(1)(f)). We keep reports to technical details and don't link them to you. You can object at any time by turning off Send crash reports, or by emailing us.
  • Website hosting logs: our legitimate interest in delivering and protecting the website (Article 6(1)(f)).
  • Website visit counts: only with your consent on the cookie banner (Article 6(1)(a)).
  • Answering your email: to reply to you, which is our legitimate interest (Article 6(1)(f)), or part of providing the service when it's about your subscription (Article 6(1)(b)).

You don't have to give us any personal data. The app works without usage analytics or crash reports. We don't make decisions about you by automated means that have legal or similarly significant effects. The app calculates your targets on your phone.

Who helps us, and where your data goes

Some of our providers are US companies, or store data outside the European Union. When your data leaves the EU, it's protected in one of three ways:

  • the EU-US Data Privacy Framework, for US companies certified under it;
  • the European Commission's standard contractual clauses, a contract that holds the provider to EU rules;
  • the European Commission's decision that the United Kingdom protects personal data adequately.

Our providers:

  • Supabase (Supabase Pte. Ltd., Singapore): your anonymous ID and recipe delivery. Stored in London, UK, which is covered by the UK decision. Supabase and its support providers, mostly in the US, may access it under standard contractual clauses.
  • RevenueCat (RevenueCat, Inc., USA): your subscription status. Stored in the US, under standard contractual clauses.
  • PostHog (PostHog Inc, USA): usage analytics, only if you turn it on. Stored in Frankfurt, Germany. PostHog and some of its providers may access it from the US, under the Data Privacy Framework and standard contractual clauses.
  • Sentry (Functional Software, Inc., USA): crash reports. Stored in Frankfurt, Germany. Sentry may access it from the US, under the Data Privacy Framework and standard contractual clauses.
  • Netlify (Netlify, Inc., USA): hosts the website. Its server logs may be stored in the US, under the Data Privacy Framework.
  • Umami Cloud (Umami Software, Inc., USA): website visit counts, only if you allow them. Stored in the EU, under standard contractual clauses.
  • Google (Gmail): our support inbox. Emails you send us are stored by Google. Google LLC in the US is certified under the Data Privacy Framework.
  • Apple: payments under your Apple ID. Apple handles that data under its own privacy policy.

We don't sell your data and don't use it for advertising or cross-app tracking.

Children

Macromaxxing is for people age 13 or older, subject to local consent rules. Users ages 13 through 17 can use recipes, planning, shopping, logging and recipe preferences, but onboarding doesn't calculate personalized calorie or macro targets for them. Personalized targets are available only when your onboarding age answer is 18 or older.

We don't ask users under 16 about usage analytics, and it stays off for them.

Your choices

You can turn usage analytics and crash reports on or off at any time in Profile > Privacy & legal.

  • Turning usage analytics off stops it at once and erases the events still waiting on your phone and the analytics ID stored there. It doesn't delete events already sent; to have those deleted, email us.
  • Turning crash reports off stops new reports at once.

You can delete your account in the same place. The app asks RevenueCat to delete your purchase record, asks PostHog to delete the analytics data linked to your ID, and deletes your Supabase ID. Once our server confirms, the app erases the account, nutrition, planning, analytics and other app data on your phone. If you keep using the app afterward, it creates a new random ID that isn't linked to the old one.

Deleting your account doesn't cancel an Apple subscription. Manage subscriptions in your App Store settings. Apple keeps its own purchase records.

Crash reports aren't linked to your ID, so they can't be matched to your account; they're deleted after 30 days.

Your rights

You have the right to:

  • see the personal data we hold about you and get a copy;
  • have it corrected;
  • have it deleted;
  • limit how we use it;
  • object to how we use it, including crash reports;
  • receive it in a format you can reuse;
  • withdraw your consent at any time.

Email info.velvetmotion@gmail.com to use any of these rights. We'll answer within one month. Because we don't know your name, we may need help from you to find which data is yours.

You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), or to the authority where you live or work. We'd like the chance to help first, but you don't have to ask us first.

How long we keep data

  • On your phone: until you delete it or reset the app. An unfinished setup is removed after seven days.
  • Your anonymous ID and purchase record (Supabase, RevenueCat): until you delete your account. Apple keeps its own purchase records.
  • Usage analytics (PostHog): up to one year, and deleted sooner when you delete your account. PostHog removes the events in a weekly batch.
  • Crash reports (Sentry): 30 days.
  • Account deletion: a small technical record, so an interrupted deletion can finish. Once your deletion is done, it no longer contains your ID and expires within seven days. An unfinished one expires within seven days of starting.
  • Your emails (Gmail): up to two years after we last write to each other.
  • Website logs (Netlify): for the period Netlify sets.
  • Our providers may keep limited security and service logs for their own set periods.

Changes to this policy

When we change this policy, we publish the new version here and in the app with a new date. If a change affects how we use data you've already shared, we'll tell you in the app.

Contact

Questions about privacy? Email info.velvetmotion@gmail.com.