Hi Strava Developer Community,
We are developing EZ Engage, a corporate employee wellness and engagement platform.
Employees may voluntarily connect their own Strava accounts to participate in a company wellness programme, typically lasting 30 days.
Our intended flow is:
- Employee authorizes Strava.
- Eligible activities such as walking, running and hiking are received automatically via the Strava API/webhook.
- EZ Engage converts the eligible activity into programme points.
- The points are accumulated toward the employee's programme progress.
- Raw Strava activity data can be deleted according to Strava's required retention period.
We would appreciate clarification on two points:
1. After the underlying Strava activity data is deleted, may we retain the accumulated programme points derived from that activity, provided the points do not expose the original Strava activity details?
For example, instead of retaining distance, route, pace or activity details, EZ Engage would retain only something such as “50 MOVE points”.
2. With the employee's explicit consent, may their employer's authorised programme administrator (PIC) view their accumulated programme points/progress for the corporate wellness programme?
There is no public Strava activity feed required for this use case. The purpose is employee wellness programme participation and progress tracking.
We want to make sure our architecture complies with the current Strava API Agreement and API Policy before implementing this workflow.
Thank you.
