Dinner Diary Privacy Policy

Last updated: September 15, 2026This Privacy Policy explains how Dinner Diary (the “App”) handles information when you install and use the Android application published under the package name com.sluimer.dinnerdiary. If you do not agree with this policy, uninstall the App from your device.---ScopeThis policy applies only to the Dinner Diary Android application and the information stored or processed through the App. It does not cover external websites, recipe sources, advertisements, or any other third-party services you may open outside the App.Information We ProcessDinner Diary operates offline. The App does not require an account, does not include analytics, and does not transmit user-generated content to external servers.- Meal journal content – Meal titles, notes, ratings, tags, instructions, and timestamps are stored in a local Room (SQLite) database on your device.
- Photos – Images captured or imported remain inside the App’s private storage and are never uploaded by the App.
- Preferences. Feature toggles (for example, smart suggestions, cache maintenance reminders, or crash reporting) are stored locally using Android DataStore.
- Crash diagnostics. If you have not disabled crash reporting in Settings, the App uses Firebase Crashlytics (provided by Google) to automatically send anonymised crash reports and ANR (App Not Responding) diagnostics to Google's servers when the App encounters an error. These reports include the stack trace, device model, Android version, and brief breadcrumb logs generated by the App (for example, the action being performed before a crash). No meal content, photos, or personally identifiable information is included in these reports. You can opt out at any time via Settings → Privacy → Crash reports; the preference takes effect immediately and persists across restarts.
- Recipe scraping requests. If you provide a recipe URL and tap “Fetch recipe details,” the App downloads the web page directly so it can auto-fill the form. No content from that page is transmitted to our servers; any data you apply to your dinner entry stays local on your device.
- Handwritten recipe scanning. The App offers two ways to turn a photo of a recipe into a pre-filled form:
- On-device (default). The photo is processed entirely on your device using Google's ML Kit Text Recognition, with no network request of any kind. The photo and the recognised text never leave your device and are not seen by us or any third party.
- AI-powered (opt-in, your own API key). If you choose to enable this in Settings, you provide your own API key for a third-party AI provider Anthropic (Claude), OpenAI (ChatGPT), or Google (Gemini). When you scan a photo with this engine active, the photo is sent directly from your device to the provider you selected, using your own API key and billed to your own account with that provider, not routed through, logged by, or paid for by us. That provider's processing of the photo is governed by its own privacy policy, not this one. Your API key is stored on your device only, encrypted at rest using Android's EncryptedSharedPreferences/Android Keystore, and is never transmitted anywhere except directly to the provider it belongs to as part of a scan request. You can remove a saved key at any time in Settings → Recipe scanning, and the on-device engine remains the default. The AI-powered engine is never used unless you explicitly switch to it and save a key.Permissions- Camera – Requested only when you open the capture dialog. If you deny the permission, the rest of the App remains fully functional, but in-app photo capture is disabled.AdvertisingDinner Diary can display an adaptive banner using Google Mobile Ads (AdMob). When ads are enabled, Google may collect device-level information (for example, Advertising ID, approximate location, IP address, and app usage) to deliver, personalize, and measure ads under Google’s privacy policies. Learn moreHow Information Is Used- Preserve your meal history on-device.
- Display content inside the App, including insights, filters, and photo galleries.
- Show banner ads when AdMob is configured in production builds.
- To receive anonymised crash and ANR diagnostics via Firebase Crashlytics so we can identify and fix stability issues (only when crash reporting is enabled).
- To turn a photographed recipe into a pre-filled form — either entirely on-device (default), or, only if you opt in and supply your own API key, by sending the photo to your chosen third-party AI provider for processing.Dinner Diary does not otherwise use, analyze, or monetize your personal data.Data Sharing and Transfers- User-generated content – Journal entries, notes, and photos are never shared with us or other third parties.
- Advertising – Device-level data processed by AdMob flows directly to Google; no other transfers occur.
- Crash diagnostics. When crash reporting is enabled, anonymised diagnostic data is sent to Firebase Crashlytics and processed by Google according to Google's privacy policy. You can review Firebase's data processing terms here.
- Recipe websites. When you fetch a recipe, your device contacts the site you selected. Dinner Diary does not proxy or log these requests.
- AI-powered recipe scanning (opt-in only). If you enable the AI-powered scan engine and save an API key, photos you scan are sent directly from your device to the AI provider you chose (Anthropic, OpenAI, or Google), using your own key and account. We do not receive, proxy, or log these photos or the provider's responses. Review the relevant provider's own privacy policy for how they handle this data: Anthropic https://www.anthropic.com/legal/privacy, OpenAI https://openai.com/policies/privacy-policy, or Google https://policies.google.com/privacy. This engine is off by default; the on-device engine never sends any data anywhere.Data Retention and Deletion- Meal entries and photos remain on your device until you delete them, clear the App’s data, or uninstall the App.
- Maintenance tools within the App let you prune cached photos or optimize the database.
- Uninstalling Dinner Diary removes the local database and photo cache.SecurityBecause all content is stored locally, the security of your device is essential. Enable a device lock, keep your operating system up to date, and avoid installing the App on shared or unsecured devices. The App uses standard Android storage directories and does not create network copies of your information, with the sole exception of photos you deliberately scan using the opt-in AI-powered recipe scanning engine (see Section 2), which are sent only to the third-party AI provider you selected. If you use that engine, any API key you enter is encrypted at rest on your device and is never included in backups, logs, or crash reports.Children’s PrivacyDinner Diary targets a general audience and does not knowingly collect information from children under 13. If you intend to distribute the App to child-directed audiences, ensure compliance with Google Play Families policies and disable personalized ads in AdMob.International ConsiderationsSince Dinner Diary does not transmit personal data to us, requests under laws such as GDPR or CCPA generally do not apply. You can manage or delete your data directly on your device through the App or by uninstalling it.Updates to This PolicyWe may revise this policy to reflect product, legal, or regulatory changes. The “Last updated” date above indicates the most recent revision. Continued use of the App after updates constitutes acceptance of the revised policy.