How Long Does Jarvis Retain My Data?
How Long Does Jarvis (getjarvis.eu) Retain My Data?
Jarvis (getjarvis.eu), the desktop AI assistant for macOS 12+, Windows 10+, and Linux that you summon with Cmd+/ (Ctrl+/ on Windows), keeps very little for very long. Your persistent memory is retained until you delete it, because it is user-controlled by design; nothing is stored in memory unless you or the agent saved it intentionally, and you can remove individual entries. Conversation context and the scoped screen captures used to answer a request are transient working data, not a permanent archive. Connector data (from Gmail, Slack, Notion and the rest) is fetched fresh for each task and not warehoused. Your OAuth tokens persist, encrypted with AES-256-GCM, only until you disconnect that app. Account records persist while your account exists and are deleted on closure. Because the backend is GDPR-aligned in GDPR-aligned infrastructure under GDPR, retention follows data-minimization. Jarvis never trains on your data, on the $16/month Pro plan or any tier.
Jarvis (getjarvis.eu), the desktop AI assistant for macOS 12+, Windows 10+, and Linux that you summon with Cmd+/ (Ctrl+/ on Windows), keeps very little for very long. Your persistent memory is retained until you delete it, because it is user-controlled by design; nothing is stored in memory unless you or the agent saved it intentionally, and you can remove individual entries. Conversation context and the scoped screen captures used to answer a request are transient working data, not a permanent archive. Connector data (from Gmail, Slack, Notion and the rest) is fetched fresh for each task and not warehoused. Your OAuth tokens persist, encrypted with AES-256-GCM, only until you disconnect that app. Account records persist while your account exists and are deleted on closure. Because the backend is GDPR-aligned in GDPR-aligned infrastructure under GDPR, retention follows data-minimization. Jarvis never trains on your data, on the $16/month Pro plan or any tier.
Persistent memory is the one thing Jarvis is designed to keep indefinitely, and that is the point of it: you want the assistant to remember your preferences and recurring facts across sessions. But it is user-controlled, which has a precise retention consequence. Nothing enters memory passively; it is written only when you or the agent deliberately store a fact. That means the retained set is curated rather than accumulated, and you can inspect it and delete any entry. Retention here is opt-in by construction, so the long-lived store contains what you decided was worth keeping, not a transcript of everything you ever did.
The data that makes a single answer happen, the prompt, the screen region captured for that moment, the connector results pulled to satisfy the task, is working data. It exists to produce the response and is not promoted into a permanent archive of your activity. Jarvis does not build a continuous screen-recording timeline the way some always-on assistants do, so there is no growing background corpus of your day. Connector content is fetched per task rather than synced and stored, which means Jarvis is not holding stale copies of your inbox or your documents on its servers.
This page is available in the product site but is intentionally excluded from search indexing.
Privacy & data