NutriBot Privacy Policy

Version: 2026-10-24 · Effective: 2026-10-24

This policy explains what personal data NutriBot collects when you use the NutriBot iOS and Android apps and the website nutribot.life (together, the "Service"). It covers why we use the data, who we share it with, where it is processed, how long we keep it and what rights you have.

Key points

  • What we collect. What we need to calculate your calorie and macronutrient targets, build your menu and keep your food diary: your account details, body metrics, diary and settings (section 3).
  • Health and religious data. Body metrics, health conditions and halal or kosher practice are special categories of data. We process them only with your explicit consent (section 3.2).
  • AI. Our AI features, called NutriBot AI, are powered by Anthropic's Claude API. In the apps nothing is sent to the AI service until you allow it, and you can turn it off at any time in Settings → Privacy → AI features. We do not store your photos, and Anthropic does not use your data to train its models (section 3.4).
  • Subscriptions. App Store purchases are processed by Apple and Google Play purchases by Google, and we use Adapty to manage subscription status. We never see your card details (section 3.11).
  • No selling, no ads, no tracking. We do not sell your data, do not use it for advertising and do not track you across other companies' apps or websites. The apps do not use Apple's advertising identifier (IDFA) or Google's advertising ID.
  • Your control. You can download your data or delete your account in the app at any time (section 9).
  • Adults only. You must be 18 or older (section 2).

1. Who we are

The controller responsible for your personal data is Serhii Molodets, an individual based in Ukraine ("NutriBot", "we", "us"). Website: https://nutribot.life. Our postal address is available on request.

  • Privacy questions and data requests: privacy@nutribot.life
  • General support: support@nutribot.life

EU representative (GDPR art. 27). We are appointing a representative in the EU and will name it here. Until then, residents of the EU/EEA can contact us directly at privacy@nutribot.life.

UK representative (UK GDPR art. 27). We are appointing a representative in the UK and will name it here. Until then, UK residents can contact us directly at privacy@nutribot.life.

We have not appointed a Data Protection Officer. privacy@nutribot.life is our privacy contact for every data protection matter.

2. Minimum age

The Service is intended only for adults. You must be at least 18 years old to use it. The sign-up form does not accept an age under 18. Apart from the accounts described in the next paragraph, we do not knowingly collect data from anyone under 18. If we learn that someone under 18 created an account by giving a wrong age, we delete the account. If you believe someone under 18 has given us data, write to privacy@nutribot.life.

3. What we collect

3.1 Account and sign-in data

  • iOS app. You sign in with Sign in with Apple, Google Sign-In or email and password (we verify your email address). Sign-in is handled by Firebase Authentication (Google). It stores your email address, a securely hashed password (email sign-in only), the sign-in method, an account identifier and sign-in timestamps, and it logs IP addresses and the device user agent for security. With Sign in with Apple you can hide your email; we then receive an Apple relay address. Apple gives us your name only on your first sign-in, and Google includes your name in the sign-in data. We store the sign-in method and that name as your display name.
  • Android app. You sign in with Google Sign-In or email and password (we verify your email address). Sign in with Apple is available only in the iOS app. Sign-in is handled by Firebase Authentication (Google) in the same way as in the iOS app: it stores and logs the data listed above. Google includes your name in the sign-in data, and we store the sign-in method and that name as your display name.
  • Google Sign-In. If you choose Google, you sign in on Google's own sign-in page (in the Android app, the Google account sheet shown by Google Play services), and Google processes the data it collects there (for example your Google account details and device information) under Google's privacy policy. NutriBot receives only your name, email address and Google account identifier.
  • Guest account. You can start using NutriBot as a guest, without a Google or email account (or, in the iOS app, an Apple account). We then create a random user ID for this app installation; it isn't linked to your name, email or phone. Your profile, diary and settings are stored under that ID exactly as for any account, and the same rights apply (export, deletion). A guest account can't be recovered: if you delete the app, sign out or lose the device before linking a sign-in method, the data can't be restored. You can link Google or email (and, in the iOS app, Apple) at any time; the account and its data stay the same. Guest accounts that haven't been used for 90 days (and have no active subscription) are deleted automatically, as are guest accounts that never finished setting up, after 7 days. If you buy a subscription as a guest, the random ID is shared with our subscription processor (Adapty) like any account ID.
  • Profile: the display name you choose in Settings, your app language and the version of the Terms and of this policy you accepted, with the date.

3.2 Body metrics and health data (special category data)

To calculate your calorie and macronutrient targets and build your menu, we ask for, and store:

  • sex, age, height, weight, activity level, goal (lose, maintain or gain weight), body type and, optionally, a goal weight;
  • optional body measurements (chest, waist, hips) and your weight history;
  • optionally, health conditions you tick in your dietary preferences (high cholesterol, type 2 diabetes, gout, high blood pressure, fluid restriction), together with your diet type (for example vegetarian or vegan), halal or kosher practice and foods you avoid.

This information can reveal data concerning your health and, for halal or kosher practice (and possibly a vegetarian or vegan diet), your religious or philosophical beliefs. These are special categories of personal data. We process them only with your explicit consent (GDPR art. 9(2)(a); art. 7 of the Law of Ukraine "On Personal Data Protection"):

  • iOS and Android apps: before you first enter your body metrics, a separate screen explains what we use and why, and you give the consent by tapping «I agree».

This consent is a condition of using NutriBot. Without these data we cannot calculate your targets or build your menu, so we cannot provide the Service. You can withdraw the consent at any time, but only by deleting your account (section 9): there is no way to keep an account and withdraw only this consent.

We use health conditions and dietary practices only to shape your menu (exclusions, limits and the water guide) and as context for NutriBot AI when you use it (section 3.4), never for advertising or analytics. The iOS app does not read or write Apple Health data, and the Android app does not read or write Health Connect data.

3.3 Food diary, menu and app settings

  • your food diary: what you ate, portion sizes, calories and macronutrients, meal times and how each entry was added (photo, barcode, search or menu), plus water intake and cheat-meal days;
  • your menu settings and edits: excluded foods, number of meals, swapped or skipped meals, your shopping list;
  • sport nutrition: selected supplements, protein and gainer doses, and protein bars, including bars you add yourself;
  • recently used foods, achievements, first-run tour progress and display preferences (units, language, "diary only" mode).

3.4 NutriBot AI (third-party AI processing)

What it is. In the app, our AI features are called NutriBot AI: food photo recognition, dish estimates from a description, the NutriBot assistant and recipes. NutriBot AI is powered by the Claude API of Anthropic (Anthropic, PBC). Anthropic processes the data on our behalf, as our data processor. Your menu and your targets are not made by AI: they come from our own planning engine (see "Automated calculations" in section 4).

Your permission.

  • iOS and Android apps: the first time you tap a NutriBot AI feature, the app shows a separate permission screen. It lists the AI features, the kind of content they send and the AI service that processes it, and you choose whether to allow it. Nothing is sent to the AI service until you allow it. You can withdraw the permission at any time in Settings → Privacy → AI features. While it is off, nothing is sent, the AI features are unavailable and the rest of the app keeps working; the app asks again only if you tap an AI feature.

What is sent:

  • the food photo and any hint you type;
  • the dish names or descriptions you ask us to estimate;
  • your question to the assistant and the recent conversation;
  • the context needed to answer: your goal, current weight and recent weight trend, daily targets, today's and recent diary entries and weekly or monthly summaries, the rest of today's menu, food exclusions, and the diet settings, dietary practices and health conditions you selected (as menu limits).

Before a photo leaves our server, we re-encode it without metadata such as location.

What is not sent: your name, email address, or account identifier.

How Anthropic handles it: Anthropic processes the content above only to return the answer to us. Under Anthropic's commercial terms, API inputs and outputs are automatically deleted from Anthropic's systems within 30 days. They may be kept longer only where the law requires it or to enforce Anthropic's usage policies: content that Anthropic's safety systems flag as a policy violation may be kept for up to 2 years. Anthropic does not use this data to train its models. Anthropic has no EU data region, so the data may be processed outside your country, including in the United States; transfers rely on the Standard Contractual Clauses in Anthropic's Data Processing Addendum (section 6).

What we keep: we do not store your photos, your questions or the AI's answers on our servers. Photos are processed in memory to get the result and then discarded. We keep only the diary entry you choose to save from the result, the recipes shown on your menu (a short cache of up to 7 days) and a daily count of your AI requests.

Other uses of the same AI service. Our team may also use it to help review and translate product entries in our catalogue and the community food database (section 3.9). Only product names and nutrition values are sent, never who added them.

Automated answers. AI answers are generated automatically and are not reviewed by a person before you see them. They can be inaccurate, and they are not medical advice (see our Terms of Service). The NutriBot assistant is an AI system, not a human, and is labelled as such in the app.

Changes. We use no other AI provider. If we change the AI provider, we will update this policy and the information on the in-app permission screen before the change.

3.5 Usage and analytics data

Only if analytics is on for your account (section 8):

  • the days on which you used the Service;
  • the platform you use (for example iOS or Android);
  • your approximate country, derived from your device's time zone;
  • how you found us (on your own, through a family invite or through a campaign link);
  • anonymous daily counters of feature use that do not identify you;
  • which setup step you reached in the app (for example goal, body measurements or diet), the platform and the time of each step, to see where people stop during setup.

Regardless of analytics, we keep a per-user daily counter of AI requests to enforce fair-use limits, and aggregate AI usage counters (without user identifiers) for cost control.

We do not use third-party analytics or advertising SDKs in the iOS or Android app. The only third-party SDK for crash reports is Firebase Crashlytics (section 3.14), which is not used for analytics or advertising.

3.6 Reminders and push notifications

  • Reminder data: your reminder settings (times, days, time zone, quiet hours, tone), delivery state (for example how many reminders went unanswered) and the date and time you last opened the Service. We record the last time you opened the Service whether or not analytics is on, because reminders depend on it: they pause when you stop responding and resume when you come back.
  • iOS app: if you allow notifications, reminders are delivered by Firebase Cloud Messaging (Google) and the Apple Push Notification service (Apple). For each device we store a push token (an identifier that Firebase Cloud Messaging issues for the app installation), the platform, the app version and build, the operating system version, the device language and region setting, and whether notifications are allowed.
  • Android app: on Android 13 and later the app asks for the system notification permission only after you choose to (in the in-app prompt or when you turn reminders on); on earlier Android versions notifications are allowed unless you turn them off in the system settings. Reminders are delivered by Firebase Cloud Messaging (Google), and we store the same device data as for the iOS app.
  • Lock screen: a reminder can contain your display name, the calories you have left and a dish, and it may appear on your lock screen. The iOS "Show Previews" setting, or the lock-screen notification settings on Android, control that.
  • Trial reminder: if you started an App Store or Google Play free trial that will renew, we send one notification about 2 days before the trial ends.
  • Notifications are optional. You can turn reminders off in the app, or notifications in your device settings, at any time.

3.7 Family sharing and invitations

If you create or join a family, the family record stores your account identifier and display name, so members can see each other's names and daily calorie targets and share one menu and shopping list. Members do not see each other's account identifiers.

To invite someone, you share a link of the form nutribot.life/join/<code> (or the code itself). Anyone who has the link can open our web page for it, which shows only the family code. After signing in to NutriBot, the person sees the family owner's display name and the number of members before deciding to join; joining does not need the owner's approval. Share the link only with people you want in your family.

3.8 Share cards

When you share a report, a trophy, your progress, a menu or a diary day, NutriBot creates an image of that card. The card's content (for example your numbers and dish names) is carried inside the link itself; the image is generated from the link when someone opens it and is not stored. Anyone with the link can open the image for 30 days; after that the link stops working. We don't publish the link anywhere: you choose where to share it.

3.9 Community food database

When you log a product that is not in our catalogue (a scanned barcode, a label you typed or an AI estimate), its name, barcode and nutrition values per 100 g may be added to our shared community food database. Other users may see the product and its nutrition values (the median of users' entries, or the label data), but never who added it. Your contribution is linked to your account identifier only so that we can combine it with other users' entries. Please do not put personal information in product names. When you delete your account or object (section 10), your contributions are erased; the product itself, without any link to you, may remain.

3.10 Product suggestions

When you suggest a product for our catalogue or add your own protein bar, the suggestion (the product data you entered) is stored with your account identifier so that our team can review it. It is deleted together with your account and included in your data export.

3.11 Purchases and subscriptions

  • iOS app: subscriptions are sold and charged by Apple through the App Store. We use Adapty to manage subscription status. Adapty receives your NutriBot account identifier, App Store transaction data (product, price, currency, dates, trial, renewal and refund status) and technical data from the app: device model, operating system and app version, and the identifier for vendors (IDFV), an identifier Apple gives each app developer that is the same across that developer's apps on your device but is not shared with other companies. We have configured Adapty not to collect your IP address or Apple's advertising identifier (IDFA), and its attribution features are off.
  • Android app: subscriptions are sold and charged by Google through Google Play (Google Play Billing). We use Adapty to manage subscription status. Adapty receives your NutriBot account identifier, Google Play purchase data (product, price, currency, purchase token and order ID, dates, trial, renewal and refund status) and technical data from the app: device model, operating system and app version, language, time zone, your Google Play country, two identifiers: the Android ID (on Android 8 and later it is unique to each app developer's signing key, user and device) and the App Set ID (the same across one developer's apps on your device and not shared with other companies) and, where Google Play provides it, the install referrer (which store page or link the app was installed from). We have configured Adapty not to collect your IP address or Google's advertising ID, the app does not declare the advertising ID permission, and Adapty's attribution features are off.
  • We never receive your card details. We keep a payment record (payment ID, plan, amount, date, renewal and refund status, your account identifier), a record of the subscription events Adapty reports to us (product, price, store, dates and status) and a record of promo codes you redeem.
  • We do not use Apple's advertising identifier or Google's advertising ID and do not track you across apps or websites of other companies, so the iOS app does not ask for tracking permission.

3.12 Barcode and product lookups

Barcodes you scan and product names you search for may be looked up in Open Food Facts by our server. No information that identifies you is sent. Searches that find nothing are counted anonymously to improve the catalogue.

3.13 Website

Our website does not use cookies, analytics, advertising tools or third-party fonts or scripts. Like every website, it is served by a hosting provider that keeps request logs (section 3.14).

3.14 Technical and security data

  • Our hosting and server providers keep technical request logs (including IP address, user agent and time) for security and troubleshooting.
  • The iOS app uses Firebase App Check with Apple's App Attest to confirm that requests come from the genuine NutriBot app. This exchanges a device integrity token, not your personal data.
  • Crash reports. The release builds of the iOS and Android apps use Firebase Crashlytics (Google). When the app crashes, it sends Google a crash report: the stack trace (where in the code the crash happened), the app version and build, your device model, operating system version, free memory and disk space, screen orientation and the time of the crash, together with a Crashlytics installation identifier and your NutriBot account identifier (Firebase user ID). Crash reports contain no name, email address, diary or health data. We use them only to find and fix crashes, not for analytics or advertising, and they are sent whether or not analytics is on.
  • Google's SDKs in the apps (Firebase and Google Sign-In; in the Android app also Google Play services, which provide Google sign-in, the barcode scanner, Google Play Billing and the rating sheet) may send Google limited technical and diagnostic data that it needs to run those services, not linked to your NutriBot account.
  • Rating prompt. After you have logged food on a few days, the app may ask the App Store or Google Play to show its built-in rating sheet. Apple or Google decides whether to show it. A rating you leave goes to the store under its own terms; NutriBot receives no data through the sheet. The counters that decide when to ask stay on your device.

3.15 Do you have to give us this data?

You do not have to use NutriBot. But to use it, you must give your body metrics and the health-data consent: without them we cannot calculate targets or build menus, so we cannot provide the Service. Health conditions, body measurements, NutriBot AI, analytics, marketing, notifications, family sharing and share cards are optional.

3.16 What we do not collect

We do not collect your precise or approximate location from your device's location services, your contacts, your browsing or search history outside NutriBot, your advertising identifier, audio recordings, or card or bank details. The apps do not read your photo library: they receive only the photo you take or pick for a NutriBot AI request (in the Android app through the system photo picker or camera app, without storage or camera permissions).

4. Why we use your data and our legal bases

  • Account and sign-in (account and sign-in data). Basis: performance of our contract with you (GDPR art. 6(1)(b)).
  • Providing the Service: targets, menus, the food diary, reports, reminders, family sharing, share cards and sync between your devices (profile, body metrics, diary, settings). Basis: contract; for health data and dietary practices, your explicit consent (art. 9(2)(a)).
  • NutriBot AI (section 3.4), when you use it. Basis: contract; for the health data and dietary practices included, your explicit consent (art. 9(2)(a)). In the apps the content is sent only after you allow NutriBot AI, and you can withdraw that permission in Settings → Privacy → AI features.
  • Reminders and push notifications (reminder settings, last time you opened the Service, push tokens), including the trial reminder about your own subscription. Basis: contract; whether to allow notifications is your choice on your device.
  • Payments, subscriptions and accounting (payment records, subscription events, App Store, Google Play and Adapty data). Basis: contract; our legal obligation to keep accounting and tax records (art. 6(1)(c)).
  • Product analytics (activity days, platform, country, acquisition source, feature counters, the setup step you reached), to understand which features help people and to keep the Service sustainable. Basis: in the EU/EEA, the UK and Switzerland, your consent (art. 6(1)(a)); elsewhere, our legitimate interest in improving the Service (art. 6(1)(f)). You can switch analytics off at any time.
  • Community food database and product suggestions (sections 3.9 and 3.10), so that logging products is faster and more accurate for everyone. Basis: our legitimate interest (art. 6(1)(f)); you can object (section 10).
  • Marketing messages, only if you opt in. Basis: consent.
  • Security, abuse prevention, app integrity checks, fair-use AI limits and technical logs (IP address, user agent, counters, App Check tokens). Basis: our legitimate interests in keeping the Service secure and its costs sustainable.
  • Crash diagnostics (crash reports, section 3.14), to find and fix crashes in the apps. Basis: our legitimate interest in keeping the apps stable (art. 6(1)(f)); you can object (section 10).
  • Legal compliance and claims (deletion log, anonymised payment records). Basis: legal obligation and our legitimate interest in demonstrating compliance.

We do not sell your personal data, do not use it for advertising and do not use it to train AI models.

Automated calculations

Your calorie and macronutrient targets are calculated automatically from your sex, age, height, weight, activity level and goal (the Mifflin–St Jeor formula with activity multipliers and goal adjustments). Your menu is composed automatically from meal templates, your exclusions and the health-condition limits you selected. These are suggestions that you can change at any time. They do not produce legal or similarly significant effects on you, so they are not automated decisions under GDPR art. 22. You can ask us how they work.

5. Who we share data with

5.1 Service providers (processors)

These providers process data only on our instructions, under written data processing agreements (GDPR art. 28). They are required to protect your data to at least the same standard as this policy and the law require, and may not use it for their own purposes.

  • Google Cloud and Firebase (Google LLC and its affiliates): our database (Cloud Firestore, EU multi-region eur3), API servers (Cloud Run, europe-west1, Belgium), website hosting (Firebase Hosting), sign-in for the apps and for our administrators (Firebase Authentication, US data centres), push messaging (Firebase Cloud Messaging, if you allow notifications), app integrity checks (Firebase App Check), crash reports (Firebase Crashlytics, iOS and Android release builds), logs and backups.
  • Anthropic (Anthropic, PBC and its affiliates, USA): NutriBot AI, that is photo recognition, dish estimates, assistant answers and recipes (section 3.4).
  • Adapty Tech Inc. (USA): subscription management for App Store and Google Play purchases.

5.2 Independent controllers

  • Apple (Apple Distribution International Ltd. for customers in the EU, Apple Inc. elsewhere): App Store purchases, refunds, Sign in with Apple, App Attest, the App Store rating sheet and delivery of push notifications. Apple's privacy policy applies to that processing.
  • Google (Google LLC, or Google Ireland Limited for users in the EEA and Switzerland): the Google Sign-In page, if you sign in with Google (section 3.1); and, for the Android app, Google Play (the Google company that sells Google Play purchases in your country): the app download, Google Play purchases and refunds (Google Play Billing) and the Google Play rating sheet. Google's privacy policy applies to that processing.

5.3 Other disclosures

Family members see your display name and daily calorie target, and people who open your family invite link see your display name (section 3.7). People you send a share card link to see that card (section 3.8). Other users may see products and their nutrition values in the community food database, never who contributed them. We may disclose data if the law requires it, or where necessary to protect the rights, safety or property of our users, the public or us. If the Service is ever transferred to another operator, your data would move only under this policy, and we would tell you in advance.

6. Where your data is processed and international transfers

NutriBot is operated from Ukraine. Our main database is stored in the European Union (Google Cloud Firestore, eur3 multi-region), and our API runs in the EU (Cloud Run, europe-west1, Belgium). Some providers process data in other countries:

  • Google (Firebase Authentication, Firebase Cloud Messaging, App Check and Crashlytics; processing in the USA and other countries): Google LLC's certification under the EU–US Data Privacy Framework (including the UK Extension and the Swiss–US framework), and the European Commission's Standard Contractual Clauses (SCCs) in Google's data processing terms.
  • Anthropic (USA and other countries where Anthropic runs its service): SCCs, with the UK and Swiss addenda, in Anthropic's Data Processing Addendum, which forms part of Anthropic's commercial terms.
  • Adapty (USA): SCCs, with the UK International Data Transfer Addendum and the Swiss adaptations, in Adapty's data processing agreement.
  • Apple and Google (for Google Sign-In and Google Play) transfer data under their own policies as independent controllers.

If the EU–US Data Privacy Framework is invalidated, we will rely on SCCs. You can ask for a copy of the relevant safeguards at privacy@nutribot.life.

Ukraine does not have an EU adequacy decision. When we, as the controller, access data from Ukraine, the GDPR continues to apply to that processing in full. Under the Law of Ukraine "On Personal Data Protection", we transfer data only to countries recognised as providing adequate protection under its art. 29 (including EEA states, parties to Council of Europe Convention 108, and states whose securities regulators have signed the IOSCO Multilateral Memorandum of Understanding, such as the USA), or on another basis allowed by that article.

7. How long we keep data

  • Profile, body metrics, diary (including the permanent diary archive), weight history, recent foods, reminders, family membership, product suggestions: until you delete your account. The full diary is kept so monthly and yearly reports work; the last 30 days are also kept in your main profile for speed.
  • Sign-in account (Firebase Authentication, iOS and Android apps): until you delete your account. Google removes it from its systems and backups within about 180 days, and keeps sign-in IP logs for a few weeks.
  • Activity days and daily AI and feature counters: 400 days, then deleted automatically.
  • Setup progress (the step you reached, platform and timestamps): until you delete your account. When you delete your account, this record is kept only in pseudonymised form, under an irreversible salted hash of your account identifier instead of the identifier itself, as for payment records, so that we can keep counting where people stop during setup, and deleted 24 months after the last step was recorded.
  • Crash reports (Firebase Crashlytics): Crashlytics keeps them for 90 days, then deletes them.
  • Payment records and subscription events: for as long as accounting and tax law requires (generally three years after the end of the relevant tax period); after that we delete them or keep them only in anonymised form. When you delete your account, they are kept but anonymised straight away: your account identifier is replaced with an irreversible salted hash and personal notes are removed.
  • Promo code redemptions: anonymised in the same way when you delete your account.
  • Subscription data at Adapty: until you delete your account, when we ask Adapty to delete the profile linked to it. Apple and Google keep their own purchase records under their own policies.
  • Push tokens and device data: until you sign out on that device or delete your account, until the token stops working, or after 60 days in which the app has not registered the device again, whichever comes first.
  • Share card links: they stop working 30 days after you create them. We do not store the images.
  • Recipes shown on your menu: up to 7 days.
  • Community food database contributions: until you delete your account or object (section 10). Product entries without any link to you may remain.
  • Deletion log: a salted hash of your account identifier and the date of deletion, kept to show that your request was fulfilled.
  • Backups: encrypted database backups are kept for up to 7 days (daily) and 14 weeks (weekly). Deleted data disappears from backups when they expire.
  • Technical logs: about 30 days.
  • Photos, AI questions and AI answers: not stored by us. Anthropic deletes API inputs and outputs within 30 days, with the exceptions described in section 3.4.

8. Your choices and controls

In the iOS and Android apps (Settings → Privacy):

  • AI features (NutriBot AI): on or off. It is off until you allow it the first time you use an AI feature.
  • Analytics: on or off. The app does not ask about analytics during sign-up. Analytics is off by default in the EU/EEA, the UK and Switzerland and on by default elsewhere; we detect the region from your device's time zone and language.
  • Marketing: off for everyone unless you switch it on.
  • Download my data; Delete account is under Settings → Account (section 9).

When analytics is off, we do not record your activity days, platform, country, acquisition source or setup progress, and your actions are not counted in feature statistics. Notifications can be turned off in the app or in your device settings at any time.

9. Deleting your account and downloading your data

Delete account. You can delete your account at any time: in the iOS or Android app in Settings → Account → Delete account, or by writing to privacy@nutribot.life (we may ask you to confirm that the account is yours). Deletion is immediate and irreversible. It removes your profile and all body metrics, your diary and its archive, weight and food history, reminders, push tokens and device data, product suggestions, AI usage counters, activity marks, your samples in the community food database, and your family membership (if you owned a family, ownership passes to the longest-standing member; a family with no other members is dissolved). It also deletes your sign-in account from Firebase Authentication and your subscription profile at Adapty, and in the iOS app it revokes your Sign in with Apple authorisation. Payment, subscription and promo records are kept only in anonymised form, as accounting law requires (section 7). The record of the setup step you reached (section 3.5) is kept only in pseudonymised form, under an irreversible salted hash of your account identifier. Share card links you have already sent keep working until they expire (at most 30 days), because the card's content is inside the link.

Subscriptions are not cancelled by deletion. Deleting your account, or deleting the app from your device, does not cancel an App Store or Google Play subscription, and Apple or Google will keep charging it until you cancel. Cancel it first: an App Store subscription in your Apple ID settings (on iPhone: Settings → your name → Subscriptions), a Google Play subscription in Google Play (the Google Play app → your profile icon → Payments & subscriptions → Subscriptions). The app reminds you of this before you confirm the deletion.

Deleting the app is not deleting the account. If you only remove the app from your device, your account and data stay with us until you delete the account as described above.

Download my data. In Settings → Privacy → Download my data you get a JSON file with the data we hold about you in NutriBot: profile, consents, diary and archive, weight and measurements, recent foods, reminders and registered devices, family, product suggestions, payments, promo redemptions, community contributions and activity days. In the apps you can save or share the file. Up to 3 exports per day.

10. Your rights

Depending on where you live (in particular under the GDPR, the UK GDPR and the Law of Ukraine "On Personal Data Protection"), you have the right to:

  • access your data and get a copy;
  • receive your data in a portable, machine-readable format (the JSON export);
  • correct inaccurate data (most data can be edited in the app);
  • have your data erased;
  • restrict processing;
  • object to processing (see below);
  • withdraw consent at any time;
  • complain to a supervisory authority.

Right to object. Where we rely on legitimate interests (analytics outside the EU/EEA, the UK and Switzerland, crash reports, security, or the community food database), you may object at any time on grounds relating to your situation. For analytics, simply switch it off in Settings → Privacy. For crash reports, write to privacy@nutribot.life. For the community food database, write to privacy@nutribot.life: we will erase your contributions and stop adding new ones.

Withdrawing consent.

  • Analytics and marketing: switch them off in Settings → Privacy.
  • NutriBot AI: switch off AI features in Settings → Privacy.
  • Notifications: in the app or in your device settings.
  • Health data: this consent is a condition of the Service, so you withdraw it by deleting your account (section 9).

Withdrawal does not affect processing that took place before it.

How to exercise your rights. Use the in-app tools, or write to privacy@nutribot.life (or to our EU or UK representative once appointed). Requests are free. We reply within one month; for complex requests we may extend this by two more months and will tell you within the first month. We may need to confirm that the request comes from you.

If you live in a US state with a consumer privacy law, you may have similar rights; write to privacy@nutribot.life. We do not sell or "share" personal information for cross-context behavioural advertising, and we will not discriminate against you for exercising your rights.

Complaints. Please contact us first; we acknowledge complaints within 30 days. You may also complain to a supervisory authority:

  • EU/EEA: the data protection authority of the country where you live or work, or where the issue arose (list of EU authorities). We have no lead supervisory authority in the EU.
  • United Kingdom: the Information Commissioner's Office (ico.org.uk).
  • Switzerland: the Federal Data Protection and Information Commissioner (edoeb.admin.ch).
  • Ukraine: the Ukrainian Parliament Commissioner for Human Rights (ombudsman.gov.ua), or a court.

11. Additional information for users in Ukraine

Under the Law of Ukraine "On Personal Data Protection", the owner (володілець) of your personal data is Serhii Molodets, Ukraine (contact: privacy@nutribot.life; postal address on request). Your data is stored in the database described in section 6, and the recipients are listed in section 5. Under art. 8 of that Law you have the right, among others: to know the sources of collection, the location of your data, the purpose of processing and the location of the owner; to know who receives your data; to access your data and get an answer within 30 calendar days; to make a reasoned objection to processing; to demand correction or destruction of data that is unlawful or inaccurate; to withdraw consent; to know how automatic processing works and to be protected from automated decisions with legal effect; and to complain to the Ukrainian Parliament Commissioner for Human Rights or to a court. We process data concerning your health only with your unambiguous consent (art. 7).

12. Security

Data is encrypted in transit (HTTPS) and at rest (Google Cloud). Requests from the apps are verified with a Firebase Authentication ID token, and requests from the iOS app are also checked with Firebase App Check (App Attest). Access to production data is limited to authorised administrators who sign in with allow-listed Google accounts (the admin panel). No method of transmission or storage is completely secure, but we work to protect your data and will notify you and the authorities of a personal data breach where the law requires.

13. Changes to this policy

When we change this policy materially, we update the version and effective date and ask you to review and accept the new version in the app. If we want to use your data for a new purpose that needs your consent, or to send it to a new AI provider, we will tell you first and, where needed, ask for your consent. The current version is always available at nutribot.life/privacy.

14. Language versions

This policy is available in English and Ukrainian, and both versions are intended to say the same thing. If they differ, the Ukrainian version prevails for users in Ukraine and the English version prevails for everyone else.

15. Contact

Serhii Molodets, Ukraine (postal address on request) · Privacy: privacy@nutribot.life · Support: support@nutribot.life · nutribot.life