Hosted icuvisor privacy
This page covers hosted mode: the optional HTTPS bridge between your MCP client and your own Intervals.icu account. Local mode runs on your machine; hosted mode keeps only what is needed to connect authorized clients, call Intervals.icu when you ask, and let you manage access later.
What we keep
- A hosted user record tied to your Intervals OAuth athlete id, display name, and timezone.
- Your hosted preferences: toolset, scope profile, calendar-write choice, and delete mode.
- Encrypted Intervals OAuth credential material, including granted scopes and expiry metadata.
- MCP client and grant metadata for clients you authorize.
- Hash-only lookup rows for MCP tokens, authorization codes, client secrets, browser sessions, nonce cookies, pending authorizations, and rate-limit buckets.
What we do not keep
- Intervals API keys; hosted mode uses Intervals OAuth instead.
- Plaintext bearer tokens, refresh tokens, authorization codes, client secrets, cookies, nonce values, or authorization headers.
- AI conversations, prompts, MCP tool request bodies, or tool responses.
- Training payload archives, activity streams, wellness history, calendar contents, workout libraries, or custom item contents after the current request finishes.
How tool calls work
When an authorized client invokes a tool, hosted icuvisor calls Intervals.icu live, returns the result to that client, and does not build a hosted training-data history. Intervals.icu and the AI client or model provider you choose process data under their own terms.
Operator access
Maintainers can inspect account, preference, grant, rate-limit, and route/status log metadata needed to operate the service. Admin tooling is designed not to expose plaintext credentials or MCP payloads; maintainers can revoke grants or delete your hosted account if needed.
Deletion and revocation
From settings, you can revoke individual MCP client grants or delete your hosted account. Deletion removes icuvisor-hosted user data, credentials, sessions, token lookups, grants, pending authorization records, preferences, and user-scoped rate-limit buckets. It does not delete anything from your Intervals.icu account.
Mode choice
Use local mode when your MCP client can run the icuvisor binary and you want the smallest trust boundary. Use hosted mode when the client needs a public HTTPS MCP endpoint.