Privacy Policy for Trainer (iOS and Android)
Last updated: August 3, 2026
This Privacy Policy explains how the Trainer app for iOS and Android processes personal data.
1. Data Controller
The data controller for Trainer is:
Joe Waldow
Hasenbusch 52
25335 Elmshorn
Germany
Contact:
2. Overview
Trainer is designed so that most workout and planning data is stored locally on your device.
In the current version of Trainer, this means in particular:
- No separate user account with me is required to use the core app features.
- Most workout data is stored locally on your device.
- The current iOS Trainer flow does not use iCloud sync for this local workout data.
- The current Android version disables automatic Android cloud backup and device-transfer backup for Trainer app data.
- No cloud backend operated by me is used to centrally store your local workout data.
In some areas, Trainer uses third-party services or platform services, in particular:
- Apple App Store and/or Google Play for distribution and purchases
- RevenueCat for the technical handling of subscriptions and entitlements
- Apple Health / HealthKit on iOS, if you enable that integration
- local notifications on your device
- export, import, and sharing features triggered manually by you
3. What data does Trainer process?
3.1 Local workout and app data
When you use Trainer, the app may store the following data locally on your device, for example:
- workout plans
- completed workouts
- exercises and custom exercises
- set entries, repetitions, weights, times, and similar workout values
- progress and statistics data
- app settings
- local reminder and configuration data
This data does not leave your device: there is no server operated by me that Trainer transmits it to, and no user account with me. The legal basis is Article 6(1)(b) GDPR, because this is precisely the function you installed the app for. Storing it on your device does not require consent under Section 25(1) of the German TDDDG, because it is strictly necessary to provide the function you requested (Section 25(2) no. 2 TDDDG).
3.2 Purchases, memberships, and RevenueCat
Paid features and memberships are offered through the Apple App Store and/or Google Play. Trainer also uses RevenueCat for the technical management of purchases, subscriptions, trials, entitlements, and restore flows.
In this context, the following data may in particular be processed:
- a randomly assigned app user identifier
- information about active or past subscriptions
- purchase-related metadata about products and offerings
- technical information required to provide, validate, and restore purchases
Trainer itself does not receive full credit card or payment details. Payment processing is handled by Apple or Google.
In addition, Trainer stores attributes with RevenueCat recording when you were last shown the request for an App Store rating or last opened the rating function in the settings yourself, and on what occasion. This serves solely to avoid showing that request too often.
Recipients and transfer to third countries: RevenueCat is operated by RevenueCat, Inc., based in the USA, acting as a processor on my behalf. Transfer to the USA is based on the European Commission's Standard Contractual Clauses and, where the provider is certified, the EU-US Data Privacy Framework. For users in the European Economic Area, Apple is represented by Apple Distribution International Ltd. in Ireland, and Google Play by Google Commerce Limited and Google Ireland Limited in Ireland.
Legal basis: Article 6(1)(b) GDPR for providing and restoring the features you purchased, and Article 6(1)(f) GDPR for fraud prevention and for keeping the rating request to a reasonable frequency.
More information:
Apple Privacy: https://www.apple.com/legal/privacy/
Google Privacy: https://policies.google.com/privacy
RevenueCat Privacy: https://www.revenuecat.com/privacy
3.3 Apple Health / HealthKit on iOS
On iOS, Trainer can optionally integrate with Apple Health (HealthKit) if you actively allow this.
If you use this feature, Trainer may:
- write completed strength workouts to Apple Health, including rest periods and a per-set note with exercise, repetitions, weight and effort rating
- read workout data from Apple Health
- read body weight / body mass data from Apple Health in order to support bodyweight-related progress features
If you use the body weight feature, Trainer additionally stores the weight values read from Apple Health in its own database on your device, so that history views work without renewed Health access and so that each workout keeps the weight value that applied at the time. This copy stays on your device. If you revoke Health access or delete values in Apple Health, this copy does not disappear automatically; you can remove it in the app.
This integration is voluntary. You can change or revoke Health permissions at any time in iOS Settings or in Apple Health.
Trainer does not itself delete any entries in Apple Health. You remove a workout written by Trainer directly in the Apple Health app.
Apple Watch: When you start a workout on Apple Watch or mirror one to it, the Watch app reads your heart rate and your active energy from HealthKit during the session in order to display and record the ongoing workout, and writes the completed session to Apple Health as a workout. These values are transferred between watch and iPhone so that both devices show the same workout state.
Live Activity and widgets: During a workout, heart rate and energy burned may be shown in the Live Activity on the Lock Screen or in the Dynamic Island, and in the Apple Watch widgets. This display is produced by the operating system on your device; the values are placed in a shared storage area of the app on the device for this purpose and are not transmitted. Please note that Lock Screen content is also visible to anyone looking at your device.
Legal basis: Health data belongs to the special categories of personal data (Article 9(1) GDPR). Processing takes place exclusively on your devices; I do not receive this data, have no access to it and do not store it. The integration is off by default and only becomes active after you have explicitly granted it in the iOS permission dialog. To the extent that this permission constitutes consent within the meaning of Article 9(2)(a) GDPR, the processing is based on that consent; you can withdraw it at any time.
Health data read from Apple Health is used by Trainer solely to provide workout, history, and progress features. It is not used for personalized advertising, not sold to data brokers, and not used for cross-app advertising tracking.
3.4 Android note on health data
The current Android version of Trainer does not currently integrate with Google Fit or Health Connect.
4. Notifications and reminders
Trainer can optionally remind you about planned workouts or app features. For this purpose, the app uses local notifications on your device.
If you enable reminders, Trainer may:
- schedule notifications locally on your device
- manage recurring reminders locally
I do not send any promotional push campaigns or marketing notifications; there is no push server.
On Android, local reminders may be rescheduled on the device after a reboot or after changes to time or time-zone settings.
You can disable notifications at any time in your device settings or, where available, inside the app.
5. Export, import, and manual sharing
Trainer provides features that allow you to manually export and import workout data, for example for backups or when moving to another device.
In addition, certain content may be handed over to other apps or services only when you explicitly use system sharing features.
Such files or content are created, imported, or shared only when you actively trigger this yourself.
If you store or share exported data in third-party services, cloud storage providers, or other apps, the privacy policy of the respective provider will also apply to the further processing of that data.
6. Apple Search Ads / AdServices attribution on iOS
On iOS, Trainer may process attribution information from Apple AdServices / Apple Search Ads together with RevenueCat in order to determine whether an app installation originated from Apple Search Ads.
This is used for technical campaign attribution and not for cross-app tracking for personalized advertising within Trainer. The legal basis is Article 6(1)(f) GDPR (legitimate interest in measuring the performance of my own App Store search ads).
More information:
Apple Privacy: https://www.apple.com/legal/privacy/
RevenueCat Apple Search Ads: https://www.revenuecat.com/docs/integrations/attribution/apple-search-ads
7. No advertising, no classic analytics, and no cross-app tracking
Except for the purchase-related services described above and the iOS-specific attribution via Apple AdServices / Apple Search Ads, the current version of Trainer does not in particular use:
- advertising SDKs for personalized ads inside the app
- classic third-party marketing trackers
- App Tracking Transparency prompts
- cross-app or cross-website tracking for advertising purposes
8. Storage and deletion
8.1 Local app data
Local workout and app data generally remains stored on your device until you change or delete it inside the app or remove the app from your device.
8.2 Apple Health data
If you connected Trainer to Apple Health, you can manage permissions in iOS or Apple Health and delete Health data there.
8.3 Notifications
You can disable reminders and notifications in the app or in your device settings.
8.4 Purchase and subscription data
Purchase and subscription information is managed through Apple, Google, and RevenueCat.
If you want to request deletion of app-related purchase or subscription data processed through RevenueCat, you can contact me at joe@waldow.app.
To help identify the relevant customer profile, I may ask you to provide information such as your RevenueCat app user identifier or a purchase reference.
Deleting app-related purchase or subscription data does not automatically cancel an active subscription. Active subscriptions must be managed separately through the relevant Apple App Store or Google Play account.
8.5 Exported files and shared content
Files you export or share remain at the storage or sharing destination you selected until you delete them there yourself.
9. Your rights
Where applicable, including under the GDPR, you may have rights such as:
- access to personal data
- correction of inaccurate data
- deletion of personal data
- restriction of processing
- objection to processing
- data portability
- withdrawal of consent for the future where processing is based on consent
Important notice:
Because Trainer stores most data locally on your device and because certain features depend on Apple, Google, RevenueCat, or third-party services chosen by you, I often cannot directly access, correct, export, or delete all relevant data for you. In such cases, please also use the controls provided by your device or the respective provider.
Where app-related purchase or subscription data is processed through RevenueCat, you can also contact me at joe@waldow.app to request deletion of such data.
No automated decision-making including profiling within the meaning of Art. 22 GDPR takes place. The app's training suggestions are based on predefined rules and have no legal effect on you.
10. Right to lodge a complaint
You have the right to lodge a complaint with a data protection supervisory authority, in particular in the country of your residence, your place of work or the place of the suspected infringement. For me as the controller, based in Schleswig-Holstein, Germany, the competent authority is:
Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein (ULD)
Holstenstraße 98
24103 Kiel, Germany
www.datenschutzzentrum.de
11. Changes to this Privacy Policy
This Privacy Policy may be updated from time to time.
The version published on the Trainer website is the version that applies.
12. Contact
If you have questions about privacy in connection with Trainer, you can contact: