Home › Our promise
Our promise
What leaves your phone, written down in full.
Everyone promises “privacy”. Almost nobody publishes the detail. Here is ours: what we refuse to do, then the complete table of what leaves the device — which action, which data, to whom, when. Including the cases where something really does leave.
Radish is a nutrition tracker, and a macro tracker for anyone following protein, carbs and fat. Calling it privacy friendly only means something if the detail is published, so here is the detail: there is no account needed to open the app, and the food diary app writes your entries on the device rather than on a server of ours. It is a free nutrition app in that same checkable sense — a calorie counter without subscription for the log, the search and the scan — while an optional Premium subscription, listed on the download page, funds what sits beyond them.
What we refuse
Six things Radish does not do
A promise is judged better by what it rules out than by what it announces. These six refusals are architectural choices: they do not depend on a setting you would have to hunt for in a menu.
-
No account
No sign-up, no password. You open the app and log your first meal.
-
No email
We never ask for an address. So there is no list to end up on, and no follow-up emails to put up with.
-
No advertising tracker
No ad-network SDK, no advertising identifier read, no advert displayed.
-
No data resale
Your food diary is not sold, rented or handed to anyone — not raw, not “aggregated”, not “anonymised”.
-
No shared profile
Weight, goals, slip-ups: none of it forms a profile a third party can look up. There is no account to share.
-
No social ranking
No leaderboard, no friends, no public streak to keep up in front of others. You measure yourself against your own markers only.
The full detail
What leaves, and what does not
Two Radish features need the network. We would rather write them down here than let you find out later. Read the table row by row: for each action in the app, what leaves the device, to whom, and when. Anonymised usage statistics are also sent to Google (in the EU, only if you agree); your diary, foods and weight never are.
| Action in the app | What leaves the phone | To whom | When |
|---|---|---|---|
| Counting, logging, building recipes, reading the Nutri-Score | Nothing | Nobody | Never |
| Meal planner, protein tracker, water tracker, weekly report | Nothing | Nobody | Never |
| Scanning a barcode the app already knows | Nothing | Nobody | Never |
| Scanning an unknown barcode | The barcode, on its own | Open Food Facts | On that one scan |
| AI “describe a meal” or photo (optional) | The text or the photo of the meal | The AI provider | Each time you use it, on your action |
| Purchase or subscription | The transaction | Apple, Google, and our subscription processor (RevenueCat) | At the time of purchase |
| Anonymised usage statistics: opening the app, finishing setup, seeing the subscription screen | A screen-name event, a day counter since install, and technical device info (model, app version) | Google (Firebase Analytics) | In the EU/UK/Switzerland: only after your consent. Elsewhere: automatically, from install — switch it off in Settings > Data & privacy |
| Account, email, advertising identifier | Does not exist in the app | Nobody | Not applicable |
Three of the rows marked “↗” only ever fire on an action of yours: scanning a product the app does not know, asking the AI to read a meal, or making a purchase. The fourth — Google Firebase audience measurement — fires automatically from install, except in the EU, UK and Switzerland, where it waits for your consent first; either way, you can switch it off in Settings > Data & privacy. None of these rows send a food, weight, calorie or photo. The AI is optional and can be switched off. The detail, provider by provider, is in the privacy policy. Our nutrition figures are sourced from public databases: see the data sources page. This table is about the app. The website you're reading right now (nutri-track.fr) measures its own audience separately (page views, download clicks) via Google Analytics, under the same prior-consent principle in Europe; details in the privacy policy, “Website audience measurement” section.
How we make a living
The business model, in plain words
Our model is the subscription — not your data.
The core of the app is free: diary, scanner, Nutri-Score, macros, micronutrients, recipes, with no meal limit and no adverts. What pays for development is the Premium subscription (AI included, long-term trends, CSV export) and a one-off plan where the AI runs on your own key. Nothing else.
That sentence has a direct consequence for the table above: we have no economic interest in collecting your diary, so we never built the account, the server or the tracker that would make it possible. A full backup of your data, re-importable into the app, stays free: the subscription sells convenience, never the way out.
Put us to the test
The aeroplane-mode test
A promise you cannot prove wrong is worth nothing. This one takes thirty seconds to test, without taking our word for it.
Thirty seconds, your phone, no tools
- Turn on aeroplane mode. Switch Wi-Fi off too, if it stays on.
- Open Radish and log a meal: search for a food, set the portion, save it.
- Build a recipe from two or three ingredients, and look at its total.
- Read the Nutri-Score and the micronutrients of foods in the built-in database.
- Then try what is meant to fail: scan a product the app does not know, or ask the AI to read a meal. Those two stop, because they need the network.
If step 5 worked without a connection, our table would be wrong. If you ever catch it out, write to us: we will fix the page, not the wording.
The other half of the promise
A figure you can trace back
Privacy is one half. The other is that the numbers themselves can be checked, which is why every food carrying sourced nutrition data in the app names the table it came from and its record number inside it.
Those cited sources are not a badge we award ourselves: they point to an official food table anyone can open — CIQUAL, published by ANSES, and USDA FoodData Central where CIQUAL has no entry. Where neither holds a value, the app prints “unknown” rather than a figure we made up. The method, and the share still estimated, are on the data sources page.
What next
Read it, then judge
Nothing to create, nothing to hand over. Whether you open it as a plain calorie count or as a macro counter, the same line holds: your data stays on your phone — never sent to our servers (except AI or barcode scanning, if you use them), and whatever does not is listed above, row by row. The full inventory is here: what a calorie tracker with no account keeps on your phone, line by line. You can also start by reading where our figures come from.
Last updated: 30 August 2026. Lire cette page en français