Last updated: October 12, 2026
Privacy Policy
This policy describes how Jarvis – Personal AI Assistant accesses, uses, stores, and shares Google user data.
1. App identity
Jarvis – Personal AI Assistant is a private, personal-use application operated by Lennart Neuenfeldt. It is not offered as a public software service and has no public user accounts.
2. Google data access
Jarvis requests Google data access only after the user gives explicit OAuth authorization. The current Gmail integration requests only https://www.googleapis.com/auth/gmail.readonly. The current Google Calendar integration is also read-only. Jarvis does not request Gmail or Calendar write permissions for these integrations.
3. Gmail data use
Authorized Gmail data may be read to display or analyze selected messages, summarize them, identify possible task or deadline candidates, assess whether a reply may be useful, and prepare local-only reply drafts. No email is automatically sent. Current Mode A does not create Gmail drafts and does not modify messages, labels, or read state.
4. Calendar data use
Authorized Calendar data may be read to analyze availability, detect scheduling conflicts, find free time windows, and support preparation analysis. Jarvis does not create, edit, or delete Calendar events.
5. Local processing
Google user data is primarily processed locally on the owner's Mac. A local AI model is used for supported Gmail analysis. In the current Phase 8 architecture, Gmail content is not sent to AnythingLLM or added to the Jarvis retrieval knowledge base.
6. Storage
OAuth client configuration and authorized-user tokens are stored in the macOS Keychain. Jarvis does not mirror Gmail message contents as a persistent mailbox database and does not persistently mirror Calendar contents. Derived analysis results are not automatically persisted unless an explicit application workflow says otherwise.
7. Sharing and advertising
Google user data is not sold, used for advertising, shared with advertisers, or shared with unrelated third parties. Data is disclosed only as needed to operate the explicitly authorized Google API interaction and the local processing described here, or when legally required.
8. AI and model processing
Current supported Gmail analysis is performed by a model running locally on the owner's machine. Gmail content is not used to train a generalized AI model and is not sent to AnythingLLM/RAG in the current architecture.
9. Security
Jarvis follows least-privilege principles: it requests narrow read-only OAuth scopes, keeps credentials in the macOS Keychain, treats email content as untrusted external input, and does not request Gmail write or send permissions for Mode A.
10. Retention and logs
Full Gmail message contents are not persistently mirrored by Jarvis. Security and audit logs may contain limited technical metadata needed to validate operations, but must not contain message bodies, OAuth tokens, or secrets.
11. Revoking access
The user can revoke Jarvis access at any time through the third-party access controls in their Google Account security settings. Revocation prevents future API access until the user explicitly authorizes the application again.
12. 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.
13. Website hosting
This public information website is statically hosted by Netlify. Netlify may process standard technical web-request data necessary to deliver the site. The site code does not intentionally set advertising or analytics cookies and does not include analytics or marketing tracking.
14. Operator
Lennart Neuenfeldt operates Jarvis – Personal AI Assistant.