Privacy policy

On your iPhone, the app may keep:

• Your first-run profile: name, age, sex used for estimation, height, weight, activity level, and preferred weight unit.
• Optional goal settings and the acknowledgment that the app is not medical advice.
• Meal entries you log (name, calories, category, timestamp).
• Weight entries you log in the app.
• Whether Health connection and iCloud sync are enabled, and when onboarding finished.

By default these stay in the app’s storage on your iPhone. If you enable iCloud sync, profile settings, meal entries, and app weight entries use your private iCloud storage so they can appear on your other devices signed into the same Apple ID. Health samples read through HealthKit are not copied into that CloudKit store.

If you connect Apple Health, CalorieCurrent asks iOS for permission to:

• Read Active Energy and Resting / Basal Energy.
• Write body mass only when you add a weight and the “Save new weights to Health” switch is on.

Apple controls each permission. The app cannot see other Health information it did not request. A failed HealthKit write does not discard a weight already saved in the app. Editing a weight later does not change or delete samples previously written to Apple Health.

• It does not currently require a CalorieCurrent login or email to use the core tracking features. That may change for a future subscription or account feature.
• It does not include advertising, analytics, crash-reporting, or attribution SDKs.
• It does not track you across apps or websites.
• It does not send meal history, weight history, or profile details to a server I operate.
• It does not upload food photos. Version 1 has no food-photo feature.

Settings contains “Erase all CalorieCurrent data,” behind a confirmation. It deletes meals, app weight entries, profile, goal, and settings on the iPhone, and when iCloud sync is on it also deletes the corresponding private iCloud records. The app then returns to first-run setup. Data already in Apple Health is not deleted. Deleting the app from your iPhone removes the local store as well.

If you install the app from the App Store, Apple handles the download and any future purchase under Apple’s privacy policy. Apple may show me aggregate, anonymous statistics such as download counts and crash summaries in App Store Connect. I never receive anything from Apple that identifies an individual CalorieCurrent user.

The site is a handful of static pages hosted on Cloudflare Pages. It sets no cookies and runs no analytics. It embeds no third-party scripts, fonts, or images, and has no forms. As with any web host, Cloudflare processes basic request data such as IP address while delivering the page and protecting it from abuse; see Cloudflare’s privacy policy. I do not have access to a per-visitor record of it.

Mail to caloriecurrent@irony.dev is forwarded to a personal inbox and stored there. I use it to answer you and to keep track of bug reports and feature requests. I do not add you to a mailing list or share your address. Ask me to delete a message thread and I will.

CalorieCurrent is not directed at children under 13. The app’s own estimate calculator rejects ages under 13.

Privacy laws including the GDPR and the CCPA give you rights to access, correct, delete, and port personal data a company holds about you, and to object to it being sold. Today I do not run a CalorieCurrent user database. What I may hold is an email thread if you started one. If an account or subscription system is added later, that data will be described here. Write to me and I will confirm what I hold in writing if you need it. Data on your iPhone or in your private iCloud account is under your Apple ID and the erase control in the app.

If this policy changes, the updated version will appear on this page with a new date at the top. Material changes that affect how the app handles data will also be reflected in onboarding and Settings copy.