$ jarvis --privacy
Jarvis privacy policy
Jarvis is a personal assistant used only by its author, on his own Mac. This page explains which data it uses, how, and how to delete it. Contact: brightefoo@gmail.com
Last updated: October 2, 2026
1. Who uses Jarvis
Jarvis is not a public service: there is no sign-up and a single user, its author. It only accesses the accounts that this user connects himself.
2. Google data used
Gmail, read-only (gmail.readonly): list, sort and summarise email, on request.
Gmail drafts (gmail.compose): prepare reply drafts. No email is sent without my explicit confirmation.
Google Calendar, read-only (calendar.readonly): read my events for the daily briefing.
Jarvis requests no other access and never modifies or deletes email or events.
3. Where the data goes
Processing happens on my Mac. The Google access token is kept in the macOS Keychain. Jarvis has no server and no remote database.
To phrase an answer, Jarvis sends only what is needed (for example the excerpt of an email to summarise) to Anthropic's Claude model, through my own account. That processing falls under Anthropic's policy: https://www.anthropic.com/legal/privacy
No other transfer takes place.
4. What Jarvis never does
It does not sell this data, use it for advertising, share it with anyone beyond what is described above, let any other person read it, or use it to train artificial intelligence models.
5. Limited Use
Jarvis's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy
6. Retention and deletion
Jarvis keeps a local log of its actions (date, kind of action, decision), without copying email content. Summaries are not kept beyond the current conversation.
Jarvis's access to the Google account can be revoked at any time here: https://myaccount.google.com/permissions. Uninstalling Jarvis deletes its local data and tokens.
7. Security
Encrypted connections (TLS), secrets in the macOS Keychain, permissions checked in code for every action, an append-only hash-chained log.
8. Contact
For any question: brightefoo@gmail.com