Extended Access Request - AISRi Endurance Coaching Platform (Client ID: 162971)

Please read the Strava API policy on https://www.strava.com/legal/api_policy regarding AI usage (in short, it’s not allowed in any way) and the 

 for information about the access tiers and the review form as the only contact option (with an undefined response time).

Hi Jan, are you referring to this part?

5.3 You may not use the Strava API Materials or Strava Data, directly or indirectly, in connection with the development, training, evaluation, or operation of any AI Application. 

English is not my first language, analyzing a runners data with AI, is in my opinion not the same as using Strava’s data to develop, train or operate an AI application.

Do I understand this wrong, or are you referring to another part of the API policy? 

Yes, that’s the part I referred to. Strava sees every byte you download from the API as Strava data, therefore they won’t be convinced it’s the runners data instead.

That is not the problem as I see it.
Its not used to “the development, training, evaluation, or operation of any AI Application”.

Analyzing data from individual runners for the benefit of creating training advice has nothing to do with development, training, evaluation of an AI application.

Now if you want to read that sentence in a certain way you might argue that it is used in operating an AI application, but that seems a bit far fetched (to me). So I doubt wether 5.3 is preventing you from analyzing individual runners data as long as it is fetched and stored in compliance with the Strava rules.

On a side note, In my app this data is first aggregated before it is stored and analyzed so you could also argue if this is still the same Strava data. 

5.3 also says data aggregated from Strava data is not allowed and it says you may not ingest into a context window.

Well it would be really nice if Strava could confirm if this article should be read this way because it would rid them of 99% of all current open ‘extended access’ requests.

@Strava please inform us if a construction like below is forbidden under 5.3 of your API policy:
 
Single user Strava data → retrieved → temporarily locally stored → analyzed by AI
 

But I sincerely hope this is not the case, it would be a real missed opportunity.