Last updated: 10 October 2026 · Effective: 27 August 2026
CalForge is a nutrition and health tracking app. This policy explains what it collects, why, who it is shared with, and how to get rid of it. It is written to be specific rather than reassuring — where data leaves your device, it says so.
The data controller is Atanas Korabov, trading as CalForge, Sofia, Bulgaria, contactable at privacy@calforge.app.
| Data | Why | Legal basis (GDPR) |
|---|---|---|
| Account identifier. A random user ID created when you first open the app. An email address only if you choose to create an account or sign in with Google. | To store your data and let you reach it from your device. | Contract (Art. 6(1)(b)) |
| Health and body data. Name, age or date of birth, gender, height, current and target weight, weight history, activity level, goal, calorie and macronutrient targets, eating window and meal preferences. | To calculate your calorie target and show your progress. These are the app's core function. | Explicit consent (Art. 9(2)(a)) |
| Food and exercise logs. What you type or say, the food items and estimated nutrition derived from it, barcodes you scan, and photos of meals. | To log what you eat and estimate its nutrition. | Explicit consent (Art. 9(2)(a)) |
| Health Connect data (Android, optional). Steps, calories burned, distance, heart rate, hydration and exercise sessions — read only. CalForge never writes to Health Connect. | To account for activity in your daily calorie balance. | Explicit consent, granted per data type in Health Connect |
| Device identifier (Android and iPhone). A one-way, salted hash of the Android ID, or on an iPhone of a random code the app creates and keeps in the phone's Keychain — a value that identifies your device to this app only, and to no other app. We never store the identifier itself, only the hash, and the hash cannot be turned back into it or matched against any identifier held elsewhere. | Fraud prevention only. The free allowance is granted once per device, so this is what stops the same phone reinstalling the app repeatedly to claim it again. It is not used for advertising, analytics, profiling or tracking you across apps or websites. | Legitimate interest (Art. 6(1)(f)) |
Referral records. If you invite a friend or use someone's invite code: the
code, who invited whom, the dates the invite was accepted and rewarded, and the bonus
entries granted. Someone who invites you can see a masked form of your email address
(for example a***@example.com), never the full address. |
To run the invite programme and award the bonuses it promises. | Contract (Art. 6(1)(b)) |
| Account events. A short record of milestones on your account — when it was registered, when an invite was used or rewarded, when a subscription started or ended, and when a log was refused because an allowance was spent. Not a record of what you eat, and not page-by-page tracking of how you use the app. | To explain how allowances and rewards were calculated, and to answer support questions about them. | Legitimate interest (Art. 6(1)(f)) |
| Technical records. For each AI request: which model ran, how many tokens it used, what it cost, how long it took, and whether it succeeded. Also daily usage counts used to enforce your plan's limits. | To control costs, enforce fair-use limits, and diagnose failures. | Legitimate interest (Art. 6(1)(f)) |
CalForge does not collect your contacts, precise location, advertising identifiers, or browsing activity. The device identifier described above is used solely to stop the free allowance being claimed repeatedly from one device; it is never shared, never used for advertising, and never linked to anything outside CalForge.
The app creates an anonymous account on first launch so it works without signing up. That account is real data storage — it just is not linked to an email. If you later create an account, the same identifier is kept so your existing history carries over. If you never create one and uninstall the app, that data becomes unreachable and is eventually removed. Note that the one-off free allowance is counted per device, so reinstalling does not reset it.
If you joined the launch waitlist on calforge.app (now closed, as CalForge is live on Google Play), we store your email address, the time you signed up, the consent text you agreed to, the page or campaign you came from, your browser language and your approximate country (from your IP address, which itself is not stored). We use it only to email you when CalForge launches on Google Play. The list is stored with our website host in the EU. The legal basis is your consent, which you can withdraw at any time by replying to our email or writing to privacy@calforge.app.
This deserves its own section because it is the least obvious part.
We do not sell your data and we do not use it for advertising. We share it only with service providers that we need to run the app, in the categories below. Each category says what those providers receive. Nothing outside it is sent to them.
| Category | What they receive | Where |
|---|---|---|
| AI service providers — to estimate nutrition, tell food, weight and exercise apart, recognise foods you have logged before, and answer questions you ask the coach | The text you type or say in the app, meal photos and nutrition-label photos you submit, the names of foods you have logged before, a summary of your day and week and the earlier messages of that conversation when you use the coach, and body metrics (weight, height, age, gender, activity level, goal) when they are needed for an estimate. Never your name, email address or account identifier. | USA and other countries; see below |
| Hosting and database | Everything in section 1 that is stored: account, profile, weight history, food log, technical records. | European Union |
| Subscriptions and payments — the app store and the service that manages subscriptions for us | Your purchases and subscription status, linked to an app account identifier. Card and payment details are handled by the app store and never reach us. | USA and the app store’s own regions |
| Product databases | Barcode numbers you scan, to look up the product. No personal data. | European Union |
| App platform and sign-in (on Android: Google Play services, Health Connect, and Google Sign-In if you use it; on iOS: the App Store, Apple Health, and Sign in with Apple if you use it) | Standard app-distribution and sign-in data. Health Connect and Apple Health data is read on your device to show your day; it is never sent to our servers, never used for advertising, and never shared with anyone. Google and Apple do not receive it from us. | Per Google's and Apple's terms |
Every provider in these categories processes your data only to provide its service to us, under a data-processing agreement or terms of equivalent effect. AI providers may not train their models on what we send. Where a provider is outside the EEA, transfers rely on the European Commission's Standard Contractual Clauses or an adequacy decision.
The specific companies we use within a category can change, for example when we switch to a more accurate AI model, without this policy changing, as long as they receive only what the category above says. If we ever add a new category, or send a provider something its category does not list, we will update this policy first. For the current list of providers, write to privacy@calforge.app.
In the app: Profile → Delete Account. This permanently removes your profile, weight history, food log, saved foods, usage counters and the meal photos held on your device. It cannot be undone.
Without the app installed, use our account deletion request page or email privacy@calforge.app. We respond within 30 days.
If you are in the EEA or UK you can request access, correction, deletion, restriction, portability, or object to processing, and you may withdraw consent at any time — for health data, withdrawing consent means the app can no longer perform its core function. Contact privacy@calforge.app.
You may also complain to your supervisory authority. In Bulgaria that is the Commission for Personal Data Protection (Комисия за защита на личните данни), cpdp.bg.
Data is encrypted in transit (TLS). Database access is restricted per user by row-level security, so one account cannot read another's data. AI requests pass through our own server so that provider API keys are never present in the app. No system is perfectly secure, and we do not claim otherwise.
CalForge is not intended for anyone under 18 and we do not knowingly collect their data. If you believe someone under 18 has used the app, contact us and we will delete the account.
Nutrition figures produced from text or photos are estimates generated by an AI model, typically within about 25% of the true value for photos. CalForge is a tracking tool, not a medical device, and nothing in it is medical advice. Do not rely on it to manage a medical condition without professional guidance.
We will update the date at the top when this policy changes, and notify you in the app if the change is significant.