Last updated: 2026-07-04.
Nibble is a calorie and food diary that runs entirely in your web browser. This policy explains, in plain language, exactly what happens to your data. The short version: your diary never leaves your device, and we have no way to see it.
What Nibble stores, and where
Everything you enter — the foods and amounts you log, your exercise, your body weight, and your calorie goal — is saved in your browser's local storage on the device you're using. It is stored only on that device. We operate no accounts and no database of users, so there is no copy of your diary on any server we run — there is nothing for us to see, lose, or hand over.
Your data stays until you remove it. You can delete all of it at any time from Settings → Erase all my data, or by clearing your browser's site data for this site. Uninstalling / clearing the browser also removes it.
The one thing that leaves your device
When you search for a food or scan/enter a barcode, Nibble sends that search text or barcode number directly from your browser to Open Food Facts, a free, open, public food database, in order to look up nutrition information. This is an anonymous, read-only lookup — it requires no Open Food Facts account and we never log in to one. For that single request, Open Food Facts's servers receive the barcode or search term and your device's IP address (as with any website you visit). We are not in the middle of that request and never receive it. Open Food Facts is an independent project with its own privacy policy and terms; we only send the minimum needed to look up a product, and only when you ask for a lookup.
Nibble never sends your diary entries, weight, goal, or exercise anywhere — those are used only to draw your own totals on your own screen.
No tracking, no ads, no analytics
Nibble contains no analytics, no advertising, no cookies for tracking, and no third-party code that phones home. The one piece of outside code is an open-source barcode decoder (ZXing) that we host on this site and that only loads if your browser can't scan barcodes on its own — it runs entirely on your device and makes no network requests of its own. The page enforces all of this at the network layer: a Content-Security-Policy restricts outbound connections to this site and Open Food Facts only — nothing else can be contacted, by design, so no script on the page (ours or the decoder) can send your diary anywhere.
Offline caching
Nibble uses a service worker to cache its own program files (the HTML, styles, and scripts) so it can load quickly and work offline. That cache holds only the app itself — it never stores your diary entries or any food-lookup responses.
Your rights
Because your data lives only on your device and we hold no copy, you are in direct control of it: you can view it (it's your diary), export a full copy as a JSON file (Settings → Export my data), and erase all of it (Settings → Erase all my data) at any moment, without asking us. If EU data-protection law applies to your use, the practical effect of this architecture is that the rights of access, portability, and erasure are satisfied directly in the app.
Children
Nibble is a general-purpose tool and is not directed at children.
Contact
Questions about this policy can be raised via the project's support channel linked from the app. Because we hold no personal data about you, there is no account to recover and nothing for us to delete on your behalf — the erase button does it.