Storing derived (non-Strava) metrics for an athlete's own activities under the June 2026 API Agreement

Hi all,
I run a cycling nutrition app. When an athlete opens one of their own activities, we read its power/heart-rate stream and compute metrics that Strava doesn't provide (estimated carbohydrate burned per hour, fluid and sodium estimates, and a comparison with the athlete's nutrition plan). We only show these to the same athlete.
Section 5.5 of the API Agreement in force since 1 June 2026 restricts storing "any data derived from Strava Data" in a store "configured to enable subsequent retrieval, query, or use". How are other developers handling this?
- Do you store derived summary metrics (not raw streams, coordinates or Strava fields) for the athlete's history, with a retention limit, or recompute them on demand?
- Has anyone had official guidance from Strava on this?

Thanks!