Hi everyone,
We are building VelUP, a bike-maintenance app for cyclists in Brazil. Athletes authorize their own Strava account (scope activity:read only). We receive activity webhooks (no polling) and, for each ride, read only the distance, the start time and the bike (gear id). We do not store routes, GPS, heart rate, titles or segments. The athlete links each Strava bike to a bike they registered in our app, and the distance is added to that bike’s odometer to drive maintenance reminders (chain, brake pads, tires...). The Strava-derived distance is shown only to that same athlete, never to workshops or other users.
We are within the first 10 athletes and want to be sure we are compliant before asking for more capacity. Could anyone from the community, or from Strava, help clarify these points under the current API Agreement/Policy (June 2026)?
7-day cache rule (Policy 6.2). We convert each ride into a per-bike odometer delta (a number of meters added to a running total). The activity id, start time and metadata are deleted after 7 days; only the running total remains. Is that running total still considered Strava Data subject to the 7-day limit? If so, how should an app keep a lifetime odometer? If it is allowed, we keep it only while the athlete stays connected and delete it when the athlete disconnects, revokes access or asks for deletion.
Overlap with Strava Gear (Policy 5.2). Our reminders are about the wear of components based on the distance of the athlete’s own bikes, plus booking maintenance with a workshop. Does a maintenance/wear reminder like this count as “replicating Strava functionality” because of Gear? Is there any guidance on where the line is?
Subscription requirement (Policy 3.3). Does the Standard-tier subscription requirement apply to the developer only, or to every connected athlete?
Thanks in advance. We will update this thread with what we learn so it helps others.
