Cloudflare Docs
Data Localization Suite
Visit Data Localization Suite on GitHub
Set theme to dark (⇧+D)

Data Localization Suite

The Data Localization Suite (DLS) is a collection of tools that enable customers to choose the location where Cloudflare inspects and stores data, while maintaining the security and performance benefits of our global network.

The Data Localization Suite consists of the following products:

Support by product and region is summarized in the following table:

Region Geo Key Manager Regional Services Customer Metadata Boundary
US
EU
UK 1 Can use EU metadata boundary.
Canada 1
Australia 1
Japan 1
India 1
ISO 27001 Certified European Union 1 Can use EU metadata boundary.
Germany 1 Can use EU metadata boundary.
Singapore 1
South Korea 1

Overview by product-behavior is summarized in the following table. Below you can find the table legend to help you read the table:

✅ Product works with no caveats
🚧 Product can be used with some caveats
✘ Product cannot be used
⚫️ Not applicable

Suite/Category Product Geo Key Manager Regional Services Customer Metadata Boundary
Application Performance Caching/CDN
Cache Reserve ⚫️ 🚧2
DNS ⚫️ ⚫️ 🚧3
Image Resizing 🚧3
Load Balancing 🚧3
Stream Delivery
Tiered Caching 🚧4 🚧4
Waiting Room ⚫️
Zaraz
Email Routing ⚫️ ⚫️
Application Security Advanced Certificate Manager ⚫️ ⚫️ ⚫️
Advanced DDoS Protection 🚧5
API Shield 6
Bot Management 🚧7
DNS Firewall ⚫️ ⚫️ 🚧3
Page Shield
Rate Limiting 🚧3
SSL
Cloudflare for SaaS
Turnstile ⚫️
WAF/L7 Firewall
DMARC Management ⚫️ ⚫️
Developer Platform Cloudflare Images ⚫️
Cloudflare Pages 8
Durable Objects ⚫️ 9 🚧3
R2 ⚫️ 🚧2
Stream ⚫️
Workers (deployed on a Zone) 🚧3
Workers KV ⚫️
Workers.dev
Network Services Argo Smart Routing 10 11
BYOIP ⚫️ ⚫️
Magic Firewall ⚫️ ⚫️ 🚧3
Magic Transit ⚫️ ⚫️ 🚧3
Magic WAN ⚫️ ⚫️ 🚧3
Spectrum 🚧3
Platform Logpull ⚫️ 🚧12
Logpush ⚫️ 🚧13
Zero Trust Access 🚧14 🚧15 🚧16
Area 1 ⚫️ 17 🚧18
Browser Isolation ⚫️ 🚧19
CASB ⚫️ ⚫️
Cloudflare Tunnel ⚫️ 🚧20 ⚫️
DLP ⚫️21 ⚫️21
Gateway 🚧22 🚧23 🚧24
WARP ⚫️ ⚫️ 🚧3

  1. Only supported in Geo Key Manager v2↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  2. You can not yet specify region location for object storage; this is expected in 2023. ↩︎ ↩︎

  3. Logs / Analytics not available outside US region when using Customer Metadata Boundary. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  4. Regular and Custom Tiered Cache works; Smart Tiered Caching not available with Regional Services. ↩︎ ↩︎

  5. Network Analytics (including DoS analytics) will not be sent outside the region. However, these are only viewable today in US region. ↩︎

  6. API shield will not yet work with Customer Metadata Boundary enabled outside of US region. ↩︎

  7. Some advanced Enterprise features, including the Anomaly Detection engine, are not available. ↩︎

  8. Only when using Custom Domain set to a region. ↩︎

  9. Jurisdiction restrictions for Durable Objects↩︎

  10. Argo cannot be used with Regional Services. ↩︎

  11. Argo cannot be used with Customer Metadata Boundary. ↩︎

  12. Logpull not available when using Customer Metadata Boundary outside US region. Logs may be stored and retrieved with Logs Engine which is adding region support in 2023. ↩︎

  13. Logpush available with Customer Metadata Boundary for HTTP requests and Firewall events. Please contact your Customer Success Manager if you need to push another dataset. ↩︎

  14. Access App SSL keys can use Geo Key Manager. Access JWT is not yet localized. ↩︎

  15. Can be localized to US FedRAMP region only. More regions coming in 2023. ↩︎

  16. Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region. ↩︎

  17. US, EU and India regions.
    For Area 1, this is called the Processing & Inspection Boundary↩︎

  18. Email metadata (subject, from:, to:) can only be stored in US.
    Customers have the option to obfuscate metadata from being viewed by Cloudflare.
    Email message bodies are only stored for emails that are marked with a disposition (like MALICIOUS or SPAM). ↩︎

  19. Currently may only be used with US FedRAMP region. ↩︎

  20. Only US FedRAMP region. ↩︎

  21. Uses Gateway and CASB. ↩︎ ↩︎

  22. You can bring your own certificate to Gateway but these cannot yet be restricted to a specific region. ↩︎

  23. Gateway HTTP supports Regional Services. Gateway DNS does not yet support regionalization.
    ICMP proxy and WARP-to-WARP proxy are not available to Regional Services users. ↩︎

  24. Gateway HTTP and Gateway Network can be used with Customer Metadata Boundary and logs are available via Logpush (logs are still not available in the dashboard when setting the region to the EU). ↩︎