Privacy Policy

Jarvis · last updated 11 September 2026

Jarvis is a private assistant operated by Christian Yoder for his own personal use. It has a single user: its owner. This policy describes how it handles Google user data.

What it accesses

With the owner's explicit authorization, Jarvis accesses the Google account of its owner only, for these purposes:

• Calendar — to read, create, and modify the owner's own events.
• Gmail — to read the owner's mail in order to summarize it, and to send mail the owner asks it to send.
• Contacts — read-only, to resolve names to addresses.
• Drive, Sheets, and Docs — to read and edit files the owner directs it to.

How it is stored

Jarvis runs locally on the owner's own computer. Google data is processed in memory to answer the owner's requests and is not copied to any server controlled by the developer. OAuth credentials are stored in a permission-restricted file on that computer.

How it is shared

Google user data is never sold, never used for advertising, and never shared with third parties, except that the text of a request may be sent to the language-model provider that powers the assistant solely to generate a response to that request. It is not used to train models.

Retention and deletion

No long-term copy of Google user data is retained. The owner can revoke Jarvis's access at any time at myaccount.google.com/permissions, which immediately and permanently ends all access.

Limited Use

Jarvis's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

christianyodermj23@gmail.com