For recipe authors
Updated November 12, 2026
iwant2eat is a private recipe vault: people keep the recipes they cook from in one place, in their own account. Some of those recipes come from websites and social posts, possibly yours. This page says what happens then, who can see the result, and how to reach us if you want something changed.
What happens when someone saves a recipe by link?
A person gives us the link to one page, by pasting it, by sharing it from a phone, or with our browser extension. Our server reads that page, or the person's own browser does. We don't crawl websites: a recipe page is read because someone asked to save it.
When our server reads a page, it says who it is: its user agent is
iwant2eat/1.0 with a link to this page. It follows your
robots.txt: a page it disallows for iwant2eat, or for every
robot (*) when it doesn't name us, isn't opened, and the person is told so.
To close your site to our server alone, add this to it:
User-agent: iwant2eat
Disallow: /
robots.txt speaks to programs, not people: someone can still save the page
from their own browser with our extension or their phone's Share button, which reads
what they see on screen, or copy the recipe in by hand. To stop that too, see the last
section.
AI then turns the page into a recipe they can use: title, ingredients, steps and estimated nutrition. That person's copy keeps:
- the structured recipe;
- the text we read from the page, for a week after the recipe last changes, so they can check the recipe against it and fix it. Then we delete that text;
- one photo from a website, its main one; from a social post, the post's photos, five at most. Recipes saved before November 6, 2026 may still hold up to five photos of a website;
- the link to your page, shown as "Original link" on the recipe page and printed with the recipe: on paper, in its PDF and Word copies, and in its text when it is sent on.
For a video, we read its title, description and captions, transcribe the speech and, if the recipe still isn't there, look at its frames. We don't keep the video, its sound or those frames. The transcript is removed once the recipe is written, or with the page's text for an Instagram reel, which we can't read a second time.
Who can see it?
The person who saved it and, if they use a family account, the members they added (five at most). These pages need a sign-in, and search engines can't reach them.
A recipe saved by link is never shown whole to anyone else. Nothing on iwant2eat is public: what a person shares opens only for their friends on iwant2eat, signed in. When they share a recipe saved by link, a friend sees its title, its list of ingredients and the full address of your page, with a button that opens it. Not your method, not your text, not your photos. A friend who wants the recipe saves it from your page themselves, the same way the first person did. It is left out of any copy a friend takes of a whole collection. If the person uses the Email button on the recipe page, the email carries a link to your page, not the recipe.
This doesn't apply to iwant2eat's own staff accounts. What we share from those accounts is our own responsibility. If you find your work there, tell us and we'll take it down.
Your own site. If you save recipes from your own site to your own iwant2eat account, write to us from that account's address: we can let that account share them whole with its friends. The same pages saved by anyone else stay closed.
A recipe someone typed, pasted as text or photographed isn't saved by link, so we can't tell where it came from. That person can show it to their friends on iwant2eat (people they invited, or sent the recipe's link to), and to nobody else: there are no public links, and a share link opens only for a signed-in friend of theirs. If your recipe reaches you that way, see below.
What else do you do with it?
- iwant2eat is paid for by its users' subscriptions. There are no ads on recipe pages, and we don't sell or license saved recipes to anyone.
- We don't train AI on them. The AI that reads a page is Claude, through Anthropic's API; see our Privacy Policy.
- There is no directory. Nobody can browse or search other people's recipes; search covers only the recipes in one's own account.
- A person can print their copy or export it for their own use; the copy names your page. Recipes saved by link don't go into the PDF books people make of their collections.
Why let people keep a copy at all?
We see a private copy, kept by one person to cook from, as the same thing as a printout or a screenshot. We draw the line at publishing it, which is why a friend gets only the ingredients and your address, and goes to your page for the rest. This is our position, not legal advice.
How do I complain or get my recipes removed?
You've seen your recipe on an iwant2eat page (an address with
/r/ or /c/ in it, which opens only for its owner's
friends). Send a notice as described in our
DMCA Policy, with that address in it.
You want recipes saved from your site removed from people's accounts. You can't see private copies, so you can't give us their addresses. Give us the address of your page, or of your whole site, instead: each copy keeps its link, so we can find them from that. Send it as a notice as described in our DMCA Policy. We remove what a valid notice covers and tell the person whose copy was removed, who may send a counter-notice.
You don't want your site's pages saved at all. Tell us the site's address and we close it: links to it can't be saved from then on, and our server doesn't visit it. We can do this for a site of your own, not for one account on Instagram or Facebook, because their links don't name the author. Someone can still type a recipe in by hand or photograph it, which we have no way of telling apart.
Anything else, such as a question or a correction: write to support@iwant2eat.com. A person reads it and answers.