Hello Strava Developer Team,
I am the founder of ARVENTO, a cycling-inspired brand developing ARVENTO REVEAL, an interactive geographic visualization experience.
Our vision is simple:
Every ride lights up the world.
We have recently launched our public product introduction and an interactive demonstration:
Product Website:
https://www.arventolife.com/pages/arvento-reveal
Interactive Demo:
https://arvento-reveal-demo.pages.dev/
Important: Our public demo uses synthetic data only. Real-athlete Group and Global data aggregation is not enabled.
Before launching real Strava-connected functionality, we would like to clarify whether our proposed data processing complies with Strava's API Agreement and data-use policies.
1. Personal — MY WORLD
With an athlete's explicit OAuth authorization, we would like to convert their GPS activity coordinates into H3 geographic cells and visualize their explored areas privately over a rolling 7-day period.
Question: Is this type of private, athlete-specific derived visualization permitted?
2. Group — OUR WORLD
Athletes could voluntarily opt in to contribute derived geographic coverage information to a shared group visualization over a rolling 30-day period.
Individual GPS routes and athlete-level activity details would not be publicly displayed.
Question: Does Strava permit aggregation of derived geographic activity data across multiple consenting athletes, or is this restricted regardless of consent?
3. Global — ONE WORLD
Our long-term concept is to display aggregated geographic coverage and country-level contributions on an interactive global map.
This could include illuminated H3 cells, aggregated statistics, and country rankings.
Question: Is public visualization of cross-athlete aggregated activity data permitted? If not under standard API terms, is there an additional approval process?
4. Data Retention and Deletion
We would appreciate clarification regarding:
-
Whether H3 cells derived from GPS activity data may be stored.
-
Applicable retention limits for derived geographic data and aggregated statistics.
-
Deletion requirements following athlete deauthorization or consent withdrawal.
-
Whether backend processing or a data-broker architecture is permitted.
5. Formal Review or Special Authorization
If any of these use cases are restricted under current API policies, is there an official process for obtaining additional authorization or a written policy determination?
We understand that athlete OAuth consent alone does not override Strava's platform data-use restrictions.
Our intention is to build ARVENTO REVEAL responsibly, with transparent consent, privacy protections, and appropriate data deletion.
This is a request for data-use policy clarification, not an application for increased athlete capacity.
We would appreciate guidance from an official Strava representative or direction to the appropriate review channel.
Thank you for your time and support.
Best regards,
ARVENTO Team
https://www.arventolife.com
Ride the Journey. Wear the Story.