Privacy Policy

Calorie Log is built as a local-first food and wellness tracker. This policy explains what stays on your device, what data may be shared when you use optional features, how health integrations work, and the controls available to you.

Last Updated: June 10, 2026

🏢 Who We Are

Calorie Log is developed and maintained by Nocturnal Devs.

Nocturnal Devs
Email: nocturnaldevs@gmail.com
Phone: 437 366-2920
Address: 419 Markham Rd. M1J 3E1, Toronto, Ontario, Canada

🔒 Local-First Storage

Calorie Log primarily stores your information on your device. The app does not require a separate account to use core features.

Information stored locally can include:

  • Meals, favorites, notes, tags, and nutrition history
  • Profile data such as weight, height, age, activity level, and goals
  • Meal photos and analysis results saved in the app
  • Health sync settings and local calorie or energy-burn summaries from Apple HealthKit or Android Health Connect when you enable those integrations
  • Theme, barcode, quota, and subscription state used by the app interface
  • JSON backup files that you export or import manually

❤️ Apple HealthKit and Android Health Connect

Health integrations are optional. Calorie Log only accesses Apple HealthKit, Apple Health, or Android Health Connect data after you enable the feature and approve the platform permission request.

  • On iOS, Calorie Log may use HealthKit and Apple Health to read calorie or energy-burn data, such as active energy and resting energy, for burned-calorie and net-calorie summaries.
  • On Android, Calorie Log may use Health Connect to read calorie or energy-burn data needed for burned-calorie and net-calorie summaries. If the app offers a nutrition sync option, it will only write the meal or nutrition data you choose to sync and approve through Health Connect.
  • Calorie Log requests only the health data types needed for the user-facing health and nutrition features you enable.
  • HealthKit and Health Connect data is used only to provide app functionality, such as nutrition, burned-calorie, and net-calorie views.
  • We do not use HealthKit or Health Connect data for advertising, marketing, use-based data mining, sale to data brokers, employment decisions, insurance eligibility, or unauthorized social sharing.
  • We do not send HealthKit or Health Connect data to AI analysis endpoints, analytics providers, or ad networks.
  • You can revoke health permissions at any time in Apple Health, iOS Settings, Android Health Connect, or Android settings. Revoking access stops future syncing, and clearing local app data removes local cached health summaries from that device.

🌐 When Data Leaves Your Device

Some features rely on third-party services. When you use those features, limited data may be sent to external providers:

  • Health platform sync: Apple HealthKit, Apple Health, and Android Health Connect access is handled through device platform APIs and permission screens. Calorie Log does not send HealthKit or Health Connect data to external service providers.
  • AI analysis: meal photos, typed descriptions, and related request data may be sent to the configured AI endpoint to return nutrition estimates. The app ships with a default endpoint, and users may change that endpoint in settings.
  • Barcode lookup: scanned barcode values are sent to Open Food Facts to retrieve product and nutrition information.
  • Optional location hint: if you enable location-assisted barcode lookups, the app requests your device location and may call BigDataCloud to derive a country code used to improve Open Food Facts results.
  • Analytics: the app uses Firebase Analytics to record usage and stability events such as app launches, screen actions, and feature flows.
  • Advertising: the free tier may display banner, native, or rewarded ads through Google Mobile Ads and Meta Audience Network mediation. Those providers may process device and ad request data under their own privacy terms.
  • Subscriptions: in-app subscription purchases are processed by Apple or Google, depending on your platform. Billing, renewals, refunds, and subscription management are handled through your App Store or Google Play account.

📤 Exports, Imports, and Sharing

Calorie Log lets you export your data as JSON and import that data back into the app.

  • Exported backup files are created only when you choose to export.
  • If you share an export file, it will be shared through the destination you choose.
  • Imported files are read from the location you choose and merged into local app storage.

🗑️ Retention and Deletion

You remain in control of the data stored locally in the app.

  • You can delete meals, clear data, or reset the app from within Calorie Log.
  • Uninstalling the app removes locally stored app data from that device.
  • The app may automatically remove older local content to control storage use, including clearing old non-favorite meal images after about 2 months and deleting older meals after about 6 months.
  • The app also enforces local storage limits, such as capping favorites and trimming older non-favorite content when needed.
  • You can revoke Apple HealthKit or Health Connect permissions in platform settings. Data already stored in Apple Health or Health Connect must be managed through those platform apps and settings.

⚙️ Your Choices

  • You can use the app without creating an account.
  • You can toggle location-assisted barcode lookups on or off in settings.
  • You can enable or disable Apple HealthKit or Health Connect access in the app and in your device's health permission settings.
  • You can choose whether to use the default AI endpoint or a custom one.
  • You can manage or cancel subscriptions through your App Store or Google Play subscription settings.
  • You can export, import, or delete your local data at any time.

👶 Children's Privacy

Calorie Log is not directed to children under 13. If you believe a child has provided personal information through the app or through support channels, contact us and we will review the request.

🛡️ Security

Because Calorie Log stores most information locally, your device's own protections such as passcodes, biometrics, encryption, and backup settings play an important role in protecting your data.

HealthKit and Health Connect access is controlled by device-level permission systems. Third-party providers used for analytics, ads, AI analysis, barcode lookup, location-derived country hints, and subscriptions operate under their own security and privacy practices.

📝 Changes to This Policy

We may update this Privacy Policy as the app changes. Any updates will be reflected by revising the date at the top of this page.

📧 Contact Us

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

Nocturnal Devs
Email: nocturnaldevs@gmail.com
Phone: 437 366-2920
Address: 419 Markham Rd. M1J 3E1, Toronto, Ontario, Canada