App Data

Privacy and Security

5KClock is designed to keep timing data local by default while allowing optional account-based sync to Copley Running.

Storage and Sync

Local Data

  • Athlete lists, rosters, cached races, CSV sessions, and recordings are stored on the device.
  • The default save location is On My iPhone / 5KClock unless the user chooses another folder.
  • Saved sessions can be shared or deleted from the Sessions tab.

Copley Running Sync

  • API features only appear when the user is signed in.
  • Bearer tokens are stored in the iOS Keychain.
  • Uploads send saved session CSV data for live tracking and race analysis.
  • Workout Clock uses the workout-clock API to list, export, and optionally save workout results.

Device Permissions

Permission Used For
Camera Race or workout video recording when the capture mode is set to video.
Microphone Audio-only voice notes and camera audio during video recording.
Local Network / Nearby Devices Host and follow clock synchronization between nearby Apple devices.
Files and Folders Saving CSV sessions and recordings to the selected local folder.

Encryption notes

The app does not implement custom encryption algorithms. It relies on Apple platform services such as Keychain storage and encrypted nearby-device sessions, plus HTTPS for network API communication.

Production Logging

Production logs should not print bearer token values, token prefixes, signed upload URLs, or full API response bodies that contain sensitive timing or account data.

If request or response logging is needed for debugging, it should be redacted and limited to development or explicitly controlled debug builds.