Digital contracts · Technology governance
Your cloud is European. Can you actually leave it?
Listen to the analysis
Voices and adaptation generated with NotebookLM; video illustrations generated with AI. Automatic transcription may contain errors. Historical analysis of issue 006, cut off 28 September 2026; no current legal update or certification of compliance.
Read the transcript
this audio adaptation was generated with notebook L.M. So imagine paying millions to migrate your whole enterprise to a certified European cloud, right? And then, you know, at contract renewal, you find out a vendor completely outside the continent still holds the actual administrative keys to your data. Yeah, that is a massive wake-up call for a lot of businesses. Totally. So today, our mission is really tearing down that illusion of, like, geographical data control. Welcome to the deep dive, everyone. Thanks. And our source for this is a September 28, 2026 law-right newsletter. It is basically dissecting the European Commission's June 3 technology sovereignty package. Right, the June 3 presentation. Exactly. And specifically, we are looking at the CADA proposal, so that is the Cloud and AI Development Act. It really exposes this huge gap between where your servers actually live and who actually controls them. Okay, before we dive into the mechanics of that gap, I mean, let's just ground this for you listening right now. The June 3 presentation, it rolled out an open-source strategy along with this CADA proposal. But it is crucial to remember, these are just policy directions. Right, they remain proposals at this stage. Yeah, so this doesn't automatically impose some new general obligation on your business today. That is such a vital caveat. The policy is aiming to curb reliance on foreign hyperscalers, but the way CADA outlines its framework for public sector bodies, which is based on risk assessment, it gives us this really fascinating roadmap. A roadmap for evaluating vendor lock-in, right? Exactly. Because it draws a hard line between mere geography and actual operational control. The presentation distinguishes four proposed levels. Okay, let's unpack this. Because the first level is literally just EU location, meaning data is processed and stored in the union. But then it escalates so fast. It really does. Level two adds independence and transparency. Right, and then levels three and four, that is where it demands EU ownership and control with additional criteria. And finally, full transparency and control without third country interference. Yep, it ramps up significantly. I mean, level one just means the servers are physically in the EU. That is like parking your car in a European garage, but who actually holds the keys? If my contract says the date is in Frankfurt, how does a third country even interfere? Well, that is precisely the trap of using a commercial adjective like European. Because a level one location, it just does not inherently answer questions about administrative control or third party interference. So the physical location of the hard drive doesn't matter if the software running it is like proprietary and foreign. Exactly. Think about core administrative functions. If those depend on a third party, they have operational access. Regardless of the zip code. Right, and because of that, a business really must look past marketing terms and evaluate the actual mechanics of their specific contract. Which totally brings us to the newsletter-other scenario. It's fictional, but honestly highly realistic. A business assumes they have control just because their data is in the EU. Right, they bought the European cloud. Yeah, but then renewal time comes around. They look into leaving, and they discover data exports are incomplete, core functions depend on third parties, and migration would literally take months. It is a nightmare. And this is where the author lays out some pragmatic management recommendations. You have to separate three distinct questions here. Okay, what are they? First, where does the service operate? Second, who can actually act on it? And third, the replacement question, how could your business physically replace it? So if you are listening to this, don't wait for your contract to end. The advice is to run a trial export using test data well before contract renewal. Yes, a test export and contract review are key management recommendations. You need to check if the necessary metadata and histories actually transfer. You want to know if leaving is even technically possible. Exactly. But we have to strictly clarify one crucial caveat here. Doing this migration test provides an operational baseline for management. Meeting it tells you the technical cost. Right, but it does not certify legal compliance in any way. A migration test does not certify legal compliance. Oh, wow. But really, so it tells you if the door is physically unlocked, but it doesn't mean you are legally cleared to walk through it. Correct. That is huge. So wrapping up, this is exactly why this matters to you. A single commercial adjective cannot adequately describe your legal and technical relationship with a provider. It really can't. You have to look at the actual contract mechanics, which leaves us with a pretty unsettling thought to ponder. If a physical trial is literally the only way to measure departure costs, how many of the everyday digital tools your business relies on are essentially roach motels? Roach motels. Yeah, like incredibly easy to check your data into, but technically and financially impossible to leave.
Technology sovereignty becomes practical when you examine access, dependencies and the terms of departure.
Case statusResearch closed on 28 September 2026 · check for changes before taking a decision.
01
Europe proposes a sovereignty framework
On 3 June 2026, the European Commission presented a communication on technology sovereignty, accompanied by an open-source strategy. The package includes a proposed Cloud and AI Development Act, or CADA. These documents express a policy direction: strengthening control over digital infrastructure and services. A communication does not, merely by existing, impose a new general obligation on businesses. [1,2]
The CADA presentation distinguishes four levels of sovereignty, with location in the Union only the first. That detail matters to buyers: a European data centre does not by itself answer every question about control. The pages consulted describe a proposal. They do not establish that these levels are already general requirements applying to every small business. [3]
02
Turn a marketing term into something you can test
For an upcoming purchase, we suggest separating three questions: where does the service operate, who can act on it and how could the business replace it? This is a recommendation for contract management, not an exhaustive legal definition of sovereignty. A single commercial adjective cannot adequately describe a technical architecture and a legal relationship. The answers also need to match your actual use.
Ask which providers are involved, who has administrative access and which functions depend on a third-party licence or service. Compare the answers with the contractual documents. A product presentation may be too general to establish what has been promised for your configuration. Precise responsibilities require examination of the contract and the rules applicable to the activity concerned.
Departure deserves particular attention. A promised export may be difficult to use without metadata, histories or documentation needed to transfer it elsewhere. Conversely, a dependency does not always justify an immediate change. The aim is to know its cost, timing and consequences before extending a commitment. A migration test alone establishes no general conclusion about legal compliance.
03
The Law Right approach: test an exit before renewal
- Choose an important service and request a trial export using fictional data or data suitable for the test. Ask the relevant team to check completeness and reusability. Record the manual operations required: they give an initial indication of the work departure would involve. Also note what the test could not establish, rather than treating an incomplete exercise as a full migration assessment.
- Compare the experience with written commitments on available formats, assistance, deadlines, costs and arrangements for returning or deleting information. Identify points requiring negotiated clarification. This checklist is a discussion aid; it is not presented as a set of clauses legally required in every agreement. A useful response should explain the proposed service in terms your team can verify.
- Give someone responsibility for monitoring critical dependencies and renewal dates. A replacement option becomes useful when it has an owner, an estimate and a timetable. Research closed on 28 September and needs updating before publication. Further legislative developments concerning CADA remain to be checked; this draft does not anticipate their outcome.
Sovereignty needs scrutiny at every layer.
Where is the equipment, and who can control access to it?
Explanatory schematic: illustrative relationships, not a measurement of dependencies or a legal conclusion.Control over a service also depends on your documented ability to replace it.
Watch the story
Voices and adaptation generated with NotebookLM; video illustrations generated with AI. Automatic transcription may contain errors. Historical analysis of issue 006, cut off 28 September 2026; no current legal update or certification of compliance.
Read the transcript
This video adaptation was generated with Notebook LM. Welcome to this explainer. Today, we're diving into European cloud sovereignty proposals and the very real contract management challenges businesses are facing as of September 2026. We're gonna cut through the noise and look closely at access, critical dependencies, and what it actually takes to leave a cloud service. And as you can see on screen, this video adaptation was generated with Notebook LM. Okay, here's our roadmap for today. First, the tech sovereignty proposal. Second, four proposed sovereignty levels. Third, managing digital contracts, and finally, testing a cloud exit. Let's jump in. The tech sovereignty proposal. So let's set the scene. It's September 28, 2026. You see these headlines everywhere about digital autonomy, right? But what does that actually mean on the ground? Imagine your business buys a cloud service and it's heavily marketed as European. Your data is hosted right here in the union. So your management team thinks, great, we've got total control. But then, renewal time rolls around and reality hits hard. You realize data exports are incomplete. There are hidden third party dependencies you didn't even know about. And migration, it's gonna take way longer than expected. The location of the servers answered one question, sure. But the contract left literally everything else wide open. To understand where this disconnect comes from, we have to look at the regulatory level. On June 3, 2026, the European Commission presented a technology sovereignty package. This included an open source strategy and the highly discussed Cloud and AI Development Act, or CADA for short. The main goal here, strengthening absolute control over digital infrastructure. But, and this is absolutely crucial, we have to remember what these documents actually are. These drafts remain proposals. They express a policy direction. Just because the commission puts out a presentation, doesn't magically impose a new general legal obligation on your business. They show us where the regulatory wins are blowing, for sure. But they aren't universal legal duties, applying to every single company just yet. Four proposed sovereignty levels. Now, what's really fascinating here is how this sort of proposal describes a framework for public sector bodies. And it's entirely based on risk assessment. Look at how it distinguishes sovereignty into four proposed levels. Level one, that's just an EU location, basically the bare minimum. Level two, steps it up, demanding independence and transparency. Level three goes even further, requiring EU ownership and control alongside additional criteria. And then, there's the gold standard. Level four, full transparency and control, completely free from any third country interference. The big takeaway here for you? You literally cannot describe a complex technical architecture with a single marketing adjective like European. As this quote nails it, a European data center location answers one question, but it definitely does not answer every question about control. Real sovereignty requires you to scrutinize every single layer. Managing digital contracts. Okay, so how do we take these macro level EU proposals and turn them into practical steps for your next purchase? Well, to turn a marketing term into something you can actually test, our first management recommendation is simply to ask, where exactly does this service operate? This ties right back to that level one sovereignty question. You need to know the physical jurisdiction of the servers running your apps. Next up, ask, who can actually act on it? Like, who really holds the administrative keys? Because, well, you might be buying from a European company, but if their core features secretly rely on a non-European third party dependency, your control is instantly diluted. Finally, ask yourself, how could the business replace it? Honestly, your departure deserves your utmost attention. Think about it, a promised data export is completely useless if you don't also get the metadata, the file histories, or the technical documentation you need to actually set it up somewhere else. Your control over a service absolutely depends on your documented ability to replace it. And keep in mind, a slick sales pitch is way too general to establish what you're actually owed. You've got to take the answers to those three questions and compare them directly against your written contractual documents. Finding out your precise responsibilities requires you to look hard at the contract itself. Testing a cloud exit. So, because a dependency doesn't necessarily mean you need to make a panicky overnight change, you should definitely conduct a trial export before you renew a contract. You want to know the real costs and timing, right? Here are four practical management recommendations to evaluate your readiness. One, request a trial export using suitable test data. Two, check it for completeness and reusability. Three, write down every single manual operation required. This is where you find the real friction. And four, compare that real-world experience with your written commitments. Now remember, these are strictly management recommendations. You should note what the test could not establish, rather than pretending an incomplete exercise as a full-blown migration assessment. And this is absolutely vital. A migration test evaluates your management readiness, but it does not certify legal compliance. This is just practical advice to aid your discussions, not a universal legal duty. As you start putting this into practice, make sure you assign responsibility to someone on your team to actually monitor these critical dependencies. And keep our timeline in mind. This specific research closed on September 28, 2026. Because CADA is still a draft, you've got to continuously monitor further legislative developments before you make any final decisions. Ultimately, a replacement option only becomes truly useful when it has three things. An owner, an estimate, and a timetable. Despite all the fancy marketing adjectives, you have to ask yourself the hard question. If you had to flip the switch tomorrow, would your business actually survive the exit? Or are you locked into a European cloud that you can never really leave? Thanks for joining me for this explainer. Now, go check your contracts.
