Privacy Policy

Your food diary is nobody’s business but yours.

The Last Calorie Tracker (“the app,” “we,” “us”) is built privacy-first. There is no account, and the diary you build stays on your iPhone. This page explains exactly what the app does and does not do with your information.

Last updated: June 26, 2026

The short version

  • No account, no sign-up, no email, no password — and no user profile on our servers.
  • Your food log, weights, goals, and settings live only on your device.
  • Only the specific meal text or photo you submit is sent out, to turn it into calories and macros.
  • Speech is transcribed on your iPhone — the audio never leaves it.
  • Apple Health is fully optional and off until you turn it on; Health data never reaches our servers.
  • No analytics SDKs, no advertising SDKs, no third-party trackers. We do not track you across apps or the web.

Who we are

The Last Calorie Tracker is an iOS app published by Unthinking AI, LLC. If you have any question about this policy or your privacy, contact us at info@ai-created.com.

No account, ever

You open the app and start tracking. We don’t ask for — and never collect — a name, email address, phone number, password, or any other identifier that would let us (or anyone) build a profile of you. There is nothing to log into, so there is no login to leak.

What stays on your device

The substance of the app — your food log, your learned corrections, your weigh-ins, your calorie and macro goals, and your settings — is stored locally on your iPhone and is never uploaded to us. It is not stored in iCloud’s document or photo sync, and we operate no server-side database of your meals.

The token that powers the optional Face ID / Touch ID app lock is kept in the iOS Keychain, device-only and non-syncing.

One small exception is the free-log counter — the number of free entries you’ve used before subscribing. It is stored in your own private iCloud key-value storage so it follows your Apple ID across your devices and survives reinstalls. It is just a count; it contains none of your food data, it stays inside your iCloud, and we have no access to it. There is still no account with us.

What leaves your device — and only when you ask

The app reaches the network only to do the thing you asked: turn a meal you logged into a nutrition estimate, or look up a barcode. Here is the complete picture:

DataWhere it livesLeaves device?
Food log, corrections, weights, goals, settingsOn your iPhone (on-device database)No
App-lock token (Face ID / Touch ID)iOS Keychain, device-onlyNo
Free-log counterYour private iCloud (your Apple ID)iCloud only — we can’t see it
Food text you typeSent to our API → OpenAI to estimate nutritionOnly the text you submit
Meal photoSent to our API → OpenAI to estimate nutritionOnly the image you submit
Your voiceTranscribed on your iPhone; only the text is sentAudio never leaves
BarcodeLooked up via Open Food FactsThe barcode number only
Apple Health dataRead/written locally via HealthKitNever to any server

When you log a meal by text, voice, or photo, the app sends just that one submission — the short text snippet or the single image — to our server, which forwards it to OpenAI to estimate calories and macros. Nothing about your identity is attached, because we don’t have it. Your existing diary is never included.

Voice and photos, specifically

Voice: when you speak a meal, the audio is transcribed on your iPhone using Apple’s on-device speech recognition. The audio recording never leaves your device — only the resulting text is sent for analysis.

Photos: when you log by photo, the app sends the single image you captured for that meal (downsized to a small square) to be analyzed. We do not access your photo library, and we don’t receive any other images, location data, or photo metadata.

Apple Health

Apple Health integration is entirely optional and off by default, behind separate toggles you control. When you turn it on, the app reads and writes Health data locally on your device through Apple’s HealthKit. Health data is never sent to any server — not ours, not OpenAI’s.

Everything the app writes carries its own source marker, so it’s clearly identifiable and never touches other apps’ data. You can disconnect at any time, and you can remove the data the app wrote to Health from within the app’s settings.

How the app talks to our server

Food parsing runs through a small server (our “API proxy”) so that the OpenAI key is held securely on the server and never shipped inside the app. To keep that proxy from being abused and running up costs, the app proves it is a genuine, unmodified copy of our app running on a real Apple device using Apple’s App Attest.

For this, we store an anonymous, per-install device key generated by your device’s Secure Enclave (a public key, a signature counter, and a random key identifier). This is a hardware credential, not a user identity: it is not your Apple ID, it isn’t linked to your name or contact details, and it carries none of your food data. We use it only to issue short-lived access tokens and to enforce fair-use rate limits.

Like any internet service, our server and hosting provider process your device’s IP address momentarily to deliver each request and to rate-limit abuse. We do not use it to build a profile of you or sell it to anyone.

The third parties involved

We rely on a few well-known services, and only for the narrow purposes below:

  • OpenAI — receives the meal text or image you submit, to estimate its nutrition. No name, account, or contact information is attached. Under OpenAI’s API terms, data sent through the API is not used to train their models; OpenAI may retain a submission briefly for abuse monitoring under its own policies.
  • Open Food Facts — receives a barcode number you scan, to look up the product. Only the number is sent.
  • Apple — provides App Attest (anti-abuse), the App Store and StoreKit (subscriptions), iCloud (your private free-log counter), and HealthKit. Your use of these is governed by Apple’s own privacy policy.
  • Vercel — hosts our marketing site and API proxy, and processes requests (including IP addresses) on our behalf to operate the service.

We do not sell or rent your data, and we have no advertising partners or data brokers.

Subscriptions and payments

Subscriptions are handled entirely by Apple through the App Store and StoreKit. We never see or receive your payment card, billing address, or Apple ID. Whether you’re subscribed is checked on your device against your App Store purchase — there is no payment account on our side.

No analytics, no tracking, no ads

The app contains no analytics SDKs, no advertising SDKs, and no third-party trackers. We don’t use the advertising identifier (IDFA), we don’t track you across other apps or websites, and we don’t build an advertising profile. In Apple’s App Privacy terms, we do not “track” you.

Keeping and deleting your data

Because your diary lives on your device, you control it. You can export a full CSV of your entries from Settings, and deleting the app removes its on-device data from your iPhone. Data the app wrote to Apple Health can be removed from within the app; your iCloud free-log counter is governed by your Apple ID and iCloud settings.

On our side, there is no diary to delete: we don’t keep a copy of your food log, photos, or the text you submit. A submission is processed in real time to return an estimate and is not saved into any profile. Routine, short-lived operational logs (for security and reliability) may briefly include technical request data such as timestamps and IP address; they are rotated automatically and are not used to identify or profile you.

Children

The app is intended for a general audience and is not directed to children under 13 (or the equivalent minimum age in your country). We do not knowingly collect personal information from children.

Your choices and rights

Depending on where you live, you may have rights under laws such as the GDPR or CCPA to access, correct, or delete personal data, or to object to its processing. Because we operate without accounts and don’t hold a profile tied to your identity, in practice your data is already in your hands: it’s on your device, you can export it, and you can delete it by removing the app. If you still have a request or question, email us at info@ai-created.com and we’ll help.

Where processing happens

The app is operated from, and the meal submissions you send are processed in, the United States by us and our service providers (such as OpenAI and Vercel). If you use the app from outside the United States, you understand that the limited data described above is processed there.

Changes to this policy

If we change how the app handles your information, we’ll update this page and revise the “last updated” date above. Material changes will be reflected here before they take effect.

Contact us

Questions about your privacy or this policy? Email info@ai-created.com. We read every message.