Update data-location to include jurisdiction

simonha9 · simonha9 · commit 20c4cf3d5fc8 · 2025-10-31T12:00:39.000-05:00
diff --git a/src/content/changelog/d1/2025-10-31-d1-jurisdiction.mdx b/src/content/changelog/d1/2025-10-31-d1-jurisdiction.mdx
@@ -0,0 +1,10 @@
+---
+title: D1 now supports jurisdictional restrictions.
+description: D1 now has the capability to set jurisdictional restrictions on database creation.  This restricts the location to run and store the d1 database.
+products:
+  - d1
+  - workers
+date: 2025-09-11
+---
+
+You can now set a [jurisdiction](/d1/configuration/data-location/) when creating a D1 database. Note that if a jurisdiction restriction and a location hint are both provided, the jurisdiction takes precedence and the location hint is ignored.
diff --git a/src/content/docs/d1/configuration/data-location.mdx b/src/content/docs/d1/configuration/data-location.mdx
@@ -13,6 +13,62 @@ Learn how the location of data stored in D1 is determined, including where the l
 
 By default, D1 will automatically create your primary database instance in a location close to where you issued the request to create a database. In most cases this allows D1 to choose the optimal location for your database on your behalf.
 
+## Restrict D1 Databases to a jurisdiction
+
+Jurisdictions are used to create D1 databases that only run and store data within a region to comply with local regulations such as the [GDPR](https://gdpr-info.eu/) or [FedRAMP](https://blog.cloudflare.com/cloudflare-achieves-fedramp-authorization/).
+
+Workers may still access the database constrained to a jurisdiction from anywhere in the world. The jurisdiction constraint only controls where the database itself runs and persists data. Consider using [Regional Services](/data-localization/regional-services/) to control the regions from which Cloudflare responds to requests.
+
+### Supported locations
+
+| Parameter | Location                       |
+| --------- | ------------------------------ |
+| eu        | The European Union             |
+| fedramp   | FedRAMP-compliant data centers |
+
+### Set jurisdiction via the Cloudflare dashboard
+
+1. In the Cloudflare dashboard, go to the **D1 SQL Database** page.
+
+   <DashButton url="/?to=/:account/workers/d1" />
+
+2. Select **Create Database**.
+3. Enter a name for the database.
+4. Under **Data location**, select **Specify jurisdiction** and choose a jurisdiction from the list.
+5. Select **Create** to complete the database creation process.
+
+### Using jurisdictions from Workers
+
+The example below shows how to create an R2 bucket in the `eu` jurisdiction using Wrangler
+
+```sh
+npx wrangler@latest d1 create d1-with-jurisdiction --jurisdiction eu
+```
+
+### Using jurisdictions from the REST API
+
+```curl
+curl -X POST "https://api.cloudflare.com/client/v4/accounts/<account_id>/d1/database" \
+     -H "Authorization: Bearer $token" \
+     -H "Content-Type: application/json" \
+     --data '{"name": "db-wth-jurisdiction", "jurisdiction": "eu" }'
+
+```
+
+### Available jurisdictions
+
+The following jurisdictions are supported:
+
+| Jurisdiction | Jurisdiction description |
+| ------------ | ------------------------ |
+| eu           | European Union           |
+| fedramp      | FedRAMP                  |
+
+:::note
+
+Note that jurisdiction restrictions can only be set on database creation. If a jurisdiction and a location hint are both provided, the jurisdiction takes precedence and the location hint is ignored.
+:::
+
 ## Provide a location hint
 
 Location hint is an optional parameter you can provide to indicate your desired geographical location for your primary database instance.
@@ -51,6 +107,7 @@ To provide a location hint when creating a database via the dashboard:
 1. In the Cloudflare dashboard, go to the **D1** page.
 
    <DashButton url="/?to=/:account/workers/d1" />
+
 2. Select **Create database**.
 3. Provide a database name and an optional **Location**.
 4. Select **Create** to create your database.
@@ -78,4 +135,6 @@ With read replication enabled, D1 creates and distributes read-only copies of th
 
 When using D1 read replication, D1 automatically creates a read replica in [every available region](/d1/configuration/data-location#available-location-hints), including the region where the primary database instance is located.
 
-Refer to [D1 read replication](/d1/best-practices/read-replication/) for more information.
+If jurisdictional restrictions are present, replicas are only created within the jurisdiction set on creation.
+
+Refer to [D1 read replication](/d1/best-practices/read-replication/) for more information.
