Skip to main content

Legal · Data residency

Where your data lives

AgentHub offers three regions on day one: United States, European Union, and United Kingdom. You pick a region when you create your Workspace, and your data stays there. This page explains what each one means in practice.

Last reviewed: May 16, 2026

How regions work

The region you choose is the region where your Workspace data is stored. Inference, email, retrieval, and audit logs all stay within that region as a default. The only data that ever crosses a region boundary is operational telemetry that is stripped of Customer Content (latency numbers, error rates, queue depth) and your billing record, which is held with a global card-acceptance vendor.

You can change your region only by creating a fresh Workspace in the new region; we do not silently migrate data between regions because the legal basis for the transfer is a customer decision, not ours.

Available regions

United States

US

Workspace data is stored and processed in the United States.

Primary database
US-East (Virginia) primary, US-West (Oregon) standby.
Inference
Inference calls are routed to US-region endpoints of model providers.
Email
Outbound email is sent from US infrastructure.
Knowledge search
Knowledge-search indexes are kept in the United States.

Default region for new accounts created from a US billing address. Subject to US law including the CLOUD Act; we contest disproportionate or improper requests.

European Union

EU

Workspace data is stored and processed in the European Union (Frankfurt) and stays in-region.

Primary database
EU-Central (Frankfurt) primary, EU-West (Dublin) standby.
Inference
Inference calls are routed to EU-region endpoints of model providers.
Email
Outbound email is sent from EU infrastructure.
Knowledge search
Knowledge-search indexes are kept in the European Union.

Default for accounts billed from the EU. Where a model provider has no EU endpoint, the customer is asked to either pick a different model or accept a Standard-Contractual-Clauses-backed transfer to a US region.

United Kingdom

UK

Workspace data is stored and processed in the United Kingdom (London) and stays in-region.

Primary database
UK-South (London) primary, UK-West (Cardiff) standby.
Inference
Inference calls are routed to UK-region endpoints where the provider offers them, otherwise to EU.
Email
Outbound email is sent from UK infrastructure.
Knowledge search
Knowledge-search indexes are kept in the United Kingdom.

Default for accounts billed from the UK. The UK GDPR governs processing; transfers outside the UK use the UK International Data Transfer Addendum.

What stays in your region

  • Customer Content

    Documents, knowledge bases, files, conversations, run inputs and outputs that you upload or that your agents create.

    Stored only in the region you pick.

  • Account and usage

    Account email, billing contact, member list, run counts, audit log entries.

    Stored in the region you pick. Replicated to a standby in the same region.

  • Billing data

    Invoice line items, plan, currency. Card data is tokenized by our payments processor and never reaches our servers.

    Stored with our card-acceptance and payouts vendors. See the subprocessor page for the full list.

  • Operational telemetry

    Latency, error counts, queue depth, anonymized request shapes.

    Aggregated and stored centrally so we can run the platform; never includes raw Customer Content.

Why we offer all three on day one

Buyers in regulated industries cannot use a platform that only has a US region. EU data-protection authorities have made clear that simple Standard Contractual Clauses do not cover every transfer. UK customers have a separate transfer regime under the UK GDPR and the UK Information Commissioner. Offering local storage in each jurisdiction is the simplest way to remove the transfer question entirely.

Sub-processors and transfers

Some vendors have a global stack and may store routing-only metadata across regions. We list every vendor on /legal/subprocessors with their region. Cross-region transfers are governed by the Standard Contractual Clauses (EU) and the UK Addendum (UK), as set out in the Data Processing Addendum.

Contact

Need a residency commitment in a specific region for an enterprise contract? Email legal@mvsagents.ai.

AgentHub is operated by MVS Holdings. Last reviewed: May 16, 2026.

AgentHub

Trusted AI agents for operational workflows. Approval-gated, evidence-cited, audit-ready.

Product

  • Marketplace
  • Trust badges
  • Pricing
  • Dashboard

Compliance

  • Security
  • Privacy
  • Terms
  • Acceptable use
  • Subprocessors
  • DPA
  • Data residency

Company

  • Changelog
  • Roadmap
  • Status
  • Sign in
  • Get started
© 2026 MVS Cloud. AgentHub is operated by MVS Holdings.
AgentHubby MVS
MarketplaceTrustPricing
Sign inStart free