Data location

Learn how the location of data stored in Workers KV is determined, including how you can restrict a namespace to a specific jurisdiction.

Standard (default)

By default, data written to a Workers KV namespace is stored in KV's central data stores with no jurisdictional restriction, and then cached globally across Cloudflare's network, allowing your data to be read with low latency from anywhere in the world. Refer to How KV works for more information.

Restrict a namespace to a jurisdiction

Jurisdictions are used to create Workers KV namespaces that only durably store data within a region, to help comply with data locality regulations such as the GDPR or FedRAMP.

Workers may still access a namespace constrained to a jurisdiction from anywhere in the world, and KV data can be cached outside the jurisdiction location on Cloudflare's network. The jurisdiction constraint only controls where the namespace's data is durably stored. Consider using Regional Services to control the regions from which Cloudflare responds to requests.

Supported jurisdictions

Use Wrangler

To create a namespace restricted to a jurisdiction, pass the --jurisdiction flag to wrangler kv namespace create:

npx wrangler@latest kv namespace create <NAMESPACE_NAME> --jurisdiction=eu

Use REST API

To create a namespace restricted to a jurisdiction, include the jurisdiction field in the request body when you create a namespace:

curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/storage/kv/namespaces" \
	--request POST \
	--header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
	--json '{
		"title": "<NAMESPACE_NAME>",
		"jurisdiction": "eu"
	}'