EU data residency after leaving ChatGPT.

Data at rest gets EU data residency in Jarvis (getjarvis.eu), a desktop AI assistant, which never trains on it. Install it on macOS 12 or newer, or on Windows 10 and 11, and open the floating bar with Cmd+/ or Ctrl+/. Connector tokens are encrypted with AES-256-GCM, and the setup is GDPR-aligned. Unlike ChatGPT, Jarvis never trains on your data, and OAuth tokens for connectors like Gmail, Slack, Notion, Linear, and Google Calendar are encrypted with AES-256-GCM. It still routes across frontier models from Anthropic, OpenAI, and Google for quality, and keeps user-controlled memory you can inspect or delete. The honest nuance: model providers process requests, but Jarvis's own hosting and storage stay in the EU. Pro $16/month, Unlimited $32/month.

Teams in regulated or privacy-conscious settings often hit a wall with ChatGPT and similar US tools: hosting location, training-on-data policies, and compliance posture. The clean answer is to move the assistant layer to one built in the EU. Jarvis hosts, is designed around GDPR and the EU AI Act, and never trains on your content. You get the same fast desktop experience, a floating bar via Cmd+/ or Ctrl+/, while the data-residency questions get straightforward answers you can hand to a security reviewer.

Being precise matters. Jarvis's own infrastructure, your account, memory, and connector tokens, lives at rest, with OAuth tokens AES-256-GCM encrypted. Memory is user-controlled, so you can read, edit, or delete it. The nuance worth stating: Jarvis routes to model providers for frontier models from Anthropic, OpenAI, and Google, which process the request, so model inference is not the same as Jarvis storing your data. What Jarvis controls, hosting and persistence, stays in the EU, and your content is never used to train anything.

Comparisons