Our "Promise" page didn't mention Firebase Analytics: what we fixed on 08/30/2026
In short
On August 30, 2026, an internal review found that our "Our Promise" page described opening the app as sending nothing off the phone, while our privacy policy had disclosed, since August 28, our Google Firebase Analytics audience measurement, active in the app since August 27. Both pages were corrected the same day the gap was found: the measurement is now named on the public page, with what it sends and how to turn it off.
We usually write about what our nutrition data says, and where it comes from. This time, the subject is one of our own pages that didn't say the whole story — and how we found that, then fixed it. No self-praise here: a documented public inconsistency, with dates and the exact content of the fix.
What happened
On August 27, 2026, Google Firebase Analytics audience measurement was turned on in the native app, to understand overall usage (which screens are seen, which features are used) and improve it. On August 28, that measurement was disclosed in detail in our privacy policy: which events are sent, to whom, under which legal basis, and how to turn it off.
What the privacy policy said wasn't carried over to the "Our Promise" page, which publicly summarizes — in a table — everything that leaves the phone. That page still showed "Nothing / Nobody / Never" for opening the app. Two documents, two different pictures of the same thing.
How we found it
Since August 29, that page's SEO has specifically targeted privacy-related searches, which made the gap more visible during an internal review of the page. The check consisted of comparing, line by line, what legal.html discloses against what promesse.html summarizes. That's where the missing line showed up.
What was fixed, the same day
- promesse.html / promesse-en.html: a row was added to the "what leaves your phone" table, with four columns — the action (opening the app, finishing setup, viewing the paywall screen), what's sent (a screen name seen, days since install, device model and app version), the recipient (Google Firebase Analytics), and the timing (prior consent in the EU/UK/Switzerland, automatic elsewhere, opt-out either way in Settings).
- faq.html: the claim "no advertising tracker" was clarified and links to the privacy policy for detail.
- index.html: "no account or tracker" became "no account or advertising tracker" — a distinction that matters since the audience measurement does exist.
- legal.html: a mention of "crash reports" was also removed, because that tool (Crashlytics) isn't installed — an over-statement corrected in the same pass as the under-statement.
What Firebase Analytics actually sends
Once active, the measurement sends technical usage counters: app opens, session starts, screens viewed, session length, version updates — technically app_open, onboarding_complete, paywall_view, purchase_attempt, plus the events Firebase auto-collects as soon as its SDK is integrated (session_start, screen_view, user_engagement). It also includes device model, app version, and a technical identifier Google generates to link these counters together.
It never sends a food, weight, calorie, photo, or profile record, and no advertising identifier (IDFA / Google advertising ID): that collection is disabled in our configuration. In the European Union, the UK, Switzerland, Norway, Iceland and Liechtenstein, the measurement waits for explicit consent before starting; everywhere else, it starts automatically at install. Either way, it can be switched off in Settings > Data & privacy. The full detail, provider by provider with retention periods, is in the privacy policy.
See everything that leaves your phoneThe full table, line by line, on the Our Promise page.Read the Our Promise page →Why we're documenting this publicly
A privacy policy that aims to be accurate has to stay accurate as the app changes, not just at the moment it's written. Here, one internal document (the detailed privacy policy) was up to date, but the public summary for visitors hadn't caught up yet. It's a mechanism this site has run into before, on a different claim (a wording about offline operation, removed in August 2026 after review): two pages describing the same reality can drift apart if one is updated without the other. The fix, going forward, is the check we now apply: any new measurement or data flow has to be reflected in both the detailed privacy policy and the public summary, the same day.
General information about how the site and app work, not legal advice. Accurate as of August 30, 2026.
Frequently asked questions
What exactly changed on August 30, 2026?
The "Our Promise" page (promesse.html) was updated to mention the Google Firebase Analytics audience measurement, already disclosed since August 28 in the privacy policy but missing from the public summary. The FAQ and homepage were also clarified on this point.
Does Firebase Analytics collect my food, weight, or photos?
No. This measurement sends only technical usage counters (screens seen, sessions, app version, device model) — never a record from your food log or your profile.
How do I turn this measurement off?
In the app, Settings > Data & privacy. It stops immediately, though it can't undo what was already sent before.
Where can I find the full detail, provider by provider?
In our privacy policy, "Google Firebase audience measurement" section, and in the table on the Our Promise page.
The takeaway: an audience measurement disclosed in one document wasn't yet reflected in another. The gap was found and fixed the same day, with the detail of what changed. The full table lives on the Our Promise page.
General information about how the site and app work, not legal advice.
Ready to try Radish?Private calorie counter, official Nutri-Score, no ads. Free.Get Radish →Prefer the app installed? Get Radish on iPhone or Android →