Hi all,
I'm building a read-only app that shows each athlete long-term trends in their own activity history. Each athlete only sees their own data, and nothing is shown to anyone else. We use webhooks for activity changes and deauthorisation, and delete an athlete's data when they disconnect.
The feature only makes sense across years of activities, so the 7-day cache rule in API Policy 6.2 is a real problem for us. I've read the similar thread from September and I'm hoping to get a bit further on three points:
1. Is there any approved way to retain an athlete's own activity data for as long as they're an active user, when the only purpose is showing their own history back to them?
2. If not, does aggregated data derived from their activities still count as Strava Data under 6.2? I mean summary counts, with no individual activities, names or IDs kept.
3. If an athlete downloads their own data with Strava's bulk export tool and uploads it to an app, is that covered by the API Agreement and the 7-day limit?
I'd especially value hearing from anyone who has had an app with long-term history approved, or an answer from the Strava team. Thanks!