Legal

Privacy Policy

Last updated: April 9, 2026

Calorie Tracker is designed with privacy in mind. This policy explains what data is processed by the app, where it is stored, and which third-party services are used for specific features.

1. Data Stored Locally on Your Device

The app stores your tracking data locally on your device using iOS storage:

Meal entries and nutrients
Exercise entries and calorie burn history
Goal settings and nutrient targets
Tracked nutrient preferences
PCC menu cache and related app preferences
Onboarding and app customization settings

2. iCloud Private Sync (CloudKit)

If your iCloud account is available, the app can sync app-state data through your private CloudKit database to keep data consistent across your Apple devices. This includes saved entries, goals, archives, and preferences needed to restore your tracker state.

CloudKit data is associated with your Apple ID and managed under Apple's iCloud privacy and security model.

3. Health Data (Apple Health)

If you connect Apple Health, the app reads the following data to calculate and adjust goals:

Biological sex — for BMR calculation
Date of birth — to calculate age for BMR
Height — for BMR calculation
Body mass (weight) — for BMR calculation and weight trend charts
Step count — to estimate daily activity burn
Walking/running distance — to estimate daily activity burn
Workouts — to include supported workout activity in daily burn estimates

The app does not write data to Apple Health. Health data is used in-app for BMR, activity estimates, and calorie-goal calculations only.

4. Apple Watch

If you have a paired Apple Watch with the app installed, the app sends a snapshot of your current goal, activity calories, and recent meal entries to the Watch over WatchConnectivity. This data transfer stays on your local devices and does not pass through external servers.

5. Camera and Photo Library

The app can use camera or photo-library access for:

Barcode scanning — to detect barcode values for food lookup
AI plate portion estimates — plate photos are analyzed with selected menu items to estimate portions
AI food photo / nutrition-label scan — food photos or nutrition labels are analyzed to create draft entries

6. Data Sent to External Services

The app makes limited network requests for specific features:

USDA FoodData Central (via backend proxy) — your search query is sent to our Firebase backend and then to USDA
Open Food Facts — scanned barcode numbers are sent to retrieve nutrition data
PCC Dining Nutrislice API — menu data is fetched from Nutrislice endpoints
Google Gemini (via backend) — for AI plate estimates and food/label analysis, the app sends image data and selected food-item context to backend endpoints that call Gemini
Apple CloudKit (private database) — used for app-state sync when iCloud is available

The app does not require creating an in-app account. For AI analysis requests, the backend does not store submitted image files as part of normal operation.

7. Analytics & Tracking

The app does not include third-party advertising SDKs and does not sell personal data. We use limited operational logging in backend services — such as request status codes and error diagnostics — to keep features reliable.

8. Children

The app is not directed at children under 13. We do not knowingly collect personal information from children.

9. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top reflects the most recent version. Continued use of the app after changes constitutes acceptance of the updated policy.

10. Contact

For questions about this Privacy Policy or the app's data practices, contact the developer through the app's listed support channel.