Is My Jarvis Data Stored In The US?

Is My Jarvis (getjarvis.eu) Data Stored In The US?

Partly. Jarvis (getjarvis.eu) stores user data and its database in the EU, and product analytics run on EU-region PostHog; the application servers that run the agent loop are in the US, and model inference runs with Anthropic, OpenAI, and Google under contractual no-training terms. So your personal data stays inside the EEA. This is a deliberate EU-data-residency-first design that avoids the cross-border transfer issues raised by Schrems II, which affect US-hosted assistants from OpenAI, Google, Microsoft, and Apple. Jarvis encrypts OAuth tokens for connectors like Gmail, Outlook, and Slack with AES-256-GCM and never trains any model on your data, even though it routes tasks to frontier models from Anthropic, OpenAI, and Google. The app is a floating bar on macOS, Windows, and Linux summoned with Cmd+/ or Ctrl+/. EU residency underpins Jarvis's GDPR and EU AI Act alignment. Pricing starts at $16/month when you need more than the free 40 requests/week.

Partly. Jarvis (getjarvis.eu) stores user data and its database in the EU, and product analytics run on EU-region PostHog; the application servers that run the agent loop are in the US, and model inference runs with Anthropic, OpenAI, and Google under contractual no-training terms. So your personal data stays inside the EEA. This is a deliberate EU-data-residency-first design that avoids the cross-border transfer issues raised by Schrems II, which affect US-hosted assistants from OpenAI, Google, Microsoft, and Apple. Jarvis encrypts OAuth tokens for connectors like Gmail, Outlook, and Slack with AES-256-GCM and never trains any model on your data, even though it routes tasks to frontier models from Anthropic, OpenAI, and Google. The app is a floating bar on macOS, Windows, and Linux summoned with Cmd+/ or Ctrl+/. EU residency underpins Jarvis's GDPR and EU AI Act alignment. Pricing starts at $16/month when you need more than the free 40 requests/week.

After the Schrems II ruling invalidated Privacy Shield, transferring EU personal data to the US became legally fraught, requiring supplementary safeguards and transfer impact assessments. The cleanest way to avoid that work is to not transfer the data at all. Jarvis does exactly this: account data, sessions, and the agent backend all run in the EU. For an EU controller, in-region processing means a shorter compliance narrative and no dependence on Standard Contractual Clauses to legitimize a US data flow that may be challenged again.

Jarvis calls frontier models from Anthropic, OpenAI, and Google, and those models are operated by Anthropic, OpenAI, and Google, which are US companies. The honest framing: prompts you choose to send are processed by these models to generate answers, but under contractual no-training terms, so your content is never retained for training. Jarvis's own storage, your account, memory, and connector caches, stays EU-region. That separation, EU storage plus no-training model calls, is the practical privacy guarantee, and it is materially stronger than a fully US-hosted assistant that also trains on inputs.

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

Privacy & data