🥗 Calorie Counter (com.apps.ai_food_calorie_tracker)

Privacy Policy

AI-Powered Food & Calorie Tracking Application

Effective Date: September 9, 2026
Last Updated: September 9, 2026
Application Version: 1.0.5+

🔒 Privacy Summary at a Glance

Calorie Counter is designed with a privacy-first and local-first architecture. We do not require account creation, do not sell your personal data, and do not track you across other applications. Your nutrition history and body metrics stay safely stored on your local device. Food scan photos are sent securely via encrypted HTTPS solely to generate nutritional estimates in real time and are not retained or used to identify you.

1. Introduction & Scope

This Privacy Policy describes how Calorie Counter ("we", "us", "our", or "the Application") collects, uses, processes, and protects your information when you use our mobile application on Android devices.

By downloading, installing, or using Calorie Counter, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with our policies and practices, please do not use the Application.

2. Information We Collect

We only collect data necessary to provide and enhance our calorie tracking and AI meal identification services:

A. Information You Provide (Stored Locally on Device)

Local Storage: All profile details, calorie goals, and meal log entries are stored locally on your device via encrypted local storage (Hive and SharedPreferences) and are never uploaded to a private backend database.

B. Camera & Photo Data

C. Automatically Collected Technical & Diagnostics Data

3. How We Use Your Information

The collected information is used strictly for the following purposes:

Data Category Primary Purpose Storage / Transmission
Profile & Goals Calculate BMR, TDEE, calorie targets, and track nutrition progress. Local Only
Food Images AI recognition of food items, portion estimation, and macro breakdown. Ephemeral / Encrypted HTTPS
Meal Logs & History Display daily summaries, nutrition charts, weekly stats, and streaks. Local Only
Analytics & Crash Data Diagnose crashes, monitor performance, and optimize user experience. Anonymized Firebase SDK
Reminder Preferences Schedule local alarm reminders for breakfast, lunch, and dinner. Local Only

4. Device Permissions & Purpose

To provide its core functionality, Calorie Counter requests the following Android system permissions. You can control or revoke these permissions at any time through your device settings:

Android Permission Purpose & Rationale Requirement Type
android.permission.CAMERA Allows you to take photos of your food for instant AI analysis and calorie recognition. Optional (Feature-based)
android.permission.POST_NOTIFICATIONS Delivers daily meal reminders (breakfast, lunch, dinner) on Android 13+ (API 33+). Optional
android.permission.SCHEDULE_EXACT_ALARM Ensures scheduled meal reminders trigger accurately at the specific times you configure. Optional
android.permission.RECEIVE_BOOT_COMPLETED Reschedules your configured meal reminders automatically after your device restarts. System Local
android.permission.VIBRATE Provides gentle haptic tactile feedback when logging meals and receiving reminder notifications. System Local
android.permission.INTERNET & ACCESS_NETWORK_STATE Required to query AI recognition models and fetch dynamic remote configurations. Required
com.google.android.gms.permission.AD_ID Google Play Services identifier used for analytics measurement and policy compliance. Analytics

5. Third-Party Services & Integrations

We partner with trusted third-party service providers that process technical data under strict confidentiality and privacy standards:

6. AI Processing & Image Handling

When you use the AI Food Recognition feature:

  1. The image is optimized and compressed on your device.
  2. The compressed image is transmitted via TLS/SSL encrypted connection to the AI model endpoint.
  3. The AI model analyzes the visual features of the meal, extracts nutritional information (calories, macronutrients, estimated weight), and returns structured data.
  4. Once the nutritional response is returned, the transient image transmission is discarded. We do not store, catalog, or share your personal photo library.

7. Data Storage, Retention & Security

We implement comprehensive technical and organizational safeguards to ensure user privacy:

8. Your Rights & Data Deletion Controls

We believe you should have complete autonomy over your personal data:

Under applicable privacy laws (such as GDPR, UK GDPR, and CCPA/CPRA), you have the right to access, rectify, port, or delete your personal data. Because we do not maintain central user accounts, you can exercise all of these rights directly inside the app without needing to submit an external request.

9. Children's Privacy (COPPA & GDPR-K Compliance)

Calorie Counter is intended for general audiences and is not directed at children under the age of 13 (or under 16 in the European Economic Area / UK). We do not knowingly collect, solicit, or maintain personal information from children. If you believe that a child has provided us with personal information, please contact us at nexusplayengine@protonmail.com so we can take appropriate action.

10. Changes to This Privacy Policy

We may update our Privacy Policy from time to time to reflect changes in our practices, app features, or legal requirements. When we make updates, the revised date at the top of this document will be updated. We encourage you to review this Privacy Policy periodically to stay informed about how we are protecting your information.

11. Contact Us & Developer Support

If you have any questions, concerns, feedback, or privacy-related inquiries regarding this Privacy Policy or Calorie Counter, please feel free to reach out to us:

Calorie Counter Developer Team

For support, questions, or data protection assistance: