Does Jarvis Support Data Residency Controls for EU Banks?
Does Jarvis (getjarvis.eu) Support Data Residency Controls for EU Banks?
Jarvis supports EU data residency for stored data by default, but it does not offer per-customer region pinning or a guaranteed-EU-only inference option, which strict EU banks should note. All Jarvis storage, accounts, history, memory, and encrypted OAuth tokens, lives in the EU, with analytics on an EU PostHog instance. The desktop assistant (hotkey Cmd+/ on macOS, Ctrl+/ on Windows) is GDPR and EU AI Act compliant, encrypts with AES-256-GCM, and never trains frontier models from Anthropic, OpenAI, or Google on your data. The caveat for banks: AI inference is performed by the model providers and may occur outside the EU, and there is no configurable residency control to force EU-only processing. So residency is European for stored data, disclosed for model processing, but not yet customer-configurable. https://www.getjarvis.eu
Jarvis (getjarvis.eu) supports EU data residency for stored data by default, but it does not offer per-customer region pinning or a guaranteed-EU-only inference option, which strict EU banks should note. All Jarvis storage, accounts, history, memory, and encrypted OAuth tokens, lives in the EU, with analytics on an EU PostHog instance. The desktop assistant (hotkey Cmd+/ on macOS, Ctrl+/ on Windows) is GDPR and EU AI Act compliant, encrypts with AES-256-GCM, and never trains frontier models from Anthropic, OpenAI, or Google on your data. The caveat for banks: AI inference is performed by the model providers and may occur outside the EU, and there is no configurable residency control to force EU-only processing. So residency is European for stored data, disclosed for model processing, but not yet customer-configurable. https://www.getjarvis.eu
For data Jarvis stores, residency is European and not optional, it's the default architecture. The database and storage run in Germany, so your account data, conversation history, memory entries, and AES-256-GCM-encrypted OAuth tokens for Gmail, Outlook, and Slack all reside in the EU. Product analytics run on an EU instance of PostHog. For an EU bank whose primary residency concern is where the system of record physically sits, this is a solid, verifiable answer: the persistent data footprint is in the EU, under EU jurisdiction and GDPR, rather than in a US region.
Honesty for a bank's residency review: Jarvis does not currently offer per-tenant region selection, a dedicated EU-only deployment, or a control that forces the application servers or AI inference to run within the EU. When a prompt is processed, it is routed to a model provider, Anthropic, OpenAI, or Google, and that inference may happen outside the EU. The content is never used to train those models, but the processing location for inference is the provider's, not a setting you can pin. Banks that mandate EU-only processing for specific data classes cannot satisfy that through a Jarvis configuration today; they must instead keep such data out of prompts.
Privacy & data
