Privacy policy

Last updated: 21 October 2026

Remy helps a household decide what to eat tonight, saves recipes and shows what friends cook. This page explains which data Remy uses for that, why, who else gets to see it, how long it is kept and what your rights are.

1. Who is responsible

Remy Cooks is the controller within the meaning of the General Data Protection Regulation (GDPR). For privacy questions, use the support form.

2. Which data, what for, and on what basis

2.1 Your account

• What: your e-mail address, and the handle and name you choose.
• Signing in: with a code we send to your e-mail; there is no password. An e-mail service sends that code and receives only your e-mail address and the code.
• What for: so you can sign in and find your recipes on more than one device.
• Basis: performance of the contract (GDPR art. 6(1)(b)).

2.2 Your household, preferences and allergens

• What: the names of the people in your household, what they don't like, and possibly their allergens.
• Where: this data is stored only on your phone. It does not go to our server. The one exception is your own name as a member of the household.
• Allergens:
  • These are health data, a special category (GDPR art. 9).
  • Remy asks for explicit consent per person before you can enter allergens. That consent is separate from all other terms.
  • You withdraw it by turning the switch off. Remy then erases that person's allergens from your phone.
  • Remy uses allergens only to warn you, and only if you turn on the Allergiewaarschuwingen (Allergy warnings) switch in Instellingen › Voorkeuren (off by default). Recipes never disappear, and we never call a recipe without allergen information safe.
  • If you enter someone else's allergens, such as your partner's, only do so if that person agrees. For a child under 16, you give that consent as parent or guardian.
• Basis: explicit consent (GDPR art. 9(2)(a)). For the other preferences: performance of the contract.

2.3 Recipes and what you cook

• What: the recipes you save or enter (title, ingredients, steps, source link, notes) and when you cooked what, with your rating.
• What for: saving, planning and making suggestions.
• Basis: performance of the contract.

2.4 Making a recipe with AI

When you give Remy a link, text or photo, Remy turns it into a recipe with an AI service we use for that. Which service that is, is in section 3.

• Your consent first. The first time you tap Importeren (Import), Remy asks whether it may read along, and says which service the material goes to. Nothing is sent until you choose Ja, lees mee (Yes, read along). If you choose Niet nu (Not now), nothing is sent and Remy asks again next time. While you cook, Remy doesn't ask: without your yes, it skips that step. If you turn off Recepten lezen met AI (Read recipes with AI) in Instellingen › Profiel en privacy, you withdraw your consent: Remy sends nothing more to that service and you enter recipes by hand.
• What the AI service receives: only the recipe material. That is the text of the page or the caption (with the creator's name if it's there), text you paste yourself, or the photo you choose. And the first time you cook a recipe, that recipe's ingredients and steps, so Remy can show per step what you need.
• What the AI service does not receive: your e-mail address, your name, your account or anything about your household. The request goes through our server, not from your phone.
• How the AI service handles it: we use a paid, business version. Under its terms, the provider does not use what we send to train its models or improve its products. The provider may keep it for a limited time to detect abuse, and may process it outside the EU (see section 3).
• A photo is not kept, not by us and not in your library. Remy passes it on once and forgets it.
• Check the result. A recipe made by AI can contain mistakes. Check the ingredients, especially if there's an allergy.
• YouTube: for a YouTube link, our server asks Google's YouTube Data API for the title and description. Only the video id is sent.
• Limiting abuse: per import we keep one line: a value derived from your account that can't be traced back (or a salted hash of your IP address), the platform and the time. These lines are erased automatically after 48 hours.
• Public recipes: a recipe that comes from a public web page or video may be kept as a public recipe, so the next import is faster. It does not say who imported it.

Basis: for sending to the AI service: your consent (GDPR art. 6(1)(a)), which Remy asks for before anything is sent for the first time. You withdraw it by turning it off; what was already sent remains lawfully processed. For the import lines: legitimate interest (GDPR art. 6(1)(f)), namely preventing abuse and disproportionate costs.

2.5 Videos and preview images from other platforms

• To show the image for a TikTok or Instagram recipe, your phone requests it from TikTok or Meta (oEmbed).
• When you play a source video, your phone loads the player of YouTube, TikTok, Instagram or Facebook.
• Those platforms see your IP address when that happens. Their own processing, such as cookies in their player, is covered by their privacy policies.
• A video never plays by itself.

2.6 The social layer: what others see

• Every signed-in user sees your handle and your name, and can find you by your handle.
• People who follow you see what your household cooks and saves, with the member's name, as long as Kookacties delen (Share cooking activity) is on. It's on by default; you turn it off in Instellingen › Profiel en privacy. If you chose Niet delen (Don't share) when Remy asked you earlier, it stays off.
• Your ratings count anonymously towards a recipe's overall ranking. People who follow you also see your rating with your name as long as Receptcijfers tonen (Show recipe ratings) is on. For new accounts it's on by default; you turn it off in Instellingen › Profiel en privacy.
• A public profile (off by default) also lets people who don't follow you see what you cook.
• Sending recipes:
  • You can send a recipe to someone you find by handle, with a note of up to 140 characters.
  • Only you and the recipient see it.
• Comments: comments under a recipe (up to 280 characters) are seen by you and the people who follow you.
• Who you follow:
  • Only you and the other person see that.
  • With friend suggestions we only show how many contacts you have in common, never who.
• Ate along: you can mention someone who ate with you. That name only becomes visible once that person confirms it.

What you cook can say something about your religion or health, for example halal or gluten-free. Remy doesn't ask about that and infers nothing from it. If you don't want to share it, turn off Kookacties delen and Receptcijfers tonen.

Basis: performance of the contract (GDPR art. 6(1)(b)). For Kookacties delen and Receptcijfers tonen also our legitimate interest (GDPR art. 6(1)(f)), namely an app in which friends see what the other likes; you object by turning the switch off. For a public profile: consent (GDPR art. 6(1)(a)), which you withdraw with the same switch.

2.7 Reporting, blocking and moderation

• Reporting is possible on a comment, on a recipe someone sent you, and on someone else's profile. A report contains who reports, who is reported, what was reported and when.
• Blocking is possible in the same places. Someone you block can't send you anything and no longer sees what you cook.
• Word filter: handles, names, notes and comments are checked against a list of slurs. A text with such a word is not saved.
• What the administrator does: Remy's administrator looks at every report within 24 hours. They can remove a comment or a sent recipe, reset a name or block an account. Only the administrator has that access, and it is granted per person in the database.
• Basis: legitimate interest, namely a safe environment and the requirements of the App Store.

2.8 Crash reports and usage statistics

• Crash reports (Sentry, EU region):
  • When the app crashes, a technical report goes to Sentry.
  • We don't send personal data with it. User, request data and web addresses are removed before sending.
  • Basis: legitimate interest, namely keeping the app stable.
• Usage statistics (PostHog, EU cloud in Frankfurt): on by default, can be turned off.
  • This is on by default, as the terms say. You turn it off in Instellingen › Profiel en privacy; after that Remy counts nothing.
  • When it's on, we count a fixed, short list of actions, for example "recipe imported", with app version and platform.
  • This happens under a random id per installation, not your account or e-mail. Your IP address is not kept and no location is derived from it.
  • PostHog receives no text and no ratings. There are no screen recordings and nothing is captured automatically.
  • Basis: legitimate interest (GDPR art. 6(1)(f)), namely seeing which parts are used in order to improve Remy. Because these are statistics with little or no impact on your privacy, this is allowed without prior consent (Dutch Telecommunications Act, art. 11.7a(3)(b)).

2.9 What Remy does not do

• No ads.
• No tracking across apps or websites, and no advertising id.
• No selling of data.
• No access to your microphone or location.
• Access to your photos or camera only at the moment you choose a photo yourself.
• The clipboard is only read when you tap plakken (paste) yourself.
• Notifications (the 4 pm suggestion, cooking timers) are scheduled on your phone itself. Nothing goes to a server for that.

2.10 Contacting us

• What: when you send a message with the form in the app (Instellingen › Contact en feedback) or on the support page: the topic, your message, your e-mail address so we can reply, and in the app also the app version and whether it runs on iOS or Android.
• How: the form is handled by Formspree, which passes the message on to our inbox. In the app, the screen tells you which address goes along before you send.
• What for: answering your question, fixing what doesn't work and handling reports and deletion requests.
• Basis: performance of the contract (GDPR art. 6(1)(b)) and, for suggestions, our legitimate interest in improving Remy (GDPR art. 6(1)(f)).

3. Who processes data for us

A data processing agreement applies with every processor. Apple distributes the app through the App Store and is itself responsible for that. TikTok, Meta and YouTube are not Remy's processors: your phone contacts them itself when you load a preview image or video (see 2.5).

Transfers outside the EU: Supabase, Google (YouTube and Gemini), Sentry and PostHog have a parent company in the United States, and Formspree is based there. Where data leaves the EU, or can be accessed from the US, this happens under the EU-US Data Privacy Framework if the supplier is certified for it, and otherwise under the European Commission's standard contractual clauses in their data processing agreement. The same applies to the e-mail service, unless it processes only in the EU.

4. How long we keep data

• Account, recipes, cooking moments, social data: as long as your account exists.
• Reports: as long as the accounts of the reporter and the reported person exist.
• Import lines (abuse limiting): 48 hours.
• Photos for import: not kept.
• Data on your phone (household, preferences, allergens): until you erase it, withdraw your consent (allergens), delete the app or delete your account.
• Crash reports: at most 90 days.
• Usage statistics: at most 12 months.
• Server logs and backups at Supabase: at most 7 days. After that, what you deleted is gone there too.

5. Deleting your account

In the app: Instellingen → Account → Account verwijderen (Settings → Account → Delete account), with a second confirmation. Then the following happens:

• Remy deletes your household on the server with everything under it: recipes, cooking moments and import lines.
• Then Remy deletes your account and your e-mail address. With that, your profile, follows, ratings, sent and received recipes, comments, reports you made or that were about you, and blocks disappear too.
• Finally, Remy erases the data on your phone.

What remains:

• Public recipes that came from a public source (see 2.4). They don't say who imported them.
• Do you share a household with someone else? Then you leave it, but the household remains for the other person.
• A trace can remain in server logs and backups for up to 7 days (see 4).

Can't open the app anymore? Send us a message with the support form and choose Delete my account, and we'll delete your account.

6. Your rights

You have the right to:

• access the data we have about you;
• rectification of what is incorrect;
• erasure of your data;
• restriction of processing;
• portability: your data in a common file format;
• object to processing based on legitimate interest;
• withdraw consent you gave, at any time. What already happened remains lawful.

To do so, use the support form. We respond within a month, and may ask you to confirm that the request comes from you. If you disagree with how we handle your data, you can file a complaint with the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens.

7. Age

Remy is meant for people aged 16 and over. If you're younger, please don't create an account. If we notice an account belongs to someone under 16, we delete it. You can add a child as a member of your household. That data stays on your phone (see 2.2).

8. Security

• Traffic between the app and the server is encrypted (https).
• The database shows each user only what they may see. That is set in rules per table (Row Level Security).
• Keys for external services, such as the AI service, are kept on the server, not in the app.

9. Changes

If this policy changes materially, we show that in the app the first time you open it after the change, with a button to Settings to turn something off. What you had turned off yourself stays off. The date at the top says which version applies.