THOP privacy notice
Effective date: October 13, 2026
THOP is operated by HumanOS LLC ("THOP," "we," "us"). This notice covers thop.io, the THOP waitlist and the planned personal WHOOP developer trial described below. THOP is intended for adults 18 and older in the United States. For privacy questions, contact [email protected].
The WHOOP trial is being prepared for THOP’s owner alone. The connection is not active, and this notice describes its planned design. The current waitlist form asks for email only. Joining the waitlist does not connect WHOOP or Apple Health or give THOP permission to access health records.
Planned WHOOP developer trial
If activated, the trial would use the THOP iPhone app and backend to display factual WHOOP measurements in THOP Signals and test the connection. Connecting would be optional and would require express permission before THOP accessed your WHOOP data.
The requested WHOOP permissions would be read access to recovery, sleep and cycles, plus offline access for renewing connection credentials. Offline access would not create a background health-data sync: import and refresh would be started manually while the app is in use. The trial would not request WHOOP profile, name, email, workout or body-measurement permissions.
Sign in with Apple and Google Firebase Authentication would support app sign-in. Firebase App Check would verify app requests. THOP’s backend account record would contain an internal account identifier, setup and account status, and creation, update and deletion times.
WHOOP information received and retained
WHOOP recovery, sleep and cycle responses would pass through THOP’s backend. THOP would check the WHOOP user identifiers in those records to verify that they agree before linking the connection. It would not match accounts by email or merge records across THOP accounts. Empty or unavailable records would not establish identity.
The stored measurements would be Recovery percentage, HRV measured as RMSSD in milliseconds, resting heart rate in beats per minute, total sleep duration, Sleep Performance percentage when available, and cycle Strain. Associated source details would include internal record references, observation intervals and time-zone offsets, main-sleep or nap status, quality and calibration information, and source ordering and version information.
Full responses can contain additional fields, including sleep-stage and sleep-need details, respiration, oxygen saturation, skin temperature, heart-rate summaries, energy and steps. The planned backend would handle these extra fields, raw record identifiers and the WHOOP user identifier during processing, rather than retain them as health records. The trial would not use WHOOP health data for AI coaching or health advertising.
Planned providers and safeguards
The planned flow is between the iPhone app, THOP’s backend and WHOOP. Google Cloud services would support account verification, storage and credential protection: Firebase Authentication and App Check, Firestore, Secret Manager and Cloud KMS. The selected development database region is us-central1 in the United States; this does not describe every location used by those providers.
WHOOP connection credentials would stay encrypted on the backend. The app would receive factual readouts and hold its account snapshot in memory, without a persisted readout cache. The source design prohibits raw health-response and credential logging. Actual hosting, access and diagnostic logs, key custody, backups and cleanup still need to be qualified before real access.
The 14-day measurement window
The initial import would cover a fixed 14-day period. Later manual refreshes would stay bounded. The usable measurement window would be based on the original source observation interval, not the import date. Reimporting or correcting a record would not restart its age.
After a measurement aged out, THOP would withhold it from readouts and remove its value through cleanup. A missing collection or unavailable source record would not, by itself, prove deletion. The 14-day measurement window would not set one deletion deadline for every provider backup or necessary connection or security record. Those operational retention details are still being qualified.
Disconnecting and requests
A confirmed WHOOP disconnect would first block further THOP collection and readout use, clear the app’s local snapshot and remove THOP’s imported WHOOP facts and readouts. THOP would then attempt to revoke WHOOP access and destroy the connection credentials.
If revocation failed, encrypted credentials would be restricted to revocation work for a maximum of 24 hours after the accepted disconnect, then destroyed. Successful revocation would end that custody sooner. These are planned controls awaiting deployed verification. Disconnecting would leave your THOP account and Apple sign-in in place and would not delete records held by WHOOP.
Contact [email protected] to ask to access, correct or delete information THOP holds about you. Whole-account deletion is a separate process from disconnecting WHOOP. The trial’s working access and account-deletion process must be verified before real access; a downloadable export has not been implemented. Apple Health collection and AI health use are outside this planned trial.
Website and waitlist information
The signup form asks for your email address. We use it to manage the THOP waitlist and send emails about the waitlist and access invitations. If you contact us, we receive the contact details and message you send and use them to respond. Please do not send health records or other sensitive information in a waitlist or support message.
Carrd hosts thop.io. Beehiiv stores and manages the waitlist and provides email delivery. Google Workspace handles messages sent to our contact addresses. These providers process information needed to provide their services. Beehiiv may also process technical information such as IP address, browser or device information, and referral or campaign information associated with a signup or link.
The embedded Beehiiv form loads Google Tag Manager and Cloudflare scripts. Beehiiv uses tracking technologies, and emails sent through it may record opens and link clicks. Your browser’s cookie and tracking settings may affect these technologies. Beehiiv’s privacy policy explains processing it carries out for its own service operations. We haven’t verified the embedded form’s response to Do Not Track or Global Privacy Control signals, or whether those third parties collect information across websites over time.
Waitlist retention and choices
We keep waitlist subscriber records, including unsubscribed profiles, for up to 12 months from the original signup date. We delete them sooner if you request deletion or we close the waitlist. Unsubscribing stops waitlist emails but does not immediately erase your Beehiiv profile or past engagement information.
This limit covers our waitlist records. It does not establish a single deletion deadline for every provider backup, security record or legally required record.
Contact [email protected] to ask to access, correct or delete information about you, or to stop waitlist emails. When available, you can also use the unsubscribe link in an email. Please contact us from the address you used to join the waitlist. Additional rights may apply under the laws where you live.
Contact and changes
For privacy questions, or if you believe someone under 18 has provided information, contact [email protected]. We will post changes to this notice here and update its effective date. Changes to the trial’s data or uses would need fresh review and any required permission before activation.
← Back to THOP