1. Privacy summary

  • Runs, routes, workouts, settings, and coach artifacts are stored locally on your device.
  • Apple Health access is optional and controlled through system permissions.
  • Apple Intelligence processing stays on device when it is used.
  • A personal AI provider is optional; data is sent only when you choose that mode.
  • Anonymous product analytics never include location, routes, health metrics, prompts, conversations, keys, or custom provider URLs.
  • There is no Run Buddy cloud account, workout backend, advertising SDK, or data sale.

2. Data stored on your device

Run Buddy AI may store locally:

  • completed sessions, distance, duration, pace, workout steps, and local route geometry;
  • saved routes and structured workouts;
  • training preferences, language, audio, privacy, and provider settings;
  • coach recommendations, analyses, summaries, and conversations;
  • Apple Health workout summaries and heart-rate aggregates when access is granted;
  • technical state required to reconcile duplicate recordings and refresh coach artifacts.

This information is not uploaded to a Run Buddy server because no such service is used in version 1.3.

3. Location and routes

Location is used to track an active run, calculate distance and pace, display the route, and keep a workout working in the background. Depending on the permission you grant, location may be used while the app is open or during an active background workout.

GPS coordinates and route geometry remain in the app. They are not included in product analytics, and Run Buddy AI does not import HealthKit GPS routes in version 1.3.

4. Apple Health and HealthKit

Apple Health integration is optional. If you grant access, Run Buddy AI can:

  • read running workout dates, duration, distance, active energy, and available heart-rate data;
  • write workouts completed with Run Buddy AI;
  • reconcile similar recordings from multiple devices to reduce duplicate runs;
  • use summary and heart-rate context for progress and optional coach analysis.

Heart-rate detail is aggregated before it is used by the app. Raw heart-rate samples, HealthKit identifiers, and source bundle identifiers are never sent to product analytics. You can revoke Health access at any time in iOS Settings or the Health app. Because of HealthKit privacy protections, denied read data may simply appear unavailable to the app.

5. AI modes

100% local

No language-model request is made. Tracking, workouts, history, and essential cues remain available.

Apple Intelligence

When compatible and selected automatically, supported AI processing uses Apple’s on-device frameworks.

Personal provider

You can configure OpenAI, Mistral, OpenRouter, or another compatible endpoint. When this mode is used, the app may send the selected provider the information needed for the requested feature, such as workout structure, recent training summaries, coach preferences, conversation text, and optional aggregated heart-rate context.

Exact GPS coordinates, route geometry, HealthKit identifiers, and raw heart-rate samples are not included. The provider processes requests under its own terms and privacy policy. Run Buddy AI does not control the provider’s retention practices.

6. API keys and voice providers

Personal provider keys are stored using Apple Keychain. A key is sent only to the provider you selected to authenticate the request. It is never included in analytics or technical reports. Disconnecting a provider removes the selected key and returns the app to Automatic mode.

If enhanced voice is enabled, text selected for speech may be sent to the configured voice provider. Apple system voice remains the fallback.

7. Anonymous product analytics

Run Buddy AI uses TelemetryDeck to understand whether essential product flows work, such as onboarding, starting and completing a session, hearing a cue, connecting Apple Health, configuring a personal provider, and declaring interest in a future Coach Cloud offer.

Analytics use a random installation identifier that is not linked to your Apple ID, iCloud account, HealthKit identity, or Run Buddy account. Run Buddy AI does not send TelemetryDeck your coordinates, route, health metrics, workout or route names, prompts, conversations, API keys, or custom provider URL.

You can disable analytics in Settings > Data & Privacy. You can also renew the random identifier, which deletes the previous local identifier and starts a new anonymous sequence.

8. Data sharing and sale

Run Buddy AI does not sell personal data, use advertising trackers, or share workout data with data brokers. Data leaves the device only for the optional provider features you choose, anonymous product analytics described above, system services such as HealthKit, or when legally required.

9. Retention and deletion

Sessions, routes, and workouts can be deleted where deletion controls are available. Provider keys can be removed by disconnecting the provider. Analytics can be disabled and its identifier renewed in Settings. Removing the app generally removes its local data, subject to iOS backups and Apple system behavior. Apple Health data is managed separately through Apple Health and iOS settings.

10. Fictional demo data

Debug builds may download a public demonstration dataset for testing and App Store screenshots. It contains only fictional sessions, watch names, analyses, and heart-rate summaries. The feature is not included in a standard Release build.

11. Children and medical use

Run Buddy AI is not intended to provide medical diagnosis or treatment. Training and heart-rate information should not replace professional medical advice. The app is not intended for children below the minimum age required by applicable law without guardian supervision.

12. Changes and contact

Material changes will be posted here with an updated effective date.

Privacy and support contact: support@duckway.fr