Hi all,
I'm building a web app that connects to Strava via OAuth and computes derived training metrics per user (training load, ACWR, zone distribution, that kind of thing) from their activity data, for use on a personal dashboard inside my own app.
I'm trying to reconcile two parts of the current API Agreement/Policy:
- Policy 5.4 appears to bar processing Strava derived data "for the purposes of analytics."
- Policy 5.5 appears to bar storing derived data in any "Persistent Index."
- Policy 6.2's 7 day cache cap only applies to raw Strava Data, and Policy 7.4 and 6.3 require deletion of derived data within 30 days of disconnect and sync within 48 hours of a source activity's deletion.
My question: does storing per-user computed training metrics (not raw Strava Data, values I calculate from it) in my own database, scoped to each user, for display back to that same user, count as the kind of "analytics" or "Persistent Index" that 5.4/5.5 prohibit? Or is that restriction aimed at something else, like using aggregated data across users for product/marketing analytics rather than a single user's own training dashboard?
I already plan to build in the required 30 day disconnect purge and 48 hour deletion sync jobs regardless of the answer here. I emailed developers@strava.com about this and got an automated reply saying rate limit and capacity questions aren't handled by email and pointing here instead, so I'm hoping someone from the API team or another developer who's hit this can clarify.
Thanks in advance.
