Privacy policy
Effective 26 September 2026.
Who runs Jarvis
Jarvis is a private AI assistant operated by Mo Jama (mohamedj89@gmail.com) for his own personal use. It is not offered to the public. The only Google account it is connected to is its operator's own.
Google data Jarvis accesses
With the account holder's permission, Jarvis requests these Google permissions:
- Gmail (read, modify, send) — to read and search email, apply labels, archive or mark messages, and send email when asked.
- Google Calendar (read, events) — to read calendars and create or change events when asked.
- Google Drive (read-only, and files the app creates) — to find and read files, including Google Docs.
- Google Sheets (read, edit) — to read and update spreadsheets when asked.
- Google Tasks — to read and manage task lists when asked.
- Basic profile (name, email address) — to identify which account is connected.
How the data is used
Google data is used only to carry out requests the account holder makes to Jarvis — for example, “summarise today’s email” or “what’s on my calendar tomorrow”. It is not used for advertising, not sold, and not used to build profiles for anyone else.
Where the data goes
- The operator’s own computer. Jarvis runs there. Google sign-in tokens are held by a credential gateway on that computer and added to requests to Google as they leave it; the tokens are never given to the AI model or included in messages.
- Anthropic’s Claude API. The Google content needed to answer a request (for example, the text of the emails being summarised) is sent to Anthropic’s Claude model as input, and its answer comes back to Jarvis.
- WhatsApp and Telegram. Jarvis’s replies, which can contain Google content, are delivered to the account holder through these messaging apps.
- A private automation server. Some Drive, Sheets and Tasks requests are carried out by automation workflows (n8n) on a private server the operator controls.
- The operator’s private notes. When asked, Jarvis saves notes or summaries into the operator’s personal notes, which sync between his own devices and a private backup repository.
Google data is not shared with anyone else, except where required by law.
Storage and retention
Conversation history and service logs, which can include Google content Jarvis has used, are stored on the operator’s own computer. They have no automatic expiry; they are kept until the operator deletes them, and are deleted on request. Google sign-in tokens are kept until access is revoked.
AI training
Jarvis does not use Google user data to develop, improve or train generalised AI or machine-learning models.
Limited Use
Jarvis’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.
Revoking access and deleting data
Access can be revoked at any time at myaccount.google.com/permissions. To have stored data deleted, email mohamedj89@gmail.com.
Changes
If this policy changes, the updated version will be posted on this page with a new effective date.