MYBOSPARK · iOS & Android
Privacy
Updated: 2026-10-25
Retention of youth-protection markers during data deletion applies from iOS build 148 and in correspondingly updated Android versions. In older versions, deletion may remove these markers.
1. Controller and scope
The controller is Gorden Losse, Dietrich-Bonhoeffer-Str. 32, 40595 Düsseldorf, Germany. Contact: info@mybospark.de. This notice covers this website, voice downloads and MYBOSPARK for iOS and Android. Features and permissions can vary by operating system, device and app version.
2. App data and purposes
Depending on use, the app processes profile details (such as age, height, weight and an optional photo), training plans, confirmed sets and activities, progress values, notes and settings. This can include authorised health data, Bluetooth heart-rate readings and location/route data during an outdoor recording you start. The purposes are the training planning, recording and analysis you choose. The app currently includes no advertising or analytics SDKs of its own. There is no automatic training-data cloud sync operated by us. The exercise images and coach voices are AI-generated. The camera opens only after your action for QR scanning or a profile photo. The app does not save QR camera images; a profile photo you choose is stored securely on your device and can be deleted. Device authentication is performed by the operating system using biometrics or the device passcode. The app receives only the result, not face images, fingerprints or passcodes.
3. Health access: iOS and Android
Supported health access uses Apple Health/HealthKit on iOS and Health Connect on Android, where supported by the version and device. Depending on the feature, authorised heart-rate, body-weight, height, calorie and workout data is read. App settings and the system dialogue show the requested scope. Apple Health is not an Android feature. A system permission dialogue is not equivalent to a complete record of data-protection consent.
4. Legal bases and your choice
Non-health functional data necessary for the selected service is processed for performance of the contract (GDPR Article 6(1)(b)). Optional health processing requires explicit consent (Articles 6(1)(a) and 9(2)(a)). Optional location and notification features require your authorisation. Without the required permission, the relevant additional feature is unavailable; manual training features are separate. This privacy notice does not itself grant consent. The app asks you to renew your health-access decision after 56 days. If you withdraw access, further access is blocked; previously imported data is not automatically deleted. The system age query, the selection of an age group and the local storage of an age limit serve the protection of minors and the enforcement of the minimum age of 16. The legal basis is Article 6(1)(f) GDPR (legitimate interest in protecting minors). Processing takes place on your device; MYBOSPARK does not receive this information.
5. Withdraw permissions and forget sensors
You can restrict or revoke health access in Apple Health or Health Connect, and other permissions in app or system settings. Withdrawal applies to future processing and does not retroactively invalidate earlier lawful processing. Previously imported data is not automatically removed: also use the deletion controls. Optional reconnection to a known Bluetooth sensor stores its identifier, name and your reconnection preference locally; use “Forget” to remove this association. We do not promise compatibility with every watch or chest strap.
6. Website and voice downloads
The website and voice packs are provided through Cloudflare Pages and R2 (Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA, and associated service providers). Requests involve IP address, time, requested resource and technical browser/device information. The purpose is service delivery and security, based on Article 6(1)(f), and Article 6(1)(b) for downloads you request. These connection data mean a download is not anonymous. Packs contain general audio content, not personal training data. Installed voices can be used offline.
7. Recipients and international processing
Cloudflare may process connection data outside the EEA. Its contractual privacy and transfer provisions are described in the Cloudflare Data Processing Addendum. According to Cloudflare, Cloudflare, Inc. is certified under the EU-U.S. Data Privacy Framework; transfers to the USA therefore rely on the European Commission’s adequacy decision (Art. 45 GDPR), supplemented by the standard contractual clauses in the addendum (Art. 46(2)(c) GDPR). You can check the certification status at dataprivacyframework.gov. See its privacy policy for Cloudflare’s own processing. Apple and Google independently process data when distributing apps and providing platform services. Email, cloud and sharing services you select may also receive data. The app does not use health data for advertising or sell it. When you request a map of a recorded route on iOS, the location and route data needed for the map area is sent to Apple Maps through MapKit. On Android, the route map is created locally in the app and no map provider is contacted for it.
8. Local storage, backups and deletion
App data is stored in the device’s app area. Protection also depends on the operating system, screen lock and your settings; absolute security is not promised. In current iOS builds, internal app data is excluded from iOS device and iCloud backups and from device transfer. Backup files you export and files you explicitly save to Files or iCloud Drive remain at the destination you choose and are not automatically deleted by the app. On Android, app data is stored encrypted and excluded from Android system backups and device transfers. New backup files are encrypted with your password. The password is not saved; recovery is impossible without it. The internal quick backup has no additional password protection. Previously exported unencrypted files are not retroactively protected. Choose secure destinations. Deletion in the app does not remove recipients’ copies, system/cloud backups or data in Apple Health/Health Connect. Review and delete those separately where necessary. Minimal youth-protection markers remain securely on this device: a previous under-16/youth restriction, any correction request time and a remembered system age limit. They contain no profiles, workouts or guardian approval receipts and are used only for youth protection. Deleting data neither resets the waiting period nor removes these limits.
9. Retention
Local training and profile data remains until you delete it. Downloaded voice packs remain until removed. Exports and system backups depend on your selected services and settings. Technical connection-data retention depends on the Cloudflare services and security/logging functions used; we currently cannot state a single verified fixed deletion period. Relevant criteria are necessity for delivery, troubleshooting, security and investigation of specific incidents where applicable. We do not promise indefinite retention of consent records.
10. Contact, external links and preferences
When you email us, we process your address, message and voluntary details to handle your request (Article 6(1)(b) or (f)). Please do not send unnecessary health data. Messages are kept only as long as needed for handling the request and, where applicable, legal retention or claims. External linked sites are contacted only when opened. Fonts and images are embedded locally. There are no advertising/analytics cookies of our own. The light/dark switch applies only to the current page; language is selected through the URL without persistent browser storage.
11. Your rights
Subject to legal conditions, you can request access, correction, deletion, restriction and portability. You may object to legitimate-interest processing on grounds relating to your situation, and withdraw consent at any time for the future. Contact info@mybospark.de. We have no server copy of exclusively local data; many rights can be exercised in the app. You may complain to a supervisory authority, including LDI North Rhine-Westphalia. No solely automated decisions with legal or similarly significant effects are made; training scores provide guidance.
12. Minors, groups and changes
MYBOSPARK is intended for people aged 16 or older. On first launch, the selected group “16 or 17” or “18 or older” is stored securely on the device; no date of birth is requested and the answer is not sent to MYBOSPARK. Access is blocked below 16. People aged 16 or 17 receive only a free local youth version: manually recorded strength sessions, built-in beginner exercises, simple personal plans and a factual training overview. GPS and location recording, HealthKit/Health Connect, heart-rate sensors and Watch, body metrics and profile photos, group features, custom and advanced exercises, coach and recovery advice, BO Score and reminders, purchases, sharing and file import/export are locked. To unlock access, the youth device creates a QR request valid for no more than 15 minutes. An adult scans it in their MYBOSPARK app, confirms their parental or legal authority, the limits and consent, and authenticates with device security. The signed response contains no names, dates of birth or training data. A minimal record valid for no more than twelve months is stored securely on the youth device; it is not sent to MYBOSPARK or included in exported backups. This is not an official verification of identity, age, parenthood or legal authority and must not be understood as verified parental consent. Subscriptions and Pro content are intended only for adults and require another age confirmation before purchase. If translations differ, German is the editorial reference; mandatory statutory rights remain unaffected. From iOS build 145 / Android 1.145A: An under-16 selection, a previous youth restriction and the time of a correction request are also stored securely on your device. There is no MYBOSPARK account or server-side proof of age for this. A correction can continue no earlier than 24 hours after the request. Age information and confirmation on a second device are self-declared. Age and parental responsibility are not independently verified. Waiting is not proof of age.
13. Youth protection without a birthdate · iOS 146 / Android 1.146A
MYBOSPARK receives an age range from your system account and uses it only for youth protection. For this request, the app uploads no profile or training data and no manually entered age. An identified minor age limit is stored securely on your device. Not for advertising or statistics. Apple or Google operates the system service under its own privacy rules. The service may use an internet connection. Apple determines the age range from existing account information. Apple syncs the sharing history, including the app, date, decision and shared age range, between supported devices using end-to-end encryption; Apple states that it cannot read its contents. On Google, the Play Store provides the age range. Google states that the Age Signals client library collects no data; the Play Store runs its own data-processing operations. The technical request includes our app identifier and the library version. System services may initiate network communication. A completely transmission-free or continuously offline system request is therefore not guaranteed. On supported devices, we request an age range and its declaration method from Apple or Google Play. We receive no date of birth and send none of this information to MYBOSPARK. A minor age limit is stored securely on the device. Missing signals do not lift it; waiting and self-declaration cannot override it. Checks take place at startup, on returning to the app and on request. Account information does not prove who uses the device or has parental responsibility. Minimal youth-protection markers remain securely on this device: a previous under-16/youth restriction, any correction request time and a remembered system age limit. They contain no profiles, workouts or guardian approval receipts and are used only for youth protection. Deleting data neither resets the waiting period nor removes these limits.