Privacy Policy

Last updated 6 September 2026

Who is responsible

Ride Blocks is developed and operated by Emanuel Pumnea, an individual developer. For anything in this policy, write to support@rideblocks.com.

What stays on your device

Everything you create in Ride Blocks — your FTP, training plans, generated workouts, saved rides and their power, cadence, and heart-rate samples, and your settings — is written to storage on your own device. There is no Ride Blocks account and no Ride Blocks server: we operate no service that receives your training data, and none of it is sent to us.

iCloud Sync

iCloud Sync is off by default. You turn it on per device in Settings → iCloud Sync → Sync with iCloud, on each Mac, iPhone, or iPad you want included, all signed in to the same Apple Account.

When it is on, Ride Blocks stores your generated workouts, training plan, and ride history in the private database of your own iCloud account using Apple’s CloudKit. Apple processes and stores that data under Apple’s iCloud terms and privacy policy. It is tied to your Apple Account, not to any account with us, and we cannot read it, list it, or access it in any way. Turning the switch off stops further syncing; it does not delete what is already in iCloud — see Data controls and deletion.

The Apple Watch app mirrors the workout running on your paired iPhone. It does not show or store your synced plan and history.

Health data and sensors

With your permission, Ride Blocks writes completed indoor rides — duration, energy burned, heart rate, power, and cadence — to Apple Health on iPhone and iPad. On Apple Watch it reads your heart rate during a ride.

• Sensor and health samples are used to show your live metrics, to save the finished ride, and to compute the training analytics Ride Blocks shows you — power-duration curves, time in zones, training load, and FTP history. All of that analysis happens on your device.
• Heart rate measured on Apple Watch travels to your paired iPhone over Apple’s Watch Connectivity so the phone can display and record it. This is a direct link between two of your own devices.
• Saved rides, including their samples, sync through your private iCloud database if — and only if — you have turned iCloud Sync on.
• Health and sensor data is never sent to us, never shared with third parties for their own purposes, never used for advertising or marketing, and never sold.
• Once a workout is in Apple Health, it belongs to Apple Health: it syncs and is retained according to your own Apple settings. See Apple’s Health app privacy information.
• You can review or revoke Ride Blocks’ access at any time in Apple’s Health app, under its privacy and app-permission settings.

Ride Blocks connects directly to Bluetooth power meters, heart-rate straps, and cadence sensors, and on Mac to ANT+ sensors through a USB receiver. Those are local radio links between your device and your own equipment.

Diagnostics and crash reports

Ride Blocks keeps a diagnostic log on your device to help fix bugs. It is on by default and can be turned off, and the log deleted, in Settings → Diagnostics at any time. Turning it off stops event logging and crash capture; nothing recorded while it was on leaves your device unless you send it.

• Diagnostic logs record app events and technical details: an event is drawn from a fixed list of app actions — such as “workout started” or “sensor connected” — and may carry counters, error codes, and, for errors, a code-level stack trace. The log is not a place where your notes, ride data, or fitness values are written.
• It also records your app version, operating system version, and device type (iPhone, iPad, or Mac).
• Crash reports are captured on device and stored alongside the log. Before one is written to disk it is processed to redact recognised patterns — email addresses, home-folder and app-container paths, unique identifiers, and paths in report headers. This is pattern matching, not a guarantee that every possible identifier is caught, which is why you can read a report before sending it.
• Storage is bounded: Ride Blocks keeps a small, fixed number of log segments and crash reports and discards the oldest as new ones arrive. Deleting the logs removes them immediately.
• Reports stay on your device unless you choose to share them. Ride Blocks performs no automatic upload and sends nothing to a crash-reporting service. Your operating system may run its own separate crash reporting, which is governed by your system settings and Apple’s policies rather than by Ride Blocks.

If you choose to send a diagnostic report, Ride Blocks prepares the log as a plain-text file and hands it to your own email app or share sheet. You can read the file first, and you decide each time whether to send it.

Data controls and deletion

Everything Ride Blocks stores can be removed from the app:

• Settings → iCloud Sync → Sync with iCloud — turn syncing on or off for this device. Turning it off stops further syncing but leaves data already in iCloud in place.
• Settings → iCloud Sync → Delete iCloud Data — removes all Ride Blocks data from iCloud and turns sync off. The data on the device you are using is kept.
• Settings → History → Delete All History — permanently removes every saved ride from the device.
• Settings → Diagnostics → Delete All Logs — permanently removes the diagnostic events and crash reports stored on the device.
• Deleting the app removes what remains on that device.

Workouts already written to Apple Health are stored by Apple Health, not by Ride Blocks. Deleting your Ride Blocks history does not remove them — delete those in the Health app.

If you contact support

When you email support@rideblocks.com, we receive your email address, your message, and anything you attach — including a diagnostic log, if you send one. We use them only to answer you and to investigate the problem you reported. We do not add you to any mailing list, and we do not use support correspondence for advertising or sell it to anyone.

Support mail is handled by a third-party email provider, which processes and stores messages and attachments on our behalf, as any email service does. Messages are kept only as long as they are useful for supporting you, and then deleted. If you would like your correspondence deleted sooner, ask and we will do it.

What Ride Blocks does not do

• No usage analytics and no automatic telemetry. (The training analytics in the app are computed on your device, for you.)
• No tracking, and no data linked to you across other apps, websites, or companies.
• No advertising, and no advertising identifiers.
• No Ride Blocks account, sign-up, or password. The only account involved is your own Apple Account, and only if you use iCloud Sync or Apple Health.
• No third-party analytics or advertising SDK.
• No selling or sharing of your data.

This website carries no analytics scripts, no cookies set by us, and no tracking pixels. Like any website, it is served by a host that may keep ordinary request logs for security and reliability.

Links out of the app

Ride Blocks can open the App Store so you can leave a review. That opens Apple’s own App Store app and is covered by Apple’s privacy policy.

Children

Ride Blocks is not directed at children under 13 and we do not knowingly collect information from them.

Changes to this policy

If this policy changes, the updated version will be posted here with a new date. If a future version of Ride Blocks collects something this policy does not describe, this page and the app’s App Store privacy label will be updated before that version ships.

Contact

Questions about this policy or about privacy in Ride Blocks: support@rideblocks.com.