Last updated: 14 October 2026
Name, weight, height, age, sex, activity level, goal and target weight are used to personalise the experience and calculate your daily target. They stay on your device. Your name is not sent to Firebase Analytics or to our services.
What you logged, the amount, the calories and macros, and the day. Stored on your device and never sent to our servers. Your diary is not readable by us.
If you use the photo feature, the photo is sent to our server and forwarded to a third-party AI provider (OpenAI) that identifies the food and estimates the nutrition. The photo is used for that single request and is not stored by us. The photo is reduced in size on your device before being sent.
Only photos you explicitly take or pick for this purpose are sent. The app does not read your photo library on its own.
If you scan a barcode, the number is sent to Open Food Facts, an open public food database, to look up the product. Only the barcode number is sent — no identifier of yours travels with it. See openfoodfacts.org/privacy.
If you ask the app to estimate the calories of something you typed (for example "cooked white rice"), that text is sent to our server and to the AI provider. The answer is cached by food, not by person — the cache holds "cooked white rice", never who asked for it.
We use RevenueCat to validate purchases and to tell the app whether a subscription is active. It processes purchase events, an anonymous installation identifier, technical app information and standard Apple Ads attribution when available. See revenuecat.com/privacy. Payment itself is handled by Apple; we never see your card.
If you submit a suggestion, we receive the ingredients, meal type, cooking method, optional note, language and a random installation identifier. The identifier is hashed, is used to enforce the weekly limit and does not contain your name or e-mail address. The suggestion stays in our editorial queue until it is reviewed or removed.
We use Firebase Analytics to understand how the app is used — for example, which of the three logging methods people prefer, or where onboarding is abandoned.
Analytics never carries what you ate. Food names, photos and calorie values are not part of any analytics event. The service processes a random app-instance identifier, technical app and device attributes, and an approximate region derived from the IP address. The name entered during onboarding is not sent. We measure behaviour, not meals.
We use Firebase Crashlytics. It may process crash data, technical app state, device model, operating-system version and technical installation identifiers. This is used to fix errors and measure stability; it does not include your food log or meal photos.
Data on your device lives until you delete it — and deleting the app deletes it. Photos are not retained after the request that used them. Cached food estimates are kept by food description for up to 180 days and contain nothing about you. Recipe suggestions remain in the editorial queue until they are reviewed or removed.
Easy Diet is not directed to children under 13, and we do not knowingly process their data.
If the app starts processing something new, this page is updated before that version ships, and the date at the top changes.