What Strava changed, exactly
On 20 November 2024, Strava released updated Developer API Terms of Service with retroactive effect to 11 November 2024. The announcement introduced three distinct contractual restrictions for any third-party app connecting to Strava's API:
- Display restriction:Third-party applications may now only display a user's activity data to that individual authenticated user. Public leaderboards, community group views, and coach dashboards built on third-party platforms could no longer display Strava-synced workouts.
- AI and model training prohibition: The updated terms explicitly forbid developers from using any data acquired via the API for training artificial intelligence, machine learning, or large language models.
- Look-and-feel constraints:Strict guidelines were added prohibiting third parties from mimicking Strava's distinctive user interface or branding elements.
Strava framed these updates as necessary measures to safeguard athlete privacy and prevent unauthorized scraping by commercial AI entities.
Who it actually affected
While ordinary riders simply syncing their Garmin head unit to Strava noticed no change, the developer ecosystem experienced immediate disruption.
The most prominent impact fell on analytical platforms like Intervals.icu, an independent training tool used widely by self-coached cyclists. Intervals.icu was informed that its coaching and squad sharing features violated the new display terms and was required to restrict Strava data to the single authenticated athlete only, applying retroactively to historical rides.
Other popular community platforms—including VeloViewer and various club event tools—had to re-engineer core sharing features or advise users to upload raw FIT files directly from their head units rather than relying on Strava synchronization.
What Strava said in response
Following widespread community discussion spearheaded by technical analysis from DC Rainmaker and coverage across road.cc and Cyclingnews, Strava issued a clarifying statement.
The company stated that the changes would affect fewer than 0.1% of third-party applications and reiterated that the terms were meant to prevent unauthorized aggregation by external technology firms. In contrast, competing platforms such as Ride with GPS publicly reaffirmed their philosophy that athlete ride data belongs exclusively to the rider who created it, advocating for open data portability.
What it means if you're in the EU or UK
For cyclists in the European Union and the United Kingdom, European privacy law provides an important legal distinction.
Under Article 20 of the General Data Protection Regulation (GDPR), you maintain an absolute statutory right to data portability. Regardless of commercial developer terms, Strava is legally obligated to provide you with your complete personal dataset in a structured, commonly used, and machine-readable format upon request.
The practical question: is your riding history portable?
Whether you ride on Strava or another platform, relying on any single cloud service as your sole archive is risky. Here is a practical, four-step checklist to take custody of your complete cycling history:
The Rider Data Portability Checklist
- Request your Strava bulk archive: Log into strava.com on a desktop browser. Go to Settings → My Account, scroll down to Download or Delete Your Account, and click Get Startedunder Step 2. Click “Request Your Archive.” Within a few hours, Strava will email you a download link.
- Verify what is in the export: The downloaded ZIP archive contains your raw original `.fit.gz`, `.gpx`, and `.tcx` files alongside CSV spreadsheets detailing your activity metadata. It does not include social comments, club chat logs, or starred segments.
- Keep raw head unit files: When your Garmin, Wahoo, Hammerhead, or Bryton unit is plugged into your computer via USB, copy the files from the
/Activitiesfolder into a local backup folder on an external drive or cloud storage. These raw binary files contain uncompressed sensor telemetry. - Import into an independent logbook: Drag your archive into an offline or browser-based logbook like WattsUP or GoldenCheetah to verify that your historical power numbers, elevation profiles, and 12-week training stress trends parse cleanly.
Why I built WattsUP the way I did
The Strava API episode demonstrated that when your training log lives on an ad-supported social platform, your access can change overnight without your consent.
That is why WattsUP does not rely on Strava's API. Instead, it parses raw GPX, FIT, and TCX files directly in your browser using local JavaScript decoders. Your routes, heart rate data, and power curves are never routed through third-party advertising servers or harvested for algorithmic models.
You get structured winter ERG intervals and summer road ride analysis in one logbook that you fully own. And if you ever decide to leave, your data exports in full with a single click.
Read our full privacy policy or test your files in our free GPX and FIT Ride Analyzer.
Frequently asked questions about Strava data and APIs
Does Strava own my ride data?
No. Legally, you own the telemetry and personal activity data generated by your rides. However, Strava owns the platform, social graph, and API terms dictating how third-party tools can access or display that data.
Can third-party apps still connect to Strava?
Yes, but under tighter restrictions. Third-party apps may now only display activity data to the authenticated user who recorded it, preventing shared coaching dashboards and public group views that relied on Strava sync.
How do I export all my rides from Strava?
Go to strava.com on desktop, click Settings → My Account, scroll to "Download or Delete Your Account," and click "Get Started" under Step 2: Download Request. Strava will email you a ZIP file containing your original ride files.
Does WattsUP depend on Strava's API?
No. WattsUP is completely independent of Strava's API. It parses raw GPX, FIT, and TCX files exported from any head unit or platform directly inside your browser, so your training log cannot be broken by third-party API changes.