Privacy Policy

ambofit app and ambofit.com · Last updated: 27 October 2026

Diese Seite auf Deutsch

The short version

  • ambofit needs no account. Your workouts, food, weight and body data stay on your iPhone and, if you use iCloud, in your private iCloud. We can’t access them.
  • Only what a feature needs goes online: the number of a scanned barcode and, after you agree, an AI photo with an optional note.
  • We don’t store photos or notes. Google doesn’t use them to train its AI.
  • No ads, no analytics or tracking services and no cookies, neither in the app nor on the website.
  • Subscriptions run through Apple. We never receive payment details, your name or your Apple ID.

1. Who is responsible

Christian Kau
Brunnenstraße 121
53332 Bornheim
Germany
Email: privacy@ambofit.com

We have not appointed a data protection officer because we are not legally required to.

2. Data in the app (on your iPhone)

What you enter in ambofit is saved in a database on your iPhone: training plans, exercises, workouts and sets (weights, reps, times), meals and foods, recipes, your own and scanned foods, your body weight, the details for your calorie goal (sex, age, height, daily activity, workouts per week, goal, target weight and pace), as well as goals, check-ins and settings. This data is not sent to us. Details about your body, weight and diet can be health data. They only leave your device through your own iCloud (section 3).

These also happen only on your device:

  • Camera: your iPhone itself reads barcodes and nutrition labels (iOS text recognition). A photo of a nutrition label never leaves your device.
  • Photos: if you pick a picture from your library, the iOS photo picker gives the app only that one picture.
  • Rest timer: the Lock Screen display (Live Activity), the rest sound and the notification when rest is over are created on your iPhone. No data is sent for this.
  • Export: the CSV export is created on your device. You decide where the files go in the iOS share sheet.

You can delete entries in the app. Deleting the app removes the data from your device; for the copy in iCloud see section 3.

This processing takes place on your device and under your control; we don’t receive the data. Storing and reading data on your device is strictly necessary for the features you use (Section 25 (2) no. 2 of the German TDDDG).

3. Sync with iCloud

If you are signed in to iCloud on your iPhone and haven’t turned iCloud off for ambofit, the app syncs the data from section 2 with your private iCloud database using Apple’s CloudKit, and your goals, profile and settings using iCloud key-value storage. That way your data is on your other devices and comes back on a new iPhone. To deliver changes quickly, Apple sends your device silent push notifications without content.

The data is stored in your iCloud account. The provider is Apple (for users in the EU, Apple Distribution International Ltd., Ireland); the iCloud terms and Apple’s Privacy Policy apply. As the developer, we cannot see your private iCloud database. Apple encrypts iCloud data in transit and on its servers and may also store it in data centers outside the EU.

  • Turn it off: Settings → [your name] → iCloud → ambofit (among the apps using iCloud).
  • Delete the iCloud copy: Settings → [your name] → iCloud → Manage Storage → ambofit → Delete Data. Names differ slightly between iOS versions.

Sync runs through your own iCloud account under your agreement with Apple; we don’t receive the data.

4. Food search and barcodes

Search: the more than 7,000 foods of the German Federal Food Key (BLS 4.0 by the Max Rubner-Institut) are stored in the app. Search runs on your device, without internet.

Barcodes: when you scan a barcode the app doesn’t know yet, it sends the barcode number to Open Food Facts (a non-profit association under French law, France). For technical reasons, your IP address and an app identifier with the version number (for example “ambofit/1.0”) are transmitted too. For barcodes from the US and Canada, and when Open Food Facts has no complete result, the app also asks our server at Supabase (data center in Frankfurt am Main, Germany) for the barcode. It holds a copy of the product data from USDA FoodData Central (US Department of Agriculture); the department itself receives nothing. The app saves found products on your device so they are there without internet the next time you scan them.

Open Food Facts processes the request under its own responsibility; its privacy policy applies. For barcode requests, our server only keeps the technical server logs (section 13).

Legal basis: Art. 6 (1) (b) GDPR (the product lookup you ask for); for server logs Art. 6 (1) (f) GDPR (legitimate interest in security and troubleshooting).

5. AI photo

With AI photo you take a picture of a meal or pick one, and an AI estimates the foods, amounts and nutrients. Before your first AI photo, the app explains what happens and asks for your consent. AI photo is for people 18 and older. Please only photograph food, not people or documents.

Data sent: the photo, your optional note for the AI (up to 200 characters, for example “fried in butter”), your device’s time zone (for the daily limit) and Apple’s signed purchase confirmation for your subscription (section 6). To show how many photos you have left, the app asks for the current count; only the purchase confirmation and time zone are sent for that. For a correction (up to 2 per photo, for example “It was 3 eggs”), the same photo, the list with your amounts and your correction are sent to the server again.

How it works: the app sends the data to our server function at Supabase in Frankfurt am Main. The server checks your subscription using Apple’s signature, counts the photo and forwards the photo and note to Google Gemini. Gemini recognizes the foods; the result goes back to the app, where you check it before anything is saved.

What is stored: we don’t store the photo, the note or the correction. For the limit (Pro: 10 photos a day, Basic: 3 to try), the server stores only the number of photos per subscription, identified by Apple’s original transaction ID (a pseudonymous ID of your subscription): per day for 2 days, then as one total per subscription. The total is deleted 12 months after your last AI photo. For corrections, it keeps a random photo ID, the transaction ID, a checksum of the photo (SHA-256 hash, from which the photo can’t be restored) and the number of corrections; corrections are possible for 60 minutes and the entry is deleted after 2 days. The server log contains only numbers: plan, number of foods recognized, whether there was a note, AI model, processing effort and cost.

Google: Google processes the photo and note on our behalf. For the paid Gemini API, Google’s terms say it doesn’t use prompts and responses to improve its products or train AI models, and keeps them only for a limited time to detect abuse and meet legal obligations. Processing outside the EU, for example in the US, is possible (section 12).

Legal basis: your consent (Art. 6 (1) (a) GDPR; where a photo or note reveals something about your health, Art. 9 (2) (a) GDPR) and providing the feature you ask for (Art. 6 (1) (b) GDPR); for the limit and logs also Art. 6 (1) (f) GDPR (preventing abuse). You can withdraw your consent at any time with effect for the future by no longer using AI photo (nothing is sent without your photo) or by writing to privacy@ambofit.com.

6. Subscriptions and purchase check

ambofit requires a subscription (Basic or Pro), which you buy through Apple’s App Store. Apple handles the purchase, payment, free trial and renewals. We never receive payment details, your name or your Apple ID. The app checks which subscription is active on your device using Apple’s purchase interface (StoreKit).

Only for AI photo does the app send Apple’s signed purchase confirmation to our server. Among other things, it contains transaction IDs, the product, purchase and expiry dates, whether a free trial is running, the App Store country, and the price and currency. If Apple couldn’t charge a renewal and a billing grace period is running, Apple’s signed renewal info with the end of the grace period is added. The server checks Apple’s signatures and uses only the plan, expiry date or end of the grace period, trial status and original transaction ID to check the limit (section 5).

Apple also provides us with sales reports and statistics in App Store Connect, for example the number of subscriptions per country. We can’t identify you from them.

Legal basis: Art. 6 (1) (b) GDPR. Apple’s terms and privacy policy apply to the purchase.

7. Crash reports and beta tests

If you have turned on “Share with App Developers” in iOS under Settings → Privacy & Security → Analytics & Improvements, Apple provides us with crash reports and statistics for ambofit that don’t identify you (for example device model, iOS version and where in the code the app crashed). We only use them to fix bugs. You decide in the iOS settings whether to share them.

If you test a pre-release version through TestFlight, Apple gives us the name and email address you were invited with, plus crash reports and feedback you send through TestFlight. We only use this for the test.

Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in an app without bugs); you allow the sharing with us through Apple.

8. No tracking, no ads

The app contains no ads and no third-party analytics, tracking or advertising code. It doesn’t track you across other companies’ apps and websites, and we don’t sell data. ambofit also doesn’t read or write data in Apple Health.

9. Contact by email

When you write to support@ambofit.com or privacy@ambofit.com, we process your email address, your name (if given) and your message to reply to you. Our email provider INWX (INWX GmbH, Berlin, Germany) receives the messages and forwards them to our mailbox at Google (Gmail), where we read and answer them. We delete messages 2 years after your request is closed, unless legal retention periods require otherwise.

Legal basis: Art. 6 (1) (b) GDPR for questions about the app or your subscription, otherwise Art. 6 (1) (f) GDPR (legitimate interest in answering requests); for requests about your privacy rights Art. 6 (1) (c) GDPR.

10. This website

The website ambofit.com is hosted and delivered by GitHub Pages (GitHub, Inc., USA). When you visit it, GitHub processes your IP address, date and time, the page requested, the previous page and details about your browser and operating system in server logs to deliver the site and protect it against attacks.

The website sets no cookies, stores nothing in your browser, uses no analytics or tracking services, and loads no fonts or other content from other servers. Links to other websites, such as Apple’s, only open when you click them.

Prices in your currency: a small script of our own on the start page reads your browser’s time zone and language setting and shows the prices in euros, British pounds or US dollars accordingly. This happens only in your browser; nothing is stored and nothing is sent to us or anyone else.

Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in providing the website securely and reliably). For the transfer to the US, see section 12. Reading the time zone and language for the currency is necessary for the price display you request (Section 25 (2) no. 2 of the German TDDDG); we receive no personal data from it.

11. Recipients

ProviderPurposeWhere data is processed
Apple (App Store, iCloud)Download, subscriptions and payment; sync in your iCloud; crash reports and TestFlightsee Apple’s Privacy Policy
Supabase Pte. Ltd. (Singapore)Server for AI photo, limits and USDA product dataData center in Frankfurt am Main (EU)
Google (Gemini API)Recognizing foods for AI photoEU and other countries, including the US
Open Food Facts (France)Product data for barcodesFrance (EU)
GitHub, Inc. (USA)Hosting this website (GitHub Pages)US and other countries
INWX GmbH (Germany)Domain, receiving and forwarding emailGermany
Google (Gmail)Email mailboxEU and other countries, including the US

Supabase, Google (Gemini API) and INWX process data on our behalf under Art. 28 GDPR. Apple, Open Food Facts and GitHub process it under their own responsibility and privacy policies; Google’s terms and privacy policy apply to Gmail.

12. Transfers outside the EU

Supabase Pte. Ltd. is based in Singapore; the data is stored in a data center in Frankfurt am Main. Google, GitHub and Apple are headquartered in the US. Access from these countries or processing there, including by sub-processors, can therefore not be ruled out. For Supabase, the EU Standard Contractual Clauses apply (Art. 46 (2) (c) GDPR) as part of the data processing agreement. For Google and GitHub, the European Commission’s adequacy decision for the EU-US Data Privacy Framework applies (Art. 45 GDPR) where the provider is certified, and otherwise also the Standard Contractual Clauses. For Apple, the safeguards described in Apple’s Privacy Policy apply.

13. How long we keep data

DataHow long
Data in the app and in your iClouduntil you delete it, the app or the app’s iCloud data
AI photo: photo, note and correctionnot stored on our server; at Google only briefly to detect abuse
AI photo: correction entry (random ID, transaction ID, photo checksum)usable for 60 minutes, deleted after 2 days
AI photo: number of photos per subscriptionper day for 2 days, then as a total until 12 months after the last AI photo, then deleted automatically
Server logs at Supabase (with IP address)7 days at most
Barcode requests at Open Food Factsaccording to Open Food Facts’ privacy policy
Emails to us2 years after the request is closed
Website server logs (GitHub)according to GitHub’s retention periods
Crash reports and TestFlight details (Apple)according to Apple’s retention periods

14. Your rights

You have the right to

  • access the data stored about you (Art. 15 GDPR),
  • rectification (Art. 16 GDPR) and erasure (Art. 17 GDPR),
  • restriction of processing (Art. 18 GDPR) and data portability (Art. 20 GDPR),
  • object to processing based on legitimate interests (Art. 21 GDPR),
  • withdraw consent at any time with effect for the future (Art. 7 (3) GDPR).

Because we don’t know you by name and most data is only on your device and in your iCloud, you can view, export (CSV) and delete it there yourself at any time. For questions and requests, write to privacy@ambofit.com.

You can also lodge a complaint with a data protection supervisory authority, for example the authority responsible for us: Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), Kavalleriestraße 2–4, 40213 Düsseldorf, Germany, www.ldi.nrw.de.

15. More information

  • No obligation: you don’t have to give us any data. Without body data there is no calculated calorie goal, without the camera no scanning and without consent no AI photo.
  • No automated decision-making within the meaning of Art. 22 GDPR: the app calculates your calorie goal on your device as a suggestion. A new goal only applies once you accept it.
  • Age: ambofit is designed for adults. AI photo is for people 18 and older.
  • Security: all connections of the app and the website are encrypted (HTTPS/TLS). Our server only stores the counters and checksums named above.

16. Changes

When we change the app or the website, we update this policy. The current version is always on this page; we’ll tell you about significant changes in the app. If the English and German versions differ, the German version prevails.