Strava issues Clarification
Ray Maker of DCRainmaker.com wrote a detailed article yesterday on apparently dramatic changes made by the Strava platform to how OUR data is handled, limiting the scope of what 3rd party developers can do and effectively stopping most (all) apps working with Strava. As Ray said, “…every single partner I’ve talked to over the last 24 hours has been completely broadsided by this change,”.
I encourage you to read that article for more context, as I won’t cover the same ground again here. Ray’s take on the wording of Strava’s communication seems correct. Whether or not Strava chooses to enforce its words or keep them as a backup to deal with unruly developers in the future is another matter entirely.
Either way, Strava has now issued a clarification to further muddy the water 😉
We wanted to provide some additional context around the changes to our API Agreement and the impact for our users and developers. We currently anticipate these changes will impact less than .1% of applications and proactively notified the majority of those affected last week.
Enhanced Privacy and User Control
Privacy and user control are at the forefront of our platform. As a result, we are committed to evolving our API practices as regulatory requirements and user expectations shift. This includes the decision to limit the ability of a user’s data to be displayed by third-party apps in ways the user may not expect.Specifically, we want to thoughtfully address situations where users connect to a third-party app and are unaware that their data is being surfaced not just for their own use and visibility, but also to other users (for example, in a public feed or heatmap). The latest API changes address this scenario and provide a more consistent framework for Strava user data.Training AI Models
We believe in the potential of AI to transform the athlete experience–whether it’s delivering more personalized insights to help you reach your goals, generating route or training recommendations, or countless other possibilities. But innovation in this space must be handled responsibly and with a firm focus on user control. As part of our generative AI features, we are committed to implementing thoughtful solutions that prioritize user control and the ability to opt out.Third-party developers may not take such a deliberate approach to training AI models and as a result, we believe the best decision for the platform and for users is to prohibit the use of data extracted from Strava users in this manner. Our previous terms already disallowed the use of Strava user data in model training and development but we’ve made this more explicit in light of the increasing activity in this space.
No Impact to Most Developers
We recognize that our platform thrives because of the creativity and dedication of third-party developers who build tools to complement and extend Strava’s capabilities. We are steadfast in our commitment to fostering this ecosystem.We anticipate that these changes will affect only a small fraction (less than .1%) of the applications on the Strava platform–the overwhelming majority of existing use cases are still allowed, including coaching platforms focused on providing feedback to users and tools that help users understand their data and performance. [Brian Bell, Strava VP of Communications and Social Impact]
Thus, Strava identified an issue with certain third-party applications and acted to address it, arguably somewhat heavy-handedly. Their explanation about protecting user data from being unwittingly displayed in third-party feeds is a reasonable goal, reflecting their focus on privacy and control. This change almost certainly has been driven by Strava data showing military and secret service personnel locations – hence the people they protect.
On the topic of “Training AI Models,” there seems to be some ambiguity in everyone’s understanding of what an AI model is and is not. For instance, if a developer like AI Endurance uses AI/ML solely on an individual user’s data to provide personalized insights, that seems acceptable. However, many people might find it problematic if another developer uses aggregated or anonymized user data to train a population-level AI model.
Take Out: Nut. Hammer. Sledge. Crack – Make your own sentence
Strava deserves the benefit of the doubt in this instance. These complex issues require thoughtful handling, and their intentions could be read to be aligned with safeguarding user trust. That said, there may have been a more nuanced way to announce and implement these changes!
Furthermore, Strava’s track record with third-party developers—such as its controversial action against RELIVE in 2019 adds another layer of scepticism. For those already mistrustful of Strava’s actions, moves like this don’t do much to rebuild confidence.
Strava Updates Heatmaps – Gravel and Mountain Bike now included
Spotify Links To Strava – also check out the SPAVA Club’s Superior Spotify plugin
Will Strava have to delete segments where speed limits are routinely exceeded?
Garmin Edge (via Connect) map indicators, plus Strava community surface reporting
Strava Vulnerability Reveals Israeli Securirty Staff Runners
new STRAVA Local Legends – Segments, Jim, but not as we know them
Sports Apps 2020 Report & Table – Winners & Losers of 2019 – Best Sports App
Strava Running Power – All The Details – All major watch brands now support it (after a fashion)
Suunto adds Plotaroute support for Advanced Route Creation & Easy Syncing
STRAVA Stats Show Surprising US vs UK Differences: starting with…America is Bigger
STRAVA Stats Show Surprising US vs UK Differences: starting with…America is Bigger
the5krunner.com © 2010-2025
Reader-Powered Content
