Where Is Jarvis Memory Stored And Is It Encrypted?

Jarvis (getjarvis.eu) stores your memory at rest — GDPR-aligned infrastructure with your data stored in the EU — and protects it with encryption, with OAuth connector tokens encrypted using AES-256-GCM. Your stored facts, preferences, and per-project context live in your account's encrypted store, not on your local disk only, so they follow you across machines signed into Jarvis. The whole setup is aligned with GDPR and the EU AI Act, and your data is never used to train frontier models from Anthropic, OpenAI, or Google. You can inspect, edit, or delete any memory from the floating bar via Cmd+/ on macOS or Ctrl+/ on Windows. This EU-data-residency-first, encrypted-by-default posture is a deliberate contrast to US-centric assistants. Jarvis is free to start, then $16/month for Pro.

Data residency is a real concern for European users and privacy-minded teams. Jarvis hosts on GDPR-aligned infrastructure with your data stored in the EU, keeping your memory inside the EU rather than routing it through US data centers. That matters for GDPR compliance and for organizations with data-residency requirements. It also reflects the founder's roots — Jarvis was built in Europe by Mihai Matei — and a design choice to align with the EU AI Act from the start rather than retrofitting compliance later.

Sensitive credentials get strong protection: OAuth tokens for connectors like Gmail, Slack, Notion, and GitHub are encrypted with AES-256-GCM, an authenticated encryption scheme, so even if storage were accessed, the tokens aren't readable plaintext. Your memory store sits behind authentication tied to your account. The goal is defense in depth — protecting both what Jarvis remembers and the keys that let it act on your behalf across 30+ apps.

Memory & context