Kalories privacy policy

Last updated: 22 October 2026

Kalories is a food tracker for iPhone made by Bradley Chapman ("we", "us").
This policy explains what happens to your information when you use it.

The short version

• There's no account and no sign-in. We don't run any servers of our own.
• Your meal log (with small photo thumbnails), water, weight, goals and
  settings are stored only on your iPhone. We never receive them.
• When you ask for an AI estimate, the meal photo or description you
  chose is sent to Google's Gemini API (through Google's Firebase) so it
  can work out the foods and nutrition. Kalories asks for your permission
  before it sends your first photo or description, and you can always add
  foods by hand instead.
• When you scan a barcode, only the barcode number is sent to Open Food
  Facts to look up the product.
• No ads, no tracking, no analytics of how you use the app, and we never sell
  or share your information for advertising.

What stays on your iPhone

Kalories keeps the following on your device only, in storage shared with the
Kalories widget:

• meals and foods you log, with their calories, protein, carbs, fat and fruit
  and veg, and a small copy of each meal photo (640 pixels)
• water, weight entries, meals saved in My meals, streaks and badges
• your goals and the body details you enter in the goal calculator (such as
  age, height, weight and activity level)
• your settings, such as reminder times and your buddy's name and look

None of this is sent to us or to anyone else. It's included in your iPhone's
own backups (iCloud Backup or a computer backup), which Apple handles under
its terms.

Your Koffee character. If Koffee or Koffee Tycoon is installed on the same
iPhone, Kalories reads the character you made there (its look and name) so
your buddy matches. That happens on the device; nothing is sent anywhere.

Reminders are notifications scheduled on your iPhone. There's no
notification server.

Widgets, Siri and Shortcuts read your totals on the device. If you talk to
Siri, Apple processes your request under
Apple's privacy policy.

Exports. If you export your log as a JSON or CSV file, it goes only where
you choose to send or save it. We don't receive a copy.

What leaves your iPhone, and why

AI estimates (Google Gemini through Firebase)

When you snap or pick a meal photo, or type a description, and ask Kalories
to estimate it, the app sends Google:

• the photo, shrunk to 1024 pixels on its longest side and saved fresh, so
  camera details and location data in the original aren't included
• any words you typed about the meal
• short notes you've asked Kalories to remember about how you eat (for
  example "my lattes are oat milk"), which you can see and delete in
  Settings → What your buddy knows
• Kalories' instructions to the AI, and the name of the AI model
• technical details needed to answer the request: a security token from
  Apple's App Attest (through Firebase App Check) that proves the request
  comes from the real Kalories app, and the app's Firebase app ID and
  version number

It does not send your name, your meal history, your weight or body
details, or anything from Apple Health. Google sends back the foods and
nutrition numbers, which you can edit before saving.

While Kalories is in testing, it uses the free tier of Google's Gemini
API. Under the
Gemini API Additional Terms of Service,
Google may use what's sent on the free tier (photos, descriptions and the
answers) to improve its products, and people at Google may review it. So
please keep faces, names and other personal details out of meal photos and
descriptions. Before Kalories is released to the public it will move to
Google's paid service, where Google doesn't use this content to improve its
products and keeps it only for a limited time to detect and prevent abuse,
and this policy will be updated first.
We have Firebase's AI monitoring turned off, so we can't see your photos or
descriptions either.

You stay in control: Kalories asks for your permission before your first AI
estimate, and you can add any meal by hand without sending anything. You can
also take back camera or photo access at any time in the iPhone Settings app.

App settings and security (Firebase)

When the app starts, it asks Firebase Remote Config which AI model to use.
Like every Firebase app, this request carries a random ID that Firebase
creates for this copy of the app (not your name or a device ID), plus basic
technical details such as the iOS version, app version, language, country
setting and time zone. Google uses these to send the right settings and, in
summary form, to understand which iOS and app versions are in use. Firebase
App Check uses Apple's App Attest (or DeviceCheck) to confirm requests come
from the genuine app, which stops others misusing the AI service.

Google acts as a service provider (a "data processor") for Firebase. See
Privacy and security in Firebase,
the Firebase terms
and the Google Privacy Policy.

Nutrition labels

When you photograph a nutrition label, Kalories reads the numbers on your
iPhone with Apple's built-in text recognition. Nothing is sent anywhere.

Siri and widgets

The "Log a saved meal" Siri shortcut and the Quick add widget work on your
iPhone with the meals in My meals. If you speak to Siri, Apple handles your
request under its own privacy policy.

Barcode lookups (Open Food Facts)

When you scan a packaged food's barcode, Kalories asks
Open Food Facts, a free, non-profit food
database, for that product. Only the barcode number is sent. Like any website,
Open Food Facts' servers see your internet (IP) address with the request; its
privacy policy explains how it keeps
server logs for security and statistics.

Apple Health (optional)

If you turn on "Use Apple Health", Kalories writes each meal's energy,
protein, carbohydrates and fat, your water and your weigh-ins to the Health
app on your iPhone. It reads your weight (so weigh-ins from scales and other
apps show in Trends) and, only if you turn on "Add exercise to my goal",
today's active energy. What Kalories reads from Health stays on your iPhone:
it is never sent to Google, Open Food Facts, us or anyone else. Apple's
Health app holds this data under Apple's terms. You can stop it at any time in Kalories' settings, or
turn off Kalories' access in the Health app (tap your profile picture, then
Apps, then Kalories).

What we don't do

• No accounts and no advertising. We don't use Google Analytics for
  Firebase or any other advertising or analytics SDK, and we don't record
  how you use the app.
• No tracking of you across other companies' apps or websites.
• No selling, renting or trading of your information, and no data brokers.
• Your information is never used to make decisions about you.

We only use services (Google and Open Food Facts) whose terms and privacy
policies protect your information at least as well as this policy does, and
only for the purposes described here.

How long information is kept

• On your iPhone: until you delete it. Deleting a meal removes it (and
  the Health entries Kalories wrote for it). Settings → "Erase all meals"
  deletes your whole log. Deleting the app removes everything Kalories
  stored. Anything already saved to Apple Health stays there until you
  delete it in the Health app, and files you exported stay wherever you put
  them.
• Google Gemini: under the Gemini API terms linked above: during testing
  (free tier) Google may keep and use it to improve its products; on the
  paid service, only for a limited time to detect abuse. Firebase AI Logic
  itself doesn't store it.
• Firebase: the random app ID is kept by Firebase until it's deleted;
  App Check keeps security tokens for at most 30 days. See
  Privacy and security in Firebase.
• Open Food Facts: as described in its privacy policy.

Your choices and rights

• Use "Add by hand" instead of AI estimates, or turn AI estimates off in
  Settings, and nothing about your meals leaves your iPhone.
• Turn off camera, photos, notifications or Health access in the iPhone
  Settings app (or the Health app) at any time.
• Delete meals one by one, use Settings → "Erase all meals", or delete
  the app to remove all its data.

Because we don't have accounts or servers, we hold no information that
identifies you, so there's nothing for us to look up, export or delete. If
you have a question or a request about your information (for example under
the GDPR, UK GDPR or California law), contact us at the address below and
we'll help, including with requests to Google about data sent through
Kalories.

Children

Kalories is meant for adults (18 and over). It isn't directed at children,
and we don't knowingly collect information from anyone under 18. Calorie
tracking isn't suitable for children.

Not medical advice

Kalories gives estimates to help you notice what you eat. They can be wrong,
and they aren't medical or dietary advice. Talk to a doctor or registered
dietitian before making big changes to what you eat, especially if you have a
health condition, are pregnant, or have had an eating disorder.

Where information is processed

Google and Open Food Facts may process information in the United States, the
European Union and other countries. Google states that it complies with the
EU-U.S. Data Privacy Framework and its UK and Swiss extensions.

Changes to this policy

If what Kalories does with your information changes, we'll update this page
and the date at the top before the app update that makes the change.

Contact

Questions about this policy or your information: hello@koffee-app.com