Hi everyone,
We are developing Runner, a SaaS training-management platform for running clubs and coaches, and we want to clarify two points of the current Strava API Policy before submitting the application for Athlete Capacity review.
Our use case is:
- Each athlete individually connects their own Strava account through OAuth.
- The athlete may have an explicitly assigned coach within Runner.
- That coach already manages the athlete's prescribed training plan and training history inside Runner.
- The Strava connection is optional and initiated by the athlete.
- Activity information received from Strava is currently synchronized into the athlete's training record.
1. Coach access
Section 2.3 states that Strava Data provided by a specific Strava user may be displayed only to that user.
Does an explicitly assigned coach still count as another user under this restriction when the athlete has expressly authorized both the Strava connection and the coaching relationship?
In other words, is there any supported model for a consenting athlete to allow their assigned coach to view Strava-originated activity information within a training-management application?
2. Activity retention
Section 6.2 limits caching of Strava Data to seven days and states that, except for limited caching, Strava Data may not be stored.
Does this mean that a training-management application cannot persist Strava-originated activity information as part of the athlete's historical training record, even when the athlete explicitly connected Strava for this purpose?
If persistent storage is not permitted, should all Strava-originated activity information be treated exclusively as transient data and removed within seven days?
We are asking before our production rollout because we want to design the integration in accordance with the current API Policy rather than make assumptions about these provisions.
We would particularly appreciate clarification from Strava staff, if possible.
Thank you.