Policy Draft

Location Data Policy

Location is central to ride recording, route progress, map context, and climb-ahead features. This page explains how ClimbDeck intends to handle it.

Why location is used

  • Start, pause, resume, and stop ride recording.
  • Calculate distance, speed, elevation gain, and route progress.
  • Render rider position on maps and route previews.
  • Support route-based climb progress and future route-free terrain preview providers.

How location works today

ClimbDeck currently uses location while the app is open and a ride is active. Background ride recording is not available.

Storage

Ride samples, route progress, and recovery state are intended to be stored locally first so rides can survive interruptions and poor connectivity.

Sharing

Location should not be shared with coaches or portal viewers unless the rider has explicitly approved a feature and the shared location scope is clearly documented.

Route-free previews should never fabricate the road ahead when no approved provider is configured.

Controls

Riders can control location access through device permissions. Future in-app controls should explain how location affects ride recording, navigation, and climb context.

Updates

If background tracking, cloud sync, live tracking, or portal sharing expands the location footprint, this page should be updated before release.