Privacy policy: Talerz (Plate AI)
Version of 7 November 2026
How to delete your account and data
Contents
- Who is responsible for your data
- What stays on your phone
- Meal photos
- Barcodes and search
- Subscription
- Ads
- Your rights
- Health
- Package photos
- Describing meals by text and voice
- Legal bases
- Who receives data
- How long we keep data
- Health Connect
- Your rights and complaints
- Health data in your profile
- Account and cloud sync
- Community
- Crash reports
- Coach and clients
- Household
- Referrals and sharing
- Activity
- Meal plan, check-in and workouts from a coach
- Groups and the coach directory
- What's in my fridge, At home and Better choice
- Several accounts on one phone and your name
1. Who is responsible for your data
The data controller is ToKKo Games & Software (Grzegorz Konopka), contact: kontakt@tokkogames.com. Write to this address about personal data; we reply within 30 days.
2. What stays on your phone
Your meal diary, weight, measurements, custom foods, settings and meal photos are stored on your phone. Without signing in we do not create an account and we do not keep this data on our servers. If you sign in with Google, a copy of this data without photos goes to our cloud (section Account and cloud sync).
3. Meal photos
Meal photos are recognized on your phone: with the Gemini Nano model built into the system (on phones that have it) or with a model downloaded into the app. The photo is not sent anywhere, does not reach our server or an AI model provider and is not used for ads or model training. The fallback model is downloaded once from Hugging Face; this is an ordinary file download: Hugging Face sees the connection's IP address but receives no photos or other data of yours.
4. Barcodes and search
When you search for foods outside the built-in database or scan barcodes, we send a request to the public Open Food Facts database. It contains only the search text or code number; the database sees your connection's IP address.
5. Subscription
The ad-free subscription is handled by Google Play. We pass no diary data to the store.
6. Ads
The free version shows Google AdMob ads. Advertisers and Google may receive an advertising ID, IP address and device data, and with your consent also data used to personalize ads. We do not pass your diary, photos or scan results to ads. If you do not consent to personalization, ads stay but are non-personalized: Google does not choose them based on your activity, and the identifier is used at most for frequency capping, statistics and fraud prevention. If you also do not consent to storing information on your device, Google shows limited ads without an advertising ID or cookies. You can change your consent in Profile (Ad and consent settings). The ad-free subscription turns ads off.
7. Your rights
All your data stays with you: you can export it to CSV, save a backup or delete it in Profile (Delete all data). Deletion covers the diary, photos, export files, ad consent and weights Talerz wrote to Health Connect; it is immediate and irreversible. At the same time we also delete your reports from the server (products, label photos from the last 180 days and Open Food Facts reports sent from this phone). If the phone is offline at that moment, the data on the phone is still deleted and we delete the reports on request to kontakt@tokkogames.com (give the barcodes); otherwise they disappear after 180 days.
8. Health
Talerz provides estimates and does not replace the advice of a doctor or dietitian. If you are ill, pregnant or have an eating disorder, consult a specialist about your diet.
9. Package photos
Label photos are read on your phone (Google ML Kit text recognition works offline) and stored with the reading in the app memory, linked to the barcode so the next scan is instant. A label photo leaves your phone only if you turn on the separate consent “Label photos in the shared database” (off by default, works only together with the shared database consent): it is then uploaded to our server with the barcode, values and ingredients, after the phone re-saves it without location and camera data (longer side 1280 px), and the server strips any remaining metadata again. The server keeps up to the five newest photos per product permanently, until the product is removed from the database. Only Talerz moderators can see them; they are used to check products reported inconsistently and to improve label reading, they are not public, do not reach other people’s apps or advertising and do not go to Open Food Facts. We never upload meal photos. We pass the values, name and ingredients (no photo) to Open Food Facts through our server only after you enable a separate consent in Profile; they are published there under an open licence, without your personal data. On phones with Gemini Nano the ingredients are interpreted locally, nothing is sent. When the shared product database consent is on (off by default, you can turn it on in Profile), after you scan a product we send its barcode, the values read, the ingredients and the name to our server, without personal data, and in return we download products reported by others. Product data is shared by all users. Your IP address is only used for abuse limits and is stored only as a hash. Package photos stored on your phone are deleted together with all data in Profile; photos uploaded to the server are then deleted together with your reports if less than 180 days have passed since the upload (after that the photo of the label alone stays with the product, without any link to you).
10. Describing meals by text and voice
Dictation uses the phone's own speech recognition (Google); Talerz does not record audio. We match the description against the database on your phone; items the database does not know are left for you to search or add manually. The description is not sent anywhere.
11. Legal bases
Meal photos and descriptions are analysed only on your phone and never reach us, so we do not process them on our servers. Health data in your profile is processed based on your explicit consent (Art. 9(2)(a) GDPR), described below. We handle the subscription and the account with sync (if you sign in) to perform the contract (Art. 6(1)(b)); we keep the diary, meals, weight, measurements and profile in the cloud only with explicit consent on a separate screen, and conditions, medication, pregnancy and eating disorders only with a second, separate consent (both Art. 9(2)(a)). We protect the server against abuse (request limits) under legitimate interest (Art. 6(1)(f)). The shared product database, label photos in that database and reports to Open Food Facts are based on your consent (Art. 6(1)(a)), given with separate switches in Profile. Personalised ads are shown only with consent given in the consent dialog. You can withdraw consent in Profile at any time, without affecting earlier processing.
12. Who receives data
Google (USA and EU): AdMob ads, the consent dialog, Google Play payments, Google sign-in (if you sign in; Google then knows you use Talerz) and, if you enable it, Health Connect on the phone. Netcup GmbH (Germany): the data centre where our server runs (shared product database including label photos, account and sync), as a processor. Open Food Facts (France): product queries and, only with your consent, reports of missing products, sent through our server (no photo). Gemini Nano (AICore) and ML Kit (text and barcode recognition) run on the phone and send nothing; the phone downloads the fallback meal recognition model once from Hugging Face (USA); as with any file download, Hugging Face sees your connection's IP address but receives no photos or other data of yours. Transfers to the USA rely on the European Commission decision on the EU-US Data Privacy Framework or standard contractual clauses.
13. How long we keep data
Data on the phone: until you delete it in Profile or uninstall the app. Account data in the cloud: until you delete the account, and server backups at most 14 days longer. Meal photos and descriptions never reach our server. Rate counters and the server technical log contain no content or IP address, and the device identifier is stored as a hash; counters disappear after a day. Reports to Open Food Facts pass through our server and are kept for at most 180 days. Reports to the shared product database (barcode and values) are kept for 180 days together with the sender hash, and product data for as long as the database runs. Label photos uploaded with separate consent are kept permanently (up to the five newest per product); the link between a photo and the sender hash disappears after 180 days. With consent to the shared database the app adds a random installation identifier, so we can count how many people your products helped and not ask you to confirm your own product; we store it only as a hash with a report and with a download of a user-reported product, for 180 days. When you scan a barcode that is not in any database, we store that code with a hash of the installation ID (without consent to the shared database, with a hash of the IP address) so we know which products are missing most often and can show how many people looked for a product. We delete this entry after 180 days or together with your reports. Recipe and nickname reports and community events (for example someone joined a challenge) are deleted after 180 days. App usage counters (for example a finished tutorial or a successful scan) stay only on your phone and are never sent anywhere.
14. Health Connect
If you connect Health Connect, Talerz reads steps and calories burned (to show activity and, if you want, add part of it to your goal) and reads and writes weight (one per day; deleting a measurement in Talerz also deletes the weight from that day that Talerz saved in Health Connect, and Undo saves it again); in no numbers mode it reads only steps. If you turn on Save meals to Health Connect, it saves meals with nutrition values there and changes or deletes them together with the diary entry. This data stays on the phone, is not sent to our server, is not used for ads and is not shared with anyone. You can turn off access in Health Connect settings or in Profile.
15. Your rights and complaints
You have the right to access, rectify, erase, restrict, port (CSV export and backup in Profile) and object to processing, and to withdraw consent. You have the right to lodge a complaint with the Polish supervisory authority, the President of the Personal Data Protection Office (ul. Stawki 2, 00‑193 Warsaw, uodo.gov.pl). The app is intended for people aged 16 and over.
16. Health data in your profile
If you tick them in your profile, Talerz processes health data: conditions (high blood pressure, diabetes, chronic kidney disease), taking diabetes medication (insulin, sulfonylureas), pregnancy or breastfeeding and eating disorders. We do this based on your explicit consent (Art. 9(2)(a) GDPR), given at first launch, only to adjust goals and warnings. This data stays on your phone and is never used for advertising; it reaches our server only if, after signing in, you turn on Sync health data with separate consent. You can withdraw consent in Profile with the Withdraw consent to health data button; we then remove these answers from your phone and the cloud.
17. Account and cloud sync
The account is optional. You sign in with your Google account: Google gives us a signed token with the account identifier, and we store only its cryptographic hash, without your email address or name. We treat the diary (entries, saved meals, water), weight, body measurements, supplements (name, dose and the days you tick them), the weekly meal plan with its templates and profile (height, weight, goal) as health data: we sync them only after your explicit consent on a separate screen after the first sign in, and we store the consent date and policy version on the phone and on the server. Without this consent the account is used only for the community and nothing from the diary leaves your phone. Conditions, medication, pregnancy, eating disorders, diet and allergens need a second, separate Sync health data consent. With consent we also sync settings, custom foods and recipes. We do not send meal or package photos, or paths to them. Deleting an entry on the phone (including weight, water, supplements and meals in the weekly plan) also deletes it from the cloud and from your other phones. You withdraw consent with the Withdraw cloud consent button: sync stops and we delete the diary, meals, weight, measurements, supplements, weekly plan with templates, profile and health data from the cloud immediately (they stay on the phone). Without consent the server does not accept this data. An account can keep at most 50 MB in the cloud. The data is stored on our server in a Netcup GmbH data centre in Germany, sent over HTTPS and encrypted on the server (AES‑256‑GCM) with a server key that we keep separately from the database and its backups. This is encryption at rest, not end‑to‑end encryption: it protects the data for example if only the database or a backup leaks, but the server administrator technically has access to it. We keep it until you delete the account or withdraw consent: the Delete account button deletes the account and cloud data immediately, and server backups are overwritten within 14 days. Signing out leaves the data in the cloud. The legal basis is your explicit consent (Art. 9(2)(a) GDPR) for the diary and health data, and performing the sync service contract (Art. 6(1)(b)) for settings, foods and recipes.
18. Community
The community is optional and requires an account. Public (to signed in users): your nickname, published recipes (name, ingredients with amounts, steps, time; the server calculates values, diets and allergens itself from the food database and marks ingredients outside it as unverified) and the average and number of ratings. Who rated or reported a recipe is not public. Friends (added with an invite code) see your nickname and, in a shared challenge, only the number of days completed; they see your logging streak only if you turn on Show my streak to friends. We do not send weight, calories, diary entries, steps or health data: your phone checks whether a day counts and sends only the date. There is no chat between friends and no photos (messages exist only between you and your coach, section 19). Reported recipes and nicknames are reviewed by an administrator; a report from an account younger than 7 days or without activity weighs less, so a group of new accounts cannot hide a recipe on its own. We do not publish recipes with fasting, purging or very low calorie limits. Reports and community events are deleted after 180 days. Community data is stored on the same server as the account (Netcup GmbH, Germany) until you delete the account or the recipe; Delete account erases it immediately and server backups are overwritten within 14 days. The legal basis is performing the community service contract (Art. 6(1)(b) GDPR) and, for moderation, our legitimate interest in user safety (Art. 6(1)(f)).
19. Crash reports
We send crash reports only if you turn on the Send crash reports switch in Profile (legal basis: consent, Art. 6(1)(a) GDPR). A report contains the place of the error in the app code (without error message content), the Talerz version, the phone maker and model, the Android version and the time of the crash. It contains no diary, profile, health data, photos or account identifier. The report waits on the phone until the next start, and we keep it on the server for at most 90 days. Turning the switch off deletes reports waiting on the phone.
20. Coach and clients
Connecting with a coach is optional and requires an account. The coach gives you their code and you join in Profile, Together, My coach. The coach first accepts your join request and until then sees nothing of your diary. After connecting the coach sees nothing: you turn on what they can see (meals and calories, protein, carbs and fat, weight and measurements, activity, water, consistency, day notes). Diary data is health data, so before the first sharing we ask for your explicit consent (Art. 9(2)(a) GDPR) and store its date and policy version. The phone sends the server only day summaries from the enabled scope, from the last 120 days at most, and the server cuts off everything outside the scope again when saving and on every coach read. Conditions, medicines, pregnancy, eating disorders and other health data from your profile never reach the coach. In no numbers mode you can share only activity without calories, water and consistency. Changing the scope and revoking access work immediately: data outside the scope is deleted from the server right away. Every coach view (day details, opening the dashboard with a 14 day summary at most once a day and export to a CSV file) is recorded in the access log with the coach's nickname and account number; you see it in My coach, and entries older than 365 days are deleted automatically. Blocking the coach ends the collaboration and messages. The coach can send messages, comment on days (you can turn comments off) and send goals and recommendations that you accept or decline. The coach can keep private notes about you, visible only to the coach. Messages, coach notes, recommendations and day summaries are encrypted on the server (AES-256-GCM). Either side can end the collaboration at any time; we then delete messages, recommendations, coach notes and day summaries no other coach can see. A coach can have at most 50 clients. The data is stored on a Netcup GmbH server in Germany. The legal basis is your explicit consent (Art. 9(2)(a) GDPR) and performing the collaboration service contract (Art. 6(1)(b)).
21. Household
A household is optional and requires an account. Members (up to 8 people, joining with a one-time code valid for 7 days; the founder can remove a member) see each other's nicknames, the shared shopping list (name, amount, who added it, whether ticked) and the shared dinner plan (day, recipe, calories per recipe portion). Your portion is calculated on your phone from your goal and never reaches the server or other people; each person's diary, calories, weight and goals stay private. When everyone leaves the household, we delete it together with the list and the plan. The legal basis is performing the service contract (Art. 6(1)(b) GDPR).
22. Referrals and sharing
A referral link goes through our website to the Google Play Store with the referral code in the referrer parameter. After installation the app reads this parameter once through Google Play Install Referrer (only the code, without click or install times) and after sign in sends it to the server with a hash of a random installation identifier and a signature made with a random installation secret (the secret stays on the phone, the server keeps only its hash). The server records who referred whom and on which days (by server date) the invited person had entries; a day counts when a new entry synced to the cloud appeared on the account or Google Play Integrity confirmed the app; after three different days both people get 30 days without ads. The reward turns off ads locally on the phone and is not a subscription. One reward per account and device, at most 10 rewards a month per referrer, and we never reward store ratings. Shared images (recipe, weekly summary, challenge invitation) are made on your phone and go only where you send them; weight and calories appear on the summary only if you tick them and never in no numbers mode. A recipe link opens a public page with the name, ingredients and steps of a published recipe. The challenge of the week shows others only the number of participants, the recipe of the week is chosen from ratings, and the top product database helpers list shows your nickname and how many people your products helped only if you agree. The legal basis is our legitimate interest in developing the app (Art. 6(1)(f) GDPR) and consent for the helpers list (Art. 6(1)(a)).
23. Activity
Activity you enter manually (type, duration, intensity, time, calories) is stored on the phone and, with cloud consent, synced like the rest of the diary. We calculate calories on the phone from MET and your weight; it is an estimate. If you connect Health Connect, we read steps, burned calories and workout sessions (type and time, no heart rate or route) to avoid counting the same workout twice; Health Connect data does not leave the phone unless you share activity with a coach.
24. Meal plan, check-in and workouts from a coach
Your coach builds the meal plan and the workout plan; only you and that coach see them, and they disappear when the coaching ends. In no numbers mode the server stores no calories or macros in the meal plan. Adding a meal from the plan to the Diary, the “From your coach” shopping list and the activity from a completed workout stay on your phone (the shopping list also goes to the shared household list if you belong to one). Asking for a swap is an ordinary message to the coach. Your coach can suggest a meal for a specific day and meal time: the suggestion (name, grams, ingredients, without calories in no-numbers mode) waits on the server until you accept or decline it; an accepted one goes to your weekly plan and shopping list, and the coach only sees whether it was accepted. We delete suggestions after 60 days and when the coaching ends. You send the weekly check-in (mood, sleep, hunger, stress, energy, hard moments, sticking to the plan) only with the “Weekly check-in” switch on, under the same explicit consent as the rest of the scope (Art. 9(2)(a) GDPR); turning the switch off deletes the answers from the server. Workout completion (exercises, sets, reps, weight, minutes) reaches the coach only with “Activity” on. Alerts on the coach dashboard (for example no entries, protein below target, low mood) are calculated when read, only from data you share; in no numbers mode without protein and weight. You see the coach reading your check-in and workouts in the access log. Content is encrypted on the server.
25. Groups and the coach directory
Groups: you join a group with a code from the coach; the coach and other members see only your nickname, and the shared challenge progress is shown in total, without weight, calories or ranking. You can leave a group at any time (your progress disappears). Announcements and members can be reported to moderators; a report is kept until the moderator decides, and the coach or a moderator can block a person in the group. Legal basis: performance of the contract (Art. 6(1)(b)). Directory: a coach or dietitian shows a profile (name, role, specialties, city, online mode, description, avatar from initials or an illustration, never a photo) only with explicit consent (Art. 6(1)(a)), withdrawn by turning off the switch; a moderator grants the “Verified” badge manually. When a coach has a public directory profile, members of the coach's groups see the name from that profile instead of the nickname. A coaching request from the directory works like a coach code: the coach sees your nickname and nothing else until accepting it, and then only what you share. Talerz does not handle payments for coaching.
26. What's in my fridge, At home and Better choice
Your phone recognises the photo of your fridge or products (Gemini Nano or the on-device model); we don't send the photo and delete it right after recognition. The list of products at home, use-by dates, place (fridge, freezer, pantry), servings and the “eaten” and “thrown away” marks are stored on your phone. If you sign in, we sync them in the cloud like recipes (encrypted, without health data consent, because they aren't health data). If you belong to a household, the “At home” list is shared: household members see the products, dates and the nickname of the person who changed an item; the server deletes eaten and thrown away items after 62 days. The waste statistics are calculated on your phone. The reminder a day before the use-by date is a local notification, without a server. “Better choice” sends only the product barcode to the server; your phone checks the diet and allergens from your profile. Missing ingredients added to the shopping list go to the shared household list if you have one. When you leave a household (or its founder removes you), the items you added disappear from the shared list and stay only on your phone, while items added by other household members stay with them.
27. Several accounts on one phone and your name
Each Google account signed in to Talerz on this phone has a separate data profile: its own database of diary, weight, water, activity, meals, At home and supplements, its own settings, goals, sync queue, cooperation and community cache and its own folder of meal photos. Another person who signs in with their account sees only their own data. Data used without an account sits in a separate no-account profile. On the first sign-in on a phone that already has data without an account, we ask whether to link it to that account. After you sign out, the account's data stays on the phone in its profile (it comes back when you sign in again with the same account) and the app switches to the no-account profile; Delete account also deletes that account's profile on the phone. Backup and export cover only the active account. We keep the email address and name from your Google account only on the phone, in that account's profile, to show which account you are signed in with. The name you enter at first sign-in or in Profile is saved in the profile settings and, after you agree to sync, in the cloud together with the settings (encrypted on the server like the rest of the account data); you can remove it by changing the name or deleting the account.
