1. About CalorieView
CalorieView is a photo-first nutrition diary for estimating calories and macronutrients. “CalorieView,” “we,” and “our” in this policy refer to the developer of the CalorieView application.
2. Information stored on your device
Your diary entries, nutrition goals, preferences, reminders, installation identifier and saved meal photos are stored locally on your device. CalorieView does not require a separate account.
You can export your diary or delete local CalorieView data from the app settings.
3. Meal photo analysis
When you choose to analyze a meal, the selected photo, application locale, requested model and a random installation identifier are sent to the CalorieView server. The server validates the request and forwards the image to OpenRouter and the selected AI model provider to produce an estimate.
The CalorieView server processes the photo in memory and does not intentionally retain a copy after the request finishes. AI providers process submitted content under their own service and privacy terms.
4. Food database and manual search
Ingredient estimates may be matched with a compact food-composition database based on USDA FoodData Central. Manual food searches send the search term, locale and random installation identifier to the CalorieView server. These requests are used to return nutrition information and enforce rate limits.
5. Optional iCloud sync
If you enable iCloud sync, diary and profile data are stored in your private Apple CloudKit database associated with your Apple ID. CalorieView does not receive your Apple ID credentials. Meal photo files are not currently included in iCloud sync.
Deleting local data does not automatically delete an existing iCloud copy. iCloud is governed by Apple’s terms and privacy policy.
6. Permissions
Camera and photo-library access are used only when you choose a meal image. Notification permission is used only for reminders you configure. You can change these permissions in iOS Settings.
7. Logs, security and retention
The server may process technical request data needed to operate and protect the service, including timestamps, request paths, response status and a random installation identifier used for rate limiting. Operational logs do not intentionally contain meal photos or the content of your diary. Logs are rotated and retained only as needed for reliability and security.
8. Analytics and advertising
CalorieView does not currently include third-party advertising SDKs or behavioral analytics SDKs. We do not sell personal information.
9. Children
CalorieView is not directed to children under 13. If you believe a child has provided personal information through the service, contact us so we can investigate.
10. Changes to this policy
We may update this policy when the application or its data practices change. The current version and effective date will remain available on this page.
11. Contact
Questions or privacy requests can be sent to support@calorieview.app.