Privacy policy

Last updated November 18, 2026

This policy explains what EatHabit — the app and eathabitapp.com — collects, why, who else handles it, how long it's kept, and what you can do about it.

At a glance

We collect what EatHabit needs to work and nothing for advertising: no ads, no analytics or tracking tools, and we never sell or rent your data.

Your health details are used only with the explicit consent you give when you sign up, and only for your own targets and diary — plus whatever you choose to share with friends.

AI logging sends your photo or description to OpenAI to recognise the food. The photo isn't stored.

Your account and diary are stored in the EU. You can delete them in the app at any time; deleting your account doesn't cancel a store subscription.

Who we are

EatHabit is made and run by Svetlin Dimitrov Dimitrov, an independent developer based in Bulgaria — "we" in this policy. We decide how your data is used, which makes us its controller under the EU General Data Protection Regulation (GDPR).

Postal address: ul. Vladislav Varnenchik 18, Varna, Bulgaria. Phone: +359 882 700 923.

Write to support@eathabitapp.com, in English or Bulgarian, about anything in this policy. A person answers.

Your account

To create your account we store your email address, a username, a user tag, your language and time zone, how you sign in, and the date you joined. Your email address is kept in a standard form that still reaches you: lower-case, with googlemail.com written as gmail.com, without +labels for providers such as Gmail, Outlook, Hotmail, iCloud and Proton, and without dots for Gmail.

Your username starts as your Google name, or as the part of your email address before the @ in that standard form, and you can change it. Your user tag is built from that first username — lower-case, with every character other than the letters a–z and digits turned into _ — followed by # and four random digits. It never changes, even when your username does.

If you sign up with a password, your account is created only after you confirm your email address, and we store the password only as a one-way hash that can't be read back. If you sign in with Google, Google confirms who you are and shares your name, email address, profile picture and language with us; we never see your Google password. Your Google picture becomes your profile photo until you replace or remove it; it loads from Google's servers, on your phone and on the phones of people you connect with, so Google sees those phones' IP addresses.

We also keep a record of which version of the terms and this policy you accepted and when, and a record of each sign-in, which holds no details about your device.

Your app settings are kept with your account, so they follow you to a new phone: your theme, the meal names you use, the nutrients and health goals you put in focus, and your reminders with their days and times.

Your health details

To set your energy and nutrient targets, the app asks when you sign up for your birth date, gender, height, weight and activity level; an account can't be created without them. If you're female, you can also say that you're pregnant or breastfeeding, which changes your targets; the default is neither. You can also set a weight goal when you sign up, and log your weight over time. Each time you do, the app compares the calories you logged in the weeks before with how your weight changed and, once it has enough of both, uses that to adjust your calorie target. When you change a detail, the values of earlier days are kept so your past targets and trends stay right.

These are health data under the GDPR. We use them only with the explicit consent you give with the tick box when you create your account, and only to set your targets and show them in your own diary — and to show a friend what you choose to share with them. The app can't set targets without these details, so to withdraw your consent you delete your account, which you can do in the app at any time.

Friends you share Weight with see your weigh-ins and how your weight has changed, but not your weight goal. Friends you share Meals with see your nutrient targets, which differ while you're pregnant or breastfeeding.

Your diary

The app stores what you log: meals and the foods in them, with when you ate them, under the meal names you use, with any name, photo, food group, serving or nutrient value you change; recipes with their ingredients, steps, tags and times; favorites; saved meals; your nutrient targets and diet; fasting sessions; and how many AI requests you make each day.

When you log a recipe, the meal keeps a copy of it as it was — its name, photo and nutrition — so your history stays right if you later edit or delete the recipe.

This data runs your diary — its totals, trends, scores and targets — and the parts you share with friends. None of it is used for advertising or to train AI models.

Photos

You can add photos to logged foods, favorites, recipes and their ingredients, foods in saved meals, and your profile. The app re-encodes each photo before uploading it, which removes its location and other hidden details.

Before a photo is stored, our server sends it to OpenAI's moderation service, which checks it for unsafe content; a photo that fails the check, or can't be checked, is refused. A photo that passes is stored at Cloudflare and served from a web address that is hard to guess but not secret: the address contains your account ID, and anyone who has it can open the photo. Cloudflare also compares the photos it serves against known child sexual abuse material.

When you replace or delete a photo, or delete what it belongs to, the photo is deleted from storage — right away or in our nightly cleanup — unless something else still uses it, such as a logged meal of a recipe you deleted. Copies already cached — by Cloudflare's network or on phones that showed the photo — can remain until those caches refresh.

AI logging

AI logging is part of the Premium plan. When you use it, the app sends your photo or typed description to our server, which passes it to OpenAI together with your app language and any serving and amount you entered. OpenAI recognises the foods and their portions, and we look up their nutrition in our food database.

To match what the AI recognised against our food database, to work out foods we don't have, and to screen out anything that isn't food, our server sends OpenAI text only: the food's name, any brand, a short description, the names of similar foods from our database, and your words if you typed your request. Asking the AI to check a packaged food's label sends only that product's label details.

OpenAI receives no account details and nothing from your diary. Under its API terms it doesn't use this data to train its models. The photo you send for AI logging is used only for that request: we don't store it, and it doesn't become part of your diary.

Foods the AI works out that we didn't have yet — their name, brand, food group, serving sizes and nutrition — are saved in our shared food list with nothing that links them to you, and reused when anyone logs the same food. The result of a label check is saved with the product in the same way, for everyone. The AI is told to keep personal details out of food names, but please leave them out of what you type as well.

Food search and Open Food Facts

Searching for a food runs on our own servers — packaged foods are searched in our copy of the public Open Food Facts database — so your searches aren't sent to anyone else, and a scanned barcode is looked up the same way. When our copy doesn't have a product yet, our server asks Open Food Facts for it, sending nothing but the barcode. Your diary keeps a product as it was when you logged it.

Product photos are loaded by your phone straight from Open Food Facts — in search results, on the food's page, and on a friend's phone when they open a food you shared — so Open Food Facts sees that phone's IP address, as any website you visit would.

Friends

To connect with you, someone needs your exact user tag. While a friend request is pending, each of you sees the other's username, user tag and profile photo, and when the request was sent, and the app also receives the other person's account ID, a random code. Once you're friends, each of you also sees when the other joined EatHabit and since when you've been friends.

For each friend you choose what they can open: Meals (which also covers when you ate each food, your daily nutrient totals and targets, health goals, the foods, recipes and saved meals you log most, and your logging streak and totals), Recipes, Fasting, and Weight. Nothing is shared until you turn it on, and the summary on your profile follows the same choices. You can stop sharing any part at any time, and removing a friend stops all of it.

Subscriptions

Plans are bought through the App Store or Google Play, and payment details never reach us.

We use RevenueCat to manage subscriptions. Its component in the app starts when the app opens, under a random ID, and once you sign in it uses your EatHabit account ID so your plan follows your account. RevenueCat receives your purchases from the store, and our server checks your plan with RevenueCat using the same ID.

We store your plan and when it ends, plus the purchase notices RevenueCat sends us: the kind of event and its time, the product and the plan it unlocks, which store it came from and whether it was a test, the expiry date, and the account IDs involved, including the random ID used before you signed in — never prices or payment details.

Emails

We email you only when you ask or when we have to: to confirm your email address when you sign up or change it, to reset your password, to confirm that your account was deleted, and to tell you about changes to our terms or this policy, a change that reduces a paid plan, or a security problem that affects you. We send no marketing email. For notices about changes or security, we keep a record of which one we sent you and when, so we can show that we told you; it is deleted with your account.

Our emails are sent by ZeptoMail, Zoho's email service, from its EU data centre. When you ask for a confirmation or reset link, the app sends our server your email address, with your language and theme so the email matches the app, and we keep the address, with the link and your language, until you finish that step.

If you write to us, we use your message only to answer you. PDF reports are made on your phone and never emailed by us; you decide where to share them.

On your phone

The app asks for your camera only when you scan a barcode or take a photo, and for your photo library only when you pick a photo. It doesn't use your location, contacts or microphone. It asks to show notifications only for the reminders you turn on: they are scheduled on your phone itself, and we send no push notifications. The app also asks our server whether a newer version is out, sending only whether the phone runs Android or iOS and the app's version number; our server keeps neither.

Barcodes are read on your phone by Google's ML Kit, which sends Google technical data about how it runs — such as the device model, system and app version, performance figures and error codes — but not the camera image.

Your sign-in is kept in your phone's secure storage. The phone also keeps your settings — theme, background, language, and your chart and focus choices — your meal names, fasting timer and last fasting plan, the reminders it has scheduled, copies of the photos you've looked at and the PDF reports you've made, and RevenueCat's own IDs. While you sign up, your answers stay on the phone and your targets are worked out there; your profile answers and password are sent once, when you create the account, and if you stop before that, your answers stay on the phone. Signing out or deleting your account removes your EatHabit sign-in, its scheduled reminders and your last fasting plan from the phone, but not your Google sign-in; the rest stays until you uninstall the app.

The website

eathabitapp.com is a static site: it sets no cookies, runs no analytics, and loads no fonts or scripts from anyone else. Your theme choice is stored in your own browser and never leaves it. As with any website, the service that hosts it sees your IP address in order to deliver the pages.

Security and abuse prevention

All connections are encrypted, and passwords are stored only as one-way hashes.

Your IP address is used only to slow down abuse: it limits sign-in attempts, how many signup, password-reset and email-change emails can be requested, and how often the app can check whether such a link was confirmed. For the same reason, we count the emails and password-reset attempts for each address for a short time. None of these counters is written to our database.

Our server keeps technical logs to find and fix problems. They can contain your account ID and are used for nothing else.

If a security incident puts your data at high risk, we tell you by email without undue delay.

Why we use your data

The GDPR asks us to name a legal basis for each use of your data.

Our contract with you (Art. 6(1)(b)) — your account, diary, photos, AI logging, friends, subscriptions and the emails you ask for: we need them to give you the service you signed up for.

Your explicit consent (Art. 9(2)(a)) — your health details, on top of that contract.

Our legitimate interests (Art. 6(1)(f)) — keeping EatHabit secure and free of abuse through rate limits, technical logs, the safety check on photos and the records of what you accepted and of the notices we sent you, and building our shared food list from the foods the AI works out.

A legal obligation (Art. 6(1)(c)) — telling you about changes to our terms, handling reports under the Digital Services Act, and answering lawful requests from authorities.

The app sets your targets automatically from your details and what you log, and the photo check is automatic, but neither has legal or similarly significant effects on you: targets only tune what your own diary shows, and you can ask a person to review a refused photo.

Who else handles your data

We share data only with the service providers that run parts of EatHabit for us, under contracts that let them use it only on our instructions:

Google Cloud — runs our server in Belgium and keeps its technical logs.

TiDB Cloud by PingCAP, Frankfurt, Germany — our database.

Upstash, Belgium — short-lived caches and abuse-prevention counters.

Cloudflare — stores and delivers photos, and forwards the emails you send us to our mailbox.

OpenAI, United States — AI food recognition and the photo safety check.

RevenueCat, United States — subscription status.

ZeptoMail by Zoho, EU — the emails we send you.

Others handle data under their own policies: Apple and Google when you buy a plan, and Google when you sign in with Google or scan a barcode; Open Food Facts when your phone loads a product photo; and the friends you share with. We disclose data to authorities only when the law requires it.

OpenAI and RevenueCat are in the United States, and other providers' staff or subcontractors may reach data from outside the European Economic Area. Each such transfer is covered by an EU adequacy decision, such as the EU–US Data Privacy Framework for companies certified under it, or by the European Commission's standard contractual clauses. You can ask us for a copy.

How long we keep it

Your account, health details, diary, photos and friends: until you delete them or your account.

Sign-in records: until about 30 days after their last use; signing out doesn't end them sooner, but resetting your password does.

Confirmation and reset links, with the address they go to and your language: until you finish that step, or about a day after the link expires.

Abuse-prevention counters: an hour at most; sign-in attempts are counted only in the server's memory, a minute at a time.

Technical logs: 30 days.

Cached copies on our server: a day at most.

Purchase notices from RevenueCat: 90 days after they arrive, even if you delete your account sooner.

Your account ID in our deletion queues: until the nightly cleanup has deleted your photos and your RevenueCat record.

Database backups: our database provider keeps daily backups for up to 30 days.

What we send OpenAI: it may keep it for up to 30 days to detect abuse, then deletes it.

Foods in our shared food list and label-check results: kept, with nothing that links them to you.

Emails you send us: as long as we need them to help you.

Deleting your account

Delete your account in the app under More › Settings › Delete account. If you no longer have the app, email us from the address on your account and we'll delete it for you; the support page on eathabitapp.com has the steps.

Deleting removes your account and everything in it from our database at once. Cached copies expire within a day, our nightly cleanup deletes your photos from storage and your customer record at RevenueCat within 30 days, and the deleted data drops out of our database backups as they expire. We email you a confirmation. Deleting is permanent, and it doesn't cancel a store subscription — cancel that in your store settings first.

Your rights

Under the GDPR you can ask for a copy of your data, including in a portable format; have it corrected or erased; restrict how we use it; and withdraw your consent. You can correct most of it, and delete your account, yourself in the app. For anything else, including a full copy of your data, email us. We answer within a month or, for a complex request, tell you within that month that we need up to two more. We may ask you to write from the address on your account so we know it's you.

You can complain to a data protection authority — in Bulgaria, the Commission for Personal Data Protection, 2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, cpdp.bg — or to the one where you live or work.

Your right to object

You can object at any time to our use of your data based on legitimate interests, listed under Why we use your data. We then stop, unless we have compelling reasons that override your interests, or need the data to establish or defend a legal claim.

Age

EatHabit is for adults: you must be 18 or older to create an account. We don't knowingly collect data from anyone younger, and we delete any account we learn belongs to a minor. If you think one does, tell us.

Changes to this policy

If we change this policy in a way that matters to you, we email you and show the change in the app before it applies. Each version shows its date at the top.