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, model identifier and a random installation identifier are sent to the CalorieView server. The server validates the request and sends the photo and an analysis prompt through OpenRouter to Google's AI service to produce a nutrition estimate. The prompt includes the requested language and output format; it does not include your diary, nutrition profile, installation identifier or Apple purchase identifiers.
The CalorieView server processes the photo in memory and does not intentionally retain a copy after the request finishes. OpenRouter and the AI provider process submitted content to deliver the analysis and operate and protect their services. Their retention and data-use practices are described in the OpenRouter Privacy Policy, Google Privacy Policy and Google AI service terms. You can use manual food entry instead of sending a photo for online analysis.
4. Food databases, search and barcodes
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. Barcode lookup sends the scanned or entered barcode, locale and random installation identifier to the CalorieView server and returns product data from Open Food Facts. These requests are used to return nutrition information and enforce rate limits.
Product data is provided by Open Food Facts under the Open Database License (ODbL). Open Food Facts is community-contributed, so product information may be incomplete or inaccurate; users should check the package label.
5. Purchases and service usage
Apple handles subscription payments through In-App Purchase. To verify and restore Premium access, CalorieView processes Apple transaction identifiers and subscription information. The server stores the original transaction identifier, subscription product, expiration date and any revocation information together with a hashed identifier derived from your installation identifier. We do not receive your payment-card details or Apple Account password.
The server also stores photo-analysis usage records, including the installation hash, subscription tier, date, time and completion status, to apply the free or Premium analysis allowance. These records do not contain the meal photo, food names or diary contents. Purchase and usage records are used to provide access, handle subscription changes and prevent fraud and abuse, not for advertising.
6. Permissions
Camera access is used to capture a meal photo or scan a barcode. Photo-library access is used for meal images you select, and notification permission is used for reminders you configure. You can change or revoke these permissions in iOS Settings.
7. Security and retention
The server is hosted on Cloudzy. Online requests use HTTPS, and technical request data such as timestamps, request paths, response status, network information and installation identifiers may be processed to operate and protect the service. Operational logs do not intentionally contain meal photos or diary contents. Logs are size-limited and rotated.
Service-usage records are retained to maintain an installation's analysis allowance. Subscription records are retained to verify and restore purchases and handle changes to paid access. Retention depends on these service purposes, security needs and any applicable legal requirements. AI, analytics and diagnostics providers retain the data they process according to their service terms and privacy policies linked here.
The in-app deletion option applies to data stored on your device. For requests about server-side records or data processed by our service providers, use the privacy contact below. Deleting local data does not cancel an Apple subscription; subscriptions and renewal are managed through Apple.
8. Analytics, crash reporting and app integrity
Release versions use Google Firebase Analytics and Firebase Crashlytics to understand broad feature usage and diagnose technical failures. Firebase may process an app-instance identifier, device and operating-system information, app version, screen and feature interactions, crash stack traces and related diagnostics. Analytics may derive approximate location, such as country or region, from network information; CalorieView does not request precise device-location access.
On iOS, Firebase App Check uses Apple App Attest to confirm that protected requests come from a genuine CalorieView installation. Apple and Firebase may process app and device integrity signals and a short-lived verification token for fraud and abuse prevention.
We do not send meal photos, food names, search text, diary contents, calorie or macro values, body weight, nutrition goals, age, sex, email addresses or Apple transaction identifiers to Firebase. Firebase is not used for advertising, ad personalization or cross-app tracking, and CalorieView does not use IDFA. We do not sell personal information. See Firebase Privacy and Security and the Google Privacy Policy for more information about these services.
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. Your choices and privacy requests
You can export your diary and delete local data in CalorieView Settings, change device permissions in iOS Settings, and manage subscription renewal through Apple. For questions about data processed off your device, requests for access, correction or deletion, or withdrawal of consent where applicable, contact appusersupport@gmail.com.
If you contact support, we process your email address and the information you provide to respond. We may ask for limited information needed to identify the relevant records and verify your request. Please do not send Apple Account passwords or payment-card details. We will explain any limits on a request, including records needed for purchase verification, security or applicable legal obligations.