Privacy policy

Jarvis · last updated 25 October 2026

Jarvis is a personal in-car voice assistant used only by its owner. This page explains what it does with data from Google services when the owner connects their own Google account.

What Jarvis accesses

• Google Calendar, read-only: events in the owner's calendars, to answer questions such as "what's on today?" Jarvis never creates, changes or deletes calendar events.
• Google Tasks: the owner's task lists, to read tasks aloud and to add a task when the owner asks and confirms it with a tap on the screen. Jarvis does not change or delete existing tasks.

How the data is used

• Calendar and task data is fetched only when the owner asks a question that needs it, and only to answer that question.
• To speak the answer, the relevant events or tasks (titles, times and places) are passed to the voice AI service (OpenAI) for that conversation. OpenAI processes it to produce the spoken reply under its API data policies.
• The data is not sold, not used for advertising, not shared with anyone else, and not used to train AI models.

What is stored

• Jarvis does not keep copies of calendar events or tasks. Its activity log records only how many events or tasks were read, never their content.
• The sign-in permission (a Google refresh token) is kept as an encrypted secret in the owner's own Cloudflare account, so Jarvis can read the calendar without signing in each time.

Removing access

The owner can remove Jarvis's access at any time at myaccount.google.com/permissions. After that, Jarvis can no longer read the calendar or tasks.

Google API Services User Data Policy

Jarvis's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

Questions about this policy can be sent to the support email shown on Google's sign-in screen for Jarvis.