TreadSimple is designed so that the developer does not operate a user account or workout database. The app stores workout information on the user’s iPhone. Data leaves the phone only when the user chooses an export or connects a service, or when a configured production build sends the limited diagnostics described below.
Information kept on the iPhone
TreadSimple stores:
- workout dates and times, duration, speed, incline, distance, estimated elevation gain, energy, and optional heart rate;
- Bluetooth device identifiers and names;
- integration job status and destination activity identifiers;
- optional height, weight, and birthday used to estimate workout energy;
- display and automatic-sync preferences;
- a bounded diagnostic history containing typed operational results, with at most 300 entries and a maximum age of seven days; and
- randomly generated installation and session identifiers used only to correlate diagnostic events. The installation identifier is stored in the iOS Keychain.
Strava access and refresh tokens are stored in the iOS Keychain. This information is used only to record, display, recover, export, and synchronize workouts.
Bluetooth
The app scans for and communicates with compatible treadmills and heart-rate monitors nearby. Bluetooth readings are processed on the phone and saved as part of the local workout. TreadSimple does not use Bluetooth to infer or collect geographic location.
Apple Health
If the user grants permission, TreadSimple writes completed indoor-running workouts, distance, active energy, and heart-rate samples to Apple Health. TreadSimple does not read existing Apple Health data. This transfer occurs on the device and does not pass through TreadSimple servers. Apple controls storage and processing in Apple Health under the user’s Apple settings and Apple’s terms.
Strava
If the user connects Strava, the user authorizes TreadSimple to upload completed workout files to the user’s Strava account. A file can include workout date and time, duration, distance, speed, incline, estimated elevation gain, and heart rate when recorded. Uploads travel directly from the phone to Strava. TreadSimple receives upload status and destination activity identifiers on the phone so it can show completion and avoid duplicate uploads.
A stateless service hosted on Amazon Web Services exchanges, refreshes, and revokes Strava OAuth credentials because Strava requires a server-held client secret. The broker processes authorization codes and tokens only long enough to service each request and does not store them. It also acknowledges Strava webhook event metadata, such as event type and activity or athlete identifiers, without building a user or workout database.
Operational logs contain request identifiers, routes, response status, payload length, event type, and the app-wide webhook subscription identifier. They do not contain workout content, OAuth credentials, athlete identifiers, or activity identifiers and are configured to expire after 14 days.
Strava separately processes information under its Privacy Policy. Strava may monitor and collect usage data related to access to its API for purposes including operating and improving its platform, support, and compliance. TreadSimple does not control Strava’s copies of data the user uploads.
Reliability diagnostics and Sentry
Configured production builds use Sentry to identify crashes and troubleshoot app reliability, compatibility, and security. A diagnostic event may include the app release and build, deployment environment, device platform and operating-system version, an error type and redacted error message, a stack trace, operation and failure codes, retry and outcome state, event duration, safe diagnostic breadcrumbs, and randomly generated installation and session identifiers. These identifiers are not derived from a name, email address, Strava account, advertising identifier, or hardware identifier. Only one-way hashes of these identifiers are sent to Sentry.
TreadSimple configures Sentry with default personal-information collection off, performance tracing off, session replay off, screenshots and view hierarchy off, and HTTP and user-interaction breadcrumbs off. Redaction controls prohibit workout and health data, heart-rate values, workout files, raw Bluetooth packets, device names and identifiers, Strava athlete or activity identifiers, OAuth credentials, authorization headers, and request or response bodies from diagnostic events. Provider-side controls are configured to remove IP-derived and geographic fields. Diagnostics are used for app functionality and security only, not advertising, marketing, cross-app tracking, or behavioral analytics.
Sentry acts as a service provider for TreadSimple under its customer and data-processing terms. Information about Sentry’s privacy practices is available in its Privacy Policy. Ordinary remote diagnostic events are configured for a 30-day retention period. The Sentry SDK may temporarily queue a limited number of unsent events on the iPhone while the device is offline. When a build has no Sentry configuration, remote diagnostic reporting remains off.
What TreadSimple does not do
TreadSimple does not:
- create a TreadSimple user account;
- collect a name or email address through the app;
- access contacts or photos;
- collect geographic location;
- display advertising or track users across other companies’ apps or websites;
- sell personal information;
- use health, fitness, or Strava data for advertising, marketing, data brokerage, or artificial-intelligence models; or
- use reliability diagnostics for advertising, marketing, behavioral analytics, or user profiling.
Retention and deletion
The local database remains on the iPhone until it is deleted in TreadSimple or the app is removed. Because iOS Keychain items can survive an app reinstall, Settings > Privacy & Legal > Delete all TreadSimple data should be used to revoke and clear Strava credentials and delete the local workout database, samples, remembered devices, sync jobs, settings, local diagnostic history, queued diagnostic events, and the anonymous installation identifier. Disconnecting Strava also revokes its token and removes local Strava-supplied identifiers.
If revocation cannot reach Strava, the user should remove TreadSimple from Strava’s connected-app settings. Deleting local data does not delete workouts already sent to Apple Health or Strava; those copies must be managed in the destination service. AWS operational logs expire automatically after 14 days. Sentry diagnostic events expire automatically after 30 days. Because diagnostic events are not associated with a TreadSimple account, a deletion request may require information sufficient to locate the relevant anonymous installation identifier.
Security and providers
TreadSimple uses the iOS app sandbox, Keychain, HealthKit authorization, TLS network connections, and narrow OAuth permissions. Amazon Web Services provides the stateless broker and operational logging. Sentry provides crash and reliability diagnostics. Strava receives data only when the user authorizes and uses that integration. These providers are required to protect data under their agreements and applicable law. Third parties receiving data through the app are required to provide protection equal to or greater than the protection described in this policy and required by Apple’s guidelines. No security measure can guarantee absolute security.
Choices, children, and changes
Workout recording and local history work without a TreadSimple account and without connecting Strava or Apple Health. Automatic sync is off by default. Users can disconnect Strava in the app, manage Apple Health and Bluetooth permissions in iPhone Settings, and delete all local data in the app. Essential redacted diagnostics are enabled in configured production builds; privacy questions and requests concerning retained Sentry events can be sent to the address below.
TreadSimple does not knowingly collect personal information from children through a TreadSimple account or server database. Optional third-party integrations remain subject to each service’s age requirements and terms.
This policy may be updated when data practices change. Its effective date will be revised and material changes will be presented as required.
TreadSimple is operated by the developer identified on its App Store listing. Privacy questions or deletion requests can be sent to privacy@treadsimple.com. Because TreadSimple normally has no server-side user record, the developer may direct the user to the on-device or connected-service controls described above.