Privacy Policy

JARVIS Personal Health · Effective November 8, 2026

JARVIS is a private, single-user application. The only person whose data it handles is its owner, who is also its only user.

What data is accessed

With the owner's authorization through Oura's own consent screen, JARVIS reads the owner's Oura sleep summaries (for example sleep duration, sleep stages, bedtime, wake time, and nightly heart-rate and heart-rate-variability measures). It requests only Oura's daily scope. It doesn't request email, personal profile, workout, tag, session or other scopes.

How it is used

The data is used only to show the owner their own sleep on a personal dashboard, and to answer the owner's own questions about it. Those answers are composed by fixed rules on the owner's computer. It isn't used for advertising, profiling, research or any other purpose.

Artificial intelligence

Oura data is never used to train, fine-tune, evaluate or improve any AI model, is never turned into embeddings, and is never sent to cloud AI services or large language models.

Where it is stored

• Sleep summaries are stored in a local database on the owner's own computer.
• Oura sign-in credentials (access and refresh tokens) and the app credentials are stored in the operating system's encrypted keychain on that computer. They are never written to logs, files or source code.
• Data is fetched directly from Oura over HTTPS. JARVIS operates no public server. Local backups stay on the same computer and aren't copied to cloud storage.
• The owner may view their dashboard from their own phone over an encrypted private network. It isn't publicly accessible.

Sharing

Health data is never sold, rented, shared or disclosed to anyone, and it is never sent to cloud AI services. JARVIS uses no analytics, tracking or advertising, and no third-party cookies; the only cookie is a sign-in session for the owner's own paired phone.

Retention and deletion

Stored sleep summaries are deleted automatically after about 13 months. The owner can erase all stored health data sooner at any time, delete the stored credentials, and revoke JARVIS's access in their Oura account. Once access is revoked, JARVIS reads no further Oura data. Deleting the Oura data already stored is the owner's choice, and the owner can do it with JARVIS's erase function.

Changes

If this policy changes, the updated version will be posted on this page with a new effective date.