What we keep
A one-way keyed fingerprint of your random account code, a secure password hash, your food diary, and any foods you contribute.
No fog. No thirteen-page shrug.
Privacy, in plain English
NibbleNote is designed so the service does not need to know who you are.
What we do not ask for
No name, email, phone number, birthday, sex, home address, weight, advertising ID, or social login.
What stays on-device
Your optional daily calorie target is stored in that browser only. It is never sent to the server.
Delete means delete
Delete the account and its diary rows disappear immediately. Shared food facts remain, detached from the account that added them.
Important trade-offs
There is no email recovery because there is no email. Save your account code and passphrase somewhere private; if both are lost, nobody can identify or recover the account.
Food entries are community data. They may be wrong or become outdated as recipes and pack sizes change, so check the packaging—especially when accuracy matters. Reports help an operator review dubious entries.
Normal server access logs may be created by your hosting provider or web server. The application itself does not record IP addresses or browser fingerprints. Configure the server to minimise or promptly rotate access logs if that fits your threat model.
Sharing and selling
NibbleNote contains no advertising, analytics, third-party scripts, or data broker integrations. Never sell or share diary data. If the service ever needs a materially different privacy model, ask people first rather than silently changing the bargain.
Safety
This is a recording tool, not clinical advice. Calorie needs differ from person to person. Tracking is not required for health, and anyone with a medical condition, special diet, or current or past eating disorder should seek appropriate professional guidance.