Privacy

1. Controller

2. Training, settings and synchronisation

When a workout finishes or you stop it, KieserTiming saves its date, time and cycle count. Cancelling during the iPhone’s initial countdown creates no history entry. History is stored locally on each device and synchronised through Apple CloudKit when iCloud access is available. Training entries and necessary connection data are sent to Apple for this purpose. You do not need a separate KieserTiming account.

Total duration, hold and movement times, sound and feedback preferences are stored locally. The three training times are sent from the iPhone to a paired Apple Watch with the Watch app installed. History synchronisation through iCloud is a separate process. We do not operate a server for your training history.

Processing needed to provide the timer, history and synchronisation features you request is based on Article 6(1)(b) GDPR. iCloud follows your Apple settings. Apple may also process data outside the EU/EEA. See Apple’s privacy policy for recipients, retention and safeguards.

3. Apple Watch and health data

The Watch app requests HealthKit permission to read your heart rate and use workout sessions. With your permission, it retrieves current heart rate readings and displays them during training. A workout session helps the app keep running when you lower your wrist.

KieserTiming does not save heart rate readings in its training history or send them to our servers, Google or other advertising partners. Health data is not used for advertising. Permission is optional and can be changed or revoked in Apple Health or system settings. Without permission, the relevant health features are unavailable. Processing of the health data you authorise is based on your explicit consent under Articles 6(1)(a) and 9(2)(a) GDPR.

You manage data stored in Apple Health and any Health synchronisation through iCloud separately with Apple. See Health App & Privacy.

4. Advertising and your choices

The iPhone app shows banners through Google AdMob. Data may include your IP address and approximate location, device or app identifiers, diagnostics, performance information, ad views and interactions. It is used for ad delivery, measurement, troubleshooting and abuse prevention. See Google’s data collection disclosure.

KieserTiming uses Google’s consent dialogue to manage your choices. The app checks consent status at launch and only requests ads when Google’s consent manager permits it. Where required, you are asked for consent and a privacy settings option appears in the app’s settings so you can change your choices. Refusing personalised advertising does not necessarily stop all ads or all technical processing.

Advertising processing requiring consent is based on Article 6(1)(a) GDPR. You can withdraw consent for future processing. Where legitimate interests under Article 6(1)(f) GDPR apply to necessary technical processing or abuse prevention, you may object as provided by the GDPR. The privacy dialogue explains the relevant purposes, providers and choices.

Google and any advertising partners named in the dialogue may process data outside the EU/EEA, including in the United States. See Google’s privacy policy, its international transfer safeguards and retention criteria. The app does not send training entries or HealthKit readings as advertising data.

5. Retention and deletion

Training history remains on your devices and, where applicable, in iCloud until you delete the entries or the relevant app data. KieserTiming does not automatically delete entries after a fixed period.

In the iPhone history view, you can delete individual training sessions or remove all entries for a day after confirmation. With iCloud synchronisation active, these deletions also propagate to your other synchronised devices. This may take some time depending on connectivity and synchronisation status. Deleting a KieserTiming entry does not delete data in Apple Health or existing device backups.

You can remove local data by fully deleting the app and its data from each device. Offloading the app is not a full data deletion. iCloud data, data on other devices and backups may need to be removed separately using Apple’s storage and backup management. Turning off synchronisation alone does not delete existing cloud data; synchronising again may restore it to a device. KieserTiming only holds heart rate values temporarily for display; deleting the app does not delete data stored in Apple Health.

6. Contacting us

If you use the contact form or email us, we process your name, email address and message to handle your enquiry. The form also sends the app name, language and form URL. Enquiries are sent by email and are not stored as contact submissions in the website database.

We use Resend (Plus Five Five, Inc., USA) to send email. Data needed for delivery is processed in the United States; Resend’s data-processing terms provide for EU Standard Contractual Clauses. See Resend’s Data Processing Addendum.

The legal basis is Article 6(1)(b) GDPR for contract-related enquiries, or Article 6(1)(f) GDPR for our interest in responding to other enquiries. Correspondence is retained as needed to handle the enquiry and meet any applicable legal retention obligations. Without a reply address, we cannot respond.

7. Visiting this website

These app pages are part of crazysoft.at. For hosting, server logs, session data and audience measurement with Matomo, see the website privacy policy (German). Use of the training app and website audience measurement are separate activities.

These app pages load fonts from Bunny Fonts, which establishes a connection to that provider. The provider states that Bunny Fonts uses no tracking, cookies or access logs. Fonts support a consistent, readable presentation based on our legitimate interest under Article 6(1)(f) GDPR.

8. Your rights and contact

Subject to the GDPR, you have rights of access, rectification, erasure, restriction, portability and objection, and may withdraw consent. Contact office@crazysoft.at. You may also complain to a supervisory authority, including the Austrian Data Protection Authority.

We update this policy when our processing changes. The date above identifies the current version.