Privacy Policy

Effective date: November 3, 2026

1. Data Controller

RecipeHub is run by Jeroen Stroobants, Lenniksebaan 195, 1070 Brussel, Belgium, who is the controller of your personal data. For any questions about how your data is handled, you can reach us at hello@recipehub.cc.

2. What We Collect

When you use RecipeHub, we store:

  • Account info — your name, email address and profile photo (when your sign-in account has one, for example your Google account), provided via Clerk during sign-up
  • Your content — recipes, cookbooks, meal plans, shopping lists and notes you create or import; in a family, who planned, added, checked or changed each item, and who eats with the family (a name and an age range, also for people without an account, such as children)
  • Photos — the photos you send to a photo import. When you keep them with the recipe (“Keep the photos with the recipe”, on unless you turn it off), they stay with it as its original pages, shown under “Original”, in order, until you remove them or delete the recipe. Every photo is re-encoded as soon as it arrives, which drops its metadata (where and when it was taken, the camera), before we store it or send it to an AI provider. With each photo we keep a fingerprint of its content (a hash), so we can find its copies if it is reported (see Reporting a photo).
  • Invitations — the email address you invite someone at, used to send them the invitation
  • Waitlist — your email address, when you joined, and the page and campaign link (utm parameters) you joined from, or that you joined in the iPhone app, so we know which pages bring people in; the language of the page or app you joined from, so we write to you in it; and when we sent your sign-in link again, and whether we sent the reminder (see Emails we send)
  • Usage events — a short record of the steps that tell us whether RecipeHub works for people: that you signed up (and the campaign link you came from, if any), created a recipe (and how: typed, imported or copied), planned a meal (and whether the recipe was yours, a family member’s or one of the starter recipes), made a shopping list, imported a recipe (the website’s domain, never the full link, and why an import failed) or reached a limit of your plan. They are linked to your account and kept in our own database.
  • AI usage records — for each call to an AI provider made for you (reading an imported recipe, translating one, sorting a new ingredient name): what it was for, which model, how many tokens it used, what it cost and whether it worked. Never what was sent or answered. They tell us what RecipeHub costs to run per account, and are kept in our own database.
  • Failed imports — when an import fails, what you gave it: the link, and the text you pasted. We keep it for 14 days to find out why the import failed, even if you remove the failed import from your list, and then delete it. Never the photos you uploaded.
  • Error reports — when something breaks in the app or on our server: the kind of error, where in our code, and on which page. They hold no account or person: we remove email addresses, links, ids and other values from the error’s text before we keep it.
  • Request logs — basic logs for debugging and security (IP address, timestamps, endpoints accessed)

We use no third-party analytics: the usage events and error reports stay in our own database and are never shared or sold. We don’t track you across sites or build advertising profiles.

3. What Others Can See

RecipeHub lets you plan and shop together with your family, and share recipes and cookbooks. Depending on what you share, other people see some of your data:

  • Your family — the other members see your name, your profile photo, your role (admin or member), your age range and when you joined. They see your recipes except the ones you keep private (with your own notes on them), the notes you write on family recipes, your shopping lists except the private ones, and the family’s meal plan, eaters, shopping notes and stock, with who planned, added, checked or changed what. They also see the original pages of the recipes they can see. Admins also see the addresses of open invitations. Nobody in your family sees your email address.
  • People in a cookbook — the owner and members of a shared cookbook see each other’s names and photos, and the recipes in it (never private ones) with their notes and their author’s name and photo, but not their original pages, unless they are in your family. Someone in your family can add your recipes to a cookbook they share with others.
  • Anyone with a link — a recipe link shows the recipe and its notes, without your name; a cookbook link shows the owner’s name and only their own recipes in it; a shopping list link shows the list without anyone’s name or photo; a family invitation link shows the inviter’s name and how many members the family has.
  • The RecipeHub team — when we check by hand whether a new ingredient name was sorted under the right ingredient, we see the name, the name and email address of whoever brought it in, and up to three recipe titles with the line the name is written in (for example “Kung pao · 2 tsp chilli flakes”). Never the rest of those recipes.

The original pages of a recipe show only to you and your family: never on a shared link or in a link preview, and a copy someone saves from a shared link doesn’t take them.

If you leave a family, what you added there stays with the family under your name and photo; the notes you wrote on the family’s recipes are deleted, and so are their notes on yours. A family member’s own version of one of your recipes keeps its own copy of the original pages, also after you leave the family or delete your account.

The link that loads a photo works for up to two days. Someone who opened a photo before losing access to it (they left your family, or you removed the photo) may still load it until that link runs out.

Your profile photo is shown only to people signed in to RecipeHub, never on a shared link. Your name and photo come from your sign-in account; change them there and RecipeHub follows.

4. Emails We Send

Besides the emails Clerk sends to sign you in, RecipeHub sends these emails, in English or Dutch:

  • Your sign-in link, when you join the waitlist and there is room in the beta, or later when we let you in. It works for 30 days.
  • The same link again, when you join again while your link is unused: at most twice, and at most once a day, so nobody can fill your inbox by typing in your address.
  • One reminder, three days after your sign-in link, if you haven’t used it, and only once.
  • A family invitation, when someone invites your address to their family (see What We Collect).

We send no other emails today. If we add any (for example tips for getting started), this policy will say so first, and each of them can be stopped in one click.

Our emails carry no tracking pixel, and their links aren’t rewritten to count clicks. The RecipeHub logo in them loads from our own website, the same image for everyone.

To stop the reminder or leave the waitlist, use “Take me off the list” in the email, reply to it, or write to hello@recipehub.cc. We delete your entry and revoke your link. We keep only a code of your address made with a secret key (a keyed hash): it doesn’t show your address, but it lets us recognise it if it is typed in again, so it never gets a reminder again.

Under the GDPR, we process your personal data on the following legal bases:

  • Contract performance — your account info and content are processed to provide the RecipeHub service you signed up for, and your waitlist entry to send the sign-in link you asked for, again when you ask again (Art. 6(1)(b) GDPR)
  • Legitimate interest — request logs and error reports are processed for security, debugging, and preventing abuse; the address someone invites to their family, to send that invitation; your waitlist entry, for the one reminder about a sign-in link you asked for and haven’t used; the page and campaign link you joined from, to know which pages bring people in; usage events to learn which parts of RecipeHub work and which don’t, so we can improve it; AI usage records to know and limit what running RecipeHub costs per account; what a failed import was given, to find out why it failed and fix it (Art. 6(1)(f) GDPR). You can object to your usage events at any time by emailing us, and we stop recording them for your account.
  • Consent — AI recipe extraction is initiated by you each time you use the import feature (Art. 6(1)(a) GDPR)

6. Authentication

RecipeHub uses Clerk for authentication. Clerk handles your login credentials, session management, and email verification. Your password is never stored on RecipeHub servers. See Clerk’s Privacy Policy for how they handle your authentication data.

7. Cookies

RecipeHub uses a minimal set of cookies:

  • Session cookies — set by Clerk to keep you logged in
  • Theme preference — remembers your light/dark mode choice

We do not use tracking cookies, advertising cookies, or third-party analytics. Usage events and error reports use no cookies either.

8. Third-Party Services

RecipeHub relies on a small number of third-party services:

  • Clerk — authentication and session management; it also keeps each sign-in invitation we make for your address, with the campaign link you joined from; the link works until it is used, replaced or expired, and Clerk keeps the record after that, also when we delete your waitlist entry; and with your account, the page and campaign link you signed up from
  • Anthropic & OpenAI — AI-powered recipe import and translation. When you import a recipe, the page’s content, the text you paste or the photos you upload (without their metadata) are sent to one of these providers to read the recipe; when you translate one, its text. Whatever personal data you include in what you paste or photograph goes along; it is used only to read the recipe.
  • Resend — sends our emails: an invitation to someone you invite to your family (their email address and your name), and the waitlist’s sign-in link and reminder (your email address, your sign-in link and the email’s text)
  • Discord — tells us when someone joins the waitlist or makes an account (the page and campaign link they came from, not who), and brings us the feedback you send from the app, with your name (or your email address when your account has no name)
  • Railway — hosts the app and its database, in the European Union, and stores your photos (see Data Storage)
  • Tigris Data — runs the storage Railway keeps your photos in, as Railway’s provider
  • Cloudflare — serves this website and our domain’s DNS, protects our internal dashboard, and checks that the waitlist form was filled in by a person (Turnstile, which loads once you start on the form on this website, and in the iPhone app when you join the waitlist there)

9. Data Storage & International Transfers

Your data is stored in a PostgreSQL database hosted by Railway in the European Union. Database access is restricted to the RecipeHub application via private networking. All connections use TLS encryption.

Photos are stored in a Railway Bucket in Amsterdam, run by Tigris Data, Railway’s storage provider. To load quickly, Tigris may keep a temporary copy of a photo closer to where it is opened, also outside the European Union, protected by the safeguards below. Only the RecipeHub application can store or delete a photo; the app gets a link to open one that works for up to two days.

Some of our third-party service providers (Clerk, Anthropic, OpenAI, Resend, Discord, Railway, Tigris Data, Cloudflare) are based in the United States. When your data is transferred outside the European Economic Area, these transfers are protected by appropriate safeguards, including Standard Contractual Clauses (SCCs) approved by the European Commission or the EU-U.S. Data Privacy Framework where applicable.

10. Your Rights

Under the GDPR, you have the following rights regarding your personal data:

  • Access — everything you store is visible in the app. You can also request a complete copy of your personal data.
  • Rectification — you can edit your recipes, cookbooks, and meal plans directly in the app
  • Erasure — you can delete individual recipes and cookbooks, and delete your whole account yourself in Settings.
  • Data portability — you can download a machine-readable export of your data in Settings, your usage events, AI usage records and photos included (the photos as links that work for 7 days)
  • Restriction & objection — you can ask us to restrict or stop processing your data in certain circumstances, and object to our emails at any time (Art. 21 GDPR)
  • Withdraw consent — where processing is based on consent (e.g., AI recipe import), you can withdraw it at any time by simply not using the feature

We will respond to data requests within 30 days. To exercise any of these rights, contact us at hello@recipehub.cc.

If you believe we are not handling your data correctly, you have the right to lodge a complaint with the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit): www.gegevensbeschermingsautoriteit.be.

11. Data Retention

We retain your data for as long as your account is active. If you delete your account, we will remove your personal data within 30 days. In a family with other members, the meals, shopping lists, shopping notes, stock and eaters you added stay with the family, marked as added by a former member, and copies family members made of your recipes stay theirs. Notes you wrote on recipes are deleted. A waitlist entry that never becomes an account is deleted one month after we first sent its sign-in link, which works for 30 days; an entry still waiting for room in the beta is kept while it waits. The code of an address that left the waitlist is kept as long as the waitlist exists. Usage events are kept for 13 months and then deleted; they go with your account when you delete it. AI usage records are kept for 13 months and then added up into daily totals without any account; when you delete your account they stay, without your account, as costs we had. What a failed import was given is deleted after 14 days, and with your account. The photos a photo import keeps with its draft are deleted when you save the recipe without them or dismiss the draft, and 30 days after the import if you leave the draft alone. Original pages are deleted when you remove them, with their recipe and with your account; a family member’s own version of your recipe keeps its own copy, also after you leave the family or delete your account. During the beta, photos aren’t backed up (see the terms, section 3). Error reports, which hold no account, are deleted 30 days after the error was last seen. Request logs may be retained for up to 90 days for debugging purposes.

12. Reporting a Photo

If you believe a photo stored in RecipeHub is illegal, for example because it infringes your copyright or shows you without your consent, write to report@recipehub.cc, in English or Dutch. Your report needs:

  • the link to the recipe or page where the photo shows
  • why you believe the photo is illegal
  • your name and email address
  • a statement that you believe in good faith that what your report says is accurate and complete

We confirm that we received it, decide without undue delay, and tell you what we decided. A person reads every report; we use no automated tools for it. If we take a photo down, we delete it with every copy of it, which we find by its fingerprint, and we tell the person who uploaded it what we removed and why. The terms (section 7) say how we handle reports.

13. Changes to This Policy

We may update this privacy policy from time to time. We will notify users of material changes via email or an in-app notice. The effective date at the top of this page will be updated accordingly.

14. Contact

Questions about your data or this policy? Reach out at hello@recipehub.cc.