Privacy Policy
Jarvis · Last updated: 2026-11-11
Overview
Jarvis is a personal desktop assistant that runs entirely on the user's own devices. There is no Jarvis server operated by the developer, and the developer does not collect, receive or store any user data.
Google user data accessed
- Google Calendar (
calendar.events,calendar.calendarlist.readonly): to list, create, update and delete calendar events at the user's request, and to show reminders before events. - Gmail (
gmail.metadata): to detect new messages and show a notification with the sender, subject and date. Jarvis cannot read message bodies or attachments.
How the data is used and stored
- Data is used only to provide the features above to the user who signed in.
- OAuth tokens are stored in the operating system's secure keyring (or an encrypted local file) on the user's own devices. They may be synchronized between the user's own paired devices over an encrypted (TLS) connection.
- When the user asks the assistant a question about their calendar or email, the relevant event or message metadata may be sent to the AI language model provider configured by the user (for example a local Ollama model or a cloud API) solely to answer that request.
- Google user data is never sold, never used for advertising, and never shared with any other third party.
Limited Use
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.
Revoking access and deleting data
The user can sign out in Jarvis's settings, or revoke access at any time at myaccount.google.com/permissions. Uninstalling Jarvis and deleting its data folder removes all locally stored data.
Jarvis