Privacy Policy
How EatMe processes your data, protects your privacy, and keeps your kitchen information secure.
1. Data Controller
The controller responsible for processing personal data on this website (https://eatme-app.com) and within the EatMe mobile application under the General Data Protection Regulation (GDPR) is:
EatMe, Leon Gött
Am Bug 36, 86757 Wallerstein, Germany
Phone: +49 159 0 266 7509
Email: hello@eatme-app.com
Website: https://eatme-app.com
2. Processing Overview
EatMe helps you keep track of groceries in your household, track best-before dates, synchronize shopping lists, and organize recipes. We follow strict data minimization principles: we only collect and process data strictly required to deliver our core services reliably and securely. The one exception is optional: anonymous usage statistics, which are only collected if you agree to them (see section 3 f). To keep the app stable it also sends technical error reports when something goes wrong, using the service Sentry (see section 3 g).
3. Collected Data Categories and Purposes
a) Registration, Authentication & Account
Sign-in is passwordless via email (magic link or 6-digit one-time code). We store your email address and issue secure session tokens so your pantry inventory and shopping lists synchronize seamlessly across your devices.
b) Pantry, Household & Recipe Data
We store the pantry items you record (item name, quantity, storage location, expiry date, category), shopping lists, household memberships, and your created or imported recipes. When you share a recipe, a cryptographic token is generated to allow recipe previewing and importing.
c) Camera & Media Permissions (Barcodes, Expiry Dates & Recipe Photos)
The app only accesses your camera when you actively trigger a scanning feature:
- Barcode Scanning: Recognizes barcodes directly on-device to fetch product information.
- Best-Before OCR: Reads printed expiry dates on packaging using on-device optical character recognition. Live camera streams are never sent to remote servers.
- Recipe Photo Import & Uploads: When you upload a photo of a dish or recipe text, the image is stored in encrypted cloud storage for your household access.
d) Push Notifications & Local Timers
Enabling notifications registers a device push token used solely to notify you when groceries are approaching their expiry date. Active cooking timers run locally on your device.
e) Server Logs & Technical Telemetry
When accessing web services, standard server access logs (IP address, request timestamp, browser user agent, operating system) are captured temporarily for system stability, fraud prevention, and DDoS mitigation.
f) Anonymous Usage Statistics (optional)
The app asks you once whether it may count, anonymously, which of its features are used. This tells us which features are worth improving and which ones nobody finds. It is switched off unless you say yes, and you can change your answer at any time under Settings › Data & privacy.
- What is counted: that a feature was used, for example creating or editing a recipe, importing one from a link, text, photo, TikTok or Instagram, generating a recipe, scanning a barcode, a best-before date or a receipt, sorting the shopping list or its aisle order, using tags, recipe books, the meal plan, cooking mode or households, and opening the app.
- What is stored: only totals per calendar month, feature and platform (iOS, Android, web), such as "42 devices imported a recipe from TikTok this month". No name, email address, account, household or device identifier, no IP address and no content of your kitchen, recipes or lists is stored with them.
- How duplicates are avoided: your device keeps a local note of which features it has already reported, so a device is counted once per feature and month. This note never leaves your device and is deleted when you switch the statistics off.
- Transmission: counts are collected on your device and sent in batches to our database at Supabase (see section 4). The request is sent over your signed-in connection only to keep the endpoint closed to the public; the identity is not written to the statistics.
Switching the statistics off stops all counting and deletes whatever has not been sent yet. Totals that were already counted cannot be linked to you and therefore remain.
g) Error Reports & Crash Diagnostics (Sentry)
To find and fix crashes and bugs, the app uses the error monitoring service Sentry. It is part of every build of the app, separate from the optional usage statistics in section 3 f, and cannot be switched off in the app's settings. Nothing is sent while the app runs without a problem. When the app crashes or a feature fails, a report is sent to Sentry.
- What a report contains: the kind of error and its technical trace, the app version and build, the platform, the operating system version, the device model and technical device state such as language, screen size, orientation and available memory. For some failures we add technical detail that helps to reproduce them, for example the address of the recipe page you were importing, the error code the server answered with and which feature was being used.
- The trail before the error: a short list of what happened just before, such as the screens you opened, what you tapped, the addresses and status codes of network requests the app made (never their contents) and the steps of the sign-in process. The sign-in link or code itself is never part of it.
- What is not sent: the app is set up so that no IP address, name, email address, user ID, household, device or installation identifier and no screen recording is added to a report. Reports from the same device therefore cannot be grouped by person. As with any internet connection, your IP address is technically visible to Sentry's servers while a report arrives; it is not stored with the report.
- Where and for how long: reports are sent to Sentry's EU data region (Germany) and deleted automatically after 90 days at the latest. They are not linked to your account (see section 6).
4. Subprocessors & Third-Party Services
We rely on vetted infrastructure providers bound by GDPR Data Processing Agreements (Art. 28 GDPR):
Supabase (Database, Auth & Storage)
Supabase Inc. provides our managed PostgreSQL database, user authentication, and object storage. Our database instance is hosted in the EU region Frankfurt (AWS eu-west-1). Data is encrypted in transit and at rest.
AWS Lambda (Amazon Web Services)
Serverless compute functions handle recipe URL parsing, photo text recognition, and AI-assisted recipe generation based on your ingredients. Only text and photo payloads required for processing are transmitted.
Sentry (Error Monitoring & Crash Reports)
Functional Software, Inc. (doing business as Sentry), San Francisco, USA, receives the error reports and technical device data described in section 3 g. We use Sentry's EU data region, so the data is stored in Germany. Because a US company operates the service, access from the USA cannot be ruled out; the transfer is covered by Sentry's Data Processing Addendum including the EU Standard Contractual Clauses and by Sentry's certification under the EU-U.S. Data Privacy Framework.
Open Food Facts (Product Catalog)
To match scanned barcodes with grocery names and categories, we query the Open Food Facts open database through our secure server proxy. No personal user information is passed to Open Food Facts.
Cloudflare (Hosting & Edge Delivery)
Cloudflare Inc. serves eatme-app.comand protects our web endpoints against DDoS attacks and security threats.
5. Legal Bases under the GDPR
- Art. 6(1)(b) GDPR (Performance of a contract):Processing account information, pantry inventories, shopping lists, and recipes to provide EatMe's core services.
- Art. 6(1)(a) GDPR (Consent):Voluntary permissions including push notifications and camera permissions for scanning barcodes or expiry dates. Consent can be revoked anytime in your device settings.
- Art. 6(1)(a) GDPR and § 25(1) TDDDG (Consent):Anonymous usage statistics (section 3 f), including the local note on your device that prevents double counting. Consent is voluntary and can be withdrawn at any time in the app under Settings › Data & privacy, with effect for the future.
- Art. 6(1)(f) GDPR (Legitimate interests):Ensuring technical security, fraud prevention, and service reliability, including the error reports and crash diagnostics described in section 3 g. Our interest is an app that works and in which faults are found and fixed quickly. You can object to this processing at any time (see section 7).
6. Data Retention and Account Deletion
Your data is retained for as long as your account remains active. You can delete your account and all associated household inventories, lists, and recipes at any time directly in the app settings or by emailing hello@eatme-app.com.
Anonymous usage statistics (section 3 f) are monthly totals that cannot be linked to any person or account. They are therefore not affected by deleting your account and are kept for as long as they are useful for improving the app.
Error reports at Sentry (section 3 g) are deleted automatically after 90 days at the latest. They carry no account or user ID, so they cannot be looked up by your account and are not removed when you delete it; they expire on their own.
7. Your Rights as a Data Subject
Under GDPR provisions, you have the following rights:
- Right of access (Art. 15 GDPR): Request a copy of your personal data.
- Right to rectification (Art. 16 GDPR): Correct inaccurate or incomplete data.
- Right to erasure (Art. 17 GDPR): Delete your personal data.
- Right to restriction of processing (Art. 18 GDPR): Restrict further processing.
- Right to data portability (Art. 20 GDPR): Receive data in a structured format.
- Right to object (Art. 21 GDPR): Object to processing based on legitimate interests.
- Right to lodge a complaint (Art. 77 GDPR): Lodge a complaint with a supervisory authority.
You do not have to ask us for the first two: sign in at your account and download a copy of your data as a JSON file, or open Settings › Privacy & Legal in the app. Deleting your account, and everything in it, works the same way from the app. For anything else write to hello@eatme-app.com; we answer within one month.
8. Security and Contact
We employ strict encryption (TLS), role-based database row-level security (RLS), and modern development practices to safeguard your information.
If you have privacy questions, please contact hello@eatme-app.com.