Privacy policy
Last updated November 15, 2026
1. Who processes your data
The controller is Tomaš Blaževič, company code -, address Vilnius. Send questions about your data to [email protected].
This policy covers the InFoodAI website, the app in a browser and the Android app from Google Play.
2. What data we process
- Account: your email address. Your password is handled by Google Firebase Authentication — we never see it. With Google sign-in (in the Android app, through the phone’s Google account picker) we receive your email and account identifier.
- Your records: products, expiry dates, purchases, prices, budget, food library, remembered barcodes (the name and size you saved a scanned product with), shopping list, saved recipes, weekly menu and settings.
- Food diary (if you use it): what and how much you ate, the calories and nutrients counted, and the daily goals you typed in. Only you see it — household members do not. These records can show your eating habits; we use them for nothing else and share them with no one, except Google as the storage provider.
- Eaten together (if you mark it): when a member of your household marks that you ate together, their offer appears in your diary — their name, what and how much (your share) and its calories. Only you see it; it goes into your diary only when you confirm it (or at once, if you turned that on on your device), and one not confirmed is deleted after 7 days. When you mark that you ate with a member, such an offer with your name appears in their diary.
- Recently used: who took what off the list, when and how much. In a household list, all its members see it. The records are deleted after 30 days.
- AI requests: photos of receipts, food, packages and recipes, recipe text you paste, what you ate said aloud (the recording, with the products on your list and the names of your household members), and your product list for recipes, are sent to our server and the Google Gemini API to be read. We do not keep photos, recordings or pasted text; a recipe is saved only when you check and save it. So that the same photo is not sent twice, the AI answer is kept in server memory for up to 15 minutes; checked recipe suggestions for up to 24 hours.
- Usage counters: how many AI requests you made today and this month and how many free AI tries you have used.
- Household list: membership (role, when you joined, the name or email shown) and invites. We do not keep the code in an invite link — only an irreversible hash of it.
- Subscription on the website (Stripe): Stripe customer and subscription identifiers, plan status, the end of the current period, the subscription’s price, and the version of the terms you accepted and when. Card details are handled only by Stripe — we never see them.
- Subscription in the Android app (Google Play): the purchase identifier (purchase token), plan, status, end date, whether it is a free trial, and the version of the terms you accepted and when. Google Play keeps with the purchase only an irreversible code (hash) of your account, not your email. Payment details are handled only by Google — we never see them.
- Premium given by an administrator (if any): until when it lasts and an internal note.
- Barcode lookup: the code you enter is sent to the Open Food Facts database (without your personal data).
- Technical logs: time, outcome and error code of a request. You are identified in logs only by an irreversible code (hash) — no email and no content of your records.
- Reminders (if you turn them on): the days and hour you chose, your time zone, language and the device’s notification identifier (in a browser, the Firebase installation ID; in the Android app, the Firebase Cloud Messaging registration token). Notifications show product names, so they may be visible on the lock screen. After you sign out the device gets no more reminders; you can turn them off at any time (Profile → Reminders).
- On your device: your sign-in session, chosen language and settings, unfinished scans (up to 1 hour; deleted when you sign out) and a helper script (service worker) that shows reminders.
- The Android app asks for the camera and microphone only when you use them (a photo, a barcode, your voice). It does not use the advertising ID, and its data is not copied to Google backups. The Android app has no reminders yet.
3. Why, and on what legal basis
- Performance of the contract: your account, your records, the AI features and the subscription (Stripe or Google Play).
- Legitimate interest: security of the service, preventing abuse (daily limits, logs) and fixing errors.
- Legal obligation: accounting for payments and invoices.
We do not use your data for advertising, profiling or training AI models, and we do not sell it.
For AI requests we use the paid Google Gemini API: under its terms, Google does not use your requests to improve its products and models.
4. Who else receives data
- Google (Firebase Authentication, Cloud Firestore, Firebase Cloud Messaging for reminders, Gemini API, hosting) — as our processor.
- Stripe — payment processing on the website. For payments, Stripe may also act as an independent controller.
- Google (Google Play) — buying the subscription and payments in the Android app. For payments, Google acts as an independent controller under its own privacy policy.
- Open Food Facts — the barcode only.
- Members of a household list — if you join one: the other members see your name (or your email address if there is no name), your role, and the food, purchases, shopping list items, saved recipes, weekly menu and remembered barcodes you add to that list and what you take off it. They do not see your personal list. A member you mark as having eaten with you is offered their share (see “Eaten together”).
Google and Stripe may process data outside the European Economic Area (e.g. in the USA). In that case the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses apply.
5. How long we keep data
- Account data, records and subscription records — as long as you have an account.
- The device’s notification identifier — while reminders are on for that device; we delete it when you turn them off, sign out, or the device can no longer be reached.
- Photos — not kept; AI answers in memory — up to 15 minutes; recipe suggestions — up to 24 hours.
- Payment and invoice data — as long as accounting law requires.
- Technical logs — no longer than 30 days.
You can delete your account yourself: in the app, Settings → “Delete account”. Your product list, purchases, budget, food library, shopping list, saved recipes, weekly menu, “Recently used”, food diary with offers waiting in it, reminder settings, AI usage data, subscription records and sign-in are deleted at once; a Stripe subscription ends, and a Google Play subscription stops renewing. In a shared household list, the products, purchases, shopping list items, saved recipes and weekly menu you added stay for the other members; the administrators’ log keeps only the account’s identifier (no e-mail). You can also write to [email protected] and we will delete your account and all its records within 30 days.
6. Your rights
You have the right to access, correct and delete your data, to restrict its processing, to receive it in a portable format and to object to processing based on legitimate interest. You can download your data yourself: Profile → “Download my data”. Otherwise write to [email protected]; we answer within one month.
If you believe your data is handled improperly, you can complain to the State Data Protection Inspectorate of Lithuania (vdai.lrv.lt) or the supervisory authority where you live.
7. Cookies and local storage
We only store what is needed in your browser or the Android app to keep you signed in and remember your settings. We use no advertising or analytics cookies and no third-party trackers, so we do not ask for consent to them.
8. Children
You must be at least 14 to create an account. Only adults can subscribe to Premium.
9. Changes
We will announce material changes to this policy in the app or by email before they take effect.