Privacy policy
Last updated: November 5, 2026
iwant2eat ("we", "the service") is a private recipe vault. This policy explains what personal data we collect, why, who we share it with, how long we keep it, and how to remove it. It is written plainly; nothing here is hidden in fine print.
Who we are
The service is operated by Volicsoftware, Inc., a New Jersey corporation, 19 Clive Hills Rd, Edison, NJ 08820, United States. It is the "controller" of your data in the sense of European law. For anything in this policy, write to privacy@iwant2eat.com. We have not appointed a representative in the EU or the UK; please contact us directly.
What we collect
- Account data: your primary email address, an optional display name, first/last name, avatar image, interface language and preferences, and a password hash (we never see your plaintext password). If you sign in via Google, Facebook or Apple, we receive an identifier and the email address they share with us.
- Recipe content: everything you paste, email, drop, link, or photograph into your vault — title, ingredients, steps, photos, notes, the original text, and any source URL. This is the whole point of the service. For a recipe saved from a link, the page's text is kept for a week after you last changed the recipe, then removed; the recipe and the link stay.
- Voice recordings: if you dictate a recipe or a shopping list, the recording is sent off to be turned into text and is not stored — we keep only the text.
- Scanned photos: a photo of your fridge, a store shelf, or a receipt is sent off to be read and is not stored. From a shelf or a receipt we keep what was read (products, prices, the store, and the place where you took it if you allowed your location); from a fridge, nothing.
- Additional emails: secondary email addresses you verify so the inbox (
recipe@iwant2eat.com) can ingest recipes forwarded from them. - Subscription data: your Stripe customer identifier, or your App Store transaction identifier, subscription status, trial and renewal dates. We never see or store your card number — Stripe or Apple handles payment.
- AI usage records: for every AI call made on your behalf, we record a timestamp, model name, token counts, estimated cost, and the question you typed (so you can see your own history on the AI budget page).
- Technical data about your visits: the IP address of your last visit and the country it belongs to (worked out on our own server, from a local database, so no third party sees the IP), your browser or our app's name and version, your device's time zone, and how you first found us — the campaign, search engine or site that brought you here, kept in a cookie for 90 days and copied to your account when you sign up.
- Messages to us: when you write to support@ or help@, we keep your address, name and the text of the thread so we can answer and look back at it.
- People you invite: the email address of a friend or family member you invite is kept until the invitation is accepted or expires (14 or 30 days). When you email a recipe to someone, their address is used for that one email and not stored.
- Basic analytics: we use Google Analytics 4 to count page views and understand which features are used. No recipe content is sent to GA4 — only URLs, referrers, approximate locations, and device types. It runs on our public pages only — never on a page you see while signed in, and never inside our iPhone and Android apps.
- Product usage events: inside the app we record which features you use and where something goes wrong — for example "opened Add Recipe", "the recipe could not be read", or a browser error on a page — together with your account, the page, and the time. These records never contain your recipe text, titles, notes, or questions. They stay in our own database (no third party receives them) and are deleted after 180 days, or straight away when you close your account.
- Session recordings: Microsoft Clarity records anonymised interaction with our public pages (clicks, scrolling, page layout) so we can see where the site confuses people. It is switched off once you sign in, so it never records a page showing your recipes.
- Advertising measurement: on our public pages only, the Meta (Facebook) and Reddit advertising pixels and Google's ads tag record that a visit — and, if you register, a sign-up — followed one of our ads. This lets those platforms report whether an ad worked and show our ads to similar people. Like session recording, they are switched off once you sign in.
How we use it, and on what basis
- To operate your personal recipe vault — store, display, search, and process your recipes — and to bill your subscription. Basis: the contract with you (our Terms of Use).
- To run AI features (reading a recipe from text, a photo, a video or your voice; Ask AI; nutrition and safety checks; translation) by forwarding the relevant text, photos and your query to the providers named below. Basis: the contract.
- To send you email: account messages (confirmation, password reset, replies to what you send us) and a few letters about your account — a welcome, a tip or two in the first week, notice before and after your trial ends, a reminder a month before a yearly plan renews, and occasional news. We tell you about these when you sign up, and every one carries an unsubscribe link. Basis: the contract for account messages; our legitimate interest in telling our own customers about our own service for the rest, with your right to opt out at any time.
- To keep the service secure and fair: rate limits, abuse detection, AI-spend limits per account, and records of who last signed in from where. Basis: legitimate interest.
- To find and fix the places where the service fails or confuses people, using the product usage events and the public-page analytics described above. Basis: legitimate interest.
- To measure our advertising on public pages, through the pixels described above. Basis: legitimate interest; where your law requires your consent for such cookies, we rely on your consent and you may refuse them as described under Cookies.
We do not sell your data, show you ads inside the service, or train AI models on your recipes, and we have not allowed our providers to. Your collection is visible only to you — and to the people you choose: family members you add to your account, friends you accept, and anyone you give a share link to.
Who we share it with
These companies process data for us, under their data-processing terms, only to do what is described here.
- Anthropic (Claude API, USA) — receives recipe text, your Ask AI questions, the text of a dictation or a video's narration, and photos: the ones you add to a recipe, the ones you take of a fridge, a shelf, or a receipt, and pictures from a video you import. It also receives the text of an email you send to our support address, so a draft reply can be prepared for the person who answers you. Anthropic does not train on API data per their privacy policy.
- OpenAI (USA) — receives the recording when you dictate, and returns its text; receives recipe text to build the search index that finds recipes by meaning; and receives a collection's name when an icon is drawn for it. We don't keep the recording, and OpenAI does not train on API data per their privacy policy.
- Microsoft Azure Translator — translates interface text and help pages; recipe text only when the Claude translation fails.
- Mailgun (USA) — sends our email and receives your inbound forwards to
recipe@iwant2eat.comand your messages to support@. - Stripe — processes subscription payments on the website. Card data goes to Stripe directly; we see only subscription metadata.
- Apple — Sign in with Apple, if you choose it; and subscriptions bought in the iOS app, which Apple bills and we verify with Apple's servers.
- Google — sign-in, if you choose it; Google Analytics 4 on public pages; the Google Ads conversion tag on public pages.
- Meta (Facebook) and Reddit — sign-in with Facebook, if you choose it; advertising pixels on public pages, used to measure our ads and to build audiences. These are advertising companies, and the visit they record can be linked to an existing account you hold with them.
- Microsoft Clarity — anonymised session recording and heatmaps on public pages.
- Neon — hosts our Postgres database (AWS, Ohio, USA). Hetzner — hosts our server (Ashburn, USA) and the private bucket that holds recipe photos (Falkenstein, Germany). GitHub — holds our daily database backups, encrypted before they leave our machine, in a private repository, for 35 days.
- Pexels — receives a recipe's title when you ask for a stock photo; the photo's author is credited.
- OpenStreetMap (Overpass API, Germany) — receives your location, if you allow it, to find shops near you for the shopping list. Open Food Facts — receives a barcode you scan.
- DB-IP — provides the IP-to-country database our server reads locally; no data is sent to them. IP Geolocation by DB-IP.
Where data lives
We are a United States company. Account data and recipe text are stored in a Postgres database in the United States; recipe photos in a private bucket at Hetzner in Germany, not on a public CDN. If you are in the EU, the UK or elsewhere outside the United States, your data is processed in the United States by us and by the providers above, each under its own data-protection terms, which their policies linked above describe.
Cookies
Our own cookies: authentication (keeping you signed in), anti-forgery
protection, your interface language (ui_lang), the campaign or
site that first brought you here (iwe_src, 90 days) and a share
link you followed (iwe_ref), and two set by the page itself —
whether you use the website, the installed app or our native app
(iwe_mode) and your device's time zone (iwe_tz) —
so pages and emails can show times in your own clock. All of these are
needed for the service to work as you chose, and none is read by anyone
else.
Third-party cookies: Google Analytics, Microsoft Clarity and the Meta,
Reddit and Google advertising tags set theirs on our public pages only.
None of them is loaded on any page you see while signed in, nor inside our
iPhone and Android apps, so no cookie of this kind is ever set while you
are looking at your own recipes. Visitors from the European Union, the EEA, the United Kingdom and
Switzerland get none of them until they press “Accept” in the cookie
banner; “Reject” is just as easy, and the site works the same either
way. Everywhere else they load unless you refuse them. Your choice is kept
in our own cookie iwe_consent for 180 days, and you can change it
at any time with “Cookie settings” at the bottom of every page; Google's
tags also receive it through Google Consent Mode. You can also block
third-party cookies for this site in your browser or use a tracking
blocker — nothing on iwant2eat requires them. We
do not currently respond to "Do Not Track" or Global Privacy Control
browser signals.
How long we keep it
- Account and recipe data: until you delete it or close the account. A recipe you move to the Trash stays there until you delete it for good from the Trash page, or until you close the account.
- The page text of a recipe saved from a link: 7 days after the recipe last changed.
- Product usage events and notification-center messages: 180 days. AI usage records: 12 months.
- Copies of emails we sent you: the record that a letter went — address, subject, date — while your account exists, so we don't send the same letter twice; the text of a personal letter for 12 months.
- Messages you sent to support: 24 months after the thread is closed, or sooner if you ask.
- Server logs (which may contain IP addresses): 14 days. The IP address and device of your last visit: 90 days after that visit; the country stays.
- Backups: a daily copy of the database, encrypted with a key that only we hold, is kept for 35 days in a private, access-controlled store for disaster recovery. We never restore a backup to bring back a deleted account, and deleted data drops out of the backups within 35 days as they rotate.
Your rights
- Access — your whole collection is visible to you while logged in; your AI spend history is on the AI budget page. Ask us for anything else we hold about you and we will send it within a month.
- Export — download your recipes as a file and the rest of your account data (profile, collections, lists, plans, friends, consents) as a JSON file from Account → Data at any time.
- Correct — edit any recipe or account field yourself.
- Delete — delete any recipe at any time; delete the whole account from Account → Data, see /data-deletion.
- Object or restrict — write to us to object to a use based on legitimate interest, or to ask us to restrict processing while a question is sorted out.
- Opt out of email — every letter except the ones you ask for yourself carries an unsubscribe link; one click stops the rest.
- Complain — if you are in the EU or the UK, you may complain to your data protection authority. We would appreciate the chance to answer you first.
- US state privacy laws — we do not sell your personal information or share it for cross-context behavioural advertising in the sense of those laws, and we do not discriminate against anyone for exercising a privacy right.
Children
iwant2eat is not intended for anyone under 13, or under 16 in the EU and the UK, and we do not knowingly collect their data. A younger member of the household may use the service only through a family account that a parent or guardian creates and controls.
Security and who at iwant2eat sees your data
Connections are encrypted; passwords are stored as salted hashes; access to the systems above is limited to the people who run the service. When you write to support, the person answering may open your account to see what you see; such access is recorded.
Changes
We will post any material change here with an updated date. If the change is significant, we will email registered users.
Contact
Questions, requests, or complaints: privacy@iwant2eat.com, or by post to Volicsoftware, Inc., 19 Clive Hills Rd, Edison, NJ 08820, USA.