Privacy notice

Purpose and information used

Jarvis is a personal assistant. When you authorize its WHOOP integration, it imports the profile, body measurements, cycles, recovery, sleep, and workout information made available by the WHOOP API under the permissions you grant. This may include your profile identifiers, height, weight, maximum heart rate, recovery scores, heart-rate variability, resting heart rate, respiratory rate, blood oxygen, skin temperature, sleep timing and stages, and strain. Availability depends on WHOOP and your account; not every measurement is always supplied.

Jarvis uses this information to display your measurements and generate personal baselines, recorded trends, descriptive relationships, and wellness observations. The integration does not provide a diagnosis or a complete account of your physiology.

Storage and processing

The Jarvis server stores WHOOP access and refresh credentials and imported measurements in a separate integration directory on the server host. The default import window is 90 days and can be changed by the server owner. A failed import may retain the last successful snapshot. Native widgets keep the current report in memory rather than saving health measurements in desktop-board preferences.

WHOOP provides the source data. Requests to WHOOP and connections to the server may also pass through the network and hosting services configured by the owner.

If you discuss your health with Jarvis, relevant observations may be sent to the AI backend configured for Jarvis to produce the response. These questions and answers can remain in Jarvis's task/conversation history and in the model provider's history under that provider's applicable settings and policies. Automated general-memory archival, stable answer caching, and preference-learning workflows exclude tagged WHOOP health conversations in this version.

The integration does not automatically send your health report through email or SMS. Its health endpoints and tools require an authenticated owner session with full permission. The server owner controls the host, backups, account security, and configured AI services.

Authorization and deletion

Authorization occurs through WHOOP. Jarvis does not ask for or store your WHOOP password. The offline permission lets Jarvis refresh its authorization and import updates while the server runs. You can disconnect the integration in Jarvis and can revoke access through WHOOP.

Disconnecting in Jarvis removes its saved WHOOP connection credentials and imported snapshot, clears the report, and attempts to revoke the connection with WHOOP. If revocation fails, Jarvis reports that failure so you can revoke the connection in WHOOP directly.

Disconnecting does not delete your WHOOP account, past Jarvis conversations/task records, model-provider history, or separately retained backups. Those records must be managed in their respective systems.

Contact

App owner contact: charlesjoushuasantos@gmail.com.

Last updated: September 17, 2026. Review this notice whenever the integration's data use, storage, providers, or sharing behavior changes.