Privacy Policy

Effective October 12, 2026

In short: C for Calories has no accounts. Your profile, targets, food diary and meal photos are stored on your phone. A resized meal photo is sent for analysis only when you ask for a photo estimate, and food searches send only the search text or barcode. We don't sell your data, and we never use your food diary for advertising.

This Privacy Policy explains how the C for Calories app for iOS and Android (“the app”) and this website handle information. The app is developed by Pod27 (“we”, “us”), the data controller. Contact: support@cforcalories.si.

1. Information stored on your device

The app stores the following on your phone, in its private storage:

  • Profile and targets: your goal, sex (optional), age, height, weight, activity level, preferred units and your daily calorie, protein, carbohydrate and fat targets;
  • Food diary: meals, foods, amounts, nutrition values, meal types and times, favorites and recently used foods;
  • Meal photos you save with a meal (stored as compressed images, deleted when you delete the meal);
  • Cached product data from barcode lookups, kept for up to 60 days so they work offline;
  • App settings such as your Progress layout, widget data, ad-frequency counters and your last known subscription status;
  • a random installation ID and a short-lived session token for our service (see section 3), kept in storage that is excluded from device backups and transfers.

Information about your diet and body can be sensitive. It stays on your device and is not uploaded to our servers. You can edit or delete any meal at any time. Uninstalling the app deletes all of it from the device. Your phone's own backup (iCloud or Android backup), if enabled, may contain a copy of the diary under your Apple or Google account, but not the installation ID or session token.

2. Meal photos and AI analysis

Camera and photo-library access are optional. The camera is used to photograph meals and scan barcodes; the photo library only when you choose an existing photo. Barcodes are read on your device.

When you request a photo estimate, the app resizes the photo (to at most 1,600 pixels) and sends it over an encrypted connection to our meal-estimation service. The service passes the image to an AI vision-model provider, through the OpenRouter routing service, to identify the foods and estimate portions, then returns the estimate to your phone. Our service processes the image in memory and does not store or log it. OpenRouter and the model provider process the request under their own terms and privacy policies, which may include short-term retention for abuse monitoring. Photos are not sent with your profile, targets or diary, and we don't use them to train AI models.

3. Our service, food search and abuse prevention

Food search sends the text you type, and barcode lookup sends the barcode number, to our food service, which looks them up in nutrition databases including USDA FoodData Central and Open Food Facts. If our food service doesn't have a product or can't be reached, the app asks Open Food Facts directly for that barcode number; like any web request, this shows Open Food Facts your IP address. These requests don't include your profile, targets or diary.

To protect the service from automated abuse, the app obtains a short-lived session from our service before using these features. It sends the random installation ID, the platform, the app version and build number and, where available, a device-integrity check from Apple (App Attest) or Google (Play Integrity). Apple and Google provide these checks under their own privacy policies. Like any web service, our servers and hosting providers also process technical data such as your IP address, request times and errors, which we use for security, rate limiting and troubleshooting and keep for a limited time.

4. App statistics and crash reports

Versions of the app installed from the App Store or Google Play use Google Firebase Analytics and Firebase Crashlytics to help us understand how the app is used and to fix crashes. They process an app-instance identifier, device and operating-system information, app version, approximate location derived from your IP address, and events such as screens viewed, setup completed, which logging method was used and whether a photo estimate or lookup succeeded. We also set coarse properties: your goal type, how targets were set, a calorie-target range (for example 1,800–2,100 kcal), your unit system and whether you have an Ad-Free subscription.

We deliberately do not send meal photos, food names, search text, barcodes, exact body measurements, exact calorie or macro values, or the contents of your diary. See Firebase privacy information.

5. Advertising

The app is free and supported by ads from Google AdMob. Ads are shown from your second use of the app onwards and never to Ad-Free subscribers. Where required (for example in the EEA, the UK and Switzerland), the app asks for your consent using Google's consent tool before ads are personalised, and you can change your choice at any time in Settings › Privacy › Ad privacy choices. Until you consent, ad-related signals are limited to what is needed to show non-personalised ads, measure them and prevent fraud.

Google may process your IP address, device and advertising identifiers, device information and information about ads shown, according to your choices. See how Google uses information in ads. We never share your diary, photos or body data with advertisers.

6. Purchases

The optional Ad-Free subscription is sold and billed by Apple or Google. We never receive your payment-card details. The app receives the information needed to know whether your subscription is active, and stores that status on your device. Manage or cancel the subscription in your App Store or Google Play account.

7. This website

This website has no user accounts, analytics, advertising or tracking cookies, and doesn't load third-party scripts or fonts. Our hosting provider processes technical data, including your IP address, to deliver pages and protect the site, and keeps server logs for a short period. The calculators run entirely in your browser; they remember your unit preference in your browser's local storage, and nothing you enter is sent to us.

8. How and why we use information (legal bases)

  • Providing features you ask for (photo estimates, food search, barcode lookup, purchases): performance of our contract with you.
  • Security and abuse prevention (sessions, integrity checks, rate limits, server logs): our legitimate interest in keeping the service available and affordable.
  • App statistics and crash reports: our legitimate interest in understanding and improving the app, or your consent where the law requires it.
  • Personalised advertising: your consent where required; non-personalised ads are based on our legitimate interest in funding the free app.
  • Answering you when you contact support, and meeting legal obligations.

Your diet and body data stay on your device and are processed there only to provide the app's features to you.

9. Service providers and international transfers

We use these providers, each only for the purpose described above: Apple and Google (app distribution, purchases, integrity checks, backups), Google AdMob and Firebase (ads, consent, statistics, crash reports), our cloud hosting and security providers, OpenRouter and the AI vision-model provider it routes to (photo estimates), and USDA FoodData Central and Open Food Facts (nutrition data). Some of them process data outside your country, including in the United States. Where required, transfers are protected by appropriate safeguards such as the EU Standard Contractual Clauses or the EU-U.S. Data Privacy Framework.

We don't sell or rent personal information. We may disclose information if required by law or to protect users, the service or others.

10. How long we keep information

Data on your device stays until you delete it or uninstall the app. Meal photos sent for analysis are not stored by our service. Session data and server logs are kept only as long as needed for security and troubleshooting. Support emails are kept as long as needed to help you and then deleted. Data processed by Apple, Google, Firebase, AdMob and OpenRouter follows their retention settings and policies.

11. Your rights

Depending on where you live (for example under the GDPR), you have the right to access, correct, delete, restrict or port your personal data, to object to processing based on legitimate interests, and to withdraw consent at any time. Because there are no accounts and your diary stays on your device, most of your data is under your direct control in the app. For anything else, email support@cforcalories.si. We may ask for information such as your installation details to find data relating to you.

You can also lodge a complaint with a data-protection authority, such as the authority in your country of residence or the Information Commissioner of the Republic of Slovenia.

California residents: we don't sell or share personal information for cross-context behavioural advertising as defined by California law, except as described for ads above, which you control through the ad privacy choices.

12. Children

The app is intended for users aged 13 and over (or the minimum age required in your country, if higher). It isn't directed at children, and we don't knowingly collect personal information from children. If you believe a child has provided personal information, contact support@cforcalories.si.

13. Security

All connections between the app and our service are encrypted. Your on-device data is protected by your phone's security; we recommend a passcode or biometric lock. No system is perfectly secure, but we limit what leaves your device to what each feature needs.

14. Changes and contact

We'll post any changes to this policy on this page and update the effective date. For significant changes we may also tell you in the app. Questions or requests: support@cforcalories.si.