Dotty WHOOP Integration Privacy Notice
Effective date: October 16, 2026
Operator: Taylor Wilson
Privacy contact: support@wilsontrust.org
What this notice covers
This notice covers Dotty Personal Read Only, a private, personal-use integration that helps its account holder consider WHOOP sleep, recovery, and strain alongside subjective fatigue and daily commitments. It describes the proposed initial, user-approved single-session test on a Mac. The local reader is a prototype; the OAuth connection and credential-handling flow described as planned below are not yet implemented. It does not describe Gather, Special Events, general website browsing, or a future iPhone release.
The integration provides planning context, not medical diagnosis, treatment, or a prescribed training target. A measured strain value is not a recommended target.
Permission and information accessed
The planned connection will direct you to WHOOP to sign in and choose whether to authorize access, without giving your WHOOP password to this integration. The intended authorization requests only the read permissions read:sleep, read:recovery, and read:cycles. It does not request workout, profile, or body-measurement permissions.
When invoked with authorized access, the prototype reader retrieves a rolling seven-day window of sleep, recovery, and physiological-cycle records on demand. WHOOP responses can include account and record identifiers, timestamps, timezone offsets, sleep stages, recovery scores, heart-rate and heart-rate-variability measurements, oxygen and temperature measurements, strain, and related cycle measurements. These extra response fields are processed transiently on the local device; requesting the three permissions does not limit WHOOP's responses to just the final summary fields.
How the information is used
The local reader matches related records, checks whether scores are available and recent, and creates a smaller daily summary. It reports main sleep and naps separately and flags missing, unscorable, stale, or overlapping data. The test uses the Mac's current system timezone when available, with Pacific time as an identified fallback. It does not infer your location from your IP address. A Mac left at home cannot determine a traveling iPhone's timezone.
What is shared with the assistant
Authorizing access through WHOOP does not itself authorize disclosure to ChatGPT. Before a summary is sent, the account holder must explicitly approve sharing the summary with OpenAI through their ChatGPT account for personal planning. If that separate approval is not given, the summary must not be sent to ChatGPT. This consent step is a requirement for the proposed test, not an existing consent screen.
For a user-approved test, the intended sharing flow returns only the minimized summary through the authorized Mac task to your cloud-based dotty assistant in ChatGPT. It contains:
Reporting date, timezone and timezone source, and the time the summary was made.
Recovery percentage when usable.
Main sleep minutes and session count, nap minutes and session count, and latest main sleep end time.
Measured cycle strain, cycle start and update times, and whether the cycle is complete.
Data-quality flags and a short interpretation limitation.
The summary excludes account and record identifiers, raw sleep stages, precise sleep start times, heart-rate variability, resting heart rate, oxygen, temperature, calories, and credentials. The summary is still sensitive health information. Raw WHOOP responses are not intentionally sent to the assistant or placed in diagnostic logs by this integration.
This integration does not sell WHOOP data or use it for advertising. The proposed sharing flow sends the approved summary to OpenAI through the account holder's ChatGPT account. Sending a summary to ChatGPT involves OpenAI's processing under the terms, privacy policy and data controls that apply to that account. The summary may remain in conversation history or service records according to those settings and policies. See OpenAI's chat and file retention guidance. This notice does not promise that every recipient excludes data from model improvement or that ending a local test deletes cloud copies.
Storage, access, and retention
The local reader keeps raw responses in process memory for the run and writes no raw health-data files. A memory-only OAuth adapter is planned for the single-session test but has not yet been implemented or verified. The reader does not persist access tokens. The adapter's intended design handles client credentials and access tokens locally in memory, without placing them in chat, shell arguments, source code, logs, or persistent token storage, and discards them when its process exits. An end-to-end authenticated test must not run until that handling is implemented and verified. Raw responses held by the reader are discarded when its process exits. This does not guarantee secure erasure of operating-system memory or deletion of WHOOP's or OpenAI's separate records.
The test does not request offline access or refresh tokens, schedule recurring reads, install a persistent daemon, or write to your calendar. Access tokens expire on WHOOP's schedule. WHOOP may retain the app authorization until you revoke it; a single-session test does not itself remove that authorization.
Your choices and questions
The prototype has no implemented disconnect screen or background synchronization. Stopping an invocation ends that local run; it does not revoke WHOOP authorization.
You can decline authorization, stop a test, or revoke the integration's authorization through WHOOP's account controls. Revocation stops subsequent authorized reads; it does not delete WHOOP's original records or a summary already shared with ChatGPT. Manage those records using the respective service's controls. Contact the privacy address above for questions or requests concerning records controlled by this integration. Please do not send passwords, client secrets, tokens, or raw health exports by email.
Changes to the integration
An iPhone implementation, persistent credentials, refresh access, background reads, additional recipients, or a server-side OAuth broker would change this flow. We will update this notice and obtain the relevant approval before enabling those features. The current notice does not authorize those future features.