← Back to Privacy Policy

Sub-processors

Last updated May 19, 2026

These are the third-party services Calorie Buddy uses to operate. Each receives only the data it needs to do its job, under a data-processing agreement with us.

We may change vendors from time to time. This page is the source of truth — when it changes, the change applies. We'll notify you of material changes via email or in-app before they take effect.

For the full context, see our Privacy Policy.

Cloud platform & data storage

VendorPurposeDataRegionTheir policy
Google Firebase
Google LLC
Authentication, Firestore database, Cloud Storage, Cloud Functions All app data (profile, food log, weight, meal photos, feedback events) US / EU multi-region link

AI analysis

VendorPurposeDataRegionTheir policy
Anthropic
Anthropic PBC
Analyses meal photos and text descriptions to estimate calories and macros. Retains inputs up to 30 days for abuse monitoring; does not use them for model training. Meal photo bytes, text descriptions you write US link

Subscriptions & payments

VendorPurposeDataRegionTheir policy
RevenueCat
RevenueCat Inc.
Tracks subscription entitlement across devices. Pseudonymous user ID, purchase events. No card details. US link
Apple
Apple Inc.
App Store distribution, in-app purchase processing, Apple Sign-In, push notifications, HealthKit. App Store account identifier, purchase confirmations, Apple Sign-In identifier (if used), APNs token. HealthKit data stays on your device. Global (per Apple's own infrastructure) link

Public food databases

These are read-only public APIs we query for ingredient and product lookups. We send only the query string or barcode value — no user identifier or other personal data.

ServicePurposeData sentRegionTheir policy
USDA FoodData Central
U.S. Department of Agriculture
Ingredient and food search Search query string US link
Open Food Facts
Open Food Facts (non-profit, France)
Barcode → product lookups for packaged foods Barcode value EU (France) link

Change notifications

When we add, replace, or remove a sub-processor, we'll update this page and note the change in our app's changelog. Material changes (a new category of vendor, a region change, a change that meaningfully affects how your data is handled) will also be notified to you by email at least 14 days before they take effect.