I'm building an app that shows each runner which streets in their town they've covered over time. A street run two years ago still counts today, so the app needs a runner's whole history.
The June 2026 API Policy limits caching to seven days (6.2) and says apps may not store geographic location information beyond that (5.7). How are other street-completion or lifetime-map apps handling this? Specifically:
1. Is keeping a runner's GPS tracks while they stay connected, shown only to that runner, within an app's "operational scope" (5.5) and "necessary for the purpose" (6.4)?
2. If not, is it acceptable to delete tracks within 7 days of import and keep only the derived result: which street sections the runner has completed, with no Strava coordinates?
Each runner only sees their own data; nothing is shared, aggregated or used for AI; everything is deleted when they disconnect. Any experience from developers who've been through review, or guidance from the Strava team, would help a lot. Thanks!