Marius Fraßek
Jesuitenhof 7, 41460 Neuss, Germany
Email: marius.frassek10@web.de
The app stores data that you enter yourself, record live, or import from Apple Health at your request:
All data is stored locally on your iPhone (SwiftData). If you have iCloud enabled, data is additionally stored in your private iCloud database (Apple CloudKit) and synced between your devices. This applies to all data listed in section 2 – including workouts, body weight and nutrition data imported from Apple Health.
☁️ iCloud sync only writes to your personal, private iCloud database. The developer has no access to your data at any time.
Storage serves to provide the app (Art. 6(1)(b) GDPR). The iCloud service is operated by Apple under your own iCloud agreement with Apple.
Data is used exclusively for the functionality of the app: personal journaling, habit tracking, goal planning, workout and nutrition tracking, progress analysis and – if you use them – the community features.
If you use build. Premium, additional data is processed to generate the Coach's replies and the nutrition estimates for photo logging (see section 5).
There is no other purpose – in particular no advertising and no profiling.
The Coach and photo logging require an internet connection: the data they need is sent via the developer's own server (a Cloudflare Worker) to Anthropic's Claude API. Which other features transmit data is described in sections 6 to 8.
a) Coach
When you chat with the Coach, your messages, the Coach's memory summary and the current app context are sent. The app context contains: date and time, your active annual goals with progress, your habits with streak and completion rate, today's daily goals, key figures (number and minutes of your workouts this month, books finished this year, journal streak), day ratings, successes, learnings and gratitude from the last 7 days, and the number and longest workout of the last 7 days (duration and type). Workout figures may be based on workouts imported from Apple Health. Heart rate, body weight, height, date of birth, sex and nutrition data are not sent to the Coach.
In addition, for the Coach:
The build. Worker only forwards this data and does not store it.
b) Photo Logging
When you take a photo of a meal, the photo (downscaled) and your optional hint are sent via the same Worker to Anthropic's Claude API to estimate the foods and nutrition values. The build. Worker does not store the photo. The app only saves the result you confirm – not the photo.
c) Subscription Check
To make sure only subscribers can use photo logging, your subscription's transaction identifier is sent to the Worker and verified with Apple (App Store Server API). For this, the Worker stores a counter per subscription and day (for the daily limit) for up to 2 days, and the subscription status for a few hours. No names, photos or content are stored.
d) Retention at Anthropic
build. stores neither messages nor photos. According to its own policy, Anthropic automatically deletes API inputs and outputs within 30 days. If a request is flagged by Anthropic's automated systems as violating its usage policy, the inputs and outputs may be retained for up to 2 years. Anthropic does not use data submitted via the API to train its models. Details: Anthropic – How long do you store my organization's data?
Purpose and Legal Basis
This processing serves solely to provide the build. Premium features you request (Art. 6(1)(b) GDPR). Where health data is involved (e.g. workout figures in the Coach context or photos of your meals), processing is based on your explicit consent (Art. 9(2)(a) GDPR), which you can withdraw at any time with effect for the future by no longer using the Coach or photo logging. The Coach and photo logging cannot work without this transfer. If you don't use them, none of this data is transmitted.
Recipients
These providers may also process data outside the EU, in particular in the USA. How long Cloudflare and Apple retain data and what they use it for is governed by their own privacy policies.
a) Barcode Scan (Open Food Facts)
When you scan a food barcode, the app queries the open database Open Food Facts (Open Food Facts, a non-profit association, France). The barcode number, your IP address and a technical identifier of the app (user agent with app name, app version and the developer's contact address) are transmitted – no data about you or your nutrition. The product data is licensed under the Open Database License (ODbL). Open Food Facts Privacy Policy. Scanning itself and reading nutrition labels happen on your iPhone.
b) Book Covers (Google Books)
When you add a book, the app searches for a cover via the Google Books API. The book title and author, your IP address, and the app's API key and identifier are transmitted to Google; the cover image is then loaded from Google's servers. Google Privacy Policy.
c) Maps (Apple Maps)
Maps and route images in the app are loaded via Apple Maps (MapKit). Apple receives the displayed map area and your IP address.
d) Purchases, Siri and Shortcuts
Purchases and subscriptions are handled by Apple via the App Store; the developer receives no payment data. When you use Siri or Shortcuts (e.g. "Log food"), Apple processes your voice input under Apple's terms; the app only receives the recognized text and saves the entry locally. Voice input in the app's search field is processed entirely on your iPhone.
The legal basis for these features is providing the feature you use (Art. 6(1)(b) GDPR).
The community features are optional. They use Apple CloudKit; the developer does not run a server of their own for them. Instead of your Apple ID or email address, an app-specific user identifier assigned by Apple is used.
a) Friends and Feed (shared area of your iCloud)
Your community content is stored in a separate area of your private iCloud, which you share with friends via an invite link or QR code. Anyone who opens and accepts the link can read this area – so only pass it on to people you trust. It contains:
You can remove shared entries and your own home rounds at any time, delete your own comments and remove friends. If you delete your iCloud data (section 12), this area is deleted as well.
b) Public Database (competitions, commitments, habit challenges, streak duo, home round leaderboard, notifications)
This data is stored in the app's public CloudKit database at Apple. Technically it can be retrieved by other users of the app; in the app it is only shown to the respective participants or friends.
Deletion: When you leave a competition, your participation is deleted; when you end a streak duo, the duo or your membership is deleted. You cannot delete home round best times and sent notifications yourself in the app; they are also not removed by "Reset All Data" or by deleting your iCloud data. Send an email to the developer (section 13) and they will be deleted.
The legal basis is providing the community feature you use (Art. 6(1)(b) GDPR). Where result values are based on health data, processing is based on your explicit consent (Art. 9(2)(a) GDPR), which you can withdraw by leaving the competition.
a) Apple Health
Only if you allow it in Apple Health, the app reads:
And, once allowed, writes:
Imported Health data is stored in the app and synced with your private iCloud (section 3). It only reaches third parties in the cases described and only in derived form: workout figures in the Coach context (section 5), result values in competitions (section 7b) and workouts you share yourself (section 7a). Heart rate, body weight, height, date of birth, sex and nutrition data only leave your device via your private iCloud.
❤️ Health data is not used for advertising or marketing, not sold and not passed on to data brokers.
b) Location
The app only uses your location during a live workout (also while the screen is locked) to record route, distance and pace. The route is stored in the app, in your iCloud and – once allowed – in Apple Health. Otherwise it only leaves your device if you share the workout or a home round in the community (section 7a).
c) Bluetooth
At your request, the app connects to a Bluetooth heart rate sensor. Heart rate is processed only on your device, stored with the workout and – once allowed – written to Apple Health.
d) Camera, Photos and Microphone
Barcode scanning and reading nutrition labels happen on your iPhone. Meal photos are only transmitted for photo logging (section 5b). Photos you add to entries stay in the app and your iCloud unless you share them in the community. Microphone and speech recognition are only used for voice input; processing happens on your iPhone.
The legal basis is providing the respective feature (Art. 6(1)(b) GDPR); for health data, your explicit consent, which you give via the permission in Apple Health and can withdraw there at any time (Art. 9(2)(a) GDPR).
🚫 Beyond sections 5 to 8, your data is never shared with third parties. No analytics, no tracking, no advertising.
This app does NOT use:
Notifications are only sent if you explicitly grant permission. You can disable them at any time in iOS Settings. Reminders (e.g. morning and evening reminders) are created locally on your device. Community notifications (e.g. invitations, comments, reactions, records) are delivered via Apple iCloud and the Apple Push Notification service (see section 7b).
You have the following rights regarding your personal data:
You can delete your data at any time: In the app go to Profile → Reset All Data. This permanently deletes the locally stored data.
For iCloud data (including the community area): Settings → [Your Name] → iCloud → Manage Storage → journal → Delete Data.
Data the app has written to Apple Health can be deleted in the Health app. For deleting data in the public database, see section 7b.
For any privacy-related questions, please contact:
marius.frassek10@web.de
This privacy policy may be updated with app updates. The current version is always available at this URL.