Privacy Policy

Last updated: June 8, 2026

CalorieWatch AI ("CalorieWatch," "we," or "us") respects your privacy. This policy describes how we collect, use, and protect information when you use our iOS mobile application and this website.

Information we collect

• Account data: email address and profile information (such as name and nutrition goals) when you create an account.
• Meal data: food entries you log, including descriptions, estimated nutrition, and dates. Meal log data is stored in the cloud.
• Meal photos: photos you capture are stored locally on your device only, not on our servers.
• Usage data: basic app activity needed to operate the service (for example, last visit time, notification preferences, and theme preference).
• Device permissions: camera, microphone, speech recognition, and notifications — only when you use features that require them.

How we use information

• Provide calorie and macro tracking, meal history, and personalized goals.
• Analyze meals using AI when you submit text, photos, or voice (processed via our backend services).
• Authenticate you and keep your data synced securely across sessions.
• Send local meal reminders if you enable notifications.

Service providers

We use trusted third parties to run the app, including:

• Supabase — authentication, database, and server functions.
• OpenAI — meal analysis and voice transcription (via Supabase Edge Functions).
• Expo / Apple — app distribution (TestFlight / App Store) and platform services.

These providers process data according to their own policies and our instructions for operating the app.

Data retention

We retain your account and meal data while your account is active. Meal photos on your device are removed when you uninstall the app. You may request account deletion (see Delete Account).

Security

We use industry-standard measures to protect your information, including:

• Encrypted connections: data in transit uses HTTPS/TLS between the app, website, and our service providers.
• Account passwords: must meet minimum complexity requirements (length, uppercase, lowercase, number, and symbol). Passwords are hashed by Supabase and are never stored in plain text.
• Sign-in tokens: on iOS, authentication tokens are stored in the device Keychain rather than unencrypted app storage.
• Database access: row-level security limits each user to their own profile and meal data in Supabase.
• AI processing: when you analyze a meal by photo or voice, that content is sent securely to our backend for processing (OpenAI via Supabase Edge Functions). Saved meal photos remain on your device only.

No method of transmission or storage is 100% secure.

Children

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

Your choices

• Update goals and profile in the app Settings.
• Hide meal photos in Settings (photos remain saved on your device).
• Disable notifications in iOS Settings or in the app.
• Sign out or request account deletion at any time.

Contact

Questions about privacy? Email our support team or visit Support.

Changes

We may update this policy from time to time. We will post the new date at the top of this page. Continued use of the App after we publish changes constitutes acceptance of the updated policy.