API Agreement clarification: derived completion state shown to an accountability partner

Hello,

I'm the developer of Cara, a habit and accountability app currently in closed beta. Before building a Strava integration I'd like to check one point in the API Agreement rather than assume my reading is right.

What we'd like to build. A user connects their Strava account. When they upload an activity, we mark the matching routine complete in Cara, so a morning run they've already logged with you doesn't need ticking off twice. We'd use activity:read, a webhook subscription for activity events, and we'd implement the deauthorisation webhook.

Why I'm asking. Cara's core function is that a user can nominate one partner who sees whether their routines were completed that day. So I want to be precise about what that partner would and would not see.

The partner would see: the routine name the user wrote themselves (for example "Morning run"), and whether it is complete today. That is the same thing they see now when the user taps the checkbox manually.

The partner would not see any Strava field whatsoever. No distance, duration, pace, elevation, route, map, activity title, activity ID or timestamps. There would also be no indication that the completion originated from Strava rather than a manual tap, no Strava data stored against the partner's account, and no Strava branding on that surface.

To be straightforward with you: the partner does thereby learn that the user did the activity that day. That inference is the reason I'm asking rather than proceeding, since the Agreement restricts displaying Strava Data related to a user to anyone other than that user.

My questions:

1. Does a derived completion state of the kind above, carrying no Strava fields and no attribution, fall within the restriction on displaying Strava Data to other users?
2. If it does, would you permit the integration if we limited it to routines with no partner attached, so a Strava-sourced completion is only ever visible to the athlete themselves?
3. The API Policy states that Standard Tier requires "the developer or specified end users maintain an active Strava subscription." Could you confirm which applies? Specifically, would each of our users need their own Strava subscription to connect their account?
4. What's the process and typical timeline for raising athlete capacity beyond 10, for a beta of roughly 50 to 100 users?

I'd rather build this correctly or not at all, so I'm happy to adjust the design to whatever you consider compliant.

Thanks for your time,
Ethan Rock
Cara App Limited · trycara.app