Privacy Policy

Summary

Your journal content — day notes, food items, saved meals, goals — is processed and stored only on your device. There are no accounts, no developer-operated servers, no email marketing, and no payments.

The app does use third-party services from Google for ads and app diagnostics, which collect limited technical and device data as described below:

• Google Mobile Ads (AdMob): shows the banner ad at the bottom of the day screen.
• Firebase Analytics: measures aggregate app usage.
• Firebase Crashlytics: collects crash reports.
• Firebase Performance Monitoring: collects app performance metrics.

The developer does not operate a server that receives, stores, or sells any of this data.

Information stored on your device only

Everything you enter stays in local storage on your device:

• Day notes / entries (free-text descriptions of what you ate)
• Extracted food items with calories, protein, carbs, and fat
• Saved meals (up to 30), daily goals, and day totals
• App settings, such as your selected AI model and downloaded-model list
• Downloaded on-device AI model files

Uninstalling the app, or clearing its app data, deletes this local data. Deleting an entry or day inside the app deletes it from your device immediately.

We cannot see, retrieve, or delete this data for you, because we have no access to your device. Your journal content is never sent to Google or to any analytics service — those services receive only the technical data described in the next section.

Information collected by third-party services (Google)

The app integrates Google Mobile Ads and Firebase. These services communicate directly with Google's servers and collect data under Google's Privacy Policy. The developer has no server-side access to this data. What each service collects:

• AdMob (banner ads): device information, operating system, app identifier, IP address (used to infer approximate location), advertising identifier (subject to your OS-level consent), ad interactions (impressions, clicks), and diagnostic data. This is used to serve, measure, and — where you've consented — personalize ads. See How Google uses information from apps that use Google services and What data the Google Mobile Ads SDK collects.
• Firebase Analytics: app usage events (e.g. app open, session data), device model and OS, app version, an app instance identifier, and approximate IP-based location. Used for anonymous usage statistics, not to identify you.
• Firebase Crashlytics: crash reports including stack traces, device state at the time of the crash (device model, OS version, available memory/disk, orientation), and recent in-app log breadcrumbs. The app does not attach your identity to crash reports. See Firebase data collection and privacy.
• Firebase Performance Monitoring: app startup time, screen rendering data, network request metrics (not journal content), and device attributes. See Firebase data collection and privacy.

Your controls:

• Ad personalization: manage via your device's Google ad settings (Android: Settings → Privacy → Ads) and Apple's tracking controls (iOS: Settings → Privacy & Security → Tracking). On iOS, the app may ask for tracking permission (App Tracking Transparency); if you decline, ads are served without personalized tracking.
• Analytics / diagnostics: collection is on by default, and there is currently no in-app toggle. Uninstalling the app stops all future collection. Requests about data Google holds are handled under Google's policy linked above — the developer cannot access or delete it for you.

Information we collect

The developer does not collect, store on a server, sell, or share any personal information.

In particular, the developer does not collect or have access to:

• Name, email address, phone number, or postal address
• Account credentials or social media profile data
• Precise location (GPS), contacts, photos/camera, or microphone
• Payment information

Device identifiers, usage events, crash reports, and performance metrics go to Google under the disclosures above — never to a developer-operated server.

On-device processing

Nutrition extraction runs using an on-device AI model. Your food text is processed locally on your device and is never sent to the developer or to an external AI service for processing.

Network use

The app works offline after setup, except for these cases:

• Ads and diagnostics: the Google services listed above communicate with Google servers as described.
• Model download: when you choose an AI model, the app downloads the model files over a secure (HTTPS) connection. A standard download reveals routine technical data (such as IP address and requested file) to the file host, as with any download. No journal content, identifiers, or account data are included in that request.

There is no login, sync, backup, newsletter, remarketing pixel, CAPTCHA, or payment processor in the current version of the app.

Permissions

The current version does not request location, contacts, camera, microphone, photo library, or notifications access.

On iOS, the system may show an App Tracking Transparency prompt for personalized ads (see "Your controls" above). If the OS shows a generic network or storage permission when downloading models or installing the app, that is handled by the OS and app store; the developer receives no data from it.

Children

The app is a general-purpose food journal and is not directed at children under 13. The developer knowingly collects nothing from anyone on any server. However, the Google ad and analytics services described above do collect device-level data as stated in Google's policy; parents who do not want this should not install the app, or should uninstall it. Local journal data can be deleted at any time by deleting entries, clearing app data, or uninstalling.

Your rights (GDPR / CCPA-CPRA / CalOPPA / Kazakhstan law)

Because the developer holds no personal data about you on any server, there is nothing to access, correct, export, or delete server-side.

• GDPR (EU/EEA/UK), CCPA as amended by CPRA, and CalOPPA (California): you control your journal data directly on your device. To access or delete it, review or delete entries in the app, clear app data, or uninstall. If you email a rights request to dd01x3@gmail.com, we will confirm that we hold no server-side data about you. For data held by Google (ads, analytics, crash, performance), exercise your rights via Google's privacy controls linked above. The developer does not sell personal information; ad personalization by Google is governed by your consent choices described in "Your controls."
• Kazakhstan: the developer processes no personal data on a server and therefore undertakes no cross-border transfer or third-party sharing of its own. Google's transfers are governed by Google's policy above. Local on-device storage is solely under your control.
• Do Not Track: the developer operates no tracking of its own; platform-level signals are handled by your OS and by Google per the policies above.

If a future version adds accounts, sync, or payments, this policy will be updated before that version is released.

Data security

Local data is protected by your device's operating system (app sandbox, device lock, encryption where your OS provides it). No method is 100% secure if the device itself is compromised, rooted, unlocked, or shared. Use a device passcode and keep your OS updated to protect your journal.

Third parties

No third party receives your journal content. The only third-party data recipients are Google (ads, analytics, crash reports, and performance metrics as detailed above) and the model file host during model downloads.

Changes to this policy

Material changes will be reflected in an updated effective date in the app's store listing. Continued use after an update constitutes acceptance. For questions, contact dd01x3@gmail.com.

Contact

For privacy questions or rights requests: dd01x3@gmail.com