Privacy Policy

Last updated: 2026-10-08

CycleBridge is a cycling computer from Y-A-S ApS (https://y-a-s.net/), made up of three apps that share this name: a Garmin Connect IQ watch app, an Apple Watch app, and a phone app (iPhone and Android). This policy covers all three, referred to below as “the Garmin watch app”, “the Apple Watch app” and “the phone app” to tell them apart.

The Apple Watch app is not currently distributed: it is not part of the phone app in the App Store or in TestFlight, and it is not available anywhere else. Everything this policy says about the Apple Watch app describes how it is built and applies only once it is released. This paragraph will be removed then.

What data is accessed

While recording a ride, the apps read:

• GPS location (speed, distance, route, elevation)
• Heart rate, from a watch’s sensor or a paired BLE heart rate strap
• Elapsed time
• Your configured heart rate zones — read from the watch’s own user profile on the Garmin watch app, or worked out from a maximum heart rate you enter yourself on the Apple Watch and phone apps — so each can show how much of the ride you spent in each zone

On the Apple Watch, whether GPS is read on the watch at all is your choice at the start of every ride: choosing “Phone GPS” means the watch never starts its own location services, and it reads only heart rate and elapsed time.

How that data is used

The Garmin 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 Garmin 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 Garmin watch app, on the watch itself: Time spent in each heart rate zone is counted while a ride runs and shown on the watch’s zone screen, and the watch likewise keeps a short recent history of the ride in memory — a sampled climb profile and your last few kilometres — to draw the climb and splits screens. None of it is kept once the ride ends. Your own preferences for the Garmin watch app (which metric to show large, how often to alert you by distance, and so on) are stored on the watch by Garmin’s standard app-settings mechanism and edited in Garmin Connect Mobile or Garmin Express. Neither is sent anywhere by the app.

The phone app, Garmin-watch mode: Live data received from the watch app is displayed on the phone only. It is not saved to Apple Health or Health Connect — the watch’s Garmin Connect record above remains the one saved copy, so nothing is duplicated there. The only things kept on the phone are the ride summary and route described under “Ride history” below.

The Apple Watch app (watch → Apple Health): If you save a completed ride, it’s recorded as a standard cycling workout in Apple Health (HealthKit) on the watch, exactly as a ride recorded by Apple’s own Workout app would be — including the route, if you chose “Watch GPS” for that ride, and the perceived effort and feel you rate afterwards. That storage is governed by Apple’s own health-data privacy rules, not this one. It is not sent anywhere by the app.

The Apple Watch app (watch ↔ phone): Live ride data is exchanged with the phone app over Apple’s WatchConnectivity, which carries it directly between your own paired watch and phone and nowhere else. In “Phone GPS” mode the watch sends only your heart rate and elapsed time, and receives speed and distance from the phone so it can display them; in “Watch GPS” mode it sends the full ride snapshot, including position. Either way the data goes only to your own devices — never to any server operated by the developer or any third party.

The Apple Watch app, on the watch itself: Time spent in each heart rate zone is counted while a ride runs, and a short recent history of the ride — a sampled climb profile and your last few kilometres — is kept in memory to draw the climb and splits screens. None of it is kept once the ride ends. Your preferences (which metric to show large, battery saver, distance alerts, and the maximum heart rate the zones are worked out from) are stored on the watch by the operating system’s standard app-settings storage, and are never sent anywhere.

The phone app, Apple-Watch mode: Live data received from the Apple Watch app is displayed on the phone only. As with Garmin mode, it is not saved a second time to Apple Health — the workout the watch itself saved is the one record, so nothing is duplicated. The only things kept on the phone are the ride summary and route described under “Ride history” below.

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.

The phone app, on the phone itself: While a ride runs, the app works out time spent in each heart rate zone, the last half hour of your climb profile, and per-kilometre splits from the live ride data, purely to draw them on the ride screens; none of that working-out is kept once the ride ends. Your preferences for the phone app (which data source to use, the maximum heart rate the zone screen measures against, and which ride screen preset is active) are stored on your phone by the operating system’s standard app-settings storage, and any ride screen presets you build are kept in the app’s own storage on your phone. None of it is sent anywhere.

Ride history (all phone-app modes): When a ride ends, the phone app keeps a short summary of it on your phone — start time, duration, distance, elevation gain, and average/maximum speed — so it can show your monthly and yearly totals on the Statistics screen. If the ride had GPS positions, its route is also kept as a GPX file in the app’s Route Library. Both stay only on your phone, in the app’s own storage, and are removed when the app is uninstalled. They are never sent anywhere.

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.

Map tiles: The phone app’s map draws tiles fetched from OpenStreetMap’s public tile servers as you move, so those servers necessarily see your device’s IP address and which squares of the map you asked for — which is a rough indication of where you are riding. Nothing else is sent with the request: no ride data, no position log, no identifier, no account, and there is no key or login involved. Tiles are only fetched while a map is actually on screen, and what OpenStreetMap does with the request is governed by their tile usage policy and their privacy policy, not this one.

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 watch app shows ads, and neither contains any third-party SDK.

If you are in the European Economic Area or the United Kingdom, the phone app asks for your consent to ads at the end of its short intro the first time it opens, using Google’s standard consent form, and shows no ad until you have answered. You can change your answer at any time from Ad privacy options in the app’s settings sheet.

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 and OpenStreetMap’s tile servers 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 any of the apps stops all data handling described above.

On the Apple Watch you additionally choose, at the start of every ride, whether the watch reads GPS at all. You can also revoke the Health and Location permissions the Apple Watch app asks for at any time, in the watch’s own Settings or the Watch app on your iPhone.

Garmin’s role

Any data submitted to the Garmin watch app is submitted to the developer (Y-A-S ApS), 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.

Apple imposes no equivalent attribution term, so there is no matching section for the Apple Watch app — its absence is deliberate, not an oversight. Workouts the Apple Watch app writes are stored by Apple Health on your own devices under Apple’s health-data privacy rules.

Contact

CycleBridge is published by Y-A-S ApS, CVR 45856186, Bådebrogade 1, 6700 Esbjerg, Denmark, which is the data controller for anything this policy describes.

Questions about this policy: [email protected]

If you believe your data is handled wrongly, you can complain to the Danish Data Protection Agency (Datatilsynet), https://www.datatilsynet.dk/.