Last updated: September 10, 2026
MyCalorieMeter is developed independently. This policy describes what data the app collects, why, and where it's stored.
With your permission, MyCalorieMeter reads your workouts, active energy burned, and body weight from Apple Health to calculate your true energy expenditure. It writes the calorie totals you log back to Apple Health as dietary energy, so other apps you use can see them.
This data is processed on your device to power the app's calorie and TDEE calculations. It is never sold, never shared with advertisers, and never used for advertising or marketing purposes of any kind — Apple's Health data guidelines prohibit this, and we don't do it regardless. Health data does not leave your device except as described under "Strava" below, for users who choose to connect Strava.
You control HealthKit access entirely through the Health app (Health → your profile icon → Apps and Devices → MyCalorieMeter). You can revoke access at any time.
Meals, weights, water intake, and custom dishes you log are stored locally on your device using Apple's SwiftData. This data is not uploaded to any server we operate. If you use Apple's device backup (iCloud Backup or a local computer backup), it may be included in that backup the same way any other app's data is, subject to Apple's or your computer's own backup security.
When you search for a food or scan a barcode, the search term or barcode number is sent to USDA's FoodData Central API and/or Open Food Facts' API to retrieve nutrition information. These are public food databases; no other information about you is sent with these requests.
If you choose to connect Strava, MyCalorieMeter starts Strava's own OAuth login flow. Once you approve, an authorization code is sent to our backend server, which exchanges it with Strava for an access token and refresh token. Those tokens — along with your Strava athlete ID — are stored on our server, associated with a random identifier generated by your device (not your name, email, or Apple ID). We use them solely to fetch your workout activities from Strava on your behalf, to avoid double-counting them alongside HealthKit data. You can disconnect Strava at any time in Settings, which deletes this stored data from our server.
If you choose to take a photo of your food to identify it, that photo is sent to our backend server, which forwards it to Google's Gemini API to identify the food and estimate its nutrition. We do not store the photo ourselves. Because this uses Google's free API tier, Google's terms permit them to use submitted photos to improve their models — this differs from a paid tier, which would not. The identified items and estimates are shown to you to review and correct before anything is saved; nothing is logged automatically. This feature is entirely optional and only activates when you choose to take a photo for this purpose.
Subscriptions are handled entirely by Apple through StoreKit. We never see or store your payment information — Apple's own privacy policy governs that data.
MyCalorieMeter does not use any third-party analytics or advertising SDKs, and does not track you across other apps or websites.
Deleting the app removes all locally stored data. To request deletion of any other data we may hold, contact us at support@ebappsupport.com.
MyCalorieMeter is not directed at children under 13, and we do not knowingly collect data from children under 13.
If this policy changes, the "Last updated" date above will change accordingly.
Questions about this policy: support@ebappsupport.com