Privacy Policy

CalorieTracker for iOS · Last updated 4 August 2026

The short version. CalorieTracker has no accounts and no user database. Your profile, your food log, your photos, your weight history and your training history are stored on your iPhone.

Two things are sent out, both to the AI model you have chosen, and each covering only the entry you just made: a meal's photos and description, so it can be estimated; and a workout journal entry's text, so it can be tidied up and have the exercises picked out of it. There is no analytics SDK, no advertising, and no tracking.

Who this is from

CalorieTracker is an independent iOS app. Questions about this policy or about your data can go to daregroup9@gmail.com.

What stays on your device

The following is stored locally on your iPhone, in the app's own storage. None of it is ever transmitted to us — we operate no user database — and none of it goes anywhere else except in the two cases spelled out in the next section:

There is no cloud sync and no backup service operated by us. If your iPhone is backed up to iCloud or a computer, that backup is covered by Apple's privacy policy, not this one.

What leaves your device, and when

Two things are sent, and both go to the AI model you selected. Nothing else you have logged ever leaves the app. (If your build uses the shared proxy, that route also carries a random device identifier for quota purposes — described in full further down.)

In both cases only the entry you just made is sent. Your body profile, your weight, your calorie goal, your workout history, anything read from Apple Health, and your other entries are not included in either request.

Two possible routes

Which one applies depends on how your copy of the app is set up:

RouteWhat happens
Your own API key The app talks to the provider directly from your phone, under your key. Nothing passes through any server of ours.
Shared proxy The request passes through a small Cloudflare Worker we operate, which attaches the shared API key and forwards it to the provider. The proxy does not store your photos, descriptions or journal text — it passes them through and the response comes straight back.

Which providers

Depending on the model you pick, the recipient is Google (Gemini), Anthropic (Claude) or OpenAI (GPT). What each of them does with the data it receives is governed by their own terms:

Requests are not tied to a name, an email address or an account, because the app never asks you for one.

What the proxy keeps

If your build uses the shared proxy, it keeps a small amount of operational data — enough to stop one device from spending the shared key on everyone else's behalf, and nothing more:

ItemWhyKept for
A random identifier generated by the app on first launch Counts requests per device against a daily quota. It is a random value created on your phone — not your Apple ID, your phone number, your advertising identifier, or anything that identifies you. 36 hours
A device attestation key identifier (Apple App Attest) Confirms the request came from a genuine, unmodified copy of the app rather than from a lifted credential. 90 days
Short-lived attestation challenges A single-use value used during that check. 5 minutes
Operational logs (timestamps, status codes, errors) Diagnosing outages. Meal photos, descriptions and journal text are not written to logs. A few days, then discarded by Cloudflare

As with any internet service, Cloudflare processes the network request itself — including your IP address — in order to route it. See the Cloudflare privacy policy.

Permissions the app asks for

Every one of these is optional, and each is asked for at the point it is first needed rather than up front. Decline the camera or photo library and you can still log by typed description; decline Health or the microphone and the rest of the app is unaffected. The app requests no location, no contacts and no notifications, and it does not use the advertising identifier.

Tracking and advertising

There is none. CalorieTracker contains no analytics SDK, no crash-reporting SDK, no advertising, and no third-party trackers. It does not use the advertising identifier, does not build a profile of you, and does not share or sell data to anyone. Nothing is used for App Tracking Transparency purposes, which is why the app never shows that prompt.

Children

CalorieTracker is not directed at children and is not intended for anyone under 13. It collects no personal information knowingly from children. If you believe a child has used the app in a way that concerns you, contact us at the address above.

Deleting your data

Your rights

Depending on where you live, you may have rights to access, correct, export or delete personal data held about you — including under India's Digital Personal Data Protection Act, the EU/UK GDPR, and the CCPA. In practice this app holds almost nothing to exercise them against: your data is on your own device, under your own control, and we have no account records to hand over. For the limited proxy records described above, write to daregroup9@gmail.com.

Not medical advice

Calorie and macronutrient figures are estimates produced by an AI model from a photo or a description, and can be wrong. The calorie goal is calculated from a standard population equation, not measured from your body. Nothing in the app is medical, dietary or fitness advice; talk to a qualified professional before making decisions about your diet or training.

Changes to this policy

If this policy changes, the revised version will be posted at this address with a new date at the top. Material changes will also be noted in the app's release notes.