*URGENT*- Feed display of user activity data (Section 2.3) ahead of Extended Access request

Showing max HR and routes to other users probably won’t be allowed, regardless of user consent.

Also I don’t know if you have just your wording wrong but you can’t jump from 10 users to extended tier (10000 users and more), you should aim for more realistic goals.

Hi ​@Jan_Mantau ,

Huge thanks for the response. My developer 
has raised a specific point that he thinks changes the answer, and I’d appreciate your perspective too.

His view: the data is synced via the Strava API, but the user then actively chooses 
to "publish" it themselves as a separate action - it isn't displayed automatically 
without their involvement. Our OAuth flow also redirects to Strava's own site for 
authorization, and we display "Powered by Strava" attribution without misusing the 
logo. His reasoning is that because the user is the one syncing and then separately 
choosing to publish, rather than us displaying their data without their action, this 
might fall outside the restriction - even though the end result is still that other 
users can see general workout metrics (duration, distance, pace, HR).

Appreciate you taking the time on this.

Thanks,
Michael

The user involvement doesn’t change that the displayed data comes from the Strava API.

Thanks for the clarification, Jan.

I'd like to explain our use case, as it differs from a traditional activity feed.

GOER is a gamified fitness platform where activities advance users through campaigns, arenas, tours, XP, achievements, and private competitions. The workout itself is not the primary content—it is an input into our progression system.

Strava is one of several supported activity providers, and we clearly attribute imported activities as originating from Strava.

We are also happy to adjust the amount of activity data displayed publicly if needed. For example, we can make GOER achievements the primary content while limiting public workout metrics and keeping detailed activity information private.

Our goal is not to recreate the Strava experience but to build a distinct gamified layer that encourages users to remain active while continuing to use Strava as their recording platform.

Would this type of implementation be considered acceptable under the API Terms, or are there specific aspects of the public feed that you would recommend we change?

Maybe you have a little chance in the review request if you make clear that data from the Strava API isn’t directly or aggregated displayed to other users and you emphasize the features of your app that Strava doesn’t have. But the word “leaderboard” alone is a red flag, because Strava did make some efforts to show leaderboards only to subscribers or in sponsored challenges and wouldn’t like that to be circumvented by third party apps.

Thanks Jan, this is really helpful context.

To clarify on the leaderboard point specifically: our Arena leaderboards don't 
display or aggregate raw Strava metrics (distance, pace, time) directly. They rank 
users by a proprietary score we calculate ourselves - "Effort XP" - based on 
duration and intensity, weighted differently per activity type. This is what allows 
a runner, a swimmer, and someone doing strength training to all appear on the same 
leaderboard, ranked fairly against each other - something structurally different 
from a single-sport or segment-based leaderboard.

So the workout data itself (distance, pace, HR) is never shown to other users or 
used directly in the ranking - only the derived XP value is. Would that distinction 
- ranking a proprietary, cross-activity-type score rather than displaying or 
aggregating Strava's own metrics - address the concern, or is there a further 
change you'd recommend?

You should try the review and tell us how it went.