Privacy Policy
Last updated: 6 September 2026
Calsense is a nutrition-tracking app. This policy explains what data Calsense handles. The short version: Calsense has an account, and your diary is saved to it — the meals you log, your water, your supplements, your measurements and the answers you gave during setup — so it comes back after a reinstall or on a new phone. Meal photos are saved to your account too, and are not kept on the phone. When you ask for a dish to be analysed, what you send — a description, or a photo of your plate — goes to our server and to an AI provider to make the estimate; the photo is then stored with your account, and the description and the answer are kept as a record of the request. Calsense contains no advertising and no cross-app or cross-site tracking. It does use one analytics service, PostHog, described below. Each of those is explained below.
What Calsense saves to your account
This section changed on 29 August 2026. It used to say the diary was stored only on your device and was not synced. It is now saved to your account on our server, so that it survives a reinstall and is there on a second phone.
What we hold, per account: the meals you log (the dish name, the weight, which meal of the day it was, when you logged it, the nutrition figures and any note you wrote), your water totals per day, your supplement checklist per day, your body measurements, and the answers you gave during setup — your goal, activity level, dietary patterns, health conditions, calorie and macro targets, hydration target, supplement selections, unit preferences and, if you gave it, your ethnicity.
This changed again on 13 September 2026: meal photos are now part of it, and the phone keeps none. This section used to say a picture stayed in the app's own storage and that a reinstall restored your diary but not its pictures. Both are now the other way round.
A photo you send for an analysis is stored with your account, in two sizes. Your diary carries a reference to it rather than the picture itself, so a reinstall or a second phone shows your photos along with the rest of the diary. The phone holds no copy at all, which means that with no connection the app shows a food icon in place of a picture rather than a stale one.
Before anything is stored, each photo is decoded and written out again. That removes the location, the capture time, the device identifier and everything else a camera writes alongside the image. What we keep is the picture, never a record of where you were.
Deleting a meal does not delete its photo. The record of the analysis that produced the meal refers to the same picture, so the picture outlives the entry. Deleting your account deletes every photo with it, and that is the only thing that removes one. The app says this on the screen where you delete a meal.
The app keeps a copy of everything on the phone as well, which is why it opens instantly and works with no signal. Anything you log offline is saved to your account as soon as there is a connection. Signing out removes that local copy from the device; signing back in restores it from your account.
Your account
Calsense requires an account, created with Sign in with Apple or Sign in with Google. Either way the provider gives us two things: an identifier that stands for you within our apps, and an email address — your real one or, with Apple's Hide My Email, a private relay address Apple manages. We never see your Apple or Google password. Accounts made with different providers are joined only when their verified email addresses match; otherwise they are separate accounts.
On our server we store that identifier, that email address, and session records — which app you signed in to, an identifier for the device, and timestamps — so you stay signed in and can see and revoke your sessions.
If you enter them, your basic profile — birth date, sex, height and weight — is saved to that account so our other health apps you sign in to can share it, and so you do not type it twice. Each of these fields is optional; one you have not entered is simply absent.
When you ask for a dish to be analysed, we also record that an analysis happened — which account, which app, and when — so we can limit how many analyses a day each account gets. That record says nothing about the food. That is the complete list of what our server holds about you.
Food analysis
Calsense first looks a dish up in a reference list built into the app, on your device. When the dish is not in that list and you ask for it to be analysed, what you submit is sent to our server: the description you typed, and — when you use the camera or choose a picture — a photo of your plate. The server passes it to Anthropic, the AI provider whose model produces the nutrition estimate, and returns the estimate to your phone. Our server does not keep the description or the photo. The meal entry the estimate becomes is saved to your account, and so is the photo — see the section above for how long, and for what is stripped from it first. Anthropic processes what it receives as a service provider under its commercial terms, which do not permit it to train models on this data; how long Anthropic retains it is governed by those terms, not by us. A photo can show more than food — a face, a room, a document on the table — so frame the plate, and do not put personal details in a dish description.
What we do not do
- We do not store your meal photos. Your diary is saved to your account; the pictures are not, and a photo you explicitly send for analysis is transmitted to make the estimate and is not kept by our server.
- We do not sell, rent or share your data with anyone.
- We do not track you across other companies' apps or websites, build an advertising profile of you, or serve advertising.
- We use two third-party SDKs that receive data: PostHog, limited to the events listed under “Product analytics” above, and Firebase Crashlytics, which receives the crash reports described there. We do not use an advertising SDK.
Product analytics
Calsense uses PostHog for product analytics. It records how the app is used so we can find what is broken and what is confusing. It is deliberately narrow, and this list is exhaustive:
- Screen views — the name of the screen you opened, e.g. "today" or "settings".
- Sign-in outcomes — that a sign-in succeeded or failed, and which provider (Apple or Google) was used. Cancelling a sign-in sheet records nothing.
- Error reports — the type of an error and where in the app it happened.
- Crash reports — if the app crashes, the technical report of where it stopped: the stack, your device model and its iOS version. No part of your data is in it.
- Every event carries the app's name, so events from Calsense can be told from those of our other apps.
What analytics never receives: the meals or foods you log, your calorie or macro numbers, dish names, meal notes, your photos, your body measurements, or any answer you gave during setup. Those values are not sent to PostHog by any code path in the app.
These events are not linked to you. The app never sends your user id, your email address or your name to PostHog, and never asks it to build a profile of you. PostHog does receive the technical information any network request carries, including your IP address, and it acts as our processor under our instructions. It does not sell your data or use it for advertising, and we do not combine these events with data from other companies' apps or websites.
Deleting your data
What is stored on your device goes when you delete the app. Your account keeps its own copy of what you have logged — the diary, water, supplements, measurements, setup answers and the analysis records — and deleting the app does not remove that.
If your device backs up to iCloud, your Calsense data may be included in that backup. That backup is between you and Apple under Apple's terms; we have no access to it.
Children
Calsense is not directed at children under 13, and we do not knowingly collect data from them.
Changes
If this policy changes, the date at the top of this page changes with it. This version was written ahead of photo analysis shipping, as an earlier version promised it would be: if Calsense ever sends anything further off your device, this page will say so before it does.
Contact
Questions about this policy? Write to resources@thetinyapp.com.