Jarvis home

Privacy policy

This policy describes the private Jarvis Google connection.

What Jarvis accesses and why

Jarvis uses the Google account identity to check that it is connected to its owner's account. It can search and read Gmail messages and use relevant details to identify appointments, tasks and changes that need attention. It can prepare a new unsent draft for the owner's review. Jarvis does not send email.

Jarvis can read the calendar list, event details and availability. It uses that information to check plans and keep confirmed appointments current on the owner's configured calendars.

Where the data goes

Jarvis stores the Google credential in the Mac's Keychain. Source observations and the planning records derived from them are stored in private local files so the owner can trace and reconcile decisions.

When an assistant run needs to interpret Google information, relevant results may be processed by OpenAI Codex through the owner's ChatGPT account to provide that feature. A reminder or summary may be delivered to the owner through Jarvis's iMessage account. Jarvis does not sell Google data, use it for advertising, or use it to train general-purpose models.

Control and deletion

The owner can revoke the connection in Google Account connections. This stops future access. It does not remove existing events, drafts or local records. The owner can separately remove the local grant and local records on the Mac, or manage drafts and events in Google.

Jarvis limits its use of Google information to the features described above and follows the Limited Use requirements of the Google API Services User Data Policy.