Privacy Policy — CycleBridge

Last updated: 2026-09-03

CycleBridge is a personal cycling computer project by Matej Mazur, made up of two apps that share this name: a Garmin Connect IQ watch app and a phone app (iPhone and Android). This policy covers both, referred to below as “the watch app” and “the phone app” to tell them apart.

What data is accessed

While recording a ride, the apps read:

• GPS location (speed, distance, route, elevation)
• Heart rate, from the watch’s sensor or a paired BLE heart rate strap
• Elapsed time

How that data is used

The watch app (watch → phone): Live ride data is sent over Bluetooth directly to the phone app on your own paired phone, for real-time display only. It goes only to your own device — never to any server operated by the developer or any third party.

The watch app (watch → Garmin Connect): If you save a completed ride, it’s recorded using Garmin’s standard Activity Recording (FIT file) and synced to your Garmin Connect account exactly as any other Garmin activity would. That storage is governed by Garmin’s own privacy policy, not this one.

The phone app, Garmin-watch mode: Live data received from the watch app is displayed on the phone only. It is not saved anywhere on the phone — the watch’s Garmin Connect record above remains the one saved copy, so nothing is duplicated into Apple Health or Health Connect.

The phone app, phone-sensor mode: When using the phone’s own GPS and a paired BLE heart rate strap (no watch involved), ride data is saved as a workout on your device — via Apple Health (HealthKit) on iPhone, or Health Connect on Android — governed by Apple’s or Google’s own health-data privacy rules respectively. It is not sent anywhere else.

GPX import/export: Exporting a ride or importing a route creates a file you explicitly choose to save or share via the phone’s own share/file-picker sheet — the app does not upload it anywhere itself. Imported routes are stored locally on your phone.

Advertising

The phone app shows a small banner ad, supplied by Google AdMob, on the idle screen only — it is never shown while a ride is recording. These ads are non-personalized: they are not based on your activity or a profile built from your data, only on general context (e.g. what’s in the app). Serving them still means the AdMob SDK on your phone communicates with Google’s ad servers and may access general device information (such as a device or advertising identifier, IP-based coarse location, and app usage signals) for ad delivery and fraud prevention — governed by Google’s own privacy policy, not this one. Neither app shows ads or third-party SDKs anywhere else.

What these apps do not do

• No data is sent to any server operated by the developer.
• No data is shared with third parties, other than Google AdMob as described above.
• No accounts or analytics. No personalized advertising.

Your control

Data is only recorded or transmitted while a ride is actively running, started manually. Ending a ride or uninstalling either app stops all data handling described above.

Garmin’s role

Any data submitted to the watch app is submitted to the developer (Matej Mazur), not to Garmin. Garmin has no responsibility or liability for that data. Garmin Connect’s own storage of your saved activities is governed separately by Garmin’s privacy policy, not this one.

Contact

Questions about this policy: [email protected]