Kalorika Open in Telegram

Kalorika

Privacy Policy

Last updated: 2026-11-10

Kalorika is a food and calorie diary: an iOS app with an Apple Watch companion, an Android app with a Wear OS companion, a Telegram bot (@kalorika_gobot) and a Mini App. This policy covers all of them — they are one account and one database. The service is operated by Kalorika: the website is kalorika.net, the contact address is support@kalorika.net.

In short

  • We store the diary you create — meals, photos, weight, workouts, your questions to the assistant — and nothing beyond what the service needs to work.
  • Apple Health and Health Connect data are read only with your permission, leave the device only as day totals and workout sessions, and are never used for advertising. Outside our own server it reaches two recipients only: a trainer or nutritionist, if you connect one and open sections of your diary to them, and the AI provider that prepares the assistant’s answer — only if you have agreed to it separately (see «AI and your Health data»), only when you write to the assistant or ask for a weekly review, and only as day totals, averages and workout records, without your name or e-mail. Both are described below.
  • There are no advertising or analytics SDKs in the app, no tracking across other apps and websites, and we sell data to nobody.
  • You can delete your account from the app — or, if you use only the Telegram bot, by writing to us. Deletion starts a 30-day countdown, after which the account and what is in it are erased; what is deleted separately is listed below.

Apple Health

Health access is off until you turn it on in Settings → Apple Health, one purpose group at a time. Each group is a separate iOS permission sheet, each can be refused, and you can revoke any of it later in iOS Settings → Privacy & Security → Health → Kalorika. If you refuse a group, only that group’s data will be missing from the diary — everything else works as before.

What we read

Body

so weight and composition appear in the diary without being retyped

  • Weight HKQuantityTypeIdentifierBodyMass
  • Body fat percentage HKQuantityTypeIdentifierBodyFatPercentage
  • Lean body mass HKQuantityTypeIdentifierLeanBodyMass
  • Height HKQuantityTypeIdentifierHeight
  • Waist circumference HKQuantityTypeIdentifierWaistCircumference

Energy and activity

so your expenditure is measured instead of guessed from a formula

  • Active energy HKQuantityTypeIdentifierActiveEnergyBurned
  • Resting energy HKQuantityTypeIdentifierBasalEnergyBurned
  • Steps HKQuantityTypeIdentifierStepCount
  • Walking and running distance HKQuantityTypeIdentifierDistanceWalkingRunning
  • Cycling distance HKQuantityTypeIdentifierDistanceCycling
  • Swimming distance HKQuantityTypeIdentifierDistanceSwimming
  • Flights climbed HKQuantityTypeIdentifierFlightsClimbed
  • Exercise minutes HKQuantityTypeIdentifierAppleExerciseTime
  • Stand minutes HKQuantityTypeIdentifierAppleStandTime
  • Workouts HKWorkoutTypeIdentifier
  • Heart rate (a workout’s average and maximum only) HKQuantityTypeIdentifierHeartRate

Recovery

so sleep and pulse can explain a week that did not go to plan

  • Resting heart rate HKQuantityTypeIdentifierRestingHeartRate
  • Heart rate variability (SDNN) HKQuantityTypeIdentifierHeartRateVariabilitySDNN
  • Sleep HKCategoryTypeIdentifierSleepAnalysis
  • VO₂ max HKQuantityTypeIdentifierVO2Max

Water

so water logged elsewhere counts here too

  • Water HKQuantityTypeIdentifierDietaryWater

Cycle data

Menstrual flow is read only if you switch it on yourself. It is off by default, it is never part of a group’s permission request, and switching it off stops the reading.

  • Menstrual flow HKCategoryTypeIdentifierMenstrualFlow

What we never ask for

The app does not request these types at all. The nutrients are ones we write, not read — reading them back would double-count our own meals:

  • Dietary energy HKQuantityTypeIdentifierDietaryEnergyConsumed
  • Protein HKQuantityTypeIdentifierDietaryProtein
  • Total fat HKQuantityTypeIdentifierDietaryFatTotal
  • Carbohydrates HKQuantityTypeIdentifierDietaryCarbohydrates
  • Respiratory rate HKQuantityTypeIdentifierRespiratoryRate
  • Blood oxygen HKQuantityTypeIdentifierOxygenSaturation

What leaves your device

The app sends two things to our server: one row of totals per calendar day, and one record per workout session (technically, the request POST /api/health/sync). Nothing else — no raw samples, no series, no minute-by-minute data, no location.

  • A day row: weight, body fat, lean mass, waist, active and resting energy, steps, distance, flights, exercise and stand minutes, water, resting pulse, heart rate variability (HRV), sleep (total, deep, REM), VO₂ max — and, if you enabled it, the day’s menstrual flow mark. Days are cut in the timezone saved in your profile.
  • A workout: start time, duration, type, calories, distance, average and maximum heart rate during that workout, the name of the app that recorded it, and its HealthKit identifier — which we store only so the same workout is not imported twice.

Health values are never written to our server logs. The log lines about a sync hold only how many records arrived and their identifiers — never the values themselves.

What we write back

With your separate permission the app writes your own entries back into Health, so other apps can see them. Nothing is written without that permission, and we never delete or modify data another app wrote:

  • Dietary energy HKQuantityTypeIdentifierDietaryEnergyConsumed
  • Protein HKQuantityTypeIdentifierDietaryProtein
  • Total fat HKQuantityTypeIdentifierDietaryFatTotal
  • Carbohydrates HKQuantityTypeIdentifierDietaryCarbohydrates
  • Water HKQuantityTypeIdentifierDietaryWater
  • Weight HKQuantityTypeIdentifierBodyMass

Health Connect (Android)

On Android the same data comes from Health Connect — where Samsung Health, Mi Fitness, Zepp, Fitbit and most scales and watches put theirs. Access is off until you allow it in the app: a screen explains it first, then Health Connect’s own window asks for the types below, and you can take any of them back in Health Connect’s settings. The app checks what it may read every time it starts.

On a Wear OS watch paired with the Android app, a workout started in Kalorika reads the heart rate and the activity from the watch’s sensors while it runs (Health Services, once the watch has asked for them). When it ends, its time, length, average and maximum heart rate, calories burned and distance are sent to your account like any workout, and nothing of it stays on the watch.

What we read

Body

so weight and composition appear in the diary without being retyped

  • Weight android.permission.health.READ_WEIGHT
  • Body fat android.permission.health.READ_BODY_FAT
  • Lean body mass android.permission.health.READ_LEAN_BODY_MASS
  • Height android.permission.health.READ_HEIGHT

Energy and activity

so your expenditure is measured instead of guessed from a formula

  • Active calories android.permission.health.READ_ACTIVE_CALORIES_BURNED
  • Resting energy (basal metabolic rate) android.permission.health.READ_BASAL_METABOLIC_RATE
  • Total calories burned android.permission.health.READ_TOTAL_CALORIES_BURNED
  • Steps android.permission.health.READ_STEPS
  • Distance android.permission.health.READ_DISTANCE
  • Floors climbed android.permission.health.READ_FLOORS_CLIMBED
  • Exercise sessions android.permission.health.READ_EXERCISE
  • Heart rate (a workout’s average and maximum only) android.permission.health.READ_HEART_RATE

Recovery

so sleep and pulse can explain a week that did not go to plan

  • Resting heart rate android.permission.health.READ_RESTING_HEART_RATE
  • Heart rate variability (RMSSD) android.permission.health.READ_HEART_RATE_VARIABILITY
  • Sleep android.permission.health.READ_SLEEP
  • VO₂ max android.permission.health.READ_VO2_MAX

Water

so water logged elsewhere counts here too

  • Hydration android.permission.health.READ_HYDRATION

Where Health Connect supports them, the same window also asks for these two, so that the past reaches your analytics and new data arrives with the app closed:

  • History older than 30 days android.permission.health.READ_HEALTH_DATA_HISTORY
  • Reading in the background android.permission.health.READ_HEALTH_DATA_IN_BACKGROUND

Cycle data

Menstrual flow is read only if you switch it on yourself. It is off by default, it is never part of a group’s permission request, and switching it off stops the reading.

  • Menstruation android.permission.health.READ_MENSTRUATION

What we never ask for

The app does not request these types at all. The nutrients are ones we write, not read — reading them back would double-count our own meals:

  • Nutrition android.permission.health.READ_NUTRITION
  • Respiratory rate android.permission.health.READ_RESPIRATORY_RATE
  • Blood oxygen android.permission.health.READ_OXYGEN_SATURATION

What leaves your device

What leaves the phone is the same as on the iPhone: one row of totals per calendar day and one record per workout session, through the same POST /api/health/sync — including the Health Connect record id of a workout, so it is imported once, and the package name of the app that recorded it.

What we write back

With a separate switch, off by default, the Android app writes your diary’s food and water and the weight you type into Health Connect, under the diary line’s own id, so an edited line replaces its record and a deleted one deletes it. Nothing another app wrote is changed:

  • Nutrition (your diary’s food) android.permission.health.WRITE_NUTRITION
  • Hydration (your diary’s water) android.permission.health.WRITE_HYDRATION
  • Weight (a weight you type in the app) android.permission.health.WRITE_WEIGHT

Our three promises about Health data

  • It is never used for advertising or marketing — ours or anyone else’s.
  • It is never sold or disclosed to advertisers, data brokers, insurers or employers. Besides you and our server, it is seen by a specialist you connect yourself — only the sections you open, only while you keep them connected — and, only if you have agreed to it, by the AI provider that prepares the assistant’s answer: only when you write to the assistant or ask for a weekly review, as totals, averages and workout records, without your name or e-mail.
  • It is used for one purpose: showing you your own numbers, computing your targets and trends, and answering the questions you ask the assistant.

AI and your Health data

Your weekly review and the assistant’s answers are written by AI models (OpenAI and Google Gemini). Numbers derived from Apple Health or Health Connect — steps, active energy, sleep, resting heart rate, heart rate variability, body composition, a workout’s heart rate and the burn a watch measured — reach those models only if you have agreed to it on a separate consent screen in the app.

Without that consent the review and the assistant still work, on your diary and the numbers you type yourself; the Health-derived numbers are left out of what the model receives. You can give or withdraw the consent at any time in the app’s settings, and the next review and the next answer follow it.

Menstrual cycle data never reaches an AI model, whether you have agreed or not.

Assistants you connect (ChatGPT, Claude and others)

You can connect Kalorika to a third-party AI assistant — ChatGPT by OpenAI, Claude by Anthropic or Gemini by Google. Nothing is shared until you start the connection in the assistant yourself and allow it on Kalorika’s page or in the app (Settings → Assistants). It needs Premium or the period of full access.

Once allowed, the assistant can read your food and water diary, daily totals, weight and its trend, workouts, profile, goals, analytics and weekly review for the last 90 days — nothing older — and, only if «Health data for the assistant» is on, activity, sleep, heart rate and body composition from Apple Health or Health Connect (never the cycle). It can log food, water, weight and workouts, correct today’s entries, save products of your own, and — only after you confirm — add a barcode to Kalorika’s shared product base, where its name and numbers are seen by others. It does not get your password, your sign-in details or payment information. In «no numbers» mode it gets the diary without calories, macros or weight.

That data then goes to the assistant’s provider and is handled under that provider’s own terms and privacy policy, outside Kalorika. You can end the connection at any time in the app (Settings → Assistants → Disconnect), in the assistant’s settings, or with «Sign out everywhere»; it stops at once. We keep a record of the connection (which assistant and when it was last used) while it is active.

What we store

  • Account: e-mail (if you registered with one) or Apple’s anonymous identifier for Sign in with Apple, or your Google account’s identifier for Sign in with Google, your Telegram id if you use the bot, a password hash if you set a password, and your active device sessions.
  • Profile and goal: sex, age, height, weight, target weight, pace, activity answers, timezone, language, reminder time, notification switches.
  • The diary: meals with their calories and macros, the photos you send, barcodes you scan, corrections, workouts, water, daily metrics and the trends computed from them. When you type in a package’s numbers for a barcode no database knows, the product — the code, its name, the numbers per 100 g and the package size — goes into our shared barcode table and other users who scan that code see it, without your name; it stays there if you delete your account.
  • Your conversation with the assistant: the messages you write and the answers it gives, because the diary is built out of them.
  • Payments: records of earlier payments in Telegram Stars — the amount, the date, the period paid for and Telegram’s identifier of the payment — and a record of access we gave you free of charge. No new payments are taken at the moment. We never see or store card details.
  • Technical counters: feature usage counts, request counts per day, error events. Used to keep the service running and to see which features are used at all.
  • Devices and notifications: for each device you signed in on — its model, the app version, when it was last active and the push token Apple or Google issued for it, so that notifications reach it; and the list of notifications we sent you, kept for 30 days.
  • Messages to support and our replies: what you write through Feedback in the app or to the bot, an answer of the assistant you marked as wrong (together with that answer), and the replies we sent you. A letter to our support address is kept in our mailbox.
  • Visits by our marketing links and clicks on the store and Telegram buttons of the website: the campaign label, the time, the IP address, the browser’s user-agent line and the website you came from, without the page (see “Advertising and tracking” below).
  • Kalorika Coach, if you use it: who you connected, which sections you opened and when, the wording you agreed to, when the specialist looked, the “About me” card if you filled it in, the specialist’s remarks and your replies, and the changes to your target with who made them.
  • If you are a specialist in Kalorika Coach: your name and speciality, the contact you gave for clients, your country and units, the terms you accepted and when, your notification settings, your notes about clients, and — if you filled it in — the rating card: city, a text about yourself, date of birth (shown only as an age), the year you started, directions of work, languages, format and a photo; and your replies to reviews about you, each with the version of the publication notice you saw when sending it. The card is public only while you keep it switched on.
  • The waiting list on the website, if you joined it: your e-mail address, the language and the platform you chose, and where you came from. It is used for at most two letters and nothing else: a confirmation right after you join, and one letter when the app you are waiting for is released. Every letter has a link that stops the letters, and we delete the address at your request. The list is not tied to an account.
  • A review or a story for the website, if you wrote one: the name or nickname you chose to be shown under, the text, the rating (a review), how many months it took (a story), and — only if you ticked the box for it — your weight at the start and now and up to two photos (we re-encode a photo before storing it, so the location and other hidden data in the file are not kept); also which consents you gave, when, and under which wording. It is public only after we check it and only while it is approved, and it is shown with the date it was published. We may correct a typo, shorten it, decline it or hide it. You can change or delete it with your personal link — a link works for 7 days, and the bot (/story, /rate) or the settings of the app give a fresh one — or by writing to support; a deleted text is removed, not hidden.
  • A review of your specialist, if you wrote one: the rating, the text, whether your first name is shown with it, and the version of the publication notice you saw when sending it. It is public only after we check it and only while it is approved.
  • A comment on the website, if you left one: the name you gave, your e-mail address and the text. The comment is published under that name; the address is not shown on the page. The address is used to find the comment if you ask us to delete it and to refuse the same text sent twice; an answer from the team appears on the page, not in your mail. A comment is public only after we check it. It is not tied to an account, so deleting an account does not remove it: to have one deleted, write to support from that address.

On what grounds we process data

Each kind of data has its own ground:

  • The account, the profile, the diary, the conversation with the assistant, devices and notifications — to provide the service you asked for, that is, to perform our agreement with you (the terms of use).
  • Apple Health data, cycle data and the “About me” card for a specialist are information about health; we process them only with your explicit consent. You give it when you yourself switch on a Health group or the cycle switch, fill in the card or open a section to a specialist, and you withdraw it when you switch that off or clear the card.
  • Server logs, technical counters, request limits and the records of marketing links — our legitimate interest: keeping the service running, protecting it from abuse and seeing what is used.
  • The waiting-list e-mails, and the publication of your story, review or comment — your consent; you withdraw it by unsubscribing through the link in the e-mail or by deleting the text.
  • Payment records — to perform the agreement (to open the access you paid for) and, where the law requires such records to be kept, to meet that obligation.

Sharing with your specialist

A trainer or nutritionist who uses Kalorika Coach can invite you. Nothing is shared until you accept on a consent screen that names them, lists every section with its own switch (all off at first) and asks you to tick a box yourself. We record what you agreed to, under which wording, and when.

The specialist sees only the sections you open: food, food photos, weight and measurements, workouts, activity and sleep from Health, how you feel. Menstrual cycle data is never shown to a specialist, whatever you choose. The specialist also sees your first name. Your Telegram username is shown only if you turn on its own switch, and stops being shown when you turn it off.

There is also a card called “About me, for my specialist” (the specialist sees it as “About the client”). You fill it in yourself and only if you want to: allergies, food restrictions, health conditions, and three marks — pregnancy, diabetes, an eating disorder. This is information about your health, and every specialist you have connected can read it, whichever sections you opened. Leave it empty if you do not want that; you can clear it at any time. The weekly report works the same way: if you send one — how the week went and, if you like, what was hard, what worked and a question — every specialist you have connected reads it; we keep the reports while your account exists.

Besides looking, the specialist can: change your calorie and macro target — only if you allowed it on the consent screen, and you see every change and who made it; leave a remark or a reaction on a meal or a day, if the food section is open — you get a notification, see it in your diary and can answer with one line, which the specialist sees; and keep a private note about you, which you do not see. After you disconnect, the remarks stay in your diary, and the private note is deleted 30 days later.

You can change the set of sections or disconnect the specialist at any moment, without asking them; access ends at once, past days included. You see when the specialist last looked at your data.

Connecting to a specialist is possible only from the age of 18: the age in your profile is checked when you accept an invitation.

The specialist is not our employee. Before seeing any client they accept terms: the data is used only to work with you, never exported, copied, sold or passed on. They state their own speciality; we do not check diplomas.

The specialists’ rating. A specialist can switch on a public card in the rating — on our website and in the apps. The card always shows their name, speciality, photo (if they added one), country and city; a text about themselves, their age (whole years, never the date of birth), the year they started, directions of work, languages and format are shown only if the specialist switched each of them on. No contact details are published. A client who has been connected to the specialist for at least 7 days can leave a rating and a review. It appears after our moderators check it — without the client’s name, unless the client chose to show their first name — and the client can change or delete it at any time. The order in the rating is calculated from the clients’ reviews. The specialist can reply to a review; the reply appears under it after the same check. A specialist can report a review about them, and anyone signed in to the app can report a review, a reply or a card; what was reported stays visible until our moderators decide. For a report we store which account sent it, what it is about, the reason chosen and the note, and what was decided; it is kept until it is decided and for 180 days after that, then deleted.

Who else processes it

We use a small number of providers, each for one job:

  • OpenAI and Google (Gemini) — recognising food from a photo, voice or text, and generating the assistant’s answers and the weekly review. They receive the photo or text you sent and the context the answer needs: your targets, your sex, age, height and weight from the profile, the relevant part of the diary and your recent workouts, and — for questions about activity, sleep or progress and for the weekly review — totals and averages derived from Apple Health or Health Connect, only if you have agreed to it (see «AI and your Health data»). They do not receive your e-mail, your name or any advertising identifier, and never the cycle data.
  • Telegram — the bot and the Mini App, for accounts that use them, and the earlier payments in Telegram Stars.
  • Apple — Sign in with Apple and push notifications.
  • Resend — sending our e-mail: the confirmation code, the password reset, the two waiting-list letters, a reply from support or a notice that a story or review was not published (for people who do not use Telegram), and the morning digest for a specialist in Kalorika Coach when a push did not reach the phone. Resend receives the address and the text of the letter.
  • DigitalOcean — the server and the database the service runs on.
  • Cloudflare — every request to the website and to our server passes through its network, which protects the connection; on the way it processes the IP address and the request. It also forwards mail sent to our support address to our mailbox.
  • Open Food Facts — when you scan a barcode, our server asks this open product database for the product with that code; when the assistant looks for a food by name that our own tables do not have, it sends that food’s name to the database’s search. It receives the barcode number or the food’s name and nothing about you.
  • Google — Sign in with Google, and push notifications to the Android app through Firebase Cloud Messaging: it receives the device’s push token and the text of each notification.

Where the data is processed

The diary is stored on our server and in our database, which we rent from DigitalOcean.

The providers listed above — OpenAI, Google, Telegram, Apple, Resend, Cloudflare and Open Food Facts — process data on their own infrastructure. It may be outside your country and outside the European Union and the European Economic Area.

We send them only what that list names, and only for the job named there.

Advertising and tracking

The app contains no advertising SDK and no third-party analytics SDK. We do not track you across other apps or websites, we do not build advertising profiles, and we do not sell or rent your data. Our own marketing links (for example /l/<source>) and the store and Telegram buttons on the website record each open and click on our server: the campaign label, the time, the IP address, the browser’s user-agent line and the website you came to us from (only the site’s name, never the page or a search query). We use these records to count opens and clicks per campaign; they are not tied to an account, and we do not build a profile of a person from them. They are deleted after 90 days. If you start the bot from such a link, the campaign label is saved with your account. The apps also tell our server which onboarding step you reached, whether you finished or skipped the first-run tour and when they asked the store to show its rating request — the name of the step only, never what you entered. These records are kept with your account to count how many people get through each step, and are deleted with it.

How long we keep it, and how to delete it

  • Your data is kept while your account exists — a food diary is only useful with its history.
  • Deleting the account: Settings → Delete account in the app (technically, the request DELETE /api/account). If you use only the Telegram bot, which has no such screen, write to support@kalorika.net or to the bot, and we start the same deletion for you. We do not erase on the spot, because one accidental tap would cost months of diary. Instead the account is marked, every device session is signed out, a connected specialist loses access at once, and 30 days later the account is erased automatically.
  • Changing your mind is enough to cancel it: any login, or any message to the bot, clears the mark during those 30 days.
  • Erased together with the account: the profile, meals and what they consist of, the conversation with the assistant, workouts, daily metrics and trends, usage counters, payment records, device sessions and push tokens, notifications, your messages to support and our replies, the photo files; your connections with specialists, with their remarks, notes and the records of your consents; your story and your review for the website with their photos; a review you wrote about a specialist and your reports about the rating; and, if you are a specialist, your profile, the rating card with its photo, the reviews about you, your replies to them and the reports about your page. Messages you sent to the bot also stay in your own Telegram chat — delete them there.
  • Backup copies of the database: an automatic copy is made every 5 days and deleted once it is older than 14 days, so an erased account is gone from the automatic copies within 20 days. A copy we make by hand before a risky update is deleted once it is older than 30 days — at the latest 36 days after it was made.
  • Not part of an account, and so not erased with it: a comment on the website and an address on the waiting list — each is deleted at your request, as described above — and the records of marketing links, which name no account.
  • Health specifically: revoking permission in iOS Settings or in Health Connect’s settings stops new data immediately. Workouts and diary entries already imported can be deleted one by one in the app, and all of them go when the account is erased.

The periods in one place

  • The account and everything in it — while the account exists; after a deletion request, 30 more days, then it is erased.
  • Automatic backups of the database — an erased account is gone from them within 20 days.
  • The list of notifications sent to you — 30 days.
  • A specialist’s private note about you — 30 days after the specialist is disconnected.
  • A personal link for changing a story or a review works for 7 days.
  • A comment on the website and an address in the waiting list — until you ask us to remove them.
  • The records of marketing links and of the website’s store and Telegram buttons — 90 days.
  • A backup we make by hand before a risky update — 30 days (deleted at the latest 36 days after it was made).
  • No set period yet: the server log (it is cleared with every update of the server) and mail in the support mailbox.

Your rights

With regard to your data you can:

  • find out what data we hold about you and get a copy of it: the iPhone app’s Settings → «Download my data», «My data» in the Mini App’s settings, or /export in the bot give the whole account as one file; photos are not in it and are sent when you write to us;
  • correct data that is inaccurate;
  • delete data or the whole account;
  • ask us to restrict the processing, or object to it, where it rests on our legitimate interest;
  • withdraw a consent at any time — this does not affect what was done before you withdrew it.

Much of this is done in the app itself: your diary and profile are visible there, and there you can correct them, switch off access to Health, disconnect a specialist and delete the account. For everything else, or with a question about this policy, write to support@kalorika.net. We answer within 30 days.

If you think we handle your data wrongly, you can complain to the data-protection authority of the country where you live.

Age

You must be 18 or older to use Kalorika. If you are 16 or 17, you may use it only with the consent of a parent or guardian. It is not for anyone under 16. We do not verify age at sign-up — you state it yourself; the one place where the age in the profile is checked is connecting to a specialist, which is possible only from 18.

Not medical advice

Kalorika estimates calories, macros and expenditure. These are estimates for your own planning, not a diagnosis, not a treatment and not a medical device.

Contact

Write to us by e-mail or to the bot, or use Feedback in the app’s settings:

support@kalorika.net

Telegram: @kalorika_gobot