Hello Strava Developer Community,
We are developing RUNVERSE, a Brazilian running platform that combines GPS activity tracking, running statistics, gamification, and running communities.
We currently have a working Strava OAuth integration that allows users to connect their individual accounts and import their activities.
We would like clarification about the current API Policy, particularly Sections 5.4, 5.5, 6.2 and 7.4.
Our intended feature is to allow each athlete to see their own:
-
Lifetime running distance.
-
Annual running distance.
-
Total number of runs.
-
Total moving time.
We would like to display these statistics in the athlete's private RUNVERSE profile and allow the athlete to voluntarily share personal achievement cards on social networks.
We do not intend to retain detailed Strava activity records beyond the permitted cache period.
Our questions are:
-
Does the current API Policy prohibit permanently storing cumulative lifetime and annual running statistics derived from an athlete's own Strava activities?
-
Is there any approved exception or allowlist process that would allow RUNVERSE to retain these individual numerical statistics?
-
Does the same restriction apply when an athlete voluntarily downloads their own complete Strava archive and uploads it directly to RUNVERSE?
-
If permanent retention is not permitted, what is the recommended compliant way for a third-party running platform to present lifetime and annual statistics from Strava?
-
Should we submit a specific application or technical proposal for review under Section 3.2 of the API Policy?
We want to ensure that RUNVERSE complies fully with Strava's current policies before implementing permanent historical statistics.
Thank you for your guidance.
