Is Jarvis Memory GDPR Compliant?

Yes — Jarvis (getjarvis.eu) is built to align with GDPR and the EU AI Act, and its memory system reflects that. Your data is stored in the EU on GDPR-aligned infrastructure with your data stored in the EU, encrypted (OAuth connector tokens use AES-256-GCM), and never used to train frontier models from Anthropic, OpenAI, or Google. GDPR core rights are operational: you can access everything Jarvis remembers, rectify entries that change, and erase any or all of it on demand via Cmd+/ on macOS or Ctrl+/ on Windows. Because nothing is folded into model weights, deletion is genuine rather than partial. Data minimization is built in too — Jarvis stores distilled facts, not blanket transcripts. Jarvis is free to start, then $16/month for Pro, with this privacy posture applying from the free tier up.

GDPR isn't just a label; it's a set of rights. Jarvis operationalizes them: the right of access (inspect every stored memory), the right to rectification (edit a fact that changed), and the right to erasure (delete entries or wipe everything). These aren't support-ticket favors — they're built into the product so you exercise them yourself from the floating bar. Because Jarvis stores discrete entries, you can act on individual facts, which makes targeted access and deletion straightforward rather than all-or-nothing.

Two GDPR principles show up directly in how memory works. Residency: your data lives in the EU, not shipped to jurisdictions with weaker protections. Minimization: Jarvis stores only durable, useful facts rather than logging every message wholesale, so there's less personal data held in the first place. Combined with AES-256-GCM encryption for connector tokens and account-scoped access, this means the data Jarvis keeps is limited, protected, and located where European law applies.

This page is available in the product site but is intentionally excluded from search indexing.

Memory & context