Privacy Policy
Effective date: November 12, 2026
Application: Personal Oura ETL
Operator: wjlevan1
1. Purpose and audience
Personal Oura ETL is a private, noncommercial integration intended to let its operator access, organize, and analyze the operator’s own Oura health and wellness information. It is not currently offered as a public service or to other users.
2. Information accessed
With explicit authorization through Oura’s OAuth consent process, the integration may retrieve the categories of data permitted by the scopes granted for the Oura API V2 application. Depending on those permissions and available API endpoints, this can include sleep, readiness, activity, heart-rate and other physiological measures, workouts, sessions, tags, and basic profile information. The integration will request only the permissions necessary for its personal-use features.
This legal-notices website does not request Oura credentials, collect Oura health data, or embed advertising or analytics trackers.
3. How information is used
Authorized Oura data is used for personal retrieval, structured ETL, private reporting, visualization, and analysis directly related to the operator’s own wellness information. It is not used for advertising, marketing, sale, data brokerage, or making data available to other users.
Data retrieved through the Oura API is not intentionally sent to third-party AI models or AI platforms. Any future AI-related use would first need to satisfy Oura’s then-applicable API and MCP terms and any required authorization.
4. Storage and security
If the integration stores retrieved data, storage is limited to privately controlled systems or services selected by the operator, with access restricted to authorized use. OAuth credentials and raw health information are not intended to be published in this repository or on this public website. The operator is responsible for appropriate access controls, secure transmission, and protection of stored credentials and data.
The public legal-notices pages are hosted by GitHub, which may process ordinary website access information under its own privacy terms. GitHub Pages is not used to host Oura health records.
5. Disclosure and third parties
The integration does not sell or disclose Oura health data to advertisers, data brokers, or other app users. Infrastructure providers, if used to operate the private integration, may process information only as necessary to deliver the authorized service and subject to applicable requirements. Material changes to sharing or processing practices will be disclosed in an updated policy before they are implemented, with additional consent obtained where required.
Oura’s own collection and processing of data is governed by Oura’s separate policies.
6. Retention, revocation, and deletion
Oura data will be kept only as long as necessary for the specific authorized personal-use purpose, consistent with Oura’s applicable requirements. Access may be revoked through Oura’s account/connected-app controls. Following revocation, further collection and processing under that authorization will cease; data subject to a deletion request will be deleted promptly from the integration’s controlled storage, including applicable retained copies and backups.
Deleting data from this integration does not itself delete data held by Oura.
7. Questions and requests
For privacy questions or requests, contact the operator through the support contact provided in the Oura application registration, or visit the operator’s GitHub profile for available contact details. Do not post health data, OAuth tokens, or other sensitive information in public GitHub issues.
8. Changes to this policy
This policy may change if the integration’s functionality or data handling changes. Any updated policy will be published here with a revised effective date.
Related documents: Terms of Service · Oura API and MCP Agreement