Data residency: a census of 149 listings

Data is transferred to and processed in the United States with a DPA offered to EU controllers, but no choice of region or EU-resident hosting option is published.

Checked 2026-09-23

Hosting spans AWS regions in the US, Canada, Ireland and Germany, but European storage is an option you must enrol in rather than a default, and some subprocessors are US-only.

Checked 2026-10-11

Residency is wherever your own machine is: everything runs locally with no hosted service, and state is written to platform directories on that machine.

Checked 2026-10-10

Delivery is from Montreal, Quebec for Canadian and North American clients, and deployments can be client-owned; no hosting region or residency guarantee is published.

Residency is the buyer's choice because the code runs in your own process or edge platform, but the vendor makes no jurisdiction commitment of its own anywhere on the site.

Checked 2026-10-11

Residency is yours to choose: sessions, memory and traces live in your own database in your own VPC, and the browser reads it directly.

Checked 2026-10-11

Everyone lands in one region by default, Microsoft Azure US East 2; residency elsewhere exists only as a private or public cloud provisioning discussed at Enterprise, where the plan bullet itself hedges it.

Checked 2026-09-23

The privacy policy places processing in the United States with cross-border safeguards for EU transfers, and offers no choice of hosting region on any tier.

Checked 2026-10-03

Your code stays on your own machine because the tool edits local files, but the vendor's own services and any analytics it receives are hosted in the United States with no regional choice offered.

Checked 2026-09-30

The hosted default is the United States under the EU-US, UK and Swiss-US Data Privacy Framework, with no published region menu; choosing a jurisdiction means taking the VPC, hybrid or on-premises deployment instead.

Checked 2026-09-03

The vendor names the United States as the storage jurisdiction and tells EEA, UK and Swiss users their data may be transferred there; no EU or regional hosting option is offered as an alternative.

Checked 2026-09-10

Enterprise deployments choose a global, US or EU endpoint to meet residency rules, with image generation only on global; consumer plans publish no jurisdiction choice at all.

Checked 2026-09-10

Primary infrastructure sits in the European Union, but transfers to non-adequate countries and a US corporate entity are covered by SCCs rather than avoided, and no region is selectable by the buyer.

Checked 2026-09-26

Arsum LLC is a United States entity in Wyoming and reserves the right to process data outside the country of collection, with no jurisdiction choice offered to buyers.

Checked 2026-10-03

Jurisdiction is disclosed and it is the United States for everyone; EEA, UK and Swiss transfers ride on Standard Contractual Clauses, and no EU or other regional hosting option is published on any tier.

Checked 2026-09-10

You pick the Azure region holding your data from four options, but note that account configuration, billing, call history and AI Agents are centrally managed in Frankfurt for every region.

Checked 2026-09-24

Data residency options and multi-region compute are Enterprise-only; Business gets no residency choice.

Checked 2026-09-02

Processing is in the United States and wherever subprocessors operate, with EU SCCs and the UK Addendum incorporated for transfers; no region selection or EU-only hosting is offered.

Checked 2026-09-11

The company is registered in Florida and serves US and Australian clients on Google Cloud, with cross-border transfers handled under Australian privacy principles; no per-client region choice is offered.

Checked 2026-09-11

US, EU and APAC regions with per-call pinning are offered, but the plan table restricts contractual data residency to Enterprise.

Checked 2026-09-11

Processing is US-centred with no published choice of region; only the Enterprise BYOK deployment puts the data in a tenant you control.

Checked 2026-09-11

Default hosting is AWS in the United States; European Data under the DPA is processed within Europe, but defining custom retention and residency policies is an Enterprise-only row and no region picker is documented.

Checked 2026-09-02

Region is chosen per session from us-west-2, us-east-1, eu-central-1 and ap-southeast-1, and residency is configurable for enterprise.

Checked 2026-09-02

By default api.cartesia.ai routes to the nearest endpoint; pinned regional deployments (US, EU, UK, India, Australia) are Enterprise-only.

Checked 2026-09-02

inference_geo pins inference to US infrastructure at a 1.1x token price, and workspace storage geo is currently US-only; no other jurisdiction is offered.

Checked 2026-09-02

US-only inference is selectable on the Claude API and Claude Platform on AWS at a 1.1x rate; workspace storage geo is US only, and Bedrock or Google Cloud regions follow the endpoint.

Checked 2026-09-02

You control where processing happens - VPC, on-premises or air-gapped, with inference to your own regional endpoints - but no jurisdiction is named for Cline's hosted account, billing and config service.

Checked 2026-09-12

An EU SaaS deployment is listed only under Enterprise; the trust centre lists US subprocessors and the CLI defaults to a US region, so ordinary plans are US-hosted.

Checked 2026-09-15

Retention and residency controls are Enterprise-only and apply only to eligible content and supported workloads.

Checked 2026-09-02

The company operates from the United States and each sub-processor's region is 'configured' and may include the US, with SCCs relied on for EEA transfers; customers are not offered a residency choice.

Checked 2026-09-28

No region choice is offered: every listed sub-processor sits in the United States and the DPA reserves global transfer, with EU and UK transfers covered by Standard Contractual Clauses.

Checked 2026-09-12

Hosting is disclosed as US AWS and GCP data centres, while the agreement has customers consent to processing in North America, the EEA, UK, India and Brazil; no customer-selectable region is offered.

Checked 2026-09-13

Enterprise buyers can keep execution in their own VPC or infrastructure, but no region menu is published for the managed cloud and the trust centre lists AWS in the US as cloud subprocessor.

Checked 2026-09-13

US-only residency for Enterprise teams, enabled by the account team, restricted to eligible model families and carrying a 10% model-price uplift; EU/EEA and APAC are not yet available.

Checked 2026-09-02

Default processing is US-hosted on Google Cloud; EU-only residency inside EEA infrastructure is available on request.

Checked 2026-09-02

EU and AU endpoints both serve the agent WebSocket, and Deepgram runs listen and speak in-region; managed LLM traffic is routed in-region only for OpenAI and Google in the EU, and on the AU endpoint the think step is processed outside Australia. Dedicated adds a customer-chosen AWS region.

Checked 2026-09-02

The AWS region holding a dedicated tenant is not published; the vendor confirms it on request.

Checked 2026-09-02

No region choice is published for the commercial service, which runs in Cognition's AWS environment; dedicated Enterprise deployments keep data in the customer's tenant and the federal deployment runs on AWS GovCloud.

Checked 2026-09-03

Cloud data may be processed in any country where the vendor or its providers operate; region confinement requires Enterprise VPC, dedicated or air-gapped deployment.

Checked 2026-09-02

Data can be hosted in either the United States or the European Union, and the comparison table shows US/EU residency on both Business and Enterprise with single-tenant reserved for Enterprise.

Checked 2026-10-01

US by default; EU, India and Singapore exist as separate Enterprise workspaces with their own accounts, API hosts and reduced model choice, and processing may still leave the region.

Checked 2026-09-02

Jurisdiction is disclosed and it is the United States only: every one of the fifteen listed subprocessors is US-based; no EU or UK region is offered, with transfers handled contractually by SCCs.

Checked 2026-09-14

Jurisdiction is known but not selectable: every device and volume sits on one server in Finland, with no published alternative region on any tier.

Checked 2026-10-09

The holding jurisdiction is disclosed rather than chosen: a New York LLC, DigitalOcean hosting, Indian governing law, and an explicit warning that data may move outside your own jurisdiction.

Checked 2026-10-03

Data residency and customer-managed encryption keys are Enterprise-only; hybrid and airgapped deployments keep all runtime data in your network.

Checked 2026-09-02

Three hosting regions are offered and chosen to match your residency requirement — United States, European Union or Australia — with redundancy inside the region you pick.

Checked 2026-09-18

The vendor states storage is in the United States and offers no published region choice, warning European users their data leaves their home country.

Checked 2026-09-24

Jurisdiction is stated plainly and is singular: every server sits in the United States, with standard contractual clauses covering cross-border transfers. No EU or other regional hosting option is offered.

Checked 2026-09-14

Everyone on the self-serve path is hosted in the United States; choosing EU or APAC residency, or a dedicated VPC, requires an Enterprise Order Form.

Checked 2026-09-15

US by default. Enterprise Cloud with data residency pins code and data to the EU, Australia, US or Japan on a GHE.com subdomain, and some Copilot features are unavailable there.

Checked 2026-09-02

Regional residency on Glean-hosted single tenants; Customer Hosted keeps data inside your own AWS or GCP account, with no GovCloud regions.

Checked 2026-09-02

A US (Delaware) company that explicitly processes data wherever its parties are located and may move it across borders; no region selection or residency guarantee is offered to the customer.

Checked 2026-10-05

Jurisdiction is whatever you choose, because you host the container: the vendor documents running it disconnected from Google Cloud entirely, and cloud deploys take an explicit region.

Checked 2026-09-15

Sessions, logs and secrets stay on the machine you run goose on, so residency is yours to choose, but the vendor names no jurisdiction and prompts leave for whichever provider you configure.

Checked 2026-09-16

Residency is wherever you deploy, since the vendor stores nothing; the jurisdictions that matter are your host's and your chosen providers'.

Checked 2026-09-16

Region choice comes with the optional Enterprise VPC deployment; on managed SaaS the vendor names no region options and routes open models through US-based providers.

Checked 2026-09-30

Nothing has to leave the machine, which sidesteps the question for local use, but anything synced is processed in the United States with no region choice offered short of the Enterprise on-premises option.

Checked 2026-09-07

Region and jurisdiction are a buyer choice only on the private deployment, which runs in your own VPC or data centre; for the shared SaaS the vendor names no hosting region.

Checked 2026-09-24

The database region is named (Neon Postgres in Singapore, with analytics in an EU region), but hosting regions are unstated and a buyer cannot choose where data sits.

Checked 2026-09-14

Residency is wherever you run the server: sessions and project state are written next to your code, credentials sit in an owner-only file in your home directory, and the server binds to localhost unless you open it.

Checked 2026-09-17

The jurisdiction is disclosed and singular: everything is stored and processed in the United States, with no EU or other region offered, though a DPA with standard contractual clauses is available for transfers.

Checked 2026-09-17

No hosting region or jurisdiction is named for the standard cloud service; the only published control is the enterprise deployment choice, which lets an organisation keep it in-house.

Checked 2026-09-18

The vendor is a French company marketing European hosting, but its own sub-processor list puts the database at Supabase on Singapore / AWS EU and telephony with Twilio in the United States under Standard Contractual Clauses, so data does leave the EU.

Checked 2026-09-26

EU residency is an Enterprise-scoped contractual configuration, not a switch, and depends on the providers chosen.

Checked 2026-09-02

Cloud customers pick a US or EU region, hybrid keeps the data plane in your own VPC, and a self-hosted install keeps everything inside your infrastructure.

Checked 2026-09-18

Residency follows your deployment choice rather than a vendor commitment: flows and chat history live in the database of the server you run, and the vendor publishes no jurisdiction guarantee.

Checked 2026-09-25

US or EU choice inside LangChain's cloud from Plus upward; Enterprise adds hybrid and self-hosted with the data plane in your own VPC. The Developer column reads N/A.

Checked 2026-09-02

The operator is a French SAS under GDPR and the CNIL, but the vendor explicitly warns that processing may leave the EEA for the United States and offers no region choice.

Checked 2026-09-18

European customer data is kept inside the EU, and the vendor says it runs every component itself rather than on shared third-party infrastructure, with residency options offered to enterprises.

Checked 2026-09-09

You choose the machine, local or your own App Server host, but no Letta Cloud region or jurisdiction is published.

Checked 2026-09-02

The vendor says residency requirements are supported but names no region, jurisdiction or hosting provider anywhere on the site or in the docs, and offers no self-hosted alternative.

Checked 2026-09-02

US, EU and India, configurable per project, though the region pinning row on the plan matrix is No for Build and Ship, Yes from Scale. Single-tenant deployments are not offered.

Checked 2026-09-02

Choose North America (us-east-1) or Europe (eu-central-1); uploaded data stays in its region, and regions cannot be migrated or linked.

Checked 2026-09-02

Residency follows the deployment model rather than a region picker: LuMay's own Azure tenancy for SaaS, your Azure or AWS subscription for BYOC, your VPC, or your data centre.

Checked 2026-09-09

Storage locations are disclosed as the US and Singapore with SCCs covering transfers, and the company is headquartered in Singapore, but no page read offers a customer-selectable region.

Checked 2026-09-19

Self-hosted Enterprise keeps traces, prompts and outputs inside your own VPC; for the hosted platform the vendor publishes no region or jurisdiction.

Checked 2026-09-02

Because you host it, residency follows your deployment and your chosen providers; Microsoft explicitly makes keeping data inside your compliance and geographic boundaries your responsibility rather than guaranteeing a region.

Checked 2026-09-19

The trust centre names United States processing for its cloud and inference subprocessors, with CDN processing following the customer; no choice of region is offered.

Checked 2026-09-20

The operating entity and governing law are Hong Kong, and the policy reserves the right to move data to affiliates inside or outside Hong Kong; no region choice or named hosting jurisdiction is offered to the buyer.

Checked 2026-10-03

The operator is Norwegian and data stays within a named set of regions, but processing may occur in the US or elsewhere and the buyer cannot pin a jurisdiction.

Checked 2026-10-09

Seven named AWS regions including EU, UK, Japan, Canada, Australia and US GovCloud, with per-data-centre API hosts that confirm the separation.

Checked 2026-09-20

n8n Cloud holds data in the EU, in Frankfurt, with no alternative region published; self-hosting puts it in whichever jurisdiction you deploy to.

Checked 2026-09-02

Resume and document files sit in AWS eu-central-1, but AI, analytics and payment providers are US-based, and the buyer cannot choose a region.

Checked 2026-09-29

Work sits on the buyer's own machine, while the account and website data the vendor holds is processed in the United States with no region choice offered.

Checked 2026-10-08

The firm is Pakistan-based and its policy is governed by Pakistani law with cross-border transfers only promised to be handled securely; no region choice or named hosting jurisdiction is offered.

Checked 2026-09-26

The vendor is a US company that processes data in the United States under California law; no EU, UK or India region choice is offered anywhere, despite INR billing.

Checked 2026-09-09

/v1/realtime is listed for regional storage in all ten published regions and for regional processing in the United States and Europe, but residency is a sales-approved project option and residency endpoints carry a 10% price uplift for models released on or after March 5, 2026.

Checked 2026-09-02

You choose the jurisdiction because you choose the host: state, sessions and memory live on the gateway machine you run, whether that is a laptop, a tailnet box or your own server.

Checked 2026-09-21

Zen inference is stated to be US-hosted only; for other providers residency is whatever your own provider or internal gateway gives you.

Checked 2026-09-21

Enterprise puts code and conversations in your own infrastructure, but no region or jurisdiction is published for the hosted cloud tiers.

Checked 2026-09-21

The jurisdiction is stated as AWS in North America, but no region or residency choice is offered, and enterprise data-retention configurability is contract-gated.

Checked 2026-09-02

Processing is stated to take place inside the European Economic Area, though no specific country, region or sub-processor list is published.

Checked 2026-10-03

Enterprise workspaces are pinned to a US, UK or EU region with matching API and MCP hosts; self-serve accounts live in the shared Studio region.

Checked 2026-09-02

A single jurisdiction is published and no region choice is offered: the client platform sits on Google Cloud in the United States, with daily backups for 30 days and seven-day point-in-time recovery.

Checked 2026-10-06

The library holds nothing, so residency is yours. If you send telemetry to Logfire, you choose a US or EU region at signup; regions are strictly separated and migration between them is not available.

Checked 2026-09-02

The jurisdiction is stated plainly and is singular: all customer data sits in AWS US-East in Northern Virginia, and the vendor says it offers no EU storage option, so EU-only residency is not available.

Checked 2026-09-22

Three regions are offered and chosen at signup - N. Virginia, London or Sydney - but the vendor warns the choice is fixed once the organisation exists.

Checked 2026-09-22

Data sits in US Google Cloud by default with an opt-in India region; EU hosting of published apps requires an Enterprise sales request.

Checked 2026-09-22

Processing is in the United States on AWS with SCCs for EU transfers; the vendor states plainly that it runs no services inside the European Union, so EU-resident hosting is not on offer.

Checked 2026-09-23

Transfers are covered by SCCs and the UK Addendum with named governing jurisdictions, but no region choice or hosting location is offered or published.

Checked 2026-10-11

The jurisdiction is clear: a Rotterdam company, Dutch law, Dutch arbitration. No hosting region, subprocessor list or residency choice for recordings and transcripts is published anywhere.

Checked 2026-09-09

In-region and in-VPC options are offered to enterprises with residency needs, and the DPA commits to the EU Standard Contractual Clauses; no region list or default jurisdiction is published, and every AI and cloud subprocessor on the list is US-based.

Checked 2026-09-03

The legal entity and data protection regime are Sri Lankan despite the Canadian desk, and the vendor concedes its service providers may process the data in further countries it does not name.

Checked 2026-09-28

Region is selectable on Hyperforce, with in-country storage conditional on the service being available in that country; strict EU storage and processing with in-region support is the paid Hyperforce EU OZ.

Checked 2026-09-03

The operator is in France with an EU analytics region, but some providers process outside the EEA under transfer mechanisms and no region choice is offered.

Checked 2026-09-25

The vendor names exactly one jurisdiction, the United States, and requires non-US users to consent to transfer there; no regional hosting choice or EU option is offered.

Checked 2026-09-25

Infrastructure is US-only with SCC-based transfers for EU users, and the only residency control is an EU-sensitive flag that changes AI routing rather than where data is stored.

Checked 2026-10-03

Regional hosting localization is offered in the US, EU, Southeast Asia, Japan and Australia, but some AI subprocessors are US-only or global.

Checked 2026-09-26

United States only on the hosted service, in AWS us-east-1. No EU region is offered, so self-hosting is the alternative.

Checked 2026-09-03

Processing is stated to sit on EU infrastructure operated by sipgate in Germany, positioned explicitly as the alternative to US-hosted voice AI providers.

Checked 2026-09-26

Processing is disclosed but not selectable: hosting runs on Railway and the policy reserves United States or other provider locations, with no region choice offered to a buyer.

Checked 2026-10-03

United States only, stated flatly, with AWS and Supabase named as the storage providers and CCPA plus Illinois BIPA as the governing regimes.

Checked 2026-09-03

EU only for production data, application, database, inference and backups, with the single stated exception of unattributed web-search queries sent to US providers.

Checked 2026-09-15

Residency is solved by moving the software, not by picking a region: on-premise and VPC deployments are offered, while no region list is published for the hosted cloud.

Checked 2026-09-09

Choose a US or EU cluster keeping storage and compute in one region; the legacy Global cluster stores in the EU. Choice is permanent.

Checked 2026-09-03

Cloud hosting sits in Switzerland for Swiss customers and the EU for everyone else, with AI inference kept inside the EU/EEA; self-hosters choose their own locations.

Checked 2026-10-03

The controller is a Polish sole trader operating under GDPR/RODO with Polish governing law, but no hosting region, data centre or sub-processor location is published anywhere.

Checked 2026-09-12

You select the cloud region that stores your data and Enterprise adds region pinning, yet every named telephony, speech and LLM sub-processor processes in the United States, with EU transfers covered by standard contractual clauses.

Checked 2026-09-16

Storage at rest is a hard control across US, EU (Germany), APAC (Australia) and UAE, changeable only once. Live processing location is steered by anchorsite but explicitly not guaranteed.

Checked 2026-09-09

The privacy policy allows cross-border processing with safeguards but names no jurisdiction; the country codes in proxy_config route requests, they do not place data.

Agents is provisioned per tenant and marked available across eleven published regions, with Community and Basic confined to the European Union, and UiPath warns that AI features may transit a nearby region for model availability without storing data there.

Checked 2026-09-03

United States storage, with SCCs for EEA/UK/Swiss transfers; no choice of region is offered.

Checked 2026-09-03

Hosting and every listed subprocessor are United States; no region choice is offered.

Checked 2026-09-03

US is the default region; the EU region is frozen to existing accounts and new EU residency is enterprise-only, so regional control comes from your own buckets and models.

Checked 2026-09-03

No region picker for the managed cloud, and the vendor warns of US-based storage and cross-border transfers; the jurisdiction is yours only if you self-host on your own machine or VM.

Checked 2026-09-27

Storage and processing sit in the United States, Oregon specifically, with non-US customers consenting to the transfer; sub-processors may hold data in their own regions.

Checked 2026-09-22

Nigerian jurisdiction under the NDPA, but voice data may be processed outside Nigeria by AI, cloud and speech sub-processors under NDPC-approved transfer safeguards; no region selection is offered.

Checked 2026-09-03

Ireland-operated with customer-selected regions for database and voice orchestration, but the vendor states plainly that some providers or chosen integrations may still process data outside the EEA under SCCs.

Checked 2026-10-03

The enterprise FAQ claims configurable US, EU and APAC regions, while the architecture section lists only AWS US with GCP EU available.

Checked 2026-09-03

United States only, on Google Cloud. No EU or other region is offered anywhere on the site; Enterprise BYOLLM is the one lever that moves inference into your own cloud account.

Checked 2026-09-03

Your files and commands never leave your machine, but any code pasted into the chat lands in your web AI provider's jurisdiction, not WTAgent's.

Checked 2026-09-21

Zed's websites, software and service are hosted in the United States, with EEA/UK transfers under Standard Contractual Clauses.

Checked 2026-09-03

No hosting region or jurisdiction is named for the managed cloud and no region picker is documented; the published answer to a residency mandate is to run a private deployment yourself.

Checked 2026-09-09

Region choice (US, EEA, UK, Japan, Australia) comes with the Data Center Location feature, free from Suite Professional upward and not on by default.

Checked 2026-09-03

Your code, sessions and credentials never leave the machine, so residency for stored data is yours; in-flight prompts land wherever the chosen provider and region sit, such as a configured AWS region.

Checked 2026-09-28

Residency is handled per build through on-premise or VPC deployment rather than published as a jurisdiction the vendor guarantees; the company itself operates from Houston, Texas.

Checked 2026-09-25