Your email, and the name on your account: the household name you type, or the name your sign-in provider sends if you use one. The recipe links you send us, the recipes we extract from them, the photos you keep, your notes, collections and week plan. If you enter one in Settings, a postcode: we store it and do not use it for anything yet. That's the product working, not surveillance.
To find out where signing up breaks, like a magic link that never arrives, we note the steps of the sign-in itself against a random, throwaway id that expires after 7 days. For the email steps we also keep a one-way fingerprint of your address, so that two attempts by the same person can be told apart without storing the address in that record. If a sign-in email fails to send, we keep the error text. These records are not linked to your recipes.
Yumzi does not collect dietary or allergy data today, and there is nowhere in the app to enter it. If we build diet-aware planning, that is health data under EU law (AVG art. 9): we will ask for your explicit yes first, use it only to plan your dinners, and let you delete it in one tap.
Supabase (EU region) for your data, Resend (EU region) for the emails we send you. The website and the app are served from Vercel in Frankfurt. When something breaks, we send a technical report to Sentry, our error monitoring provider, so we can fix it. It holds what went wrong and a scrambled code for your household. It never holds your email, your recipes or your health information. These companies act on our instructions. We never sell data, and no third party gets it for advertising. Everything travels over HTTPS.
If you sign in with Apple or Google, that company confirms your email address to us and we never see your password. Google also sends the name on your account, and we use it as your household's name. Supabase, which runs our sign-in, keeps the profile details they send, such as a link to your profile photo; Yumzi does not show or use them. We never post anything to those accounts. If you use Apple's Hide My Email, we only see the private address Apple gives us.
The Albert Heijn hand-off is a link into your own AH session. We never see your AH login, we never check out for you, and links may carry an affiliate tag that costs you nothing.
Recipes come from the creators you chose to save. We extract, never invent. Shared caches store structured data, not creator text.
We record what happens in the app, so that we can fix it and decide what to build: which screens open, and when you save, cook, plan, vote, share or send a list to a shop. Each record carries your account id, the platform and its version, and the country your connection comes from, which we work out from your network address. We store the country in our own records, not the address. The country is also how we decide whether to show the Albert Heijn step. To count page views we use Vercel Web Analytics, which sets no cookies. We do not use Google Analytics, advertising identifiers or any ad network.
When you send us a link, we pass it to the services that read it, and only to them. The link goes to Firecrawl for web pages, or to Apify for TikTok, Instagram, Facebook and YouTube, to fetch the public page or video. YouTube and TikTok are asked for the title and the author. The audio of a public video goes to OpenAI, to be turned into text. The text, and the frames of the video, and the photos if you add them, go to Anthropic, which reads out the ingredients and steps. These services act on our instructions. We do not say here what they keep, because that is set by their terms and not by our code.
If you allow notifications, we store a device token with your household and your account, so that we can send you a reminder about your dinners. The push service built into your phone's system delivers the message, and sees the token and the text. The text can name dishes you chose. You can turn notifications off in your phone settings, and signing out detaches the token. On Android, Firebase also gives your device an installation id. Before you create an account, the app can keep its notification token with the same random id as the sign-up steps, not with you, for at most 30 days. We use it only to tell you that something you were trying to do, like signing up, works again. On an iPhone that notification arrives quietly in Notification Center. The token is deleted when you sign in or after 30 days.
We email you a sign-in link or code, a welcome message when you create an account and a small number of reminders about your dinners and about getting started. If the sign-up screen told you we email you, these emails are on until you turn them off, in the app’s Settings or with the link in any email. Every reminder has an unsubscribe link. We keep a record that you asked not to receive reminders or marketing emails, so we never send you those again. Sign-in codes you request yourself still arrive.
When you add photos of a recipe, Yumzi's AI partners read them to write out the recipe. We remove each photo's location and device details first. If the photos become a recipe, we keep a copy of each of them, up to four, at most 1200 pixels on the longest side, with that recipe. The photo that shows the finished dish, or your first photo if none does, is the recipe's picture. Photos that do not become a recipe are not kept. For recipes you added before 1 Nov 2026 we kept only the picture. The photos are stored privately. Only the people in your household can see them in Yumzi, and a recipe you share never shows them. You can remove a photo on the recipe page, under More, then Photos. Hiding a recipe does not delete its photos, so the recipe comes back with them when you show it again. The photos are deleted with your household's recipes when the last person in your household deletes their account.
When you add a photo of a dish you cooked and leave Keep this photo on, we keep a copy in your Yumzi, at most 1200 pixels on the longest side, with that recipe. We remove its location and device details, and we do not send it to an AI partner. Only the people in your household can see it in Yumzi. The card you share is made on your phone, and only you decide where it goes. If you turn Keep this photo off, or remove the photo later on the recipe page under More, then Photos, we delete it. Dish photos are deleted with your household's recipes when the last person in your household deletes their account.
If you join Creator Partnerships we store your handles and the platforms you post on, your referral code, and the counts and earnings your dashboard shows. If you arrived through a creator's link or code, we store that creator's code on your account so we can pay them; the creator sees counts, never who you are. We do not store bank details in the app; we ask for them by email when a payout is due. We also store your accepted terms and referral rates, verified purchase references, confirmed net receipts, and earnings and payment records. Deleting an account removes the personal partner profile and household links; separate accounting records remain for reconciliation of commissions, refunds and payments. Contact hello@yumzi.food about an outstanding creator balance or an accounting-data request.
Yumzi uses a session cookie to keep you signed in. If you open one of our campaign links (a link with utm tags, such as a creator's link), your browser gets two first-party cookies for 30 days: yz_utm, which stores the campaign's source, medium and name (for a creator's link, the creator's code, so we can pay the creator if you sign up), and yz_ft, which stores the page you landed on and the name of the website you came from. If you create an account, we save these once with your household so we know which campaign brought you. They are not shared with anyone and are not used for advertising or profiling. If you open a recipe someone shared with you, we set a cookie called yz_ref for 30 days, so that if you create an account we know which shared link brought you. It holds the link's code and nothing about you. We also set a few more first-party cookies: yz_anon, a random id for the sign-up steps before you sign in, for 7 days; yz_invite, which remembers a household invite link, for 14 days; yz_app, which marks the app, for 1 year; yz_push, which holds your notification token so that it can be detached when you sign out, for 1 year; yz_m01, which notes that the sign-up screen showed our email notice, until your sign-in finishes, for 1 hour; yz_next, which remembers where your sign-in link should take you, for 1 hour; and a signed cookie, for one hour, that ties a sign-in request to the browser that made it. None is used for advertising or profiling. We do not use third-party tracking cookies. If you open a friend's invite link, or a recipe someone shared with you, your browser gets a first-party cookie named yz_friend for 30 days that stores the invite code of the person who sent it, so we know who invited you if you sign up. We count that the link was opened, for the person who sent it, without your name or address. We keep which household invited yours. To give each person the invite reward only once, we keep scrambled codes made from your Apple, Google or Facebook account number and from your email address. They cannot be turned back into that number or address.
If you install the app through an ad or a campaign link in the App Store or on Google Play, the app reads once which campaign led to the install: Google Play gives us the campaign's source, medium and name, and Apple gives us numbers for its Apple Ads campaign, ad group and keyword. If you create an account, we save this once with your household so we know which campaign brought you. It is not shared with anyone and is not used for advertising or profiling. On iPhone, the app also tells Apple, without anything that identifies you, which steps you have taken in Yumzi, such as signing up, reading or cooking recipes, inviting someone or choosing Pro, so Apple can report to us which ads lead to people using Yumzi.
You can delete your account in the app (Settings, then Delete account), on yumzi.food, or by email. Deleting removes your sign-in. If you are the last member of your household, it also removes the household: recipes, photos, notes, collections, week plans, votes, device tokens, share links, the emails we logged, and the usage records tied to the household. If others are still in your household, only your own profile and sign-in go, and they keep the shared recipes. A few things stay, and for how long: Usage records that belong to no household, such as the steps of signing in. They can carry your account id or a one-way fingerprint of your email address, and they are not linked to your recipes. They have no fixed deletion date yet. We keep a record that you asked not to receive reminders or marketing emails, so we never send you those again. Sign-in codes you request yourself still arrive. If you took part in Creator Partnerships: the financial records of your payouts, meaning earnings, payments, receipts, and the accepted terms and rates they were calculated under. We remove your partner profile and its link to your household. We keep those financial records for seven years from the end of the financial year they belong to, because Dutch tax law requires it. Backups are overwritten on our database provider's schedule. The full list is at https://yumzi.food/support/delete-account. We do not cancel a subscription for you: cancel it in the App Store or in Google Play.
See, correct, export or delete your data: one email, or Settings for deleting your account. Under the AVG (GDPR) you can also object to how we use your data, and withdraw consent. We answer within one month.
Questions, requests, complaints: hello@yumzi.food. You can also complain to the Autoriteit Persoonsgegevens.
Fair Comparisons · KvK 42031267 · Rotterdam · Last updated 3 Nov 2026