Hi everyone,
We’re developing Savills Run for Impact 2026, a non-commercial internal running challenge for approximately 1,000 employees.
The challenge runs for one month. Each participant would voluntarily connect their Strava account via OAuth, and our web app would retrieve their running distance to:
- Track individual and cumulative monthly KM
- Display name, cumulative KM and ranking on an internal leaderboard visible only to participants
- Convert the total KM into a company charity donation
Before moving forward, I’d really appreciate some clarification from anyone familiar with the current Strava API Policy:
1. Leaderboard:
Does the Data Display policy allow cumulative distance and rankings to be shown to other challenge participants if everyone explicitly consents?
2. 7-day caching/data retention:
Since the challenge lasts one month, can we store cumulative/derived KM in our database for the full challenge, or would the 7-day caching restriction also apply to this data?
3. ~1,000 participants:
Our current app has a limited athlete capacity. Has anyone gone through the Strava app review process for a similar internal challenge with around 1,000 connected athletes? Any advice on athlete capacity and rate limits would be appreciated.
We only need running distance and do not intend to display routes, GPS, heart rate, or other detailed activity data.
Thanks in advance for any guidance or experience with a similar use case!