Privacy Policy
Last updated: 23 July 2026
The short version. Eaterr stores your cooking profile, pantry, recipes and assistant chats so they follow you across devices. To generate recipes we send your ingredients, diet and allergies to an AI provider. We do not advertise, we do not track you across other apps or websites, we use no analytics SDKs, and we never sell your data. You can delete your account and everything in it from inside the app at any time.
Contents
- Who we are
- Information we collect
- Photos and camera
- Voice and dictation
- AI processing
- Barcode scanning
- How we use your information
- Who we share it with
- Legal bases (EEA and UK)
- International transfers
- How long we keep it
- Security
- Your rights
- Deleting your account
- Children
- Region-specific rights
- Cookies on our website
- Changes to this policy
- Contact
1. Who we are
Eaterr is a mobile application that turns the ingredients you have at home into recipes tailored to you. This policy explains what personal data we handle, why, and what control you have over it. It covers the Eaterr iOS app and the eaterr.app website.
The data controller is [LEGAL ENTITY NAME], registered at [REGISTERED ADDRESS], Greece. You can reach us at support@eaterr.app.
2. Information we collect
Account information
Your email address and a password (stored only as a secure hash, never in readable form). If you use Sign in with Apple, we receive an Apple identifier and the email address Apple provides, which may be a private relay address that hides your real one. We also store the display name you choose.
Your cooking profile
The answers you give during onboarding and can edit later: your name, assistant name, dietary style, allergies and ingredients to avoid, cooking skill, kitchen equipment, goals, household size, favourite cuisines, staples you always have, how often you cook, how adventurous you want recipes to be, default servings, planning days, meal reminder times, nutrition targets, and app preferences such as theme, accent colour and units.
Your kitchen content
Pantry items and their quantities, saved recipes including any edits and notes, cooking history, ratings, meal plans, and shopping lists.
Health-related information
If you log meals, we store nutrition entries: calories, protein, carbohydrates, sugar, salt, saturated fat, total fat and fibre per meal, with the date. Together with your allergies and dietary restrictions, this is treated as health data and receives extra protection under European law. See Legal bases.
Assistant conversations
The full text of messages you send to the in-app assistant and the replies you receive are stored on your account so your conversations persist across devices.
Purchase information
When you subscribe, Apple processes the payment. We never see your card details. Our subscription provider RevenueCat receives your Eaterr user identifier and confirms to us which plan is active and when it expires.
Usage measurement
We record how much AI processing each account uses per month, as a running cost counter. This stores numbers only, not the content of what you generated.
Information collected automatically
Eaterr contains no analytics, advertising, attribution or crash-reporting SDKs. We do not build behavioural profiles of you. However, whenever your device contacts a service (ours or a third party's), that service necessarily sees your IP address and basic device information as part of the connection. Where that involves a third party, we say so in the relevant section below.
3. Photos and camera
Eaterr asks for camera and photo access so you can scan ingredients, scan nutrition labels, scan barcodes, and attach a photo of a dish you cooked. We only ever access photos you specifically choose or capture. Different photos are handled differently, and the distinction matters:
| Photo | What happens to it |
|---|---|
| Ingredient scans | Sent to our server and on to an AI vision provider to identify what is in the picture. Processed and discarded. Not stored by us. |
| Nutrition labels | Same as above. Processed to read the values, then discarded. |
| Ingredient cut-outs | On recent iPhones the cut-out is produced entirely on your device and never leaves it. On older devices we fall back to a background-removal service. The finished cut-out image is stored with your pantry item. |
| Photos sent to the assistant | Sent to the AI provider so it can answer questions about them. Kept only on your device afterwards, not saved to our servers. |
| Photos of dishes you cooked | These stay on your device. We store only a reference to the file's location on your phone, never the image itself, so the photo is never uploaded anywhere. |
4. Voice and dictation
If you dictate messages to the assistant, speech recognition is performed by Apple's system recognition service on your device. We receive only the resulting text. We do not record, store or transmit audio.
5. AI processing
Recipe generation, ingredient recognition, label reading and the assistant are powered by an AI provider (OpenAI) through our server. Your device never talks to them directly and our API keys are never in the app.
Depending on the feature, what we send includes: your pantry contents, the ingredients and steps of a recipe you are cooking, your dietary style, your allergies and ingredients to avoid, your cooking skill, your kitchen equipment, your goals and nutrition targets, your household size, the free text you type, your recent messages in the conversation, and any photos you attach (up to five per message).
We send allergy and dietary information deliberately, because it is the only way the model can avoid putting something dangerous in your recipe. We want to be direct that this means health-related information about you leaves our systems and is processed by our AI provider.
Under our agreement with the provider, data sent through their API is not used to train their models. They may retain it for a limited period for abuse monitoring. Please do not type information into the assistant that you would not want processed by a third party.
6. Barcode scanning
When you scan a product barcode, your device queries public product databases directly to look up what the product is: Open Food Facts, Open Products Facts, Open Beauty Facts and UPCitemdb. These requests come from your device, so those services can see your IP address and which products you scan. We do not send them your name, account or any profile information.
7. How we use your information
- To create and run your account, and keep you signed in
- To generate recipes that fit your ingredients, diet, allergies, equipment and goals
- To sync your pantry, recipes, plans, lists and chats across your devices
- To answer your questions through the assistant
- To send the reminders you have switched on
- To provide, and enforce the limits of, free and paid plans
- To respond when you contact support
- To keep the service secure and prevent abuse
- To meet our legal obligations
We do not use your data for advertising, we do not sell or rent it, and we do not share it with data brokers.
8. Who we share it with
We share data only with service providers who process it on our behalf, for the purposes above. Each one is listed here.
| Provider | Purpose | What it receives |
|---|---|---|
| Supabase | Database, accounts, backend | All account and content data |
| OpenAI | Recipe generation, vision, assistant | See section 5 |
| Apple | Sign in with Apple, payments, notifications, speech | Account identifier, purchase data |
| RevenueCat | Subscription management | Your Eaterr user identifier, purchase status |
| remove.bg | Background removal (older devices only) | The ingredient photo being cut out |
| Open Food Facts and UPCitemdb | Product lookup | The barcode and your IP address |
| Vercel | Website hosting | Website visit data |
| Resend | Website emails | Email addresses submitted on the website |
We may also disclose information if required by law, to enforce our Terms, or to protect the rights and safety of our users or others. If the business is ever sold or transferred, your data may transfer with it, and you would be told before that happens.
9. Legal bases (EEA and UK)
If you are in the European Economic Area or the United Kingdom, we rely on these legal bases:
- Performance of a contract: running your account, generating recipes, syncing your content, and providing the plan you paid for.
- Your explicit consent: processing your allergies, dietary restrictions and nutrition logs. These are special category health data and we process them only because you choose to give them to us so the app can keep you safe and meet your goals. You can withdraw consent by removing them in the app or deleting your account.
- Legitimate interests: keeping the service secure, preventing abuse, and enforcing plan limits.
- Legal obligation: keeping records we are required to keep.
10. International transfers
Our database is hosted in the United States (Oregon), and our AI provider processes data in the United States. This means your data is transferred outside the EEA and the UK. These transfers are covered by appropriate safeguards, including Standard Contractual Clauses with our providers. Emails from our website are sent through infrastructure in the European Union.
11. How long we keep it
| Data | Retained |
|---|---|
| Account and profile | Until you delete your account |
| Pantry, saved recipes, meal plans, shopping lists | Until you delete them or your account |
| Cooking history and nutrition logs | Until you delete your account |
| Assistant conversations | Until you delete them or your account |
| Usage counters | Until you delete your account |
| Website signup emails | Until you ask us to remove them |
| Data held by our AI provider | A limited period for abuse monitoring, then deleted, under their terms |
Some data also lives on your device so the app works offline. That copy is removed when you delete your account, sign out, or delete the app.
12. Security
Access to your data is restricted at the database level so that one account cannot read another's, enforced by the database itself rather than only by the app. Traffic is encrypted in transit. Passwords are stored only as hashes. Our AI and third-party keys are held on the server and are never present in the app. No system is perfectly secure, and we cannot guarantee absolute security, but we take these measures seriously and will notify you and the relevant authority if a breach affects you.
13. Your rights
Depending on where you live, you have some or all of these rights:
- Access: get a copy of the data we hold about you
- Correction: fix anything inaccurate, mostly editable in the app directly
- Deletion: have your data erased
- Portability: receive your data in a machine-readable format
- Restriction and objection: limit or object to certain processing
- Withdraw consent: at any time, without affecting past processing
- Complain: to your data protection authority. In Greece this is the Hellenic Data Protection Authority (dpa.gr)
To exercise any of these, email support@eaterr.app. We respond within one month. We never charge for this and we will not treat you differently for asking.
14. Deleting your account
Open the app and go to Profile → Delete account. This permanently removes your account and everything attached to it: your profile, pantry, saved recipes, cooking history, meal plans, nutrition logs, shopping lists, assistant conversations and usage records. It also clears the copy held on your device. This cannot be undone.
Data already processed by our AI provider is subject to their retention period and is outside our direct control once sent. We keep no copy of it.
15. Children
Eaterr is not intended for anyone under 16. We do not knowingly collect data from children under 16. Cooking involves heat and sharp tools, and younger users should only cook with adult supervision. If you believe a child under 16 has given us personal data, contact us and we will delete it.
16. Region-specific rights
European Economic Area and United Kingdom
Your rights are set out in section 13 and our legal bases in section 9. You may lodge a complaint with your national supervisory authority.
California
We do not sell or share personal information as those terms are defined under the CCPA, and we have not done so in the past twelve months. We do not use or disclose sensitive personal information for purposes beyond those permitted. California residents may request access, deletion, correction and details of disclosures, and may not be discriminated against for exercising those rights.
Washington and other US health-privacy laws
Nutrition logs, allergies and dietary restrictions may qualify as consumer health data under laws such as Washington's My Health My Data Act. We collect them only to provide features you have asked for, we never sell them, and you can delete them at any time.
Canada
You may request access to your personal information and challenge its accuracy, and may complain to the Office of the Privacy Commissioner of Canada.
17. Cookies on our website
The eaterr.app website uses cookies and similar technologies that are necessary for it to work, and asks your consent before anything beyond that. You can change your choices at any time through the cookie settings on the site. The app itself does not use advertising or tracking cookies.
18. Changes to this policy
We may update this policy as the app changes. The date at the top always reflects the current version. If a change materially affects your rights, we will tell you in the app or by email before it takes effect.
19. Contact
Questions, requests or complaints: support@eaterr.app
[LEGAL ENTITY NAME], [REGISTERED ADDRESS], Greece