Hello Strava team and developer community,
I am developing ZeloRitmo, a mobile application for workout planning, nutrition, sleep and personal well-being. Developer Support’s automated email directed me to this forum.
We currently use OAuth to let authenticated users view their own Strava activities. Before implementing further features, we would appreciate clarification on two separate scenarios.
SCENARIO 1 — Private workout records without analytics or scoring
With the user’s explicit consent, we would:
-
Import an activity summary into that user’s private workout diary.
-
Associate it with a workout previously planned by the same user.
-
Display the workout as completed on their home screen.
-
Keep Strava-derived information separate from scores, analytics, recommendations, AI and calculations involving nutrition or sleep.
Would this scenario be permitted? Which activity fields could we retain, and for how long? How should we interpret Sections 5.5, 6.2 and 6.4 regarding a private workout history available only to the authorizing user?
SCENARIO 2 — Integration with nutrition, sleep and personal scoring
In addition to the features above, and with explicit user consent, we would:
-
Calculate personal workout frequency, duration, distance totals and progress.
-
Combine activity summaries with nutrition and sleep information recorded by the same user.
-
Use those inputs to calculate a personal score reflecting consistency with their nutrition, workout and sleep goals.
-
Provide personalized well-being suggestions.
Please distinguish suggestions generated through predefined rules from suggestions generated using an AI service.
Would any of these uses be permitted under the current policy, particularly Sections 5.3 and 5.4? If not, is there a process to request specific authorization or an appropriate partnership agreement?
For both scenarios, activity information would be visible only to the authorizing user, not to other users. We would implement the applicable consent, disconnection, deletion and security requirements.
Please address the scenarios separately, including any restrictions, retention limits or additional approvals required. We understand that user consent alone may not override API restrictions and want to clarify the permitted scope before implementation.
We would appreciate clarification from Strava staff.
Thank you,
Odair Freitas
