Privacy Policy

Purpose and operator

This privately operated application connects its owner's Oura account to Martin OS Kingdom tools. It is intended for the owner's personal sleep, readiness, and recovery tracking, not for public users, advertising, or clinical diagnosis.

Data accessed

With Oura authorization, the bridge can read Oura daily sleep summaries, readiness scores, sleep periods and related sleep-stage information. An authorization request may also include heart-rate permission for future owner-approved analysis. Only permissions approved by the owner are requested.

Processing and retention

Authenticated requests fetch records from Oura and return them to the authenticated client over HTTPS. The bridge does not intentionally save the fetched sleep and readiness response bodies in its persistent storage or application logs. It stores OAuth credentials and temporary authorization information in restricted server-side files so that authorization can work. Reverse-proxy and hosting systems may log request metadata such as timestamps, paths, and client network information. Connected clients may separately retain or process health data under their own practices.

Access and sharing

The bridge restricts personal data endpoints with an independent access credential and does not intentionally sell data, send it to advertisers, or expose it publicly. Oura independently handles account data under its own privacy practices. Writing Oura-derived data to a separate journal or memory database requires a separate integration; this read-only service does not do so automatically.

Security

Transport uses HTTPS, and Oura credentials are kept on the server rather than embedded in public code. No technical system is guaranteed entirely secure; the operator is responsible for protecting server credentials and connected clients.

Revocation and deletion

The account owner may revoke access through Oura connected-app controls. Server credentials and temporary authorization state can be deleted by the owner or administrator. Revocation does not necessarily erase data already received by separately authorized clients.

Questions

Contact the operator using the contact email registered for this application in the Oura Developer Portal.