Strava updates its API terms to prohibit third parties from using any data in AI models or similar apps, including to show a user's Strava data to other users
Yesterday Strava sent out an e-mail to users, outlining a change that's occurring almost immediately, regarding 3rd party apps …
DC RainmakerRay Maker
Context & Ripple Effects
Strava’s restriction is not limited to model training: it also bars third-party apps from using Strava data to present one user’s activity to another. That makes its API a tighter permission boundary for both AI features and cross-app social experiences.
Third-party developers using Strava API data in AI models or AI-like applications must remove or redesign those uses under the new terms.
Apps that use a person’s Strava data to power sharing or viewing experiences for other users face an immediate product and compliance constraint.
Second-order effects
Fitness-data aggregators and wearable integrations may offer less complete cross-service views, since shared Strava-derived data can no longer be repurposed freely; this is the integration friction later documented in coverage of affected fitness apps.
Developers have a stronger incentive to rely on data obtained directly from users or from other platform APIs, rather than make Strava the shared data layer for AI and social features.
Third-order effects
If platforms apply similar limits, fitness APIs shift from interoperability plumbing toward governed data channels, with owners retaining more control over downstream AI products and user-to-user distribution.
The later addition of API fees and access gates suggests a broader move toward commercialized, authenticated access rather than broadly reusable public fitness data, though the durability of that model depends on developer and user acceptance.
The trend: Consumer platforms are redrawing API permissions to keep user data from becoming freely reusable input for third-party AI and cross-platform experiences.
Wild when you think about how people use Strava to integrate data across other fitness apps, wearables, and connected fitness equipment. https://www.theverge.com/...
Strava doing @strava things. But so far in the most egregious way they ever did. And Ray does Rainmaker things: Analyzing brilliantly and on point. https://www.youtube.com/... cycling #stravaapps #stravaapi
That any sane people still use Strava blows my mind. A few years ago I killed it after they were unresponsive about trail bandits. It never ends. Here's @dcrainmaker: Strava Announces Big Changes That'll Kill Apps - YouTube https://www.youtube.com/...
Strava's recent actions suggest they're trying to stifle innovation by targeting third-party apps. Their dismissive attitude towards user feedback is both disappointing and laughable. [embedded post]
Strava's just announced some massive changes that will ultimately kill off a lot of 3rd party apps, impact other platforms, and reduce the value of Strava. Here's why this matters, who's it going to break, and more: https://www.dcrainmaker.com/ ... [image]
I was just about to apply to the app marketplace with a new app I wrote for myself... It shows a data in a heatmap kind of thing, so that's wasted effort 🫠
@dcrainmakerblog This is a bizarre and crazy change of direction. I get it that they feel like they are under duress from these third-party providers, but I think they have underestimated the value of consumer sentiment on this one.
New Strava CEO rite of passage: get cocky and think Strava is invincible, make truly idiotic API decisions undoing a decade+ of user and industry goodwill, roll eyes at any critiques, eventually capitulate to universal outrage and undo idiotic API decisions, and finally get back
@dcrainmakerblog the competitive advantage of strava is having so many apps built on top. with these changes they are killing most of them. man that's crazy