Legal
Health data notice
What this notice is
This is the notice for wearable and health data in EyeQ (Android, package in.atlethIQ.eyeqArcade_v001). The app shows it before you connect a source. Per-source steps are on connected services.
When you connect a source, we record your agreement, policy version 2026-11-06, and the scopes shown to you.
Who is asking
Atlethiq is the Data Fiduciary. Spinor Labs owns the Atlethiq backend. The Call is the readiness area inside EyeQ.
Contact ks@atlethiq.com. This notice is in English.
What each source shares
WHOOP
You authorise EyeQ on WHOOP’s own consent screen. EyeQ then reads WHOOP’s cloud API for your account.
Recovery (heart-rate variability and resting heart rate), sleep, cycles, and workouts, limited to the scopes you approve. We do not show this to other users or on leaderboards. We do not send it to Zip. We do not use it to train an AI model.
COROS
The COROS app can write to Health Connect on your phone. EyeQ reads those records from Health Connect, for the types you allow. EyeQ does not connect to COROS’s cloud in this version, and it does not write to Health Connect.
Sleep and heart rate that the COROS app has written to Health Connect, limited to the types you allow and to what The Call uses. The COROS app does not currently write heart-rate variability or resting heart rate to Health Connect. We do not show this to other users or on leaderboards. We do not send it to Zip. We do not use it to train an AI model.
Samsung Health
Samsung Health can write to Health Connect on your phone. EyeQ reads those records from Health Connect, for the types you allow. EyeQ does not connect to Samsung’s cloud and does not write to Health Connect.
Records Samsung Health has written to Health Connect, limited to the types you allow and to what The Call uses. Samsung Health does not currently write heart-rate variability or resting heart rate to Health Connect, so those two do not come from Samsung Health. We do not show this to other users or on leaderboards. We do not send it to Zip. We do not use it to train an AI model.
Garmin
If Garmin Connect writes to Health Connect on your phone, EyeQ reads those records for the types you allow. EyeQ does not connect to Garmin’s cloud. Metrics that stay in Garmin Connect are not read.
Records Garmin Connect has written to Health Connect, limited to the types you allow and to what The Call uses. Garmin’s own metrics that remain in Garmin Connect are not included. We do not show this to other users or on leaderboards. We do not send it to Zip. We do not use it to train an AI model.
Fitbit (via Google Health)
The Fitbit app, through Google Health, can write to Health Connect on your phone. EyeQ reads those records from Health Connect, for the types you allow. EyeQ does not connect to Fitbit’s cloud.
Records Google Health has written to Health Connect from Fitbit, limited to the types you allow and to what The Call uses. What arrives depends on what that app writes. We do not show this to other users or on leaderboards. We do not send it to Zip. We do not use it to train an AI model.
Android Health Connect
The Android app reads Health Connect on your phone, for the types you allow. It does not write to Health Connect.
Heart-rate variability, resting heart rate, sleep, and workouts, limited to what you allow and to what The Call uses. We do not show this to other users or on leaderboards. We do not send it to Zip. We do not use it to train an AI model.
Notes you type
You type them into EyeQ.
Effort on a 1 to 10 scale, how you feel, and a short note.
No other wearable is offered. Apple Health is not offered. Oura, Strava and Polar are not connected.
Why
To compute one daily training suggestion for you: The Call (“Go hard”, “Hold” or “Back off”), the reasons for it, the trend of those suggestions, and how fresh the source is. It is a training suggestion from your own data, not medical advice. It does not diagnose, detect or measure a condition.
We do not sell it, license it, use it for ads, show it to other athletes or on leaderboards, or analyse it across athletes. We do not use it to train an AI model.
Health Connect data is used only for that coaching feature. Zip, the chat guide, does not receive these values or The Call.
How to stop it
Stopping is as easy as connecting.
- WHOOP: disconnect in EyeQ, or remove EyeQ in WHOOP. We revoke access and delete the WHOOP data we hold within 30 days.
- Health Connect, including COROS, Samsung Health, Garmin, and Fitbit via Google Health: turn the permission off on the phone, or disconnect it in the app. That stops future reads, and we delete stored samples from that source within 30 days. In the other app, turn off its sharing to Health Connect.
- Notes you typed: delete them with Delete my health data, or delete the account.
How to delete it
Raw wearable data is kept for up to 12 months, rolling, while the source is connected. Daily Calls are kept while the account is open. Wearable data is deleted within 30 days of disconnecting the source or deleting the account.
Delete my health data removes health samples, daily Calls, notes you typed, and the health consent record. Account deletion is described on the deletion page.
Your rights and complaints
You can see the wearable data we hold, ask for a summary of how it is used, ask us to correct it, ask us to erase it, and nominate someone to act for you. Email ks@atlethiq.com. We acknowledge a request within 72 hours and answer within 30 days.
From 13 May 2027 you can also complain to the Data Protection Board of India. The full policy’s grievance section is here.