Privacy Policy
Last updated: 1 November 2026
This policy explains how Jarvis Gmail ("Jarvis", "the app") handles your information. Jarvis is a personal desktop assistant for Windows. It runs on the user's own computer, and it uses Google sign-in to provide Gmail and Google Calendar features.
1. Information the app accesses
Only after you sign in with Google and grant permission, Jarvis can access:
| Google scope | Data | Purpose |
|---|---|---|
gmail.readonly | Email messages and their metadata (sender, subject, date, body) | To find and read emails you ask about |
gmail.compose | Drafts and messages you create through Jarvis | To write and send emails you ask for. You approve every send on screen first. |
calendar.readonly | Your calendar events | To tell you about today's and upcoming events |
Jarvis does not delete email, does not modify your calendar, and does not access any other Google data.
2. How your information is used
- Data is accessed only when you ask for it (for example, "read my latest email" or "what's on my calendar today?"), or for a briefing you have set up.
- Data is used only to provide these features to you. It is not used for advertising, it is not sold, and it is not used to train AI models.
3. Where your information goes
- Your computer. The Google sign-in (refresh) token is stored only in a local configuration file on your own PC. Jarvis has no server of its own and keeps no copy of your mailbox. Short notes of your conversations with the assistant may be saved locally on your PC as its memory, and you can delete them at any time.
- Google. Jarvis talks directly to Google's Gmail and Calendar APIs to fetch, draft or send what you ask for.
- AI processing. To understand your request and write a reply, the text Jarvis needs for that request is sent to an AI language-model provider (currently Groq). This can include parts of an email or calendar event you asked about. The reply may be turned into speech by a text-to-speech service (currently Fish Audio, with Microsoft Edge text-to-speech as a fallback). These providers process the text only to return a result. Jarvis does not send them your Google sign-in token.
- No other third parties receive your Google data.
4. Google API Services User Data Policy
Jarvis Gmail's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Data retention and deletion
- Email and calendar content is fetched when needed and is not stored by Jarvis in any database.
- You can revoke Jarvis's access at any time at myaccount.google.com/permissions. You can also delete the local token from your PC, which disconnects Jarvis immediately.
- Locally saved assistant notes can be deleted from your PC at any time.
6. Security
Connections to Google and to the processing services use HTTPS. Sign-in uses Google's standard OAuth 2.0 flow, so Jarvis never sees your Google password. Sending an email always needs your on-screen approval.
7. Children
Jarvis is a personal tool. It is not directed at children under 13, and it does not knowingly collect their data.
8. Changes to this policy
If this policy changes, the updated version will be posted on this page with a new "Last updated" date.
9. Contact
For questions about this policy or your data, open an issue at github.com/hassanrazamaree/jarvis-gmail/issues.