Home › Privacy & Terms
Document
Privacy & terms.
Radish is designed to collect as little data as possible. Here is, plainly, what is processed and by whom.
Privacy Policy: last updated 12/10/2026. Terms of Use: last updated June 2026.
Contents
What this document covers
- P1Your food log, profile, weight
- P2Health connection (optional)
- P3Purchases and subscriptions
- P4AI feature (optional)
- P5Barcode scanning
- P6Usage statistics (optional)
- P6bGoogle Firebase audience measurement (depends on your country)
- P6cnutri-track.fr website audience measurement (depends on your country)
- P6dGoogle Firebase Crashlytics crash reports (depends on your country)
- P7What we don't do
- P8Your rights
- T0Terms of Use (1 to 8)
Privacy Policy
Your food log, profile, weight, and goals
This data is never sent to our servers, except in two cases that you trigger yourself and that are described below: the AI feature (the meal text or photo you choose to have analysed) and barcode scanning (the product code). Outside those two cases, we never receive your diary and never pass it to anyone. If you uninstall the app, everything is deleted from the device. A backup of your phone (iCloud on iPhone), managed by Apple, may keep a copy; delete it from your phone's settings. A plain-language summary of the same rules is here: what a calorie tracker with no account keeps on your phone.
Technical error log: the app keeps in its data the last 50 operating errors (date, version, error type, file and line of code, beginning of the error message, e-mail addresses masked). This beginning of the message may, rarely, contain an excerpt of data the app was processing. It is never sent automatically to Radish: only you decide whether to share it, copy it or delete it (Settings › Help).
Your messages (feedback form and the “What’s missing in Radish?” question) — added in version 7.77, November 2026: the app may ask you once, on the 3rd day you log a meal, “What’s missing in Radish?” (asked one more time later if you answer “Later”). Answering is optional. If you choose to send, just like the feedback form in Settings, the app transmits nothing itself: it opens your own email app with a pre-filled message that you can read, edit or not send. That message contains the text you wrote (and, for the Settings form, the rating and category you chose), the app version, its language and the technical description of your device and browser (“user-agent”); by sending it, you also give us your email address. It arrives in our mailbox, hosted by Google (Gmail). Do not include medical information (illness, treatment, test results): this is not a health-monitoring channel. If a message contains any anyway, we do not use it and we delete it as soon as we have replied. Purpose: improving the app and replying to you. Legal basis: our legitimate interest in improving the app and replying to the messages you send us (Art. 6(1)(f) GDPR). Retention: as long as needed to reply and take it into account, and no longer than 3 years after our last exchange; deleted earlier on request (see “Your rights”). Your answer to the question (sent, later, no thanks) may be counted by the audience measurement described below, never the text.
Health connection (Apple Health / Google Health Connect) — optional
If you enable the health connection, Radish only reads your daily step count from Apple Health (iOS) or Google Health Connect (Android), in read-only mode. Radish never writes data to Apple Health or Health Connect, and never shares this information with any third party — including us: it is never sent to our servers, like the rest of your diary, and it is used neither by the AI feature nor by barcode scanning. You can revoke this permission at any time in your phone's health settings.
Purchases and subscriptions
Subscription management is handled by our processor RevenueCat, which receives a pseudonymous identifier and your purchase history (needed to activate your paid features), and, in the cases described below, the source of your installation and the Google Firebase measurement identifier. No email, no name, and no data from your food log is shared with it.
Install source sent to RevenueCat (added 12/10/2026): on Android, if usage statistics are on (in the EU: only if you accepted them), Radish also sends RevenueCat the source of your installation (source, medium, campaign of the link or ad that brought you to Radish), linked to your pseudonymous ID, to learn which campaigns lead to a subscription. If you decline or turn off these statistics, it is not sent and the copy kept on your phone is erased.
Purchase events sent by RevenueCat to Google Analytics (added 14/11/2026): on Android and iOS, if Firebase audience measurement is on (in the European Union and equivalent countries: only if you accepted it; elsewhere: unless you turned it off, see "Google Firebase audience measurement"), Radish sends RevenueCat the technical identifier Firebase assigned to your installation. RevenueCat then sends your subscription events directly to Google Analytics (Google Ireland Limited / Google LLC): trial start, purchase, renewal, cancellation, expiration, billing issue, plan change, with their amount and currency. Purpose: to measure which paths in the app lead to a subscription and how many subscribers stay. Legal basis: the same as for Firebase measurement (your consent in the European Union, GDPR art. 6.1.a; our legitimate interest elsewhere, art. 6.1.f). No advertising identifier, no name, no email and no data from your food log is sent. This identifier is never sent from the team's test devices. If you decline or turn off the measurement, the identifier is erased at RevenueCat and your later purchases are no longer sent to Google; what was already sent remains subject to the Google Analytics retention period stated in the Firebase section.
AI feature (optional)
Radish offers two ways to use AI to estimate a complex meal. Neither is enabled by default.
- Hosted Premium AI: the text of your meal — or the photo you choose to have analyzed, and nothing else from your log — is sent to our server function (hosted by Netlify, Inc., United States), which immediately relays it to Anthropic (United States), the provider of the AI model used, after your explicit consent given on a dedicated screen. Our server function does not retain the text or photo: it forwards it and erases it from memory right after the request. This content is deleted by Anthropic within 30 days maximum, except where required by law or to detect misuse of its service. This transfer outside the European Union is governed by the European Commission's Standard Contractual Clauses. To enforce your monthly call quota, a counter — your pseudonymous subscription identifier linked to the current month, nothing else — is also kept by our host Netlify, Inc. (United States), under the same transfer safeguards described in the "Usage statistics" section below. Purpose: to enforce this quota and prevent abuse; legal basis: performance of the service you subscribed to (Art. 6(1)(b) GDPR). A very short copy of your subscription's validity (same identifier, with its end-of-validity date, valid for 10 minutes at most) is also kept there to avoid re-checking it on every call. Retention: the quota counter is kept for 13 months at most and the subscription-validity copy for 24 hours at most; their automatic deletion is being put in place and, until it is active, they are erased on simple request (see "Your rights").
- Pro AI (your own API key): your meal text, or the photo you have analyzed, is sent directly from your device to the provider (Anthropic, OpenAI or Google) you choose. It never passes through a Radish server. Your API key is only ever sent to the provider you chose, never to us.
Barcode scanning
Barcode scanning: the code of the scanned product is sent to the open Open Food Facts database, made available under the Open Database License (ODbL), to retrieve its nutritional information. No other data from your profile is associated with it.
Usage statistics (optional) — added 26/08/2026
Purpose: measuring where people drop off between opening the app and a purchase, so we can fix what is blocking them. Legal basis: your consent (GDPR art. 6.1.a) — a screen asks you explicitly, with two equally-weighted buttons, no pre-ticked box; the default is NO. What is sent, only if you accept: usage counters — which screens are seen, how long the first entry takes, which features are used — never a food, never a weight, never a calorie, never a photo, never your profile. A random technical identifier is created when you consent, to link these counters together over time; this is not anonymous data in the strict sense (it is pseudonymisation), but it is never linked to your identity, to an account (Radish has none), or to an advertising identifier. Processor: these counters are stored with our host Netlify, Inc. (United States — functions hosted in Ohio by default), our processor, and no other third party. This transfer outside the European Union is governed by Netlify's certification under the EU-U.S. Data Privacy Framework, with the European Commission's Standard Contractual Clauses as a fallback mechanism. Retention: a rolling 90 days. Withdrawal: any time in Settings > Data & privacy — the identifier is then destroyed immediately, not put to sleep. Your access and erasure rights: since Radish has no account, show the technical code displayed in Settings > Data & privacy in your request to bonjour@nutri-track.fr, so we can identify and erase what concerns you.
Google Firebase audience measurement (depends on your country) — added 27/08/2026, corrected 30/08/2026
Purpose: measuring overall app usage (screens seen, features used, crashes) to improve it, via Google Firebase Analytics, provided by Google. What changes depending on where you are: if you are in the European Union (or Switzerland, the United Kingdom, Norway, Iceland, or Liechtenstein), this measurement only starts after your explicit agreement, given on the same screen as the usage statistics described above — until you accept, nothing is sent to Google. Legal basis in that case: your consent (GDPR art. 6.1.a). Everywhere else in the world, this measurement starts automatically as soon as you install the app, with no prior consent screen. Legal basis invoked in that case: our legitimate interest in understanding how the app is used, to improve it (GDPR art. 6.1.f) — a qualification we stand behind but which remains a business judgment, not a guarantee against challenge. In both cases, you can turn this measurement off at any time in Settings > Data & privacy; it stops immediately, though this obviously cannot undo what was already sent before you did so. What is sent, once the measurement is active (per the above): technical usage counters — the events Firebase automatically collects as soon as an app uses this service (app opened, session started, screen displayed, session length, version update; technically named first_open, session_start, screen_view, user_engagement, app_update) — as well as device model, app version, and a technical identifier generated by Google to link these counters together, as well as usage indicators computed on your phone: whether you have already logged a meal (yes/no), the age of the installation in ranges (for example “4 to 7 days”), and coming back to the app the next day and on day 7 — never the content of your meals or a date. We also measure how people move through the app, using fixed labels we define: onboarding screens viewed, skipped, left or gone back from, and time spent in ranges (for example "10 to 30 seconds"); opening and closing of the subscription screen and the plan viewed; the outcome of a trial, purchase or restore (successful, cancelled, type of error) and, for a completed purchase, its amount and currency; use of features (search, scan, AI assistant, diary, sharing, settings); the answer to the “What’s missing?” question (sent, later, no thanks — never the text, added in version 7.77); the reason you pick, if you answer, when you leave the add-food screen without logging anything during your first days (food not found, took too long, just looking, other, or closed without answering — never the food searched for nor any text); whether the journal's "next step" card was shown and what you did with it (tapped or closed), added in version 7.77; earning a usage badge (its name, its tier and whether it was awarded for past activity) — never a food, a weight or any data about your body, added in version 7.80. If a technical error occurs in the app (at most 5 per session, added in version 7.76), we also receive a fixed label giving the area concerned (AI assistant, purchase, scan, startup, other) and the kind of error (network, syntax, failed operation, other) — never the error message, the file or the line of code. Never your answers to the onboarding questions, a search term, a barcode, a food, a photo or any text you typed. What is never sent: any advertising identifier (IDFA on iOS, Google advertising ID on Android) — collection of this identifier and advertising personalization ("Google signals") are disabled in our configuration — and any food, weight, calorie, photo, or profile data. Processor: Google Ireland Limited / Google LLC (United States), which receives and processes these counters. This transfer outside the European Union is governed by Google's certification under the EU-U.S. Data Privacy Framework, with the European Commission's Standard Contractual Clauses as a fallback mechanism. Retention: verified on 29/08/2026 in our Firebase configuration (GA4 property #551812482) — 2 months for event data (what happens in the app: screens seen, sessions, etc.) and 14 months for user- and device-level data; this 14-month counter resets on each new user activity for as long as the measurement stays active. Your rights: see "Your rights" below; a request specifically about Google's data can also be sent directly to Google.
Android install source (added 16/09/2026): if you installed the app from the Google Play Store, your device receives the campaign labels that brought you there (source, medium, campaign — not an advertising identifier, not your name, not your email). In the European Union (and the equivalent countries listed above), these three items stay on your device only until you give your consent on the consent screen; they are only sent to Google Analytics after your explicit consent. Legal basis: your consent (GDPR art. 6.1.a). If you decline, these three items are deleted from your phone, not just set aside. Everywhere else in the world, as with the rest of the Firebase measurement described above, this transmission may happen automatically upon installation. For how this source is sent to RevenueCat, see the “Purchases and subscriptions” section.
nutri-track.fr website audience measurement (depends on your country) — added 31/08/2026
The following is about the website you're reading right now (nutri-track.fr), not the app described in the sections above. Purpose: measuring website traffic (pages visited, clicks on App Store / Google Play buttons) to know which pages actually drive downloads, via Google Analytics 4, provided by Google. What changes depending on where you are: if you are in the European Union (or Switzerland, the United Kingdom, Norway, Iceland, or Liechtenstein), this measurement only starts after your explicit agreement, given via the banner shown at the bottom of the screen — until you click "Accept," nothing is sent to Google. Legal basis in that case: your consent (GDPR art. 6.1.a). Everywhere else in the world, this measurement starts automatically when the page loads, with no prior banner. Legal basis invoked in that case: our legitimate interest in understanding which pages of the site work (GDPR art. 6.1.f) — a qualification we stand behind but which remains a business judgment, not a guarantee against challenge. In both cases, you can withdraw your consent by clearing this site's browsing data in your browser. What is sent, once the measurement is active: the page visited, and a technical event when you click a download button (App Store or Google Play, and from which page). IP anonymization is enabled, and Google advertising signals and ad personalization are disabled in our configuration. What is never sent: any advertising identifier, and no data about your use of the app (journal, weight, calories, photos) — this website has no access to that anyway. Processor: Google Ireland Limited / Google LLC (United States). This transfer outside the European Union is governed by Google's certification under the EU-U.S. Data Privacy Framework, with the European Commission's Standard Contractual Clauses as a fallback mechanism. Retention: Google Analytics 4's default, 14 months for user- and device-linked data. Your rights: see "Your rights" below; a request specifically about Google's data can also be sent directly to Google. This measurement is separate from the app's Firebase audience measurement (section P6b): two tools, two separate consents, neither ever triggers the other.
Cookie-free click counter — added 18/09/2026. nutri-track.fr uses an anonymous click counter (page visited, store chosen, day) to measure traffic, with no cookie, no identifier and no stored IP address. This measurement does not require your consent (CNIL recommendation on exempted audience-measurement tools). What is counted: a click on a download button (App Store, Google Play or the "Download" page), with the page it came from and the day — never the time. What is never recorded: your IP address, your browser, the page you came from, and no identifier of any kind; nothing is stored on your device. These totals are processed on our servers (Netlify), shared with no one, and erased after 13 months.
Anonymous app counter — added in version 7.76, November 2026. In the app, an anonymous counter sends a single "first meal logged" signal to our servers. It contains no identifier and no meal content, and your IP address is neither read nor stored: only the day (computed by our servers, never the time), the platform (Android or iOS) and the zone (European Union and the equivalent countries listed above, or rest of the world) are recorded, the zone being derived from the phone's time zone and language, never from the IP address. The totals are used only for our internal statistics, are shared with no one and are deleted after 13 months. This counter is one of the audience-measurement tools exempt from consent (CNIL recommendation): it is therefore sent even if you have not yet answered the usage-statistics question. It is not sent if you have declined or turned off statistics, in that question or in Settings › Data & privacy. Until you have answered, that setting's switch appears off: this means Google Firebase measurement is not active, not that this counter is turned off.
Google Firebase Crashlytics crash reports (depends on your country) — added in version 7.74, November 2026
Purpose: if the app closes unexpectedly, a technical report is sent to Google to help us find and fix the defect, through the Google Firebase Crashlytics service. What is sent: the technical trace of the error in the app's code, the time of the crash, the device model and operating system version and its technical state at the time of the crash, the app version, and technical identifiers generated by Google (an installation identifier and a session identifier) used to count how many devices are affected by the same defect. If the audience measurement described above is active, the report also contains the most recent events from that measurement recorded just before the crash (screens and features used, with the same fixed labels). What is never sent: no food, weight, calorie, health data, photo or text you typed, and no advertising, purchase or account identifier. When it is active: same rules as the audience measurement above. In the European Union and the equivalent countries listed above, nothing is sent without your explicit consent, given on the same screen (legal basis: your consent, Art. 6(1)(a) GDPR); crashes that happened before your consent are deleted from the phone without being sent. Everywhere else, sending is active from installation (legal basis relied on: our legitimate interest in fixing defects in the app, Art. 6(1)(f) GDPR). In all cases, the same switch (Settings › Data & privacy) turns it off: the stop is immediate and pending reports on the phone are deleted, but what has already been sent cannot be recalled. Processor: Google Ireland Limited / Google LLC (United States), with the same safeguards for the transfer outside the European Union as for the audience measurement above. Retention: 90 days, after which Google starts removing the data from its live and backup systems (source: Firebase privacy page, checked on 11/11/2026).
What we don't do
No advertising identifier (IDFA/Google advertising ID) or cross-app tracker actively collected: neither our own usage statistics, nor the Firebase and Google Analytics audience measurements, nor the crash reports above collect them. Your data is never shared with third-party ad networks or sold to data brokers. No advertising, no advertising identifier and no ad personalization.
Your rights — corrected 02/09/2026
Under the GDPR, you have the right to access, correct, erase, object to the processing of, restrict the processing of, and port your data (Art. 15 to 21 GDPR), and to withdraw at any time a consent you have given. Your locally stored data (see the exceptions described above: AI, barcode scanning, audience measurement and crash reports) is never sent to our servers (except for AI and barcode scanning, if you use them), so uninstalling the app erases it from the device. A backup of your phone (iCloud on iPhone), managed by Apple, may keep a copy; delete it from your phone's settings. For the optional usage statistics described above, see the dedicated section. Data controller: the developer of the Radish app, published under the name “Nutri-track” on Google Play; contact: bonjour@nutri-track.fr. For any question or to exercise your rights, write to us at bonjour@nutri-track.fr. Without an account, we cannot find you by name: include in your message the identifier that matches your request — the technical code shown in Settings › Data & privacy (usage statistics), your subscription identifier or purchase receipt (subscription and AI feature), or the email address you wrote to us from (feedback messages). We will never ask you for an ID document. For your local data, self-service is the fastest: Settings › My data › “Export my data” (access and portability, in a readable file) and “Erase my log” (erasure). You can also object to audience measurement or withdraw your consent at any time in Settings › Data & privacy, and ask by email for the processing to be restricted (your data is then frozen while a check is made). We reply within one month (extendable by two months for a complex request, with an explanation). What has already been sent to Google remains subject to Google's retention periods stated above. You also have the right to lodge a complaint with a supervisory authority — in France, the CNIL (www.cnil.fr) — if you believe your data isn't processed in accordance with the GDPR.
Terms of Use
The eight articles
Last updated: June 2026.
-
1
Acceptance
By using Radish, you accept these terms. If you disagree, do not use the app.
-
2
Service provided "as is"
Radish is usable free of charge; some advanced features (including Premium AI) are offered via an optional subscription. The service is provided "as is", with no warranty of being error-free or continuously available.
-
3
Not medical advice
Radish is for informational and educational purposes. Calculations (calories, macros) and nutrition data are estimates and may be inaccurate. The app does not replace advice from a doctor, dietitian, or health professional. Consult a professional before any major dietary change, or in case of illness, pregnancy, or medical treatment.
-
4
Data accuracy
Food and recipe values come from open databases and user input; we do not guarantee their accuracy. Verify important information against the product packaging.
-
5
AI feature & costs
If you use the AI coach with your own key, usage costs are your responsibility and governed by your agreement with the AI provider.
-
6
Liability
To the extent permitted by law, we disclaim liability for direct or indirect damages arising from use of the app, including data loss (remember to export backups regularly).
-
7
Intellectual property
The Radish name, logo, design, and code are protected. Third-party nutrition data remains the property of its respective sources.
Part of the nutrition values comes from the ANSES Ciqual table. Source: ANSES, Ciqual 2025 table, updated 19/11/2025 (DOI 10.57745/RDMHWY), reused under the Licence Ouverte / Open Licence Etalab 2.0. ANSES does not endorse Radish and is in no way associated with this app. Other values come from USDA FoodData Central (public domain, CC0). Other values come from national public tables, reused under their licences: BLS (© Max Rubner-Institut, CC BY 4.0), AUSNUT 2023 (© Food Standards Australia New Zealand, CC BY 4.0), CoFID (Public Health England, Open Government Licence v3.0) and the Canadian Nutrient File (Health Canada, Open Government Licence – Canada). None of these bodies endorses Radish. Details and full notices: Data sources.
-
8
Contact
Questions or reports: bonjour@nutri-track.fr.
Where the numbers come from: Data sources.About Radish