Legal

Privacy Policy — HUB.

Last updated: 2 July 2026

This Privacy Policy explains how the HUB. iOS app (“HUB.”, “the app”, “we”, “us”) handles your information. HUB. is a cycling computer app developed by an individual developer, Jan Kraner (“the Developer”).

In short: HUB. is built to keep your data with you. It has no servers of its own, no analytics, no advertising, no tracking, no third‑party SDKs, and no user accounts or logins. Your data stays on your device, in your own private iCloud, and in Apple Health. The only company that processes any of your data is Apple, through services you already use (iCloud, Apple Health/HealthKit, and Apple Weather/WeatherKit).

1.Who is responsible for your data

The data controller for the purposes of the EU General Data Protection Regulation (GDPR) and similar laws is:

• Jan Kraner (independent app developer), Czech Republic
• Contact: privacy [at] ridewithhub [dot] com

Because HUB. has no back‑end servers, the Developer does not have access to your rides, routes, health data, photos, or location. That information is stored only on your device and in accounts that belong to you (your iCloud and your Apple Health).

2.What data HUB. uses, and why

a) Precise location / GPS

• What: Your precise GPS location and the route you cycle.
• Why: To track a ride, calculate speed and distance, and draw your route on the map.
• Background use: With your permission, HUB. uses location in the background (“Always”) so it can keep recording a ride when your phone is locked or the app is not on screen. iOS shows the system location indicator while this happens.
• Where it goes: Stored on your device and synced to your own private iCloud (see Section 4). It is not sent to the Developer or any third party.

b) Health & fitness (Apple Health / HealthKit)

• What: Cycling workouts, distance travelled, and the route of a workout.
• Why: To save your rides as workouts in Apple Health, and to read health data to improve ride tracking.
• Where it goes: Stored in Apple Health on your device. In line with Apple’s rules, HealthKit data is never copied to iCloud or anywhere else by HUB.

c) Weather (Apple Weather / WeatherKit)

• What: Your current location is sent to Apple’s WeatherKit service to fetch weather conditions (temperature, wind, precipitation) for your ride.
• Why: To show live weather during a ride and to record a weather summary for each ride.
• Where it goes: Sent to Apple as the weather provider. Weather data provided by Apple Weather. See Apple’s legal attribution page: https://weatherkit.apple.com/legal-attribution.html

d) Content you create

• What: Your display name, an optional profile photo, and optional bike names and photos.
• Why: To personalize the app and let you organize rides by bike.
• Where it goes: Stored on your device and synced to your own private iCloud. Photos are compressed before storage.

HUB. does not collect your contacts, browsing history, advertising identifiers, or any data for advertising or tracking purposes.

3.Legal basis for processing (GDPR)

Where GDPR applies, we rely on the following legal bases:

• Consent (Art. 6(1)(a)) — for access to precise location and to Apple Health. You grant this through the standard iOS permission prompts, and you can withdraw it at any time in iOS Settings.
• Performance of the app’s core function (Art. 6(1)(b)) — processing needed to provide the ride‑tracking features you asked for.

Location and health data are special/sensitive categories of data. They are processed only on the basis of your explicit consent given through the iOS system permission prompts, and only to provide the features you use.

4.Where your data is stored

• On your device — ride history, routes, bikes, and settings are stored locally using Apple’s on‑device database (SwiftData) and Apple Health.
• In your own iCloud — if you are signed in to iCloud, your rides, bikes, and app settings sync through your private iCloud account (Apple’s CloudKit private database and iCloud key‑value storage). This is your personal iCloud storage; the Developer cannot see or access it.
• Apple as a processor — iCloud, Apple Health, and Apple Weather are provided by Apple. Apple processes this data under Apple’s own privacy policy: https://www.apple.com/legal/privacy/

The Developer operates no servers and stores none of your data on its own infrastructure.

5.Data sharing

We do not sell, rent, or share your personal data with third parties for their own purposes. There are no advertising networks, analytics providers, or third‑party SDKs in HUB. The only data flows are to Apple’s services (iCloud, HealthKit, WeatherKit) as described above, acting as a processor on your behalf.

6.Data retention

Your data stays until you delete it. You are in control:

• Delete an individual ride by swiping it away in the History screen.
• Remove bikes and photos from within the app.
• Turn off iCloud sync for HUB. in iOS Settings to stop cloud syncing.
• Revoke location or Health access at any time in iOS Settings.
• Delete the app to remove its on‑device data; iCloud copies can be removed via iOS Settings → your name → iCloud → Manage Account Storage.
• Health data is managed in the Apple Health app.

7.Your rights

Depending on where you live (e.g. the EU/EEA under GDPR, or California under CCPA/CPRA), you may have rights to access, correct, delete, or export your personal data, and to withdraw consent.

Because HUB. stores your data only on your own device and in your own iCloud and Apple Health, you already have direct access to all of it and can view, change, export, or delete it yourself at any time using the app, iOS Settings, and the Apple Health app.

HUB. does not sell or share personal information as those terms are defined under California law. If you have any questions or requests regarding your data, contact privacy [at] ridewithhub [dot] com.

8.Children’s privacy

HUB. is not directed at children and does not knowingly collect data from children. It is a general‑audience fitness app.

9.Security

Data on your device is protected by iOS’s built‑in security and device encryption. Data in transit (for example, weather requests and iCloud sync) is protected using standard system encryption (HTTPS/TLS). HUB. uses only Apple’s system frameworks for networking and does not implement any custom or non‑standard encryption.

10.Changes to this policy

We may update this Privacy Policy from time to time. The “Last updated” date at the top will reflect the latest version. Material changes will be reflected in an updated version of the app or this page.

11.The website (ridewithhub.com)

The policy above describes the HUB. app. This website is operated by the same developer and is separate from the app; the app itself contains no analytics or tracking. For transparency, here is what happens on the website:

• Analytics: We use PostHog, configured in a privacy‑friendly, cookieless way. It stores nothing on your device — no cookies and no persistent identifiers — and we do not use session recording or advertising. It runs first‑party through our own domain and only helps us understand aggregate, anonymous usage (page views, scroll depth, and whether the “Get notified” button was clicked). Because nothing is stored on your device, no cookie banner is required.
• Waitlist email: If you enter your email in the “Get notified” form, it is stored by our email provider Brevo for the sole purpose of notifying you when HUB. launches. We do not use it for anything else, and you can ask us to remove it at any time via the contact below. Brevo acts as our processor; see Brevo’s privacy policy: https://www.brevo.com/legal/privacypolicy/
• Hosting: The site is hosted by Wedos. As with any website, the host may process standard server logs (including your IP address) for security and operation.

12.Contact

Questions about this Privacy Policy or your data:
Jan Kraner — privacy [at] ridewithhub [dot] com