Privacy Policy for Eating30

Last updated: August 6, 2026

This Privacy Policy applies to the Eating30 app on both iOS and Android, and explains how data is handled when you use it. Where the two versions differ, this policy says so.

Overview

Eating30 is designed to work primarily on your device. You do not need to create an Eating30 account to use the app, and we do not operate our own backend servers to store your journal or personal profile data. Most app data is stored locally on your device and, depending on your platform and settings, in your personal Apple iCloud account or your personal Google account backup.

We do not sell your personal data.

Data Stored on Your Device

Eating30 stores most app data locally on your device, including data such as:

  • journal and tracking entries
  • favorites, removed items, custom plants, combos, and custom categories
  • app settings and reminder preferences

If you enable reminders, the app stores your reminder settings locally and may schedule notifications on your device.

Analytics and Crash Reporting

Eating30 uses Firebase Analytics and Firebase Crashlytics, services provided by Google, to understand how the app is used, improve features, and diagnose crashes and stability issues.

Firebase Analytics may process standard technical information about your app and device, and the app also sends usage events that may include, depending on how you use Eating30:

  • screen views, app opens, and notification opens
  • onboarding selections and certain settings choices
  • counts and sources of plant tracking activity
  • plant names you track, suggestion selections, combo names, custom plant names, and custom category names
  • AI Search queries you enter (iOS only)
  • barcode numbers and certain barcode-related metadata, such as product name, brand, ingredient preview, and matched plant results
  • paywall, purchase restore, rating, feedback, export, and reminder-related events

Because Eating30 is a food and habit-tracking app, some analytics values may relate to foods, plants, or preferences you enter into the app.

Firebase Analytics identifies your installation of the app using an app instance identifier, and processes basic device and app information alongside it. On Android, Eating30 explicitly removes the advertising ID permission: the app does not access your device's advertising identifier, and we do not use your data for advertising, ad targeting, or attribution.

Firebase Crashlytics may process crash and diagnostic data such as crash logs, stack traces, device/app information, operating system version, and related technical details needed to investigate problems.

Further information about Firebase privacy and security is available here: https://firebase.google.com/support/privacy

Google's Privacy Policy is available here: https://policies.google.com/privacy

AI Search (iOS only)

AI Search is available only in the iOS version of Eating30. It is not included in the Android app, which has no equivalent feature and sends no search text anywhere.

On iOS, AI Search uses Apple-provided AI features available on supported devices. Based on the current implementation of the app, Eating30 does not use a separate non-Apple cloud AI service operated by us for this feature.

However, the text you enter into AI Search may still be logged to Firebase Analytics as described above for product improvement and feature measurement.

Apple's Privacy Policy is available here: https://www.apple.com/legal/privacy/

Barcode Scanning and Product Lookup

If you choose to use barcode scanning, Eating30 uses your device camera permission to detect a barcode. The detected barcode number is then sent to Open Food Facts to retrieve public product information such as product name, brand, and ingredients.

The app does not send the camera image itself to us for barcode lookup. However, the barcode number and some barcode-related product metadata may be logged to Firebase Analytics as described above.

Payments and Subscriptions

In-app purchases and subscriptions are processed by the store you installed the app from: Apple on iOS, and Google on Android. That store, not NoBigApps, is the merchant of record.

Eating30 uses RevenueCat to manage subscription status, entitlements, restore purchases, and receipt syncing. RevenueCat may process limited transaction-related and technical information needed to provide subscription functionality, such as receipt data, entitlement status, and device/app-related information necessary to verify purchases.

Eating30 does not receive or store your full payment card details.

Further information about RevenueCat's privacy practices can be found here: https://www.revenuecat.com/privacy

Apple may collect data related to in-app purchases in accordance with its own privacy policy: https://www.apple.com/legal/privacy/

Google may collect data related to purchases made through Google Play in accordance with its own privacy policy: https://policies.google.com/privacy

iCloud Sync (iOS)

If you enable iCloud, the iOS version of Eating30 uses Apple's iCloud services, including CloudKit and iCloud Key-Value Storage, to sync app data and certain settings across your devices.

This may include app data such as journal entries, favorites, custom plants and categories, and related records, as well as certain preferences such as week-start settings, category ordering, and tracking preferences.

This synced data is stored in your iCloud account and managed by Apple according to Apple's privacy policies.

Backup (Android)

The Android version of Eating30 does not sync between devices. It does, however, support Android's built-in backup, which is provided and controlled by Google rather than by us.

If backup is enabled in your Android system settings, your device may copy Eating30's app data — including your journal entries, custom plants, combos, categories, and app settings — to your personal Google account, so it can be restored when you reinstall the app or set up a new device.

This backup is stored in your own Google account, not on our servers. We cannot read it. You can turn Android backup off, or delete existing backups, in your device or Google account settings.

Purchases are not part of this backup. Your subscription is tied to the Google account that bought it and is restored through Google Play.

Feedback and Contacting Us

If you choose to send feedback from within the app, the app opens your device's email app and pre-fills a message to us. That draft includes your device model, operating system version, and app version, along with anything else you choose to write. We receive that information only if you choose to send the email.

If you contact us directly by email, we will receive your email address and any information you include in your message.

Data Retention

Data stored locally on your device, in your iCloud account, or in your Google account backup remains there until you delete it, remove the app, or disable the relevant Apple or Google services. Deleting the app does not automatically delete an existing backup; you can remove those from your Apple or Google account settings.

Data processed by third-party providers such as Google, Apple, and RevenueCat is retained according to their own policies.

Changes to This Policy

We may update this Privacy Policy if the app's functionality or data practices change. Any updates will be posted in the app listing, on our website, or wherever this Privacy Policy is made available.

Contact Us

If you have any questions about this Privacy Policy, please contact us at:

Email: [email protected]

Website: https://eating30.app