Jarvis Dispatch privacy policy

Data access and use

Jarvis Dispatch accesses Gmail messages and labels, Calendar events, and Drive files according to the permissions granted by the account owner. It uses this information to carry out the owner's requested searches, summaries, messages, scheduling, and file operations.

Storage and connected services

OAuth credentials are stored in the owner's Infisical secrets service. The app uses these credentials to obtain short-lived Google access tokens.

Information returned by Google can be passed to the AI client making the request and to the AI provider configured for that client. It may be retained in the client's conversation history and operational records. Retention depends on the owner's configuration of those systems.

Jarvis Dispatch does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. It follows the Google API Services User Data Policy, including its Limited Use requirements.

Revoking access and deleting records

The owner can revoke access through Google Account connections. Revoking access stops new API access; it does not erase records already retained by connected clients. The owner manages those records and can remove stored credentials from Infisical.

Contact

Contact the operator using the support email shown on the Google consent screen.