Skip to main content
Question

5.3/5.4: read-only Strava viewer inside an app that uses AI on other data sources?

  • October 13, 2026
  • 1 reply
  • 21 views

Forum|alt.badge.img

Hi all,

I'm building a running app and rethinking how it uses Strava. I'd like to check one design before building it, ideally with input from Strava staff.

The design:

  • Strava is used only as a read-only viewer: an athlete connects their own account and sees their own activities, in a separate screen.
  • Strava Data is not used for AI/ML, analytics, training load, predictions or plan adjustment, and is not combined with any other source.
  • Cache of at most 7 days (6.2), deletions reflected within 48 hours (6.3), deletion on revocation or request (7.4).
  • Everything else in the app (analysis, coaching, AI) would run on other sources the athlete connects, such as Apple Health or their watch maker.

Questions:

  1. Is an isolated viewer like this allowed when the same app uses AI on non-Strava data (5.3, "directly or indirectly")?
  2. Where is the line for deterministic, rule-based calculations on Strava Data under 5.4 ("analytics, analyses")?
  3. Is there a way to get a written answer on questions like this? Developer Support redirects me here.

Thanks. Short answers from anyone with experience are welcome too.

1 reply

Jan_Mantau
Forum|alt.badge.img+26
  • Hub Powerhouse
  • October 13, 2026
  1. If the viewer provides additional values compared to viewing the activity directly on Strava it should be allowed.
  2. Rule 5.4 is against web analytics, tracking and marketing.
  3. No, Strava never answers API policy questions.