Our app currently computes and stores a long-term running total per user (e.g. cumulative mileage since a bike component was last serviced), derived by summing Strava activity distances over time. Section 5.5 of the API Policy prohibits storing "Strava Data, or any data derived from Strava Data, in any Persistent Index," and Section 6.2 limits caching of Strava Data to 7 days. Does this restrict indefinite storage of a computed running total like this, or does it apply only to cached copies of raw API responses (activities/gear payloads)? We want to make sure our data model is compliant before scaling past our current single-user use.
Question
Long term running totals
+26That total would be “derived from Strava data”. But you could get this value also fresh from Strava with the activity list 😉
By the way, single-user use actually is a thing of the past since everyone can update to 10 users without review.
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.