Garmin Connect integration

Garmin import is not yet available. Today, rides are added by manually dropping a .FIT file into the analyzer. Garmin Connect Activity API access has been requested; automatic import will appear here only after Garmin grants approval and the integration is fully implemented.

Only data needed to perform drivetrain analysis on cycling activities:

• Activity FIT files
• Activity timestamps
• Cadence, power, speed, and distance
• Device metadata (for attribution and equipment context)
• GPS points within the activity (for optional location label)
• Gear, shifting, and developer fields where present

Cycling activity data only. The integration will not request sleep, HRV, women's health, daily wellness, non-activity location, social graph, or any other broad health or lifestyle data.

1. Sign in to DrivetrainStats.
2. Choose Connect Garmin on this page once available.
3. Grant Garmin consent through Garmin Connect's OAuth 2.0 flow.
4. After your next device sync, eligible cycling activities become available.
5. DrivetrainStats imports cycling activities only.
6. View drivetrain analysis on each imported ride.

Garmin connections can be disconnected at any time from the Account page once the integration ships. Disconnecting stops further imports and removes stored Garmin tokens. Already-imported rides remain in your account until you delete them individually or delete your account.

You can also revoke DrivetrainStats's access directly from Garmin Connect at any time.

Each imported ride can be deleted from the analyzer. Deleting a saved ride removes the stored FIT bytes and derived summary for that ride.

Full account deletion (including all imported rides and any Garmin tokens) is available from the Account page and is immediate.

Garmin data is used only for drivetrain, gear usage, efficiency, cadence/power, and equipment analysis inside DrivetrainStats.

Garmin data is not sold. Garmin data is not used to train external AI, ML, or LLM models.

Rides imported from Garmin will display visible attribution near the ride title or summary (for example, Garmin or Garmin [device model] when device model is available). Any export or screenshot generated from Garmin-sourced data preserves that attribution.

Account access is protected by signed session cookies and password hashing. When the integration ships, Garmin OAuth tokens will be stored encrypted at rest and scoped to the owning account, and Garmin's revocation endpoint will be called when an account or connection is deleted.

See the privacy policy for the full data and deletion terms, and the terms of use for service terms. Questions can be sent to [email protected].