CaloryFi

Open app

Privacy Policy

How CaloryFi handles your information. Short version: your nutrition data stays on your device.

Last updated: August 11, 2026

Summary

CaloryFi is a local-first calorie and nutrition tracker. Your diary, profile, recipes favorites, fasting history, and preferences stay on your device. We do not operate a user account system, cloud sync backend, advertising network, or analytics pipeline for this app.

1. Who we are

This Privacy Policy describes how CaloryFi (“we”, “us”, or “the app”) handles information when you use the mobile or web versions of the product.

For privacy questions about CaloryFi, open an issue on the project repository: CaloryFi on GitHub.

2. Information stored on your device

Depending on how you use the app, the following may be stored locally:

  • Profile & goals — age, sex, height, weight, activity level, calorie/macro targets, and units preference (metric/imperial).
  • Food diary — meals logged, servings, custom foods, custom meals, water intake, workouts, steps, and weight history.
  • Preferences — theme (light/dark/system), notification reminder settings, favorites, and onboarding status.
  • Fasting — selected plan and fasting session timing data.
  • Exports you create — if you use Settings → Export, a JSON file is generated on your device for you to save or share.

Bundled seed content (common foods, sample recipes, barcode mappings, education cards) ships with the app and is not personal data about you.

3. What we do not collect

In the current MVP, we do not:

  • Require sign-in or create online accounts
  • Upload your diary or profile to our servers
  • Sell or share your data with advertisers
  • Run third-party analytics SDKs or tracking pixels
  • Process payments or subscriptions

If you visit this Privacy Policy page on the web, your browser and hosting provider may process standard technical request data (such as IP address and user agent) as part of delivering the page. That is separate from in-app nutrition data, which remains local.

4. Device permissions

  • Camera — used only when you scan a barcode. Scans are looked up against the local food/barcode database. Images are not uploaded.
  • Notifications — optional local reminders (for example fasting windows, water, or meals). These are scheduled on your device; we do not use remote push services (FCM/APNs) in the MVP.

You can deny or revoke these permissions in your device settings.

5. Where data is stored

  • Mobile — SQLite database on the device (via Drift).
  • Web — browser IndexedDB (via Dexie) for the origin that hosts the app.

Data does not leave your device unless you export it or clear/share it through your own OS/browser tools.

6. Retention & deletion

Your data remains on the device until you remove it.

  • Use Settings → Clear all data / reset to wipe user content in the app (seed catalog content may remain after reset).
  • On web, clearing site data for this origin in your browser also removes IndexedDB content.
  • Uninstalling the mobile app removes the app’s local database, subject to your platform’s normal uninstall behavior.

7. Children’s privacy

The app is not directed at children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided data in the app, clear the local data or uninstall the app, and contact us via the repository linked above.

8. International users

Because processing is local on your device, your information generally stays where you use the app. If you later choose to export a file and transfer it yourself, that transfer is under your control.

9. Changes to this policy

We may update this Privacy Policy when the product changes (for example, if cloud sync or accounts are added later). The “Last updated” date at the top will change when we do. Continued use after an update means you acknowledge the revised policy. Material changes that involve collecting data off-device will be described clearly in this document.

10. Contact

Questions about CaloryFi privacy: please use the GitHub repository at CaloryFi Issues.