Last updated 19 October 2026
The short version: Mash asks you to sign in with your email address so your meal plans, preferences and grocery lists follow you across devices. We hold your email (plus the name and profile picture Google shares if you sign in with Google) and a copy of your app data tied to it, including any allergies and diet you choose to add. In the current app, the body details you give the nutrition calculator, and your name in Profile, stay on your phone. The free plan shows non-personalised ads from Google AdMob, and Google Analytics for Firebase counts installs and new accounts so we can see which of our own ads work. We don't track you across other companies' apps or websites, we never sell your data, and you can delete your account and your app data from inside the app at any time (section 8 lists the few records others keep after that).
Mash is published by MyFitTrack (eenmanszaak, KVK 72366095), the data controller for the limited processing described below. You can reach us at support@myfittrack.net.
Your account. Mash requires sign-in. You sign in with your email address and a one-time code we email you, or with your Apple or Google account; there is no password. We store your email address and the time you signed in, in Supabase (European Union, eu-west-1), so we can send you codes and recognise you on another device. If you sign in with Google, Google shares your name and profile picture, and the sign-in service stores them with your account; Apple shares only your email address (or a private relay address). For security, for example to spot misuse of your account, the sign-in service also records the IP address and device information of your sign-ins and signed-in sessions.
Your app data. Everything you enter into Mash is written to your phone's own app storage. While you are signed in, the following is also mirrored to your account so it can be restored on another device:
Allergies and diet. Allergies and diet can say something about your health. Mash stores them only if you add them yourself, and keeps them in your account copy on purpose, so that every device you sign in on plans around them. We rely on your consent for this. Since version 1.2.4 the screens where you choose allergies say that they are saved to your account; earlier versions saved them there without that note. You can withdraw your consent at any time by removing them in Profile → Food preferences (the change syncs to your account copy) or by deleting your account.
What stays on your device. From version 1.2.4, the body details behind the nutrition calculator (age, sex, height, weight, activity level and goal), your calorie and protein targets and the name you enter in Profile are kept on your phone only and are never sent to your account. Earlier versions also sent them with each sync. Our server now discards them as they arrive, so they are no longer stored in your account copy, and the copies stored before 16 October 2026 have been deleted. Updating the app stops them from being sent at all.
The mirrored copy is readable only by your own signed-in session (enforced by row-level security in the database). We do not read, analyse or profile it, except to count how Mash is used (for example how many plans an account has made and when it was last active) so we can run and improve the app. Signing out leaves the copy in place for your next sign-in. Deleting your account (Profile → Delete account) permanently removes, immediately and irreversibly, your email and sign-in, your app data copy, the photos of recipes you imported with version 1.2.4 or later, the feedback linked to your account and your account’s abuse-prevention counters and the records of the public social-media links you imported (section 3). Feedback sent from versions before 1.2.4 is not linked to your account; it is removed too if you gave your account’s email address as the reply address, and otherwise we delete it when you ask us at support@myfittrack.net. Uninstalling the app without deleting the account removes only the copy on that device.
Beyond the account sync described above, Mash makes these outbound requests:
| Request | Purpose | What is sent |
|---|---|---|
| Recipe photos and the recipe catalogue | Showing recipe images and delivering catalogue updates without a full app update | An ordinary anonymous web request for a public file. No identifier, no account, no plan data. |
| In-app feedback | Sending us a message from Profile → Send feedback | What you type (your message and, if you add one, an email address for our reply), your platform, app version, language, region and supermarket, a one-way hash of your IP address made with a secret key and used only to limit abuse, and, when you are signed in on version 1.2.4 or later, your account id. That feedback is linked to your account and deleted with it; feedback from earlier versions carries no account id (see section 2). |
| Recipe import from a link | Turning a recipe web page you share into a Mash recipe | The page URL you shared or the text you paste, with your sign-in token so our server can check your Mash Pro subscription or how many free imports you have left this month. Our server fetches the page and sends its text, together with any text you pasted, to OpenAI, which extracts the recipe. The recipe’s photo is copied into Mash’s image storage so it keeps loading. The copy is stored in a folder named after your account id, at a web address that contains that id, and is deleted when you delete your account; copies made by app versions before 1.2.4 are stored without any account id and are not linked to you. The imported recipe itself is saved with your app data. |
| Recipe import from a photo | Turning a photo of a recipe you choose (a screenshot, a cookbook page or a handwritten card) into a Mash recipe | The photo you choose, with your sign-in token so our server can check your Mash Pro subscription or how many free imports you have left this month. Our server sends the photo to OpenAI, which reads the recipe from it. Mash does not store the photo: our server discards it once the recipe has been read, and the imported recipe gets no picture. Only the recipe text extracted from it is saved with your app data. |
| Recipe videos in Discover | Showing popular recipe videos from YouTube and TikTok, and the social-media recipes Mash cooks import most | Your app language and region, so our server returns the list for them; no account id or other identifier, and the list is the same for everyone with that language and region. To limit abuse our server counts these requests per hour under a one-way hash of your IP address made with a secret key (see Abuse prevention below). The photos load from YouTube’s, TikTok’s or Mash’s servers; YouTube and TikTok see your IP address, as any website does. Tapping a video opens it in the YouTube or TikTok app or website, where their own privacy policies apply. Importing one is a recipe import from a link (above). |
| Order at a supermarket | Opening your grocery list in Albert Heijn, Jumbo or Walmart | Opens the retailer's app or website with the product list. From there the retailer's own privacy policy applies; Mash sends the retailer nothing about you. |
| App Store / Google Play purchases | Selling and restoring a Mash Pro subscription | Handled entirely by Apple or Google. RevenueCat, our subscription processor, tells Mash only whether a subscription is active, keyed to your account id. |
| Ads (free plan only) — Google AdMob | Showing banner and full-screen ads to free users; Mash Pro removes them | Ad requests are non-personalised. Google receives standard ad-request data: device and app information, an IP address (for approximate location) and, on Android, the advertising ID, which Google uses for frequency capping, fraud prevention and ad measurement, not to personalise ads. In the EEA, UK and Switzerland Google's consent form asks you first. You can reset or delete the Android advertising ID in your device settings. |
| Ad measurement — Google Analytics for Firebase | Seeing which of our own ads bring people to Mash | The app's automatic first-open and session events, and a “sign-up” event with the sign-in method when an account is created, with a random app-instance id and device and app information. No email address, no plan or grocery data and no advertising ID; all of Google's advertising consent settings are switched off, so Google may count these events but not use them to personalise ads. |
Abuse prevention. To stop misuse of recipe import, feedback and the supermarket links, our server counts requests per hour: per account (keyed to your account id) when you are signed in, otherwise per IP address, stored only as a hash made with a secret key. A counter holds just that key, the hour and a number. Counters are deleted automatically after about two days, and an account’s counters are deleted straight away when the account is deleted.
Free imports. Without Mash Pro you can import 6 recipes a month. To count them, our server keeps one record per account and month: your account id, the month and how many imports you have used. Only imports that succeed are counted. Records from earlier months are deleted after the following month, and all of them are deleted straight away when you delete your account.
Popular imports. When you import a recipe from a public YouTube, TikTok or Instagram link, our server records the link, the post’s public title, creator name and photo address, your app language, the time, and a one-way code made from your account id with a secret key, so that one person is counted once. Without that key the code cannot be linked to you; we use the key only to count each person once and to delete your records when you delete your account. “Popular with Mash cooks” in Discover shows links imported by at least two different people in the last 30 days, with only the number of people, never who they are. Records are deleted after 90 days, and straight away when you delete your account. Links to other websites, pasted text and photos are not recorded.
OpenAI (United States) processes recipe-import text, and the photos you import, on our behalf, only to extract the recipe. Under OpenAI’s API terms it does not use them to train its models and may keep them for up to 30 days to detect abuse. Nothing that identifies you, such as your email address or account id, is sent to OpenAI.
The recipe files are hosted on Supabase Storage in the European Union (eu-west-1). As with any web server, the hosting provider's logs record the IP address and timestamp of a request as a technical necessity of delivering the file. For catalogue photos and files Mash sends no identifier alongside the request, so those logs cannot be linked to a person. The web address of a photo from a recipe you imported contains your account id, so the logs of those requests could be; we do not use them for that or to build profiles.
Mash Pro is sold through the App Store and Google Play. Your payment details are handled by Apple or Google under their own privacy policies and are never seen by, or transmitted to, us. We receive only a signed confirmation from the store that an entitlement is active. Manage or cancel a subscription in your App Store or Google Play account settings.
Item prices shown in Mash are estimates held in the app's own recipe catalogue. Mash does not connect to any supermarket account, loyalty card or payment method, and it cannot see your purchases.
Mash is a general-audience cooking app and is not directed at children under 13. We do not knowingly create accounts for children; if you believe a child has signed up, contact us and we will delete the account.
Under the GDPR you have the right to access, correct, erase, restrict and port your personal data, and to object to its processing. Erasure is built in: Profile → Delete account immediately removes your account and the data listed in section 2. A few records are kept elsewhere: the sign-in service’s security log of your sign-ins (times, IP addresses and device information) is not erased automatically, and we erase it when you ask; RevenueCat keeps its record of your subscription status under your former account id until we ask it to delete it, which we do on request; Apple or Google keep your purchase history under their own policies; and the hosting logs and OpenAI’s abuse-monitoring copy described in section 3 expire on their own schedule. Your app data is portable by design, since it follows your sign-in to any device. For access or correction requests, or if anything is unclear, write to support@myfittrack.net and we will respond within 30 days. You also have the right to lodge a complaint with your local supervisory authority — in the Netherlands, the Autoriteit Persoonsgegevens.
When Mash changes what it collects, this policy is updated before the feature ships and the date at the top reflects the current version. 9 September 2026: added accounts (email sign-in with cloud copy of app data), in-app feedback, recipe import and supermarket handoff. 30 September 2026: described the non-personalised Google AdMob ads on the free plan, Apple and Google sign-in and RevenueCat, and added Google Analytics for Firebase for ad measurement. 16 October 2026: from version 1.2.4 the nutrition calculator's body details, your calorie and protein targets and your Profile name stay on your device, our server discards them when older versions send them, and they have been deleted from the account copy; explained why allergies and diet are kept in the account copy and the consent they rest on; named OpenAI as the processor for recipe import and described the stored recipe photos, which are filed under your account id; described the name and profile picture shared by Google sign-in and the security records of sign-in sessions; listed what in-app feedback stores and when it is deleted with your account; described the abuse-prevention counters; and listed what Delete account removes and which records others keep. 18 October 2026: described recipe import from a photo, for which the photo you choose is sent to OpenAI to read the recipe and is not stored by Mash, and only the recipe text extracted from it is saved with your app data; and described the monthly count of free imports kept for accounts without Mash Pro. 19 October 2026: described the recipe videos from YouTube and TikTok in Discover, and the anonymous count of imported public social-media links behind “Popular with Mash cooks”.
Questions about this policy: support@myfittrack.net.