Watchletic MCP Privacy Policy
How Hesselbom Tech AB collects, uses, shares and retains personal data when you connect Watchletic to an AI assistant or another MCP client.
Who operates Watchletic
Hesselbom Tech AB operates Watchletic and its MCP connection. This policy explains how we handle personal data when you connect Watchletic to ChatGPT, Claude, Codex, or another compatible client. Our general Watchletic privacy policy also describes the app and its service providers; the links below let you read that policy or contact us.
Personal data used by the connection
We process your Watchletic account identifier, connection and client identifiers, the access permissions you approve, connection timestamps, and the inputs you send to individual tools. Depending on your requests, the connection can read or change remotely stored settings, structured workouts, activities, routes, layouts, logical Bluetooth device profiles, integrations, readiness, training analytics, and live-tracking settings. Workout and readiness data can include health and fitness measurements such as heart rate, HRV, sleep and raw sensor signals. Routes and activities can contain precise location data; live-tracking settings can include recipient names and email addresses. Exports can contain these same categories of data.
Why we use this data
We use this information to authenticate your connection, enforce your approved permissions and account access, answer training and readiness questions, retrieve and export the data you request, and carry out changes you approve. Connection and action records help prevent duplicate changes and credential misuse, investigate errors, and protect the service. We use health and fitness information to provide the requested health and fitness features, not for advertising. The MCP server receives the tool inputs and resources supplied by the client; it does not retrieve your full conversation history from the client.
Your permission and sensitive data
Connecting requires you to sign in to Watchletic and approve either Read-only or Full access. Full access is selected by default, and you can choose Read-only instead. Read-only permits analysis, exports and previews; applying changes requires Full access and the preview-and-confirm workflow. Health, fitness, precise location and recipient information is sensitive. Only request those details when you intend to share them with the connected client. Device health and location permissions remain under your device settings; changing those permissions does not delete data previously stored or shared.
Who receives information
The client you connect, such as OpenAI or Anthropic, receives the tool results and files requested through that connection. It processes and retains that information under its own terms and privacy policy. Services you explicitly choose for integrations, exports or sharing may also receive the information needed for those actions. Hosting, storage and operational service providers process data on our behalf to run and protect Watchletic. The general Watchletic app also uses analytics, diagnostics, attribution and subscription providers described in our general privacy policy. Authorizing an MCP connection does not by itself send your complete training history to every such provider.
Connection security and operational records
Access and refresh tokens are stored as hashes rather than reusable token values. We also store connection metadata, permissions and token expiry times. MCP tool-call logs record the tool name, success or failure, duration and connection reference. API audit events record account and connection identifiers, action and resource identifiers, status and timestamps. To prevent duplicate mutations, saved action receipts can include the action result, which may contain personal data returned by that change. These saved results are separate from the brief tool-call logs.
Retention of account data and records
Account information, settings, workouts and other cloud data are retained while your account remains active or as needed to provide Watchletic. Disconnecting a client or letting a token expire does not delete this data. Connection records, API audit events and saved action results do not currently have a fixed automatic deletion period tied to token expiry. They may remain after a connection expires or is revoked and are included in requests to delete associated account data, subject to the exceptions below. We have not specified a fixed retention period for operational logs in this policy; contact us with questions or deletion requests concerning those records.
Token and export expiry
Access tokens expire after one hour. Each refresh token expires after 180 days; a successful refresh replaces it and starts a new 180-day refresh period, so an actively used connection can continue until revoked. MCP download links expire after ten minutes, and bulk export downloads expire after 24 hours. Link expiry blocks further download through that link; it does not mean that every underlying server file, job record or previously downloaded copy is immediately deleted. Expired bulk export files are removed by the export worker cleanup process.
Your controls
You can review and revoke connected apps in Watchletic API access settings. Revocation stops future authenticated tool access, but cannot remove information already received by a client or revoke copies it downloaded. Already-issued download links have their own expiry times. You can choose Read-only when authorizing or reconnecting, decline a proposed change, and use the available export tools to obtain your data. For copies held by OpenAI, Anthropic, another connected client or an integration provider, use that provider's privacy controls or contact it directly.
Account deletion and requests
To request deletion of your Watchletic account and associated personal data, email viktor@watchletic.com and include your Watchletic user ID, available at the bottom of Settings in the app. We use the request information to verify your identity and process deletion. Under our existing account deletion policy, we verify the request and delete associated personal data from active systems within three days of receiving the email. Encrypted backup copies may remain for up to 30 days. Limited information may be retained longer when required by law or necessary to prevent fraud or abuse, protect security, resolve disputes or enforce agreements, and only as long as needed for those purposes. Independent client providers have their own retention and deletion practices.
Contact and policy updates
For privacy questions, access or correction requests, or questions about retained connection and log records, contact viktor@watchletic.com. We publish policy changes on this page. This policy was last updated on 29 October 2026.