Kaloria Privacy Policy
Kaloria is an AI-powered food and nutrition tracker operated by AI Chat & Voice Systems ("Kaloria", "we", "us"). This Privacy Policy explains what data the Kaloria app and the kaloria.ai website collect, why we collect it, who we share it with, how long we keep it, and the choices you have.
Kaloria works without an account: your food journal lives on your phone. From version 2.0 you can optionally sign in to back up your journal and sync it between devices. This policy covers both ways of using the app. By using Kaloria you agree to the practices described here. If you do not agree, please do not use the app.
Questions or requests: info@kaloria.ai. Terms of Service: kaloria.ai/terms-of-service.html. How to delete your data: kaloria.ai/delete-account.html.
1. Information We Collect
Account and contact information (only if you sign in). Your e-mail address and, if you sign in with Apple or Google, the name and e-mail those services share with you (Apple may give us a private relay address instead of your real one). We use a one-time code sent by e-mail to verify addresses; we never store passwords. We also keep a list of the devices signed in to your account.
Food journal and health data. The meals you log (food names, portions, calories and nutrients, meal photos and descriptions), weight, water intake, workouts, your nutrition goals, dietary preferences and the profile details you enter during onboarding (age, sex, height, weight, activity level, goal). With your permission, data read from Apple Health or Google Health Connect (see section 4). Without an account this data stays on your device and is only transmitted for the analysis you request. With an account and cloud backup enabled, it is stored on our servers so we can restore and sync it.
Photos. The food photos you take or pick for analysis are sent to our servers and to our AI providers to recognise the meal and estimate its nutrition. Pro subscribers who enable photo backup also have their meal photos stored in our EU cloud storage.
Voice. If you use voice logging or voice refinement, your microphone audio is streamed to a speech-recognition provider and turned into text in real time. The audio itself is not stored by us; only the resulting text becomes part of your journal or conversation.
Conversations with Kalo (AI assistant). The messages you exchange with the in-app assistant and the actions it takes on your behalf (for example logging a meal or changing a goal). Conversations are stored on your device and, when you are signed in, also on our servers so they follow you across devices.
Purchases and subscriptions. Whether you have a trial or an active subscription, which plan, and the store transaction identifiers needed to unlock Pro features and to handle restores. We never see your card number or payment details; those stay with Apple or Google.
Device, usage and diagnostic data. Device model and operating system version, app version, language, country, an app-instance identifier, in-app events (screens viewed, features used, purchases started or completed) and crash and performance reports. On iOS, and only if you allow tracking in the system prompt, the advertising identifier (IDFA) is used to measure which advertising campaign brought you to Kaloria.
Support requests. If you contact us from the app or by e-mail, we keep your message, your e-mail address and our reply.
Website. kaloria.ai serves static pages. Our web server records standard technical logs (IP address, requested page, browser type, time). The website uses Google Analytics, which sets cookies to measure visits in aggregate; you can block these cookies in your browser. The website does not use advertising cookies.
2. How We Use Your Information
Where the GDPR or similar laws apply, we rely on the performance of our contract with you (providing the app), your consent (cloud backup of health-related data, Apple Health / Health Connect access, the microphone, and tracking on iOS; you can withdraw consent at any time), and our legitimate interests (analytics, security, service improvement). Kaloria's food analysis and coaching are informational and are not medical advice.
3. AI Processing and Service Providers
We use carefully selected providers to run Kaloria. They process data only on our instructions, for the purposes below, and must not use it for their own purposes. We do not sell your personal data. Under the API terms we use, our AI providers do not use the photos, text or conversations submitted through the API to train their models.
| Provider | What they process | Purpose | Location |
|---|---|---|---|
| Kaloria servers (hosted by INTERNET CZ, a.s.) | Everything described in section 1 | Running the app, accounts, backup and sync | Czech Republic (EU) |
| OVHcloud | Backed-up meal photos of Pro subscribers | Photo backup storage (encrypted at rest) | Paris, France (EU) |
| OpenAI and other model providers via OpenRouter | Meal photos, food descriptions, Kalo conversations, your goals and journal context needed for an answer | Food recognition, nutrition estimation, AI coaching | United States |
| Soniox | Microphone audio while you dictate | Real-time speech-to-text | United States |
| RevenueCat | Store transaction identifiers, subscription status, an app user ID | Subscriptions, trials and restores | United States |
| Google Firebase (Analytics, Crashlytics) | Usage events, device and app information, crash reports | Analytics, stability | United States and EU |
| AppsFlyer | Install and purchase events, device identifiers (IDFA only with your permission) | Marketing attribution | United States and EU |
| Resend | Your e-mail address and the content of account e-mails | Sending sign-in codes and account notices | EU (Ireland) |
| Apple and Google | Sign-in identity (if you use Sign in with Apple / Google), purchases, Apple Health / Health Connect data on your device | Sign-in, payments, health integration | Per their policies |
Their privacy policies: OpenAI, OpenRouter, Soniox, RevenueCat, Google Firebase, AppsFlyer, Resend, OVHcloud.
Some providers process data in the United States. Where that happens we rely on the EU–US Data Privacy Framework or the European Commission's Standard Contractual Clauses.
4. Apple Health and Google Health Connect
Kaloria integrates with Apple Health (iOS) and Google Health Connect (Android). Only with your explicit permission, the app reads and writes the following:
Health data we read:
• Steps and active / total calories burned to show your activity and calculate your net calorie balance
• Workouts to import your activities automatically
• Weight from smart scales and other apps to track progress and adjust your goals
• Hydration and nutrition logged in other apps for a complete picture
Health data we write: the meals (calories, protein, carbohydrates, fat, fiber, sugar, sodium), water, weight and workouts you log in Kaloria.
How we use it: daily summaries and charts, net-calorie calculation, adjusting your calorie budget to your activity, and personalised coaching based on your real activity level.
Where it is stored: health data read from these platforms is stored on your device. It is sent to our servers only as part of the analysis or coaching you request and, if you are signed in with cloud backup on, as part of your backed-up journal (weight, water, workouts). Health data is never used for advertising or shared with advertisers, and it is never sold. You can revoke access at any time in the Health app (iOS) or Health Connect settings (Android), or turn health sync off in Kaloria's settings; the core tracking features keep working without it.
5. Sharing, Advertising and Tracking
We share personal data only with the providers listed in section 3, with Apple and Google as required to run the app, and when the law requires it (for example a valid legal request) or to protect our rights and the safety of our users. We do not sell personal data and we do not show third-party ads in the app.
To know whether our own advertising works, we use AppsFlyer to attribute installs and subscriptions to the campaign that brought you to Kaloria. On iOS this uses the advertising identifier only if you tap "Allow" in the App Tracking Transparency prompt; you can change this at any time in Settings → Privacy & Security → Tracking. On Android the advertising ID is used for the same purpose and can be reset or deleted in your device's Google settings. Purchase events sent for attribution never include your name, e-mail or journal.
6. Data Retention
We keep personal data only as long as needed for the purposes above, and then delete or anonymise it. The retention periods below apply unless the law requires us to keep something longer (for example tax records of purchases).
| Data | How long we keep it |
|---|---|
| Journal, photos, chats and settings stored on your phone | Until you delete them in the app (Profile → Delete All Data) or uninstall the app. They are under your control and never expire. |
| Account (e-mail, name, sign-in identity, device list) | While your account exists. When you delete your account, it is scheduled for deletion and permanently erased from our servers 7 days later (signing in during those 7 days cancels the deletion). |
| Cloud backup (meals, weight, water, workouts, Kalo conversations) and backed-up photos | While your account exists; erased together with the account 7 days after you delete it. Entries you delete in the app are also deleted from the backup at the next sync. Turning backup off stops further uploads; data already backed up stays until you delete it or delete the account. |
| Sign-in sessions | Access tokens 15 minutes; refresh tokens 90 days of inactivity; all sessions are revoked when you sign out, delete the account or remove a device. |
| One-time sign-in codes | 10 minutes, then invalid; the code record is deleted afterwards. |
| Analysis logs (the photo or text you submitted, the nutrition estimate returned, model used, date; no name or e-mail) | Kept as pseudonymous quality-assurance records for up to 12 months, then deleted. The most recent 30 days are kept on the production server; older logs are moved to an offline archive. |
| Voice audio | Not stored. Processed in real time and discarded once transcribed. |
| Purchase and subscription records | While your subscription or trial is active and for as long as required to handle restores, refunds and accounting obligations (up to 10 years for accounting records, as required by law). |
| Usage analytics (Google Firebase in the app, Google Analytics on the website) | Event-level data up to 14 months, as configured in our analytics properties; aggregated reports may be kept longer. |
| Crash and performance reports (Firebase Crashlytics) | 90 days. |
| Marketing attribution data (AppsFlyer) | Up to 24 months from the install event. |
| Support correspondence | Up to 3 years after the last message, unless you ask us to delete it earlier. |
| Account e-mails (sign-in codes, deletion notices) and their delivery logs | We do not keep copies of these e-mails. Our e-mail provider keeps delivery logs for a limited period under its own retention policy (linked in section 3). |
| Technical server logs (IP address, request metadata) | Up to 90 days. |
| Backups of our database | Encrypted backups are kept for up to 90 days and then overwritten. Data deleted from the live system disappears from backups within that period. |
If you never sign in, the only personal data we hold about you are the pseudonymous analysis logs and the usage, crash and attribution data described above; there is no account to delete on our side, and the data on your phone is entirely yours.
7. Your Rights and Choices
8. Security
All data travels between the app, our servers and our providers over encrypted connections (TLS). Backed-up photos are encrypted at rest. Access to production systems is limited to the people who operate the service, and sign-in codes, tokens and sessions are protected against reuse. No method of transmission or storage is completely secure, so we cannot guarantee absolute security, but we work to protect your data with appropriate technical and organisational measures. If a breach affects your data we will inform you and the authorities as the law requires.
9. Children's Privacy
Kaloria is not directed to children under 13 (or under 16 where local law sets a higher age for consent) and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us and we will delete it.
10. Changes to This Privacy Policy
We may update this policy from time to time. The date at the top shows the latest version. For material changes we will notify you in the app or by e-mail before they take effect. Continued use after that date means you accept the updated policy.
11. Contact Us
AI Chat & Voice Systems, operator of Kaloria
info@kaloria.ai