Skip to content
Ridgeset
Early access
Menu

Ridgeset Integrations

Garmin Connect integration proposal

How Ridgeset proposes to connect with Garmin Connect, and how athlete data will be handled.

Status: proposed, pending approval

Ridgeset has no live Garmin integration and does not collect any Garmin data. Access depends on application to, and approval through, the Garmin Connect Developer Program. Ridgeset is not affiliated with or endorsed by Garmin.

Summary

Developer
Anorthic Labs, an independent UK software business. Anorthic Labs is a trading name of Steve Perry Creative Limited.
Product
Ridgeset, subscription training software for endurance and strength training. In development.
Users
Individual athletes: runners, endurance athletes, strength athletes and people who combine disciplines. Coaches may follow later.
Primary request
Activity API: automatic delivery of completed activities, including FIT files where available.
Secondary interest
Training API: publishing structured workouts from Ridgeset to the Garmin Connect calendar.
Authorisation
Garmin’s OAuth 2.0 consent flow, started by the athlete.
Data sale
None. We will not sell users’ personal or training data.
Contact
info@anorthiclabs.com

Who is developing Ridgeset

Ridgeset is developed by Anorthic Labs, an independent software business based in the United Kingdom. Anorthic Labs builds and operates its own digital products. Ridgeset is one of them.

The founding background combines substantial professional software development experience with firsthand experience of endurance sport and strength training.

Company details: Steve Perry Creative Limited, company number 08354632, registered office 4 Back Lane, Brown Edge, Staffordshire, ST6 8QS.

Use case and audience

Ridgeset is planned as a commercial subscription product for individual athletes. It brings endurance and strength training into one platform for planning, recording and analysing all training. It may later support coaches working with athletes.

Most training software focuses on endurance or on gym-based strength training. Athletes who do both use several applications, which leaves their training records fragmented and their plans disconnected. Ridgeset’s purpose is to give those athletes one complete training record and one plan.

Why Garmin integration matters

  • Many of Ridgeset’s intended users record their runs, rides and strength sessions on Garmin devices.
  • A complete training record depends on those activities arriving automatically. Manual file exports are not an acceptable primary experience.
  • Detailed activity data, including the original FIT file, is needed for accurate pace, heart rate, power, elevation and GPS analysis.
  • Publishing planned workouts to Garmin devices would let athletes follow a Ridgeset programme without re-entering it.

APIs requested

API Priority Direction Purpose
Activity API Primary Garmin to Ridgeset Receive completed activities automatically after the athlete’s device syncs: activity summaries and FIT files where available, to populate the training calendar, history and analysis.
Training API Secondary Ridgeset to Garmin Publish structured workouts from a Ridgeset programme to the athlete’s Garmin Connect calendar, so compatible workouts can be completed on their device. Not required for the initial product.

We are not requesting health or wellness data at this stage.

How athletes authorise access

  1. The athlete chooses to connect their Garmin Connect account from Ridgeset’s connected services settings. Nothing is connected by default.
  2. Ridgeset explains what will be shared and why, then redirects the athlete to Garmin.
  3. The athlete signs in on Garmin’s own pages and grants consent through Garmin’s OAuth 2.0 authorisation process. Ridgeset never sees the athlete’s Garmin password.
  4. Garmin returns the athlete to Ridgeset, which exchanges the authorisation for an access token and stores it server-side.
  5. From then on, new activities arrive automatically after each device sync.

When the integration is built, Ridgeset will use Garmin’s current authorisation process as specified in the developer programme documentation.

Data flow

The integration is cloud-to-cloud. Activity data flows from Garmin Connect to Ridgeset. Planned workouts, if the Training API is approved, flow from Ridgeset to Garmin Connect.

Once, at connection

  1. Athlete chooses to connect their Garmin Connect account from Ridgeset settings.
  2. Garmin handles sign-in and consent on its own pages (OAuth 2.0).
  3. Ridgeset stores the access token server-side, encrypted at rest.

Each completed activity

  1. 1Athlete records an activity on a Garmin device.
  2. 2Garmin Connect receives it when the device syncs.
  3. 3Ridgeset ingestion receives it through the Activity API over HTTPS.
  4. 4Processing parses and validates the summary and FIT file.
  5. 5Calendar and history show the activity with Garmin device attribution.

Secondary, under investigation

  1. Ridgeset publishes a planned workout through the Training API.
  2. Garmin Connect adds it to the calendar and syncs it to the device.
  3. Athlete follows the workout on the device.
Proposed architecture. Cloud-to-cloud: Ridgeset never connects to the athlete’s device directly and never handles Garmin passwords.

Data handling and privacy

Ridgeset is being designed around the following principles. They describe the intended implementation; none is in operation yet because the product is not live.

  • No sale of data. We will not sell users’ personal or training data, including data received from Garmin.
  • Explicit consent. A Garmin Connect account is linked only when the athlete chooses to link it.
  • Data minimisation. We request only the data needed to provide Ridgeset’s training features.
  • Purpose limitation. Garmin-sourced data is used to provide the service to the athlete it belongs to. It is not used for advertising.
  • Credential security. Access tokens are stored server-side, encrypted, and never exposed to the browser.
  • Access control. Production data access is restricted to the systems and people that need it to operate the service.
  • Deletion. Athletes can delete their Ridgeset account and data, including activities imported from Garmin.
  • UK data protection law. Processing will comply with UK GDPR and the Data Protection Act 2018.

A product privacy notice covering Garmin-sourced data will be published before any athlete can connect a Garmin Connect account. The current website privacy policy covers this site only.

Attribution and AI-assisted analysis

Ridgeset will follow the Garmin API Brand Guidelines and the applicable developer programme licence agreement. In practice this means:

  • Activity views, detailed views and history will carry a “Garmin [device model]” attribution next to the data, or “Garmin” where the model is not provided.
  • Exports and shared images containing Garmin device-sourced data will retain the attribution.
  • Where Garmin data contributes to combined analysis, such as training load across strength and endurance, Garmin will be listed as a contributing data source without implying endorsement.
  • Garmin’s name will be shown in full as “Garmin Connect” wherever an athlete connects or manages the connection.

Ridgeset may offer optional AI-assisted coaching and planning. Any AI-assisted analysis of Garmin-sourced information will be subject to Garmin’s licensing, attribution and data-use requirements. We will confirm those requirements with Garmin before implementing it, and AI processing will be disclosed to athletes before they use it.

Revoking access

  • From Ridgeset. The athlete can disconnect their Garmin Connect account from connected services settings at any time. Ridgeset stops receiving data and deletes its stored access token.
  • From Garmin Connect. The athlete can remove Ridgeset’s access in their Garmin Connect account. Ridgeset will act on Garmin’s deregistration and permission-change notifications.
  • Imported data. After disconnecting, the athlete can delete activities previously imported from Garmin. Deleting the Ridgeset account removes all of their data.

Retention of Garmin-sourced data after disconnection will follow the developer programme licence agreement, which we will confirm before implementation.

Status

  • Ridgeset is in development and is not publicly available.
  • No Garmin integration exists, and no Garmin data is collected or processed.
  • The integration will be built only after approval through the Garmin Connect Developer Program, and in line with its licence agreement and brand guidelines.
  • This site does not use Garmin logos, badges or other restricted brand assets.

References

Questions about this proposal

Email info@anorthiclabs.com. See also the contact page.