A private integration with the Oura API, used by its operator and by a small number of invited study participants. This page states exactly what it reads, where that data is stored, and who can see it. The short version: it reads two scopes, stores them on hardware in the operator's home, and shares them with nobody.
daily · heartrateThis policy applies to everyone whose data the application holds. At present that is its operator alone. It is written to also cover a small research study — no more than ten enrolled participants at any time — in which each participant connects their own Oura account. It is not a consumer product, there is no public sign-up, and nobody's data enters the system without that person having connected it themselves.
Participation is by invitation and is entirely voluntary. Before any data is collected, each participant is told what will be read, why, how long it is kept, and how to leave; they then authorise access through Oura's own OAuth screen, which they control. Consent can be withdrawn at any time without giving a reason and without consequence. Only adults aged 18 or over may take part; the application is not offered to children and no children's data is knowingly collected.
The application requests two OAuth scopes and no others — daily and
heartrate. Within those, it retrieves:
It does not request the personal scope (age, sex, height,
weight) or the email scope, and it does not read tags, workouts, sessions,
SpO₂, stress, or ring configuration. Nothing beyond the above is collected from any
participant.
Retrieved data is written to a time-series database running on a single computer on the operator's home network. It is not stored in any cloud service, not replicated to a hosting provider, and not synchronised to any file-sharing service. Records are filed under a pseudonymous participant code; the list linking a code to a person is held separately from the measurements and is accessible only to the operator.
Nobody. The data is not sold, licensed, or disclosed to any third party. There is no analytics service, no advertising network, no crash reporter, and no external processor of any kind. The only network connections the application makes are outbound requests to Oura's own API. Should any finding ever be published or submitted to a regulator, it would report aggregate or de-identified results, and no participant would be identified without their separate, specific, written permission.
Measurements are retained indefinitely, because the purpose is longitudinal — comparing sleep across months is the point — and because research records may need to remain available for verification. A participant may ask for their data to be deleted at any time, and it will be, other than any figure already incorporated into a completed analysis, which cannot be un-published; that residue is de-identified.
Whether or not the law where you live grants them, everyone whose data is held here may: ask what is held about them and receive a copy in a portable format; have anything inaccurate corrected; have their data deleted; withdraw from the study; and object to a particular use. Requests go to legal@coherentstrategiesllc.com and are answered within 30 days. There is no charge, and asking costs you nothing — withdrawing will never affect anything else.
Authorisation can be revoked at any time from Oura account settings, which immediately stops all further retrieval and needs no notice to anyone. To also have data already collected removed, email the address above; deletion is confirmed in writing once done.
The purpose is to study sleep quality and its physiological correlates. Findings may inform future product development and may, in time, form part of a submission to a regulator such as the FDA. Data is used only for that research purpose and is not repurposed for marketing, profiling, or automated decisions about anyone. If the study ever moves to a stage requiring independent ethical review, that review will be obtained before the relevant work begins, and participants will be told.
API credentials are held in files readable only by their owner, and the application refuses to start if it finds them readable by anyone else. All API traffic uses verified TLS; there is no option to disable certificate verification. The database listens only on the local loopback interface and is not reachable from the network. Each participant's credentials are held separately, so access to one account never confers access to another.
Any change is published on this page with a new effective date. If a change materially affects how participants' data is handled, everyone enrolled at the time is told directly by email before it takes effect.