CalorieCount

Privacy Policy

Version 3.0 · Effective July 8, 2026

Covers Android and iOS platforms

CalorieCount is built on a simple principle: your health data belongs to you. No user accounts. No central servers storing your meals. No selling data to advertisers. Everything you log stays on your device unless you explicitly choose to sync it.

1. About This Policy

This Privacy Policy explains how we handle information in connection with the CalorieCount mobile application (App), available on Google Play (Android) and the Apple App Store (iOS).

This policy applies to both platform versions. Where behaviour differs between Android and iOS, each platform is described separately. References to 'Health Connect' apply to Android only; references to 'Apple Health' or 'HealthKit' apply to iOS only.

By using CalorieCount you agree to the practices described here.

2. Information We Collect

2.1 Nutrition & Health Data (Local)

The following data is created by you and stored solely on your device:

• Food log entries: food name, calories, protein, carbohydrates, fat, fibre, sugar, sodium

• Meal type and timestamp for each entry

• Daily calorie goal

• Historical log (past days)

This data never leaves your device except when you explicitly use a health platform sync feature (see Sections 4 and 5).

2.2 Food Photographs

When you use the camera or photo library to analyse a meal, the image is sent directly to Anthropic's API for AI analysis and is not stored by us.. See Section 6.1 for Anthropic's data practices.

2.3 Search Queries

When you search for foods manually, your query is sent to Open Food Facts or FatSecret to retrieve nutritional data. No user identifier accompanies these requests.

2.4 Device Information

The App reads your device model, OS version, and platform flag (Android / iOS) for compatibility purposes. This information is not transmitted to us..

We do NOT collect: name, email address, location, contacts, payment information, advertising identifiers, or biometric data.

3. How We Use Information

• Provide core calorie and macro tracking functionality

• Analyse food photographs using AI (Anthropic Claude)

• Look up nutritional information in food databases

• Write nutrition entries to Apple Health or Android Health Connect, if you enable sync

• Improve in-app performance and compatibility

We do not use your data for advertising, profiling, or sale to third parties.

4. Android Health Connect

4.1 What It Is

Health Connect is Google's on-device health data platform. CalorieCount can optionally write your food log entries to Health Connect so they appear in compatible health apps.

4.2 Permissions Requested

• WRITE_NUTRITION — to create NutritionRecord entries

• READ_NUTRITION — not actively used; declared for future deduplication capability

Both permissions are optional. The App works fully without them.

4.3 Data Written to Health Connect

Each synced food log entry writes the following fields to an HKCorrelation / NutritionRecord:

• Dietary energy (kilocalories)

• Protein (grams)

• Total carbohydrates (grams)

• Total fat (grams)

• Dietary fibre (grams)

• Sugar (grams)

• Sodium (milligrams)

• Meal type (breakfast, lunch, dinner, snack)

• Start and end timestamp

• Data origin: com.calorie.count

4.4 Sync Behaviour

Health Connect sync is always manual and user-initiated. CalorieCount performs no background sync. Tapping the HC Sync button syncs today's visible entries only.

4.5 Revoking Access

You can revoke CalorieCount's Health Connect permissions at any time in: Settings → Apps → CalorieCount → Permissions, or within the Health Connect app. Previously synced records remain in Health Connect until you delete them from within the Health Connect app under Browse → Nutrition.

5. Apple Health (HealthKit) — iOS Only

5.1 What It Is

Apple Health (powered by HealthKit) is Apple's on-device health data platform available on iPhone and iPad. CalorieCount for iOS can optionally write your food log entries to Apple Health so they appear in the Health app and compatible third-party apps.

5.2 Permissions Requested

CalorieCount requests write-only access to the following HealthKit data types:

• HKQuantityTypeIdentifierDietaryEnergyConsumed — dietary energy (kcal)

• HKQuantityTypeIdentifierDietaryProtein — protein (grams)

• HKQuantityTypeIdentifierDietaryCarbohydrates — carbohydrates (grams)

• HKQuantityTypeIdentifierDietaryFatTotal — total fat (grams)

• HKQuantityTypeIdentifierDietaryFiber — dietary fibre (grams)

• HKQuantityTypeIdentifierDietarySugar — sugar (grams)

• HKQuantityTypeIdentifierDietarySodium — sodium (grams)

CalorieCount does NOT request read access to Apple Health. We cannot see any data previously stored in your Apple Health profile.

5.3 Data Written to Apple Health

Each synced entry is saved as an HKCorrelation of type HKCorrelationTypeIdentifierFood containing individual HKQuantitySample objects for each nutrient listed above. The following metadata is also written:

• HKMetadataKeyFoodType — the food name as recorded in CalorieCount

• Start timestamp — the log entry time

• End timestamp — 15 minutes after the log entry time

• Data source bundle ID: com.calorie.count

5.4 Sync Behaviour

Apple Health sync is always manual and user-initiated. CalorieCount performs no background sync. Tapping ♥ Sync on the Log tab syncs today's visible entries only. iOS will present the standard HealthKit permission sheet before the first sync.

5.5 HealthKit Data Policy

In accordance with Apple's HealthKit guidelines:

• CalorieCount does not use HealthKit data for advertising or with advertising APIs.

• CalorieCount does not share HealthKit data with third parties, including Anthropic, Open Food Facts, or FatSecret.

• HealthKit data is used solely to write nutrition entries at your explicit request.

• No HealthKit data is transmitted to Ark Labs LLC's servers (we have none).

5.6 Revoking Access & Deleting Data

You can revoke CalorieCount's HealthKit permissions at any time in: iPhone Settings → Privacy & Security → Health → CalorieCount → turn off all toggles.

Previously written entries remain in Apple Health until you delete them manually. To do so: open the Health app → Browse → Nutrition → select a nutrient → tap Show All Data → swipe left on any entry and tap Delete.

Revoking permissions prevents future syncs but does not remove previously written records.

6. Third-Party Services

6.1 Anthropic (AI Analysis)

Food photographs you submit for analysis are sent to Anthropic's Claude API over HTTPS. Anthropic may retain images for safety monitoring per their privacy policy at https://www.anthropic.com/privacy. We do not store the images.

6.2 Open Food Facts

Barcode scans and food name searches may query the Open Food Facts database (world.openfoodfacts.org). Queries contain no user identifier. Open Food Facts is an open-source, nonprofit project — see https://world.openfoodfacts.org/terms-of-use.

6.3 FatSecret

Food name searches may query the FatSecret API. Queries contain no user identifier. See FatSecret's privacy policy at https://www.fatsecret.com/privacy-policy.

6.4 Cloudflare

Network requests pass through Cloudflare's infrastructure, which may log IP addresses transiently for DDoS protection. See https://www.cloudflare.com/privacypolicy/.

6.5 Apple (iOS Only)

The iOS App is distributed via the Apple App Store. Apple collects purchase and download records per Apple's privacy policy at https://www.apple.com/legal/privacy/.

7. Local Data Storage

All nutrition data is stored using the platform's local storage mechanism:

• Android: browser localStorage within the WebView

• iOS: WKWebsiteDataStore (persistent) within the WKWebView

Data persists between sessions on the same device. Uninstalling the App deletes all locally stored data. No backup to our servers occurs.

8. Data Retention

9. Security

All API calls use HTTPS/TLS. Local data is protected by the device's own encryption (Android File-Based Encryption; iOS Data Protection). We do not operate servers that store your health data, which eliminates the most common server-side breach risk.

10. Children's Privacy

CalorieCount is not directed at children under 13 (or under 16 in the EU/UK). We do not knowingly collect personal information from children. If you believe a child has provided information through the App, contact us at areebahmed@arklabs.llc.

11. Your Rights

Because we hold no central user accounts or health databases, most data rights are exercised directly on your device:

• Access: view your data in the App's Log and Stats tabs

• Deletion (local): clear App data in device Settings or uninstall the App

• Deletion (Apple Health): see Section 5.6

• Deletion (Health Connect): see Section 4.5

• Portability: your data is already on your device

If you are in the EU, UK, or California and have questions about data rights, contact areebahmed@arklabs.llc. We will respond within 30 days.

12. Changes to This Policy

We will post any changes to this policy at https://arklabs.llc/Privacy-Policy/ and update the version number and effective date at the top of this document. Continued use of the App after the effective date constitutes acceptance of the revised policy.

13. Contact

areebahmed@arklabs.llc

https://arklabs.llc

Annex A — Data Flow Summary

This table summarises every category of data and where it goes.

CalorieCount Privacy Policy | Version 3.0 | Effective July 8, 2026

Nutrition information provided by FatSecret Platform API