Privacy Policy
Privacy Policy for El Comandante
Last updated: October 8, 2026
What this app does
El Comandante provides MCP tools and a REST API that connect to Intervals.icu. Requests use authorized Intervals.icu credentials. When shared MCP OAuth is enabled, each user connects their own Intervals.icu account. The client receives an encrypted access credential restricted to this MCP server. A separate private deployment can use operator-configured credentials.
Data processed
Depending on the action used, the backend may process Intervals.icu athlete settings, activities, activity streams, wellness and training load data, planned workouts, calendar events, and activity descriptions.
OAuth tokens
For shared MCP access, the backend decrypts the client-held credential and uses its Intervals.icu token only for that request. The backend does not persist OAuth tokens. Login state and single-use authorization codes are held temporarily in memory and expire automatically. The client may retain its encrypted access credential.
Connection approval cookie
After you explicitly approve a client connection, an encrypted, HttpOnly browser cookie remembers that approval for 30 days. It contains a bounded list of connection fingerprints, not training data or Intervals access tokens. Approval is bound to the client, callback and requested permissions. The same approved connection can then go directly to Intervals.icu. Clearing the cookie requires approval again; it does not revoke existing access tokens. Revoke app access in Intervals.icu to disconnect.
Storage
The backend does not maintain an athlete database or store user profiles, coaching context, goals, preferences, or training data. Users manage their personal context in their own client environment. Request handling is transient. Explicit writes persist only in Intervals.icu. Standard server logs may record operational metadata such as timestamps, endpoint names, status codes, and error diagnostics.
Writes to Intervals.icu
Some actions can update Intervals.icu, for example by creating planned calendar events or writing a marked coach analysis block into an activity description. These writes happen only through explicit action endpoints.
Third parties
The app relies on Intervals.icu for training data and on the user's chosen client, such as ChatGPT/OpenAI, for the coaching experience. Data returned to the client may be processed or retained by that service according to its own terms and policies.
Revoking access
Users can revoke the app's Intervals.icu access from their Intervals.icu settings. After access is revoked, the backend can no longer call Intervals.icu for that user.
Contact
For privacy questions, contact the owner through the channel where this app was shared.