I am the developer of dameto.sk, a sport-focused dating site built on Joomla. Our application (Client ID 276814, athlete capacity 10/10) lets a member optionally connect their own Strava account.
Before we apply for a capacity increase, we would like to confirm that our intended use is allowed under the API Policy of June 1, 2026. We do not want to submit screenshots of a design that Strava would reject.
What we want to do:
1. A member connects Strava voluntarily (OAuth, with the consent information required by section 2.1).
2. From that member's own activities we compute a few coarse values: main sport, a weekly volume band, and typical time of day.
3. When two members are shown to each other, we use a simple rule-based formula (no AI or ML) to calculate a single compatibility figure, and show only that figure to the other member. The underlying activities, routes and numbers are never shown to anyone else.
4. Optionally, a member can explicitly choose to share a coarse band (for example "runs 20-40 km a week") with other members.
Our questions:
1. Is showing a derived compatibility figure to another member permitted, given sections 2.3 and 5.4? If not, is it permitted when the member has given explicit opt-in consent (section 5.13)?
2. Is the opt-in sharing of coarse bands in point 4 permitted, or must every Strava-derived value be shown only to the member it belongs to?
3. Do the derived values in point 2 count as Strava Data for the 7-day retention limit in section 6.2? If yes, we will recompute them from fresh data instead of storing them.
4. If none of this is permitted, we will switch to a private mode: each member sees only their own Strava data and nothing derived is shown to others. Would you confirm that this mode is acceptable for a capacity request?
Thank you for your time. A short written answer would let us design the application correctly and prepare the Developer Program submission.
