Privacy policy
Effective November 7, 2026
Jarvis is a private personal assistant used only by its developer, Fritz Desir, on his own computer. This policy explains what Google user data it accesses and how that data is handled.
What Jarvis accesses
- Gmail: reads message headers and content to show and summarize the inbox, and creates drafts or sends messages only when the owner asks.
- Google Calendar: reads events to show the schedule and class countdown, and creates events the owner asks for.
- Google Drive and Google Docs: lists files and folders, opens documents, and edits or creates documents the owner asks for.
- Basic account information: the signed-in email address, used to pick the right account.
How the data is used
Data is used only to perform the specific requests the owner makes to the assistant and to display results on the owner's own screen. It is not used for advertising, profiling, or any purpose unrelated to those requests.
Where the data is stored
Sign-in tokens are stored in files on the owner's own computer. Jarvis does not run a server or database of its own, and no Google user data is stored on any server operated by the developer.
Sharing and third parties
Jarvis does not sell Google user data and does not share it with third parties. To produce an answer to a request (for example, summarizing an email the owner asked about), the relevant content is sent to the Anthropic API for processing, solely to generate the response to that request.
Google API Services User Data Policy
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.
Retention and deletion
Jarvis keeps no copy of Google data beyond what is held temporarily in the computer's memory while a request is carried out. Access can be revoked at any time at myaccount.google.com/permissions, and deleting the local token files removes Jarvis's saved sign-in.
Contact
Questions about this policy: fritzdesir3@gmail.com