This is an English translation of the Dutch original, provided for convenience. The Dutch version is legally binding.
Last updated: 8/20/2026
Receppy is an app for saving and managing recipes. This privacy policy describes how we handle your data.
We process data you provide yourself: your account details (via sign-in), your recipes (title, description, ingredients, steps, images, categories, servings, preparation time, optionally estimated calories per serving, difficulty level and wine pairing, etc.), the number of times you have completed a recipe (counter per recipe), your favorites and your star ratings per recipe. We use this data to make the app work and to link your recipes, favorites and ratings to your account. If you share to the installed Receppy web app on Android via the share sheet, we temporarily process the title, text and/or URL of that action to send you on to recipe import; we do not keep that share payload as a separate record. We do not review recipe content for completeness, food safety or suitability for your health; see the terms and conditions.
For the "My statistics" feature we keep counters per account in our database (Upstash Redis): how often you activate cooking mode, start a cooking timer and complete a recipe. Daily counters (per calendar day) are automatically deleted after about 13 months; the totals remain stored with your account. For the leaderboard of completed recipes we only store a score per account ID; you only see your own position and the total number of participating cooks — names or scores of other users are never shown, and nothing about you is shown to others either. We also record per account through which entry point you use Receppy (website, installed web app or the iOS app), so we know where to focus our attention. In addition, we keep fully anonymized usage counters (numbers per feature per day, without any link to your account) to improve the app. If a recipe import via a link fails, we temporarily store that URL (without any link to your account) so we can improve the import for that website. When your account is deleted, your personal statistics and leaderboard score are deleted.
Signing in is handled by Clerk. We do not store passwords. Your recipes, favorites and ratings are stored in a database (Upstash Redis) and are only accessible to you after signing in. The recipe overview fetches the matching recipes per page via an API (same account data; your search and filter choices are included in the request and are not stored as a separate profile). For speed, your full recipe list may briefly (tens of seconds) sit in that same Redis database as an intermediate buffer; that buffer is cleared as soon as you add, edit or delete a recipe (or a related action affects the list). The app runs on Vercel; traffic is encrypted (HTTPS). When a new account is created, we may send an internal notification by email (via Resend) to our admin address including, among other things, your Clerk user ID and the email address of your account, so we can track sign-ups. Once a day (automated), that same admin address may receive an internal overview with aggregated figures (new accounts, new recipes, use of the fridge AI that day, indicators of low activity, and — where this has been set up technically — aggregated Google Analytics figures for that same day) and an up-to-date list of all accounts with email address, number of saved recipes and how many recipes that user created on that report day — so we can monitor the platform.
When you share a recipe, the recipient gets a link through which the recipe (its content only) is visible. Shared recipes are not searchable; the recipe can only be viewed with the link. You only share recipes for which you are responsible yourself and which you are entitled to share. Do you believe someone is infringing your rights through the app? See the terms and conditions (complaints about content) and email info@receppy.nl.
With Receppy you can optionally upload a photo of your fridge or pantry to have a recipe suggested. That photo is only sent to our server during the request and from there to Mistral AI (EU/contractual arrangements: see Mistral's privacy policy) to generate a text suggestion, possibly with a short list of what the model thinks it recognizes in the photo; that list is only shown in your session and is not stored separately in Redis. We do not store that photo permanently; to limit too many consecutive requests, a temporary marker may briefly (roughly a few seconds) be set in Redis per user (no content of the photo). You save the generated recipe yourself as a regular recipe in your account (Redis) if you choose to keep it. The app may put your fridge photo (as a shortened data URL) in the Image field; if you leave it there when saving, that value is stored with the recipe in Redis (you can clear the field before saving or replace it with a regular https URL or upload). If generation fails, the error message may show a short token count from Mistral (technical diagnostics; no content of your photo).
If we enable this, carefully selected parties can read recipes via a secured server API under a separate agreement. Access uses a secret key (API key) known only to that party; there is no public search index. Only recipes of explicitly permitted accounts (recorded as Clerk user IDs in our server configuration) can be read through that route. The party receives the same kind of recipe data as in the app (title, ingredients, steps, etc.). We log server-side as usual; the party processes the received data in accordance with its own arrangements with the relevant account owner and this policy where applicable.
"Search recipes on the web" uses Google Custom Search; your search query is processed by Google in the process. Google may place cookies as part of this. See Google's privacy policy for more information.
When you import a recipe via a link (URL), our server fetches that page (such as a recipe website or a public Instagram post) to read public metadata or text. That page sees which server (User-Agent) makes the request; we do not keep the fetched HTML permanently, only the recipe you save to your account.
On the "My recipes" overview you can optionally use your microphone to speak a search term. The audio is then converted to text by your browser's speech recognition (or the operating system); Receppy's servers receive no audio recording, only the text you then see in the search field, which is sent locally to our API just like regular typing. Which party technically performs the recognition depends on your browser and device; consult that provider's privacy policy if needed.
For cooking mode we store locally on your device which ingredients and steps you have ticked off (localStorage); this data never leaves your device. Your shopping list (lines you add from recipes) lives locally in localStorage; if you are signed in, that same list is also linked to your account in our Upstash Redis storage, so it stays in sync across your devices. When you sign out, the local list remains. If you copy or share the list, your browser or operating system processes that text (clipboard or chosen app); that does not go through Receppy servers. If you go from the list to Albert Heijn (ah.nl), Jumbo (jumbo.com) or Plus (plus.nl), that site's privacy policy and cookies apply; Receppy does not send your search term to our servers. Cooking timers are only kept in the page's memory while you are viewing the recipe with cooking mode active and are not sent to a server. On some devices (such as iPhone), your browser's speech feature may briefly be used for a notification when a timer ends; that happens locally on your device. Your accessibility settings (contrast, text size, dark mode) are also stored locally only. If you click "Later" when asked to install Receppy as an app, that is remembered locally for about three days. If you dismiss the iOS app announcement on your recipe overview, we also remember that locally (localStorage) so it does not come back. For offline reading of your own recipes, after a successful sync we store a copy of your recipes locally in IndexedDB in your browser (per device and signed-in account). That copy only serves to show your collection when there is no network; we do not read that database from our servers. You can clear it via your browser (clear site data / storage for receppy.nl).
We use no tracking for advertising.
If we receive a formal request from a competent government authority to disclose users' personal data, we first assess whether the request is valid and legally binding; where necessary we seek legal advice. We reserve the right to challenge requests we consider unlawful or disproportionate. We aim to disclose only the minimum data necessary within the scope of the request and applicable law. We keep documentation of requests received and how we handled them (including legal basis, scope and parties involved), to the extent the law allows.
You have the right to access, correct and delete your data. You can manage or delete recipes, favorites and ratings yourself. You can clear the local checkmarks of cooking mode by clearing your browser data or by editing the recipe. You can empty your shopping list on the Shopping list page (which also empties the version on your account) or by clearing your browser data. For questions about your data, deletion, correction or this policy, you can contact us at info@receppy.nl.
