API Policy clarification – Multiplayer territory game using derived GPS data

Hello,

I'm developing TERAYA (https://teraya.run), an outdoor territory-conquest game currently in beta.

The game processes authorized Strava GPS activities into H3 geographic cells. Players accumulate presence in these cells, and the player with the highest presence becomes the territory owner.

Other registered players can see territory ownership, TERAYA nicknames and game rankings, but not the original Strava GPS tracks or activity details.

Before expanding beyond our current 10-athlete capacity, I would like to clarify:

1. Is it permitted to display multiplayer territory ownership derived from authorized Strava activities?

2. Can H3 presence scores and territorial ownership be stored persistently?

3. Does the seven-day caching restriction apply to these derived game data?

4. What derived data must be removed when an athlete revokes access or deletes an activity?

I have reviewed the Strava API Agreement and API Policy, but I would appreciate guidance on how these restrictions apply to this specific use case.

Thank you for your help.