kcalculate

App Privacy Policy

Last updated: 16 November 2026

In short

1. Controller

App Werkstatt Taudt, owner Aaron Taudt
Am Kurpark 2A, 93077 Bad Abbach, Germany
Email: support@kcalculate.de

This policy covers the kcalculate app on iOS and Android. For this website, the website privacy policy applies.

2. What stays on your device

Your entries (meals with their ingredients, amounts and nutrition values), the photos of your meals, your weight, your body data and goals, your activities and your settings are stored only in the app's own database on your device. We do not receive them.

3. Device ID and device check

On first launch the app creates a random device ID. It accompanies every request to our server, so that we can count your quota and show you our replies to your reports. On the server we store it only as a salted hash.

So that only the genuine app can use our server, every request proves that it comes from a real device: on iOS with Apple's App Attest, on Android with Google's Play Integrity API. Apple or Google process information about the app and the device for this. For App Attest we store your device's public key with the device ID.

The legal basis is our legitimate interest in protecting the service from abuse and unpaid AI costs (Art. 6(1)(f) GDPR).

4. AI capture

When you log a meal with AI, the app sends our server: up to three photos, your text, the details of scanned products, the app's language and the time with your time zone. The server passes the photos, text and product details in one request to an AI model from one of these two providers:

We choose which of the two answers by quality and cost, which is why we name both. The model returns a list of ingredients with amounts. Our server then assigns the nutrition values itself: for this the ingredient names (including those you type into a meal by hand) always go to Google Vertex AI, which turns them into numeric vectors.

We store neither the photos nor the text nor the result; the result goes to the app and is stored only there. Both providers process the data as our processors, only to produce the answer, and do not use it to train their models. The request may be processed outside the EU, by Anthropic in the USA (see section 14).

The legal basis is the performance of the contract of use, since the capture is the feature you trigger (Art. 6(1)(b) GDPR).

5. Barcodes and Open Food Facts

When you scan a barcode, the app sends the code to our server. The server asks the open food database Open Food Facts (Open Food Facts, France) for the product's name and nutrition values. Open Food Facts sees our server, not you. We log neither codes nor products. Legal basis: Art. 6(1)(b) GDPR.

Adding a product: if Open Food Facts does not know a scanned product, or lacks its nutrition values, the app offers to add it. Only if you do, the app sends your photos of the pack (ingredient list, nutrition table, front) with the barcode to our server. An AI model from one of the two providers in section 4 reads the ingredients and nutrition values from them, and the server sends the missing details and the photos to Open Food Facts. We submit them under kcalculate's account with a pseudonymous identifier per device that Open Food Facts cannot trace back to you. They are published there publicly under open licences (photos under CC BY-SA, data under the Open Database License), so please photograph only the pack. We do not store the photos. The legal basis is your consent, which you give by sending (Art. 6(1)(a) GDPR). Once published, the contribution is managed by Open Food Facts; to have it removed, write to support@kcalculate.de.

6. Quota and capture measurements

For every AI capture, and every label read for Open Food Facts, the server stores one row: the hashed device ID, the time, the model used, the duration, the cost, the number of ingredients and, if it failed, the kind of failure. Photos, text, ingredients, meals and barcodes are not in it.

These rows are also the record of your quota (3 captures a day without Premium, a cost budget over 30 days with Premium). We keep them as long as we need them for the quota and for cost control. "Delete my data" therefore does not remove them; otherwise every deletion would reset the quota. The legal basis is our legitimate interest in fair distribution and in controlling our costs (Art. 6(1)(f) GDPR).

7. Bug reports and requests

Bug reports, feature requests, comments and votes you send in the app are stored with the hashed device ID so that you can see our replies. Feature requests and their comments are visible to other users too, without saying who wrote them. Please do not write anything there about your health or about other people. The data remains until you delete it with "Delete my data" or we no longer need it. Legal basis: Art. 6(1)(b) and (f) GDPR.

8. "Report this meal as wrong"

If the AI recognised a meal wrongly, you can report it. Only then, and only after your explicit consent in the report sheet, the app sends: the meal's first photo, the model's original answer with the model's name, the meal as stored on your device, the time, the app version and your optional comment. We use this to find errors in the recognition and to improve it.

Since information about your diet can be health data, the legal basis is your explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR). The photo is kept in non-public Google Cloud Storage in Frankfurt. We delete the photo and attachment after 12 months; the report itself with your comment remains as in section 7. You can withdraw your consent at any time: "Delete my data" in Profile deletes the report and its photo at once.

9. Premium and purchases

You buy Premium through the App Store or Google Play; Apple or Google handle the payment, and your payment details never reach us. Subscriptions are managed by RevenueCat (RevenueCat, Inc., USA): the app reports the purchase receipts to RevenueCat with your device ID, and our server asks RevenueCat whether your device ID has Premium. Legal basis: Art. 6(1)(b) GDPR.

10. Crash and error reports

If the app crashes or something goes wrong on our server, an error report goes to Sentry (Functional Software, Inc., USA; stored in the EU, Frankfurt): device model, operating system, app version, the technical course of the error and the screens before it. We send no name, no content of your meals and no identifier that identifies you. The legal basis is our legitimate interest in an app that works (Art. 6(1)(f) GDPR).

11. App updates

On launch the app asks Expo's update service EAS Update (650 Industries, Inc., USA) whether there is a new version of its program code, and downloads it if so. Expo receives your IP address, the platform, the app version and a random installation identifier of Expo's, but no content and not our device ID. The legal basis is our legitimate interest in shipping bug fixes quickly (Art. 6(1)(f) GDPR).

12. Apple Health and Health Connect

With Premium, and only if you turn it on and allow it, the app reads from Apple Health (iOS) or Health Connect (Android):

The app uses these values only to raise your daily goal when you move beyond your everyday activity. It stores them in its database on your device and never sends them to our server or to third parties. It writes nothing to Apple Health or Health Connect, does not use the values for advertising and does not share them. You revoke access in the settings of Apple Health or Health Connect; if you turn the connection off in the app, it deletes the values it has read.

13. Camera and photo library

The app uses the camera for photos of your meals and for scanning barcodes, and the photo library only when you pick a photo from it. Only the picked photo enters the app.

14. Recipients and transfers to third countries

RecipientPurposeLocation
Render Services, Inc.Running our server; server logs with IP address for a short timeFrankfurt
Supabase, Inc.Database for quota, measurements and reportsFrankfurt
Anthropic PBCAI capture (section 4)USA
Google Cloud (Vertex AI)AI capture, matching ingredients (section 4)worldwide, including the USA
Google Cloud StoragePhotos of reported meals (section 8)Frankfurt
RevenueCat, Inc.Subscriptions (section 9)USA
Functional Software, Inc. (Sentry)Error reports (section 10)EU
650 Industries, Inc. (Expo)App updates (section 11)USA
Apple, GoogleDevice check, purchases, device backupunder their terms
Open Food FactsProduct data for barcodes; photos and details of a product you add (section 5)France

We have data processing agreements (Art. 28 GDPR) with every provider that processes data on our behalf. We base transfers to the USA on the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR) and, where the recipient is certified, on the EU-US Data Privacy Framework (Art. 45 GDPR).

15. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). You can withdraw consent at any time with effect for the future.

What we hold on the server for your device ID you delete yourself, at once, with Profile → "Delete my data" (except the measurements from section 6). For anything else, write to support@kcalculate.de. Since there is no account, we can find your data only through the device ID, so the easiest way to reach us is a bug report in the app.

You can lodge a complaint with a data protection supervisory authority, for example the Bavarian Data Protection Authority (BayLDA), Promenade 18, 91522 Ansbach, Germany.

16. Age

The app is meant for people aged 16 and over.

17. No ads, no tracking

The app shows no ads, uses no advertising ID, does not track you across other apps or websites and sells no data.

18. Changes

If the app changes so that this policy is no longer accurate, we update it. The version on this page, dated above, applies.