Privacy Policy

Effective: November 12, 2026

This policy describes the privately operated Jarvis household assistant's use of Google account data. Jarvis is maintained for the account owner's personal household use; it is not a public application.

Data accessed

With the Google account owner's permission, Jarvis can access Google Drive using the OAuth scopes shown during the Google consent process. The current Drive integration is intended to read incoming instructions and reference documents in an owner-managed exchange folder, create reports, and acknowledge messages. The approved scope can permit broader Drive access than those specific uses.

How information is used

Google Drive information is used for owner-requested document exchange, review, task continuity, reporting, and other workflows explicitly enabled by the owner. Jarvis does not sell Google user data or use it for advertising.

Where information is processed and stored

Jarvis operates on private, owner-managed infrastructure. Depending on the configured workflow, data may be retained in local task records, operating logs, reports, and backups, as well as files intentionally stored in Google Drive. The owner manages those systems and their retention settings. Data exchanged with Google is processed by Google under its applicable terms.

Sharing with connected services

Some optional owner-enabled workflows deliver selected reports or notifications to external connected services, including a ChatGPT-based review workflow. Data provided through those integrations is subject to their own applicable policies. The owner is responsible for choosing what information is sent, and Jarvis should not transmit credentials or unrelated private household content through notification emails.

Security and access

OAuth tokens and service credentials are intended to be kept in secured, owner-managed configuration or credential storage, not in the public information pages. Access is restricted to the account owner's authorized workflows. No security system can guarantee absolute protection.

Control and revocation

The Google account owner can revoke Jarvis's Google access at any time in their Google Account connections. The owner can inspect and delete locally retained records and reports using the systems where they are stored. Revoking Google access does not automatically remove local copies previously created.

Contact and updates

Questions about this private integration should be directed to the application owner using the support email listed on the Google OAuth consent screen. This policy may be revised if the application's actual use of Google data or connected services changes.