Hi all,
I run TailwindKompass (Client ID 150588), a read-only app that helps cyclists find Strava segments with favorable wind conditions. It's on the Standard Tier and currently has 978 of 999 allowed athletes connected. At our current growth of roughly 15 new athletes per week, we'll hit the cap within 14 days, after which new users can't connect and effectively can't sign up.
I've emailed the developer team with a capacity request, screenshots of the connect flow and our Strava attribution. A few questions for anyone who has been through this:
1. Is email the right channel, or is there a specific form for athlete capacity increases?
2. How long did your review take?
3. Is there anything that commonly causes delays or rejections that I should fix up front?
Some context on compliance: read scope only, each athlete only sees their own data, no data is shared with third parties, data is deleted on deauthorization, and we use the official "Connect with Strava" button and "Powered by Strava" logo. Peak usage is around 500 requests per 15 minutes, well under the 600 read limit.
If anyone from the Strava team sees this, I'd really appreciate a look before we hit the limit.
Thanks!
Thom
