EU data residency for your cached content. Named data centres, written into the agreement, and content that does not leave the region even when a node fails.
Reply within 3 business hours. No sales sequence.
A data-residency requirement is answered with facts about geography, not with adjectives. These are the ones we commit to.
The locations that hold your cache are listed in the agreement before the build starts. Not a region preference, not a routing policy: a list you can hand to an auditor.
This is the question every DPO asks second: what happens when a node fails. Cached objects stay inside the agreed region, including during failover. Traffic does not spill to a node outside it.
Log storage and support access can both be kept inside the European Union. Ask for it during scoping and it goes into the agreement with everything else.
The contract and the invoicing come from our headquarters in Poland. For a European procurement team that is one less cross-border question to answer.
Most vendors in this category imply they hand you compliance. They cannot, and neither can we. Here is the honest split.
Where the nodes physically are. What is in the agreement. That cached content stays in the agreed region. Where logs live and who reaches them. Encrypted connections and access control on the cache.
You are the data controller. What you cache, on what legal basis, for how long and what you tell your users stays your decision. We will not claim otherwise, and we do not advertise certifications we do not hold.
One more distinction worth making, because it is often blurred: we commit to residency, which is where the bytes physically sit. We do not claim sovereignty, which is a question about legal ownership chains, and no CDN can honestly promise it.
Three platform classes cover almost every residency build. The machine itself is ordinary cache hardware; what makes it a GDPR node is the facility it goes into and what the agreement says about it.
The standard build for a residency node. The working set for one country or one region, answered from flash inside the EU.
For a catalogue that has to stay inside the EU in full, not only the part that is popular this week.
Where a single EU location has to carry a lot of traffic. The DPU takes network processing off the cores.
Every configuration is specified per build, and the data centre is named in the quote before anything is ordered. Cores, memory, flash and port speed follow the size of the library that has to stay inside the EU.
Same dedicated hardware underneath. Different person asking for it.
The request came from legal, procurement or your DPO. What you need is a contractual answer about where bytes sit and what happens when a node fails.
The request came from engineering. What you need is retention, cache policy and a smaller origin bill. See Private Cache Servers.
Residency is priced like any other dedicated build: a fixed monthly figure per node, quoted before anything is ordered, plus delivery on your agreed tier. The whole ladder sits on Custom Enterprise CDN Infrastructure.
Written the way we would answer them in a vendor review, including the answers that are a plain no.
In data centres we name before the build, inside the European Union. The list is part of the agreement, so it does not change quietly when routing changes.
Traffic stays inside the region you agreed on. Content does not fail over to a node outside it. This is usually the second question in a review and the one that ends most conversations elsewhere.
Log storage and support access can both be kept inside the EU. It is not the default on the shared platform, so name it during scoping and it is written in alongside the locations.
We do not advertise certifications we do not hold, and you will not find badges on this page for that reason. What we offer instead is a contractual answer about geography, which is the part most residency clauses actually turn on.
Any delivery network handles request metadata such as IP addresses in order to route and log a request, so claiming otherwise would be false. What your cached objects contain is your decision as the controller, and that decision belongs in your own assessment rather than in our marketing copy.
The facility operators for your locations are named in the agreement, so your review covers the actual chain rather than a brand on a map.
Tell us which regions you are required to stay inside and what your review asks for. You get a reply within 3 business hours, from an engineer who will say plainly if we cannot meet a clause.
He reads every request sent from this page and replies within 3 business hours, including the reply that says a dedicated node is not what your review needs. No sales sequence in between.