Kalipr privacy policy
Last updated 13 November 2026
Kalipr is a personal health app being tested by a small group of invited people through Apple's TestFlight. It brings body, nutrition and activity data together on the iPhone. This page explains what it collects and where that data goes.
Health data stays on the phone
Everything Kalipr shows (weight, body composition, nutrition, workouts and activity) is stored in a database inside the app on the phone. There is no Kalipr server that holds health data. Deleting the app deletes that data. It is included in the phone's normal iCloud or computer backup, like other app data.
Apple Health
With permission, Kalipr reads the Apple Health types it displays, such as weight, body fat, workouts, active energy and nutrition. With permission, it can also save nutrition entered in Kalipr to Apple Health. Data from Apple Health is never used for advertising, never sold, and never shared with anyone else.
Screenshots
Kalipr can read screenshots on the iPhone itself, with Apple's built-in text recognition; those screenshots never leave the phone. On iPhones with Apple Intelligence, Apple's on-device model also answers meal descriptions, exercise names and chart requests on the phone; nothing leaves it. In versions of the app that use Apple's Private Cloud Compute, typed meal descriptions and chart requests are answered there when the phone is online; Apple states that Private Cloud Compute keeps no request data and that not even Apple can read it. Offline, they are answered on the phone.
When someone with Kalipr's own screenshot reading chooses a screenshot for Kalipr to read (for example a nutrition or body composition summary from another app), the phone shrinks the image and sends it to Kalipr's screenshot function, which runs on Cloudflare. The function passes it to Anthropic's Claude API to read the numbers, and sends the numbers back to the phone. Neither the image nor the numbers are kept by the function. Anthropic does not use data sent through its API to train its models. Only the numbers are saved, on the phone.
When someone types a request for a chart on the Reports tab (for example "show it weekly"), the words and the chart's current setting (which data points and which kind of chart) go to the same function and on to Claude, which answers with a new chart setting. No health data is sent with them, and nothing is kept.
Food search, barcodes and meal estimates
When someone searches for a food or scans a barcode, the words or the barcode number go through the same function to the public food databases USDA FoodData Central and Open Food Facts, and the matching foods come back. When someone asks for an estimate of a meal, the description and, if one is taken, the meal photo go through the function to Anthropic's Claude API, as with screenshots. The function keeps none of it. Foods that get logged are saved on the phone only.
Accounts
Kalipr needs an account so access can be approved for invited testers.
- Sign in with Apple: Kalipr receives Apple's anonymous user ID for this app and, if shared, a name. It does not ask for an email address.
- Email sign-up: Kalipr keeps the email address and a salted hash of the password (never the password itself).
For each account the function keeps only the user ID, the name given, the email for email accounts, and whether access is pending, approved or declined. No email is ever sent to it.
What is not collected
No advertising, no tracking across apps or websites, no analytics, and no selling or sharing of personal data. App updates are downloaded from Expo, which, like any web service, sees the phone's IP address when it does.
Deleting data
Settings → Account → Delete account removes the account (name, user ID, email login and access status) from the function and erases all data Kalipr holds on the phone. Data in Apple Health stays in Apple Health. Deleting the app also erases everything on the phone.
Children
Kalipr is not intended for anyone under 16.
Changes
If this policy changes, the date at the top will change and testers will be told in the app's TestFlight notes.