Privacy Policy.

Jarvis AI Assistant (“the app”, “we”, “us”) is a personal AI assistant that you install and run on your own Windows computer. This policy explains what information the app can access, how it is used, how long it is kept, and the choices you have. It applies to the Jarvis AI Assistant desktop and mobile apps and to this website, jarvis.institute.

Because Jarvis AI Assistant is local-first, most information never leaves your device. Depending on what you choose to use, the app may access the items below. Section 5 covers the account and diagnostic information our server receives.

• Your API keys and credentials. Keys for the LLM providers you choose (e.g. Anthropic, OpenAI, Google, Groq, Ollama) and tokens for services you connect. These are stored on your device, encrypted with Windows DPAPI, and used only to talk to those providers on your behalf.
• Content you give it. The messages, files, and commands you send. These are processed locally and, when you choose a cloud model, sent to that model provider to generate a response.
• Google user data (optional). If you choose to connect your Google account, Jarvis AI Assistant can view and edit your Google Calendar events through the Google Calendar API. This is optional: the app works without it. Section 3 lists the exact permissions and why each one is requested. Google sign-in does not grant any access to your Gmail.
• Your email (optional, separate). If you connect a mailbox, Jarvis AI Assistant reads, searches and sends your mail over IMAP and SMTP using an app password you create and can revoke yourself. This is independent of Google sign-in and works with any mail provider, Gmail included. Section 3 explains why mail is handled this way.

Jarvis AI Assistant connects to your Google account using Google OAuth 2.0. You sign in on Google’s own consent screen, and Jarvis AI Assistant only accesses Google data after you explicitly grant permission there. The app requests only the scopes needed for the features it actually implements:

Google sign-in runs entirely on your PC: Google sends you back to the app on your own machine, and the app exchanges the sign-in code for a token locally. Google user data is processed locally on your own device to fulfil your requests. It is never transmitted to, stored on, or processed by any server we operate.

Your email (optional, and not via Google)

Jarvis AI Assistant can read, search, and send mail over IMAP and SMTP — the standard mail protocols — using an app password you create yourself and can revoke at any time. This is separate from Google sign-in and works with Gmail, Outlook, iCloud, Fastmail and any other IMAP provider. Your mailbox password is stored encrypted on your own computer and is never transmitted to us; the connection is made directly from your machine to your mail provider.

This is a deliberate choice. Every Google permission capable of reading mailbox content is classified by Google as a restricted scope, which obliges the publisher to complete a paid third-party security assessment every year. Jarvis AI Assistant requests no Gmail permission at all. Handling mail over IMAP and SMTP with a credential that belongs to you keeps your Google permissions limited to your calendar — and the mailbox password can be revoked by you at any moment, independently of Google.

Information is used solely to operate the assistant for you:

• To carry out the tasks, questions, and commands you give it.
• To route requests to the model provider you selected and return the result.
• To provide memory and continuity across your own sessions, stored on your device.
• To run your account, check your purchase, and fix errors (see section 5).

We do not build advertising profiles, and we do not use your content to train AI models.

Jarvis AI Assistant talks to one server we operate, the Jarvis account server. It receives only the following:

• Your account. Email address, password hash, display name, timezone, locale, country and city if you provide them, and your consent and marketing preferences.
• Your profile, when you save it. Saving your profile in the app syncs fields such as name, location, role, organisation, team, tech stack, “about you”, interests, goals and preferences to your account.
• Error reports (on by default). Error messages and stack traces, automatically scrubbed of secrets, plus the app version and platform. Also on by default: aggregate counts of AI model errors, and a daily device check-in with your operating system, CPU, RAM and app version.
• Feedback you give. Thumbs up or down on a reply (the reaction only, not the message text), and any support messages you write to us.
• Microsoft Store purchase check. When you sign in, the app sends a Microsoft Store ID key. The server asks Microsoft whether your account owns Jarvis and stores the result, the Microsoft order ID, and the key (encrypted). The key is used only to re-check the purchase, for example after a refund.
• GitHub sign-in. If you sign in with GitHub, the one-time sign-in code passes through our server. Your GitHub token is not stored there.
• Android app. The mobile app sends crash reports through Firebase Crashlytics. This is on by default.

Your chat conversations, memory, files, Google data and email content are not sent to our server. There is no advertising or third-party tracking in the app.

Your conversations, memory, settings, logs and connected-account tokens are stored locally on your device, in the .jarvis folder in your Windows user profile. When you use a cloud LLM provider, your prompt (and any content you include) is sent to that provider under their terms; when you use a local model such as Ollama, the prompt stays on your machine.

Retention. Concretely:

• Google user data is not retained by us at all. Calendar events are fetched from Google when a request needs them, used to answer that request, and never sent to a server we operate.
• Your Google access token is kept on your own device only, encrypted with Windows DPAPI, so you do not have to sign in again on every launch. It is deleted when you disconnect Google in the app or delete the app’s data folder. Uninstalling the app does not delete it.
• Conversations and memory stay on your device until you delete them. They are kept so the assistant can remember context across your own sessions. You can clear them at any time — see section 9.
• Local logs are kept for 30 days.
• Account server data (section 5) is kept while your account exists. See section 9 for what happens when you delete your account.
• Anything you send to a cloud model provider is retained by that provider under their own policy, not ours.

We do not sell your personal information. Data is shared only in these limited cases:

• Model & service providers you choose. When you send a request to a cloud model or a connected service, the necessary content is transmitted to that provider to fulfil it. Their handling of that data is governed by their own privacy policies.
• Microsoft, to verify your Microsoft Store purchase, as described in section 5.
• Legal requirements. If required by law or to protect rights, safety, and security.

Your API keys and integration tokens, including your Google token, are encrypted on your PC with Windows DPAPI. Your conversations, memory, settings and logs are not encrypted at rest: they are stored in your Windows user profile and protected by your Windows account permissions.

In GUARDED privacy mode, credential-like strings such as API keys, passwords and tokens are stripped before a request goes to a cloud AI model. Email addresses and phone numbers are not redacted. A local log records which provider and model were called and how many messages were sent, not their content.

Because most data is local, its security depends on the security of your own computer and your Windows user account — anyone with access to your logged-in machine could reach it. No system is perfectly secure.

Users may disconnect Google access at any time. Here is what each option does:

• Disconnect Google in the app. Use the Google integration’s disconnect action. This deletes the stored token from your device, and the app stops being able to reach your Calendar. It does not revoke the grant at Google — see the next item.
• Revoke access at Google. To withdraw the grant itself, remove Jarvis AI Assistant from your Google Account permissions. This works whether or not the app is installed, and is the definitive way to end access. We recommend doing this as well as disconnecting in the app.
• Disconnect your mailbox. Use the inbox disconnect action to erase the stored mailbox password from your device. You can also revoke the app password directly with your mail provider — for Google, on the App passwords page — which cuts access instantly and affects nothing else you use.
• Clear data in the app. There is no single “delete everything” button. You can delete conversations, reset your memory and profile, and disconnect integrations one by one.
• Delete all local data by closing the app and deleting the %USERPROFILE%\.jarvis folder. This removes your conversations, memory, settings, logs and stored tokens, including the Google token.
• Uninstalling does not remove your data. The .jarvis folder stays behind, as do the jarvis-postgres-data Docker volume (if you used Docker features), any Ollama models you downloaded, and Docker Desktop or Node if setup installed them. Delete the folder as above; in Docker Desktop, delete the jarvis containers and the jarvis-postgres-data volume; and remove models with ollama rm <model> or uninstall Ollama.
• Delete your account. Deleting your account deactivates it and signs you out everywhere. Some records are kept, such as your original email address and error reports. To have the data on our server deleted in full, email [email protected].

If you have a question about deleting data, contact us at [email protected].

jarvis.institute is an informational site. It does not require an account and does not use advertising or cross-site tracking cookies. Any analytics used are limited to understanding aggregate, non-identifying usage of the site.

Jarvis AI Assistant is not directed to children under 13 (or the minimum age in your jurisdiction), and we do not knowingly collect their data.

We may update this policy as the product evolves. Material changes will be reflected here with a new “last updated” date. Continued use after an update means you accept the revised policy.

Questions about this policy or your data? Email [email protected].