Who this covers
Jarvis is a private assistant operated by Nelo Automation for a single user, its owner. It is not offered to the public. This policy describes what Jarvis does with the owner's Google data.
Google data Jarvis accesses
After the owner approves Google's consent screen, Jarvis may access the following through the owner's Google account:
- Gmail: message content and metadata (read and search), and the ability to create drafts.
- Google Calendar: events (read, create and edit).
- Google Drive and Google Docs: file names and contents (search, read, create).
- Google Sheets: spreadsheet contents (read, append, create).
Jarvis requests this data only when the owner asks it to do something that needs it.
How the data is used
Google data is used only to carry out the owner's own requests, such as summarizing unread mail, checking the calendar, or filing a document. It is not used for advertising, and it is not used to build profiles of anyone.
Where the data goes
- Google to the owner's computer. Jarvis runs on the owner's own computer and calls Google's APIs directly from there.
- To Anthropic. To understand a request and write an answer, Jarvis sends the relevant request and the Google content it retrieved (for example, the text of an email or an event list) to Anthropic's Claude API. Anthropic's handling of that content is governed by Anthropic's own terms and privacy policy.
- Voice and messaging. If the owner asks Jarvis to speak an answer aloud or send it to a phone messaging app, the text of that answer is sent to the voice or messaging service used for that feature.
- Jarvis does not give Google data to any other third party, and Nelo Automation does not sell Google user data.
What is stored, and where
- Sign-in tokens. Google's sign-in tokens are stored in a protected file on the owner's own computer. They are not sent to Nelo Automation servers.
- Activity records. Jarvis keeps a local log on the owner's computer of the requests it handled, which tools it used, and the answers it gave. An answer may include a short summary of Google content. Credentials, card numbers and ID numbers are masked before text is saved to the assistant's memory.
- Jarvis does not keep a separate copy of the owner's mailbox, calendar or Drive.
Google API Services User Data Policy
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.
Human access
Google data is read by the owner and by the automated assistant working on the owner's behalf. No other person reads it, except where needed for security, to comply with law, or with the owner's consent.
Control, revocation and deletion
- The owner can revoke Jarvis's access at any time at myaccount.google.com/permissions. Jarvis stops being able to read Google data immediately.
- Deleting Jarvis's local files from the owner's computer removes the stored tokens and activity records.
Changes and contact
This policy will be updated here if Jarvis's handling of Google data changes. Questions: mquiteke@gmail.com