HEARTTX PRIVACY
Your data, explained.
Your heart rate is processed on your watch and sent directly over Bluetooth. It is not sent to the developer.
Who is responsible
HeartTX is provided by Matus Kramarik, U Hrncir 643, Vestec, Czechia. Contact: mat.kramarik@gmail.com.
Heart rate and workout access
With your permission, HeartTX uses Apple HealthKit to read your current heart rate and starts an indoor cycling workout session to keep measurement running. It displays your pulse and sends fresh readings through the standard Bluetooth Heart Rate Service while a session is active.
The app keeps the latest reading and a pending transmission in memory. Readings older than 10 seconds are not displayed or sent. It does not build a heart rate history or upload health data to a server. Stopping clears these temporary readings and discards the HeartTX workout.
Apple Watch and Apple Health may independently retain health samples or credit Activity rings. HeartTX does not erase Apple Health records. See Apple’s Health privacy information for how Apple handles these records.
Bluetooth sharing
Starting a session makes HeartTX discoverable as a heart rate sensor. Nearby compatible devices can connect and receive your live heart rate without a pairing code. HeartTX does not authenticate the receiver or require an encrypted Bluetooth connection, so the broadcast is not private to a selected app or person. Broadcast only when you intend to share your pulse with nearby receivers.
Tap Stop or let the timer finish to stop broadcasting. The receiving fitness app or device may store, sync or share received measurements under its own privacy policy. HeartTX cannot delete those records. Check the receiver’s privacy settings before pairing.
What stays on the watch
The selected timer duration is stored locally so it can be reused. Temporary Bluetooth connection identifiers are used in memory to count connected receivers and route measurements; the app does not retain a device history. There is no account, cloud sync, advertising, tracking or analytics SDK in HeartTX.
Your choices
Start and Stop control a session. Timer limits its duration. You can revoke heart rate, workout or Bluetooth permissions in the relevant Apple Health or watch Settings controls. Removing the app removes its app data, subject to the system’s backup and restore behavior. Manage any records in Apple Health or a receiving app separately.
Support messages
If you email the developer, your email address and message are used to respond and resolve the request. This is optional and not required to use the app. Please avoid including health readings or other sensitive information. Email is handled through Gmail under Google’s privacy policy, and may be processed outside your country, including outside the European Economic Area.
Support correspondence is kept only as needed to handle your request and any related legal obligations or disputes. You can request deletion by email. We do not sell support contact details or use them for marketing.
This website
These static pages use no cookies, analytics, advertising, forms, external fonts or client-side scripts. The personal server in Czechia processes the network information necessary to deliver a page, including your IP address. Access logging is disabled for the HeartTX pages. Email and external links open services with their own privacy practices.
Rights and requests
Where applicable, you may request access, correction, deletion, restriction or portability of personal data held by the developer, and object to processing. Permission for on-watch health access can be withdrawn in Settings. Support processing is based on handling your request and the legitimate interest in resolving it; technical website processing is necessary to deliver the requested pages.
Contact mat.kramarik@gmail.com to exercise your rights. The developer does not hold your heart rate history or a HeartTX user profile. You may also contact your local data protection authority; in Czechia this is the Office for Personal Data Protection.
Changes
This policy will be updated if the app’s data practices change. The effective date above identifies the current policy.