Effective 26 September 2026.
Who is responsible
Controller: Paweł Orzech
Contact: [email protected]
What this app stores
Your intolerances, aversions, safe foods, plan, meal history and reminder settings are health-related data. They are stored only in a local database on this device (Room/SQLite), never on a server this app's developer controls. There is no account and no login — nothing here is tied to your identity by this app.
Backups are switched off for this data: Android's own cloud backup and device-to-device transfer both explicitly exclude the app's database, preferences and files, so this data does not leave the device even through those system features.
What leaves this device, and to whom
1. Requests to Google's Gemini model (through Firebase AI Logic), sent only after you turn on the consent switch in onboarding or Settings. What is sent: the names of your standard intolerance tags (like "gluten"), sensory attribute ids from a closed list, the names of the safe things you've added, and the names of ingredients from meals you rejected. If you describe what you dislike in your own words, that sentence is sent as you typed it. If you ask for Thermomix steps, the meal's name, ingredients with amounts and steps are sent. Never sent: your name, any intolerance you typed yourself, notes, severities, or any other number about you. You can withdraw consent at any time in Settings, which stops all further requests.
2. A barcode lookup, sent to Open Food Facts, an independent open database. Only the barcode number is sent — no profile data.
3. A subscription purchase, handled entirely by Google Play Billing. This app never sees your card details.
4. When the developer's Firebase project is connected (the production path), your device also exchanges a Firebase installation identifier and an App Check / Play Integrity attestation with Google as part of authenticating those requests, and fetches configuration values (such as the model name and free-tier limits) from Firebase Remote Config.
Meal reminders are entirely local: nothing about them is sent anywhere.
This app does not currently use crash reporting or analytics of any kind. If that changes in a future version, this policy and the in-app disclosure will be updated first.
Your choices
Delete everything: Settings → Delete all my data. This clears the local database, your reminders and your consent choice, and returns you to the start of onboarding. There is no account to also delete elsewhere, because there never was one.
Withdraw consent: Settings → Consent and data. Meal generation stops using Google's model; everything else keeps working.
Uninstalling the app removes the local database as well, since Android backups for it are switched off.
Retention
Local data stays on the device until you delete it or uninstall the app. Meal generation requests are not stored by this app beyond the reply the model gives, which then goes through the same safety checks and storage as any other meal. What Google itself retains from a request is governed by Google's own terms for the Gemini API / Firebase AI Logic. This app uses Gemini as a paid service: Google does not use these requests to improve its products and keeps them only briefly, to detect abuse.
Your rights
Because there is no account, this app itself is where you exercise your rights under GDPR: you read and change what's stored directly in Settings, and you erase it with the delete action above. You may also lodge a complaint with your national data protection authority (in Poland, the UODO).