Family Food Diary
Privacy Policy
Last updated: October 24, 2026
1. General
Family Food Diary respects your privacy. The app is designed for nutrition tracking and does not collect personal information for sharing with third parties.
2. Information Stored
Everything you enter yourself: meals, foods and dishes with their nutrients, nutrition statistics, and family member profiles — name, date of birth and personal nutrient targets.
3. Health Data
The app keeps a history of weight and height measurements for each profile, and the date of birth used to pick age-appropriate nutrition targets. This data is kept alongside the rest and is never sent anywhere except the cloud storage you choose.
4. Data Storage
Locally on your device and, if you enable it, in the cloud storage you select — Google Drive or Yandex Disk. The files live in your own account; the developer has no access to them and keeps no copies.
5. Google User Data
If you choose Google Drive as storage, the app requests access to your Google Drive (scope https://www.googleapis.com/auth/drive). Full Drive access is needed so you can pick an existing folder for the diary — including a folder another family member has shared with you — and keep a shared family diary in it.
The app uses this access only to: list folders so you can choose one; create the diary folder and the diary files in it; read and update those files. The app does not read, modify or delete any other files in your Drive.
Data from Google Drive is processed on your device. It is not sold, is not used for advertising or to train AI models, and the developer does not store it. It leaves the device only if you yourself ask a language model assistant for a diet review (section 7): a nutrition summary for the period then goes to the service you chose — directly, or for the App assistant through the developer’s server, which does not store it. The access token is kept in the device secure storage. You can revoke access at any time at myaccount.google.com/permissions.
Family Food Diary's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Apple Health
On iPhone you may optionally sync weight and height with the Health app — it is off by default. Reading and writing happen only when you act, read and write access are granted separately, and both can be revoked in iOS settings. Health data stays on your device and in your cloud: it is not sent to the developer and never enters analytics.
7. AI Assistant
You can ask a language model to review your diet. A request is sent only when you have chosen an assistant and tapped “Analyse my diet”. You can see it beforehand with “Show the request” — exactly that text is sent: profile name, weight, your goal (if you wrote one), nutrient targets, meals by day with times and weights, and what the dishes and foods of the period contain.
App assistant. The request goes to the developer’s server and from there to Ollama, a language model service that produces the answer. The server only passes the request and the answer through: their text is not stored, not written to logs and not used to train models. The server log keeps technical data only: time, request path and response code. Processing on Ollama’s side is governed by its own policy. Servers may be located outside your country. The number of reviews is limited; the counter is kept on your device.
The same assistant can fill in a product’s nutrients by its name. Only the product name and your extra details, if any, are sent — no diary or profile. The server temporarily remembers answers by product name so it does not ask the model about the same product twice; they are not linked to you. The number of fills is limited too.
Your own service. If you connected a service yourself (for example OpenAI, DeepSeek or another from the list) and supplied your own API key, the request goes straight to that service, bypassing the developer. Processing on that side is governed by that service’s own policy. Your API key is kept in the device secure storage and is never sent to the developer.
The “No neural network” review is calculated on your device and sends nothing. Do not use a language model assistant if you would rather not share nutrition data with a third party.
8. Analytics and Crash Reports
The app uses Firebase Analytics and Firebase Crashlytics (Google) — anonymous usage statistics and crash reports: device model, OS and app version, and technical crash details. Your diary, measurements and profile contents are not included in these reports.
9. Third-Party Sharing
The developer does not sell your data and does not store it. It leaves the device in three cases only, each of which you enable yourself: cloud storage, a language model assistant and Apple Health. The recipient is a service you use. The exception is the App assistant: the request passes through the developer’s server to Ollama and is not stored anywhere (section 7).
10. Permissions
Camera — only to scan a barcode on packaging; no images are stored or transmitted. Notifications — meal reminders. Start after reboot — so reminders already scheduled are not lost. Apple Health access — only when sync is enabled. Each permission is requested at the moment the feature needs it, and the app works without any of them.
11. Children’s Data
This is a family app: children’s profiles are created by an adult, who is responsible for the data entered. A child profile is no different from any other — same local storage, same cloud. Children have no separate accounts, and the app does not collect their data on its own.
12. Contact
If you have any questions regarding this Privacy Policy, please contact: