Privacy Policy

Effective date: August 31, 2026

This Privacy Policy describes how JDVA — Jarvis Desktop Voice Assistant ("JDVA") accesses, uses, protects, stores, and shares information when users interact with JDVA and enable supported connected services.

1. Information JDVA may access

JDVA is designed to request only the permissions required for features that a user chooses to enable.

When a user authorizes a Google-connected feature, the information available to JDVA depends on the Google API permissions displayed on Google's OAuth consent screen.

Depending on the enabled feature, this may include:

• Basic account information provided as part of Google's authorization process.
• Gmail data required for an explicitly enabled read-only email feature, such as message information or content made available through an authorized Gmail read-only scope.
• Permission to send email through Gmail when the user enables a user-directed email-sending feature.

JDVA does not obtain Google account passwords. Google authentication and authorization are performed through Google's OAuth services.

2. How Google user data is used

Google user data is used only to provide or improve user-facing JDVA functionality that the user has requested or enabled.

Examples may include retrieving information for a user-requested email workflow, presenting relevant information to the user, or sending an email that the user has authorized JDVA to send.

JDVA does not use Google user data for targeted advertising, personalized advertising, credit decisions, data-broker services, or unrelated commercial profiling.

3. Artificial intelligence and machine learning

Google Workspace API data obtained through JDVA is not used to develop, train, or improve generalized or non-personalized artificial intelligence or machine-learning models.

Any processing of Google user data is limited to providing or improving the user-facing functionality that the user has requested and to uses permitted by applicable Google API policies.

4. Storage and processing

JDVA is designed to minimize storage of Google user data. OAuth credentials and tokens may be stored using protected credential storage associated with the JDVA environment so that an authorized connection can operate without requiring the user to sign in for every permitted action.

Where a connected feature requires cloud-based transport or processing, information may be processed through infrastructure used to provide that feature. Such processing is limited to what is necessary for the authorized user-facing functionality.

JDVA does not intentionally create permanent copies of Google user data unless such storage is required for an enabled feature, permitted by applicable Google policies, and appropriately disclosed to the user.

5. Sharing and disclosure

JDVA does not sell, rent, or provide Google user data to data brokers, advertisers, or information resellers.

Google user data may be transferred or processed only when necessary to provide an authorized JDVA feature, when directed or consented to by the user, when required for security purposes, or when disclosure is required by applicable law.

6. Data security

JDVA uses technical and administrative safeguards intended to protect user information, including least-privilege authorization practices, protected credential handling, encrypted network transport where applicable, and controlled access to connected-service functionality.

No method of electronic storage or transmission can be guaranteed to be completely secure, but JDVA is designed to minimize unnecessary access and exposure.

7. Data retention and deletion

JDVA is designed to retain Google user data only for as long as needed to provide an enabled user-facing feature, satisfy an authorized workflow, maintain security, or meet applicable legal obligations.

OAuth credentials may remain available to JDVA until the authorization is revoked, removed, expires, or is otherwise invalidated.

Users can revoke JDVA's access to their Google Account through Google's account security and third-party connection controls. Revoking access prevents JDVA from continuing to use the revoked Google authorization.

8. User control

Use of Google-connected features is optional. Users choose whether to authorize the permissions presented by Google and may revoke those permissions through their Google Account.

JDVA will request additional authorization if a future feature requires permissions beyond those already granted.

9. Google API Services User Data Policy

10. Changes to this Privacy Policy

This Privacy Policy may be updated as JDVA functionality, connected services, or data-handling practices change. Material changes will be reflected on this page together with an updated effective date.

JDVA's actual data practices will be maintained consistently with the disclosures published in the current version of this Privacy Policy.