What to eat today?Privacy Policy
This policy explains what data we collect when you use the “What to eat today?” mobile app, why, who we share it with, and what your rights are.
1. Data controller
The controller of your personal data is Damian Olech, running a business as DAMIAN OLECH SOFTWARE, ul. Św. Maksymiliana 11C/26, 44-207 Rybnik, Poland, tax ID (NIP) 6423238485, REGON 522357790.
Contact for data protection matters: support@whateattoday.online.
2. What data and why
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Account: name, email address and the identifier from Sign in with Google or Apple | Creating and running your account, syncing between phones, contacting you about your account | Art. 6(1)(b) — performance of a contract |
| Ingredients, preferences (diet, ingredients you don’t eat, servings, goals), recipe history, favorites, shopping list | Creating recipes tailored to you and saving them to your account | Art. 6(1)(b) |
| Photos of your fridge and receipts, voice recordings | Recognizing products and adding them to your pantry. We don’t store photos or recordings — they’re sent for analysis and discarded right away | Art. 6(1)(b) |
| Comments, likes, reports and blocks of other users | Community features and moderation. Other users see your first name with your comments (from your Google account; with Sign in with Apple usually “Kucharz”, Polish for “Cook”) — never your surname or email | Art. 6(1)(b) and (f) — keeping the community safe |
| Subscription status and in-app purchase history | Access to Premium, renewals and refunds | Art. 6(1)(b) and (c) — contract and accounting obligations |
| Number and cost of AI feature uses | Usage limits and preventing abuse | Art. 6(1)(f) — legitimate interest |
| Crash reports (Firebase Crashlytics): phone model, system and app version, error details | Finding and fixing bugs | Art. 6(1)(f) — legitimate interest |
| Usage statistics (Firebase Analytics): screens opened and steps such as creating a recipe | Improving the app. Only with your consent, asked on first launch; change it anytime in Profile | Art. 6(1)(a) — consent |
We show no ads, sell no data and don’t use the advertising ID. We don’t collect your location or contacts.
We don’t ask about your health. In preferences you can choose ingredients you don’t eat — we don’t ask why and treat them as ordinary food preferences. Please don’t enter information about medical conditions there.
3. Artificial intelligence
Recipes, dish photos and recognizing products in photos and recordings are done by an AI model (Google Gemini). We send it only what the task needs: the ingredient list, preferences, the photo or recording. We don’t send your name or email address. We use Google’s paid service, under which submitted data isn’t used to train models.
Recipes the AI generates may be added to the shared catalog (“Discover”) and shown to other users — without any data about you.
We don’t make decisions about you based solely on automated processing that produce legal effects or similarly significantly affect you.
4. Who processes data for us
- Supabase — database, sign-in and app server; data stored in the European Union (Frankfurt).
- Google — Gemini AI model (recipes, photos, product recognition), Firebase Crashlytics and Firebase Analytics, Sign in with Google.
- Apple — Sign in with Apple, App Store payments.
- Google Play — payments on Android.
- RevenueCat — subscription management; receives your account identifier and purchase history, not your name or email.
- Cloudflare — hosting this website and forwarding messages sent to support@whateattoday.online.
Some of these companies may process data outside the European Economic Area, mainly in the USA. This is based on the European Commission’s adequacy decision (EU-US Data Privacy Framework) or standard contractual clauses.
5. How long we keep data
- Account data and content — until you delete your account.
- Crash reports and statistics — according to the retention periods set in Firebase, without your name or email.
- Payment-related data — as long as tax and accounting laws require (usually 5 years from the end of the tax year).
Your pantry and some settings are stored only on your phone and are removed when you uninstall the app.
6. Your rights
You have the right to access your data, rectify it, erase it, restrict processing, data portability, and to object to processing based on legitimate interest. You can withdraw consent at any time, without affecting the lawfulness of processing before withdrawal.
To exercise your rights, email support@whateattoday.online. We reply within one month. You can also delete your account yourself — see how to delete your account.
You have the right to lodge a complaint with a supervisory authority — in Poland, the President of the Personal Data Protection Office (UODO, ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl), or the authority in your country.
7. Children
The app isn’t intended for people under 16. If we learn that such a person created an account without a guardian’s consent, we’ll delete it.
8. Security
Connections are encrypted and database access is limited to each data owner.
9. Changes
If we change this policy, we’ll publish the new version on this page and update the effective date. We’ll tell you about significant changes in the app.