CalFood
Notify me at launch

CalFood - Privacy Policy

Effective Date: October 27, 2026

This policy describes the CalFood website and the free iOS version of CalFood, provided by xBlog AI LLC. It explains what information we process, why we process it, and the choices available to you. The iOS version has no paid subscriptions or in-app purchases.

Website analytics

Website analytics is currently disabled for all visitors, including browsers that previously allowed it. The website does not load Google Analytics or send website usage events, and we have hidden the analytics consent banner while collection is paused.

This pause does not delete events Google received before analytics was disabled. See Google’s privacy policy for its data handling.

App Store launch notifications

If you join the launch list, we collect your email address, signup time, and a record of the launch-notification wording you agreed to. We use this information to send one email when CalFood becomes available on the App Store, with a link to claim free access during the limited launch offer. Joining the list does not create an app account, start a subscription, or guarantee permanently free access.

Your launch signup is separate from your app account and is not used for marketing updates. To limit spam, we use a daily-changing hashed version of your IP address; we do not store your raw IP address with launch signups. Spam-prevention records expire within 24 hours and are removed when the service next processes a valid signup.

You can withdraw your request before launch or ask us to delete your email by contacting contact@mycalnote.com. We remove the launch list within 30 days after sending the launch notification. Cloudflare may separately process technical request information to operate and secure its services.

1. Information We Process

Account information

Firebase Authentication processes your login information, email address, and account identifier. You can sign in with email and password or Sign in with Apple.

Nutrition profile and meal data

The onboarding information you provide may include your date of birth, gender, height, current and target weight, activity level, dietary considerations, and preferences. We store your profile in Firebase to provide the service. Meal notes submitted for analysis, their dates, nutrition estimates, and saved meals are associated with your account and stored in Firebase Firestore.

Photos and AI requests

With your explicit permission, meal text, photos you choose, and the request language are sent through our backend to Google Gemini for nutrition estimates. CalFood processes photo image files in memory and does not store those image files in its database or an image-storage service. The generated meal descriptions and nutrition results may be saved with your meal notes. Google's processing is governed by its applicable policies.

Usage and technical information

We process an app-generated device identifier, account identifiers, usage events, device and app metadata, and operational diagnostics to run the service, understand feature usage, and prevent abuse. Analysis metrics may include request counts, token counts, latency, and error status. These identifiers can be associated with your account.

2. Why We Use Information

  • Authenticate your account and provide your nutrition profile, meal history, and saved meals.
  • Estimate calories and nutrients from the meal text or photos you choose to share with AI.
  • Maintain the service, investigate errors, and enforce security and abuse-prevention limits.
  • Understand feature usage and respond to support requests.

We do not sell your personal information or use meal content for advertising.

3. Service Providers and AI Sharing

  • Cloudflare hosts the website and processes launch-notification signups.
  • Firebase and Google Cloud provide authentication, database storage, backend processing, and operational diagnostics.
  • Google Gemini processes the meal text, selected photos, and request language you explicitly permit us to share for AI estimates.
  • PostHog processes usage events and technical metrics linked to an account identifier. The iOS app does not send passwords, email addresses, meal text, photos, or onboarding answers in its analytics events. Session replay is disabled.

We ask for AI-sharing permission before sending your meal text or photos to Gemini. You can decline and keep writing notes without AI estimates. You can revoke future AI sharing in Settings under Data sharing. Revoking does not delete information already saved or undo earlier processing. Account and profile services continue to use Firebase.

4. Retention and Account Deletion

We keep your account, profile, and cloud meal data while your account is active. You can delete your account in the app: open Settings, then choose Delete Account. The deletion process removes your Firebase login, profile, cloud meal notes, saved meals, and associated device registrations.

A minimal record containing the account identifier and deletion time is retained to block stale access tokens and protect deleted accounts. Operational logs, analytics, backups, and information already processed by service providers may be subject to separate retention periods. Contact us for questions or requests about that information.

5. Security

We use encrypted connections, authentication, and access controls to protect your information. No service can guarantee absolute security. Please keep your login credentials private and contact us if you suspect unauthorized access.

6. Children's Privacy

CalFood is not intended for children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so we can investigate and remove it.

7. Your Choices and Rights

  • Decline or revoke AI sharing in the app.
  • Delete your account and its associated cloud data from Settings.
  • Contact us to request access, correction, or deletion of personal information, subject to applicable law and necessary identity verification.

For privacy questions or requests, visit our contact page.

8. Policy Updates

We may update this policy as the service changes. We will update the effective date and provide any notice or obtain any additional permission required by applicable law. This policy was last updated on October 27, 2026.