Hi Strava team and fellow developers,
I run RunMirror (Client ID 8313), a small personal app on Standard Tier. It shows a runner their own running history back to themselves — lifetime miles, milestones, and a mile-by-mile view of their own past races. Direct OAuth integration. Each athlete sees only their own data. Nothing shared between athletes, no public feed, no leaderboard. All insights are computed by my own rule-based logic — no AI/LLM anywhere in the product.
I organically filled all 10 Standard Tier slots with runners from my own circle, and I'd like a Standard Tier growth review to raise the athlete cap to 100 so a few more people can connect.
I've submitted twice and both times received a response citing API Policy Section 5.16 (abstraction layers / intermediaries). I've reviewed my setup carefully against that section:
- It's a direct integration — no third-party intermediary platform routing Strava data.
- No re-exposure of Strava data to third parties; each athlete only ever sees their own.
- I removed an internal admin view I'd been using to monitor my own athletes, in case that aggregation read as re-exposure.
My question: Could a staff member help me understand what specifically is being read as a "5.16 abstraction layer" so I can fix the actual issue rather than keep guessing? Even a one-line pointer — whether it's something in the app, the integration, or how I described it — would let me correct the right thing and resubmit properly.
Happy to provide any detail. Thanks for the help.
— Balaji
