Who operates Jarvis
Jarvis is a personal, non-commercial AI assistant operated by one individual (the "owner") on hardware in the owner's home. It is used only by the owner. This policy describes how Jarvis handles data it receives from Google when the owner connects their own Gmail account.
What Gmail data Jarvis accesses
Jarvis uses Google's read-only Gmail permission (gmail.readonly) for the owner's own account only.
When the owner asks a question that needs it, Jarvis can:
- search the mailbox, and see each matching message's sender, subject, date, read/unread state and the short preview Google provides;
- read the headers and plain-text body of a specific message the owner asks about.
Jarvis does not send, delete, modify, label or archive email, and it does not have permission to. It does not scan the mailbox in the background; Gmail is read only in response to the owner's requests.
Why it is accessed
Only to answer the owner's own questions about their email (for example, finding an order confirmation or a delivery notice). Gmail data is not used for advertising, is not sold, and is not used to train AI models.
Where data is processed and stored
- Gmail data is processed on the owner's own server at home. The AI model that reads it runs locally on that server. Jarvis is configured so that Gmail content, and conversations that include it, are not sent to third-party AI services, and answers based on email are not turned into long-term assistant memories.
- Answers that mention email content may be kept in the assistant's conversation history on the owner's home server until the owner deletes it. Temporary working files that can contain excerpts are deleted automatically about 30 days after each request finishes.
- Data travels between Google and the home server over encrypted HTTPS connections.
How the Google authorization is protected
- The OAuth client credentials and the refresh token are stored on the home server in files that the operating system restricts to the system service account and administrators. They are used only by a separate, audited service inside Jarvis; they are never shown to the AI model, written to chat, or stored in source code.
- Short-lived access tokens are kept only in that service's memory.
- Email content is treated as untrusted text: instructions written inside an email cannot make Jarvis take actions.
Sharing
Gmail data is not shared with, sold to, or transferred to any third party. 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
- Access can be revoked at any time at myaccount.google.com/permissions (select Jarvis, then "Remove access"). Jarvis then can no longer read the mailbox.
- After revocation the stored refresh token no longer works, and the owner deletes it from the home server. Conversation history that contains email content can be deleted by the owner at any time.
Contact
Questions about this policy: [email protected]
Changes to this policy will be posted on this page with a new "last updated" date.