Indoor Rodeo Privacy Policy

Scope

This policy covers the apps, websites, beta programs, and support services published under the Indoor Rodeo brand. Some sections apply only when an app offers the feature described.

How our apps handle workout data

Our apps process workout data locally to provide their features and record your activity. Live health or fitness data can come from an Apple Watch or a Bluetooth source. Apple Health access is optional and requires your permission. Depending on the app and the permissions you grant, an app may read health data locally or write a completed workout to Apple Health. Using Apple Health, an Apple Watch, or a Bluetooth source does not by itself send that data to our servers.

HOLDR keeps its complete ride history, heart-rate samples, controller evidence, and learning/profile state on the device. HOLDR does not upload that graph to an app-owned iCloud/CloudKit database, so it does not automatically sync between devices. Device-local data may be included in an Apple-managed device backup when you enable that backup; that backup is controlled by you and Apple, not an app-owned CloudKit database, and HOLDR cannot directly access it.

Optional workout analytics

An app may ask whether you want to share eligible future workouts so we can evaluate and improve its algorithms. Sharing is optional and off by default in public releases. A screened beta may require sharing as a condition of participation. For a screened beta that requires it, HOLDR shows a blocking in-app acknowledgement before enabling the sharing queue. The app and its Settings screen disclose the requirement.

When workout sharing is available, the app explains which workouts qualify before you enable it. Shared data may include:

• A workout trace, such as heart rate, targets, measured power, cadence, speed, workout-relative sample offsets, and workout phase
• Workout targets, phases, settings, summaries, warnings, and measurements used by adaptive features
• Controller states and decisions, feature switches, calibration proposals, and whether a proposed adjustment was shown, accepted, rejected, or applied
• Answers to a short series of bounded, categorical warmup questions. The app does not collect free-form warmup narratives
• App version and build, operating-system version, device class, and the type of connected health or fitness source
• A submission date at day granularity
• A random sharing ID

The sharing ID is pseudonymous, not anonymous: it can link workouts you choose to share so we can evaluate an app's algorithms across workouts. It is random and is not derived from your Apple ID, name, account, or hardware identifier.

The upload does not include your name, email address, location, Apple ID, HealthKit identifiers, a device serial number or UDID, or precise workout timestamps.

If you contact us for support, give beta feedback, or request deletion, the information you provide may let us identify which shared workouts are yours. We may associate your identity or feedback with those workouts only to investigate the issue, evaluate the controller behavior described in your feedback, provide support, or act on your deletion request. This does not add your identity or contact information to the app's workout upload.

What we never do

Our apps show no ads and use no third-party advertising trackers. We never sell your data. We do not use health data for advertising or marketing.

Your control

When optional workout sharing is available, you can turn it on or off in the app's Settings screen. Turning it off deletes unsent workouts and calibration events from that app's local upload queues and deletes its local sharing ID. It does not delete data already uploaded. In a screened beta that requires sharing, you can withdraw by stopping use of and uninstalling the beta.

Deleting or discarding a ride from the app's local history does not delete telemetry already uploaded.

To request deletion of uploaded data, email privacy@indoor.rodeo. If the information you provide lets us locate matching records, we will delete them. Because the upload itself has no name, email address, account, or hardware identifier, we may be unable to locate every record and cannot guarantee that an identity-to-workout mapping exists.

Data retention

Workout analytics and warmup-calibration events are kept for 90 days based on the UTC date received. The daily cleanup deletes them on day 91. Any case-specific association we create between a tester's identity or feedback and those records is kept only with the support case and deleted within 90 days based on the UTC date the association was created. We do not maintain a standing identity-to-sharing-ID directory.

Problem reports

When you choose to send a problem report, the app sends the description you provide and may include a diagnostics file. Depending on the problem and app, the file can include app activity, Bluetooth activity, nearby and remembered device names, hashed device identifiers, signal strength, permission and connection states, app version, operating-system version, device model, and diagnostic logs. We use this information only to investigate the report and provide support. When useful for that investigation, we may associate the report with a beta tester or shared workouts. We keep the report for 90 days based on the UTC date received, then delete it in the daily cleanup on day 91.

Website support

If you contact us through indoor.rodeo/support, we use your message and email address to reply and provide support. We may associate them with shared workouts when useful to investigate your request. We keep them for 90 days based on the UTC date received, then delete them in the daily cleanup on day 91. If you email us, we retain your message and email address for up to 90 days, then delete them.

Website campaign measurement

When you open a published campaign link or continue from that page to a beta application, we record only the campaign label, event type, UTC calendar day, and an aggregate count. We do not store IP addresses, device identifiers, cookies, referrers, or application answers for this measurement. We use these counts to compare outreach channels.

Beta applications

If you apply for a screened beta through a third-party form, your application may include your name, email address, device and operating-system version, connected-equipment details, expected usage, and answers about beta participation. The form provider processes this information under its own privacy terms. We use application data to select testers, send beta invitations, communicate about testing, provide support, and associate a tester's feedback with shared workouts when needed to evaluate the controller behavior described in that feedback. Application data is deleted within 90 days after the beta ends.

Contact

For privacy questions or requests, email privacy@indoor.rodeo.