Athlete capacity increase request and API policy guidance – Ötzi Coach

Hello Strava Developer Team,

I am the developer of Ötzi Coach, a German-language cycling coaching application for athletes preparing for the Ötztaler Radmarathon.

• Application name: Ötzi Coach
• Website: https://oetzicoach.app
• Client ID: [insert Client ID from the Strava dashboard]
• Current athlete capacity: [insert current limit]
• Requested athlete capacity: 999 connected athletes
• Developer contact: support@oetzicoach.app

We are requesting guidance on the correct process for increasing the connected-athlete capacity of our application.

Ötzi Coach is designed to provide personal training support to each individual athlete. The planned Strava integration would be used for:

• importing the athlete’s own cycling activities;
• personal training history;
• estimated FTP;
• training-load calculations;
• race-readiness estimates;
• personal finish-time projections;
• individual coaching recommendations.

The application does not intend to:

• display one athlete’s data to another athlete;
• create public leaderboards or cross-user comparisons;
• sell or share Strava data;
• use Strava data for advertising;
• train or improve a general AI model;
• create aggregated athlete datasets;
• imitate the Strava platform or social network.

We have implemented or are implementing:

• OAuth authorization;
• explicit permission explanations;
• the official Strava connection button;
• Strava webhook handling;
• user-controlled disconnection;
• deletion of imported Strava data after disconnection;
• public privacy and Strava data information pages.

We would also appreciate clarification regarding the current Strava API Policy, particularly Sections 5.3, 5.4 and 6.2.

Specifically:

1. May an application use an individual athlete’s Strava activities to calculate personal FTP, training load, race readiness and finish-time projections?

2. May those calculated values be displayed exclusively to the same athlete?

3. May Strava data, or values derived from Strava data, be used to generate a personal coaching response with an external AI provider?

4. What retention period applies to imported Strava activities and values derived from them?

5. Is an application with this use case eligible to request a capacity of 999 connected athletes?

6. Where should we submit the formal capacity-increase request?

We are not looking for a way to bypass athlete limits or API restrictions. We want to use the official process and ensure that our architecture and data handling comply with Strava’s current requirements.

If the planned use of Strava data is not permitted, we would appreciate guidance on the compliant architecture Strava recommends for this type of personal training application.

Thank you for your help.