WEBVTT

1
00:00:00.000 --> 00:00:03.320
this audio adaptation was generated with notebook L.M.

2
00:00:03.320 --> 00:00:08.880
So imagine paying millions to migrate your whole enterprise

3
00:00:08.880 --> 00:00:11.480
to a certified European cloud, right?

4
00:00:11.480 --> 00:00:14.800
And then, you know, at contract renewal,

5
00:00:14.800 --> 00:00:17.720
you find out a vendor completely outside the continent

6
00:00:17.720 --> 00:00:21.000
still holds the actual administrative keys to your data.

7
00:00:21.000 --> 00:00:24.640
Yeah, that is a massive wake-up call for a lot of businesses.

8
00:00:24.640 --> 00:00:29.200
Totally. So today, our mission is really tearing down

9
00:00:29.200 --> 00:00:32.480
that illusion of, like, geographical data control.

10
00:00:32.480 --> 00:00:33.960
Welcome to the deep dive, everyone.

11
00:00:33.960 --> 00:00:35.280
Thanks.

12
00:00:35.280 --> 00:00:39.120
And our source for this is a September 28, 2026

13
00:00:39.120 --> 00:00:40.600
law-right newsletter.

14
00:00:40.600 --> 00:00:43.200
It is basically dissecting the European Commission's

15
00:00:43.200 --> 00:00:45.520
June 3 technology sovereignty package.

16
00:00:45.520 --> 00:00:47.040
Right, the June 3 presentation.

17
00:00:47.040 --> 00:00:50.880
Exactly. And specifically, we are looking at the CADA proposal,

18
00:00:50.880 --> 00:00:53.600
so that is the Cloud and AI Development Act.

19
00:00:53.600 --> 00:00:56.720
It really exposes this huge gap between where your servers

20
00:00:56.720 --> 00:00:59.280
actually live and who actually controls them.

21
00:00:59.280 --> 00:01:01.520
Okay, before we dive into the mechanics of that gap,

22
00:01:01.520 --> 00:01:04.640
I mean, let's just ground this for you listening right now.

23
00:01:04.640 --> 00:01:08.320
The June 3 presentation, it rolled out an open-source strategy

24
00:01:08.320 --> 00:01:10.960
along with this CADA proposal.

25
00:01:10.960 --> 00:01:14.320
But it is crucial to remember, these are just policy directions.

26
00:01:14.320 --> 00:01:16.960
Right, they remain proposals at this stage.

27
00:01:16.960 --> 00:01:19.120
Yeah, so this doesn't automatically impose some new

28
00:01:19.120 --> 00:01:21.120
general obligation on your business today.

29
00:01:21.120 --> 00:01:23.920
That is such a vital caveat.

30
00:01:23.920 --> 00:01:28.400
The policy is aiming to curb reliance on foreign hyperscalers,

31
00:01:28.400 --> 00:01:31.040
but the way CADA outlines its framework for public sector

32
00:01:31.040 --> 00:01:33.440
bodies, which is based on risk assessment,

33
00:01:33.440 --> 00:01:36.560
it gives us this really fascinating roadmap.

34
00:01:36.560 --> 00:01:39.280
A roadmap for evaluating vendor lock-in, right?

35
00:01:39.280 --> 00:01:40.160
Exactly.

36
00:01:40.160 --> 00:01:43.040
Because it draws a hard line between mere geography

37
00:01:43.040 --> 00:01:44.960
and actual operational control.

38
00:01:44.960 --> 00:01:48.160
The presentation distinguishes four proposed levels.

39
00:01:48.160 --> 00:01:49.600
Okay, let's unpack this.

40
00:01:49.600 --> 00:01:52.320
Because the first level is literally just EU location,

41
00:01:52.320 --> 00:01:56.320
meaning data is processed and stored in the union.

42
00:01:56.320 --> 00:01:58.320
But then it escalates so fast.

43
00:01:58.320 --> 00:01:59.200
It really does.

44
00:01:59.200 --> 00:02:02.240
Level two adds independence and transparency.

45
00:02:02.240 --> 00:02:04.240
Right, and then levels three and four,

46
00:02:04.240 --> 00:02:06.960
that is where it demands EU ownership and control

47
00:02:06.960 --> 00:02:08.480
with additional criteria.

48
00:02:08.480 --> 00:02:10.720
And finally, full transparency and control

49
00:02:10.720 --> 00:02:12.560
without third country interference.

50
00:02:12.560 --> 00:02:14.640
Yep, it ramps up significantly.

51
00:02:14.640 --> 00:02:17.520
I mean, level one just means the servers are physically in the EU.

52
00:02:17.520 --> 00:02:20.640
That is like parking your car in a European garage,

53
00:02:20.640 --> 00:02:23.040
but who actually holds the keys?

54
00:02:23.040 --> 00:02:25.200
If my contract says the date is in Frankfurt,

55
00:02:25.200 --> 00:02:27.040
how does a third country even interfere?

56
00:02:27.040 --> 00:02:29.760
Well, that is precisely the trap of using

57
00:02:29.760 --> 00:02:32.400
a commercial adjective like European.

58
00:02:32.400 --> 00:02:34.240
Because a level one location,

59
00:02:34.240 --> 00:02:36.560
it just does not inherently answer questions

60
00:02:36.560 --> 00:02:39.760
about administrative control or third party interference.

61
00:02:39.760 --> 00:02:41.760
So the physical location of the hard drive

62
00:02:41.760 --> 00:02:43.600
doesn't matter if the software running it

63
00:02:43.600 --> 00:02:45.680
is like proprietary and foreign.

64
00:02:45.680 --> 00:02:46.880
Exactly.

65
00:02:46.880 --> 00:02:48.800
Think about core administrative functions.

66
00:02:48.800 --> 00:02:50.720
If those depend on a third party,

67
00:02:50.720 --> 00:02:52.320
they have operational access.

68
00:02:52.320 --> 00:02:53.760
Regardless of the zip code.

69
00:02:53.760 --> 00:02:55.600
Right, and because of that,

70
00:02:55.600 --> 00:02:58.000
a business really must look past marketing terms

71
00:02:58.000 --> 00:03:00.320
and evaluate the actual mechanics

72
00:03:00.320 --> 00:03:02.080
of their specific contract.

73
00:03:02.080 --> 00:03:04.560
Which totally brings us to the newsletter-other scenario.

74
00:03:04.560 --> 00:03:07.760
It's fictional, but honestly highly realistic.

75
00:03:07.760 --> 00:03:09.440
A business assumes they have control

76
00:03:09.440 --> 00:03:11.760
just because their data is in the EU.

77
00:03:11.760 --> 00:03:13.680
Right, they bought the European cloud.

78
00:03:13.680 --> 00:03:15.680
Yeah, but then renewal time comes around.

79
00:03:16.240 --> 00:03:19.200
They look into leaving, and they discover data exports

80
00:03:19.200 --> 00:03:22.800
are incomplete, core functions depend on third parties,

81
00:03:22.800 --> 00:03:25.120
and migration would literally take months.

82
00:03:25.120 --> 00:03:26.560
It is a nightmare.

83
00:03:26.560 --> 00:03:28.160
And this is where the author lays out

84
00:03:28.160 --> 00:03:30.880
some pragmatic management recommendations.

85
00:03:30.880 --> 00:03:33.120
You have to separate three distinct questions here.

86
00:03:33.120 --> 00:03:34.000
Okay, what are they?

87
00:03:34.000 --> 00:03:36.480
First, where does the service operate?

88
00:03:36.480 --> 00:03:39.040
Second, who can actually act on it?

89
00:03:39.040 --> 00:03:40.960
And third, the replacement question,

90
00:03:40.960 --> 00:03:43.200
how could your business physically replace it?

91
00:03:43.200 --> 00:03:44.720
So if you are listening to this,

92
00:03:45.520 --> 00:03:47.360
don't wait for your contract to end.

93
00:03:47.360 --> 00:03:50.480
The advice is to run a trial export using test data

94
00:03:50.480 --> 00:03:52.320
well before contract renewal.

95
00:03:52.320 --> 00:03:54.560
Yes, a test export and contract review

96
00:03:54.560 --> 00:03:56.560
are key management recommendations.

97
00:03:56.560 --> 00:03:59.040
You need to check if the necessary metadata

98
00:03:59.040 --> 00:04:00.960
and histories actually transfer.

99
00:04:00.960 --> 00:04:03.680
You want to know if leaving is even technically possible.

100
00:04:03.680 --> 00:04:04.560
Exactly.

101
00:04:04.560 --> 00:04:07.440
But we have to strictly clarify one crucial caveat here.

102
00:04:08.080 --> 00:04:09.840
Doing this migration test provides

103
00:04:09.840 --> 00:04:11.920
an operational baseline for management.

104
00:04:11.920 --> 00:04:14.080
Meeting it tells you the technical cost.

105
00:04:14.080 --> 00:04:18.800
Right, but it does not certify legal compliance in any way.

106
00:04:18.800 --> 00:04:21.920
A migration test does not certify legal compliance.

107
00:04:21.920 --> 00:04:22.800
Oh, wow.

108
00:04:22.800 --> 00:04:26.800
But really, so it tells you if the door is physically unlocked,

109
00:04:26.800 --> 00:04:29.680
but it doesn't mean you are legally cleared to walk through it.

110
00:04:29.680 --> 00:04:30.320
Correct.

111
00:04:30.320 --> 00:04:31.360
That is huge.

112
00:04:31.360 --> 00:04:34.320
So wrapping up, this is exactly why this matters to you.

113
00:04:34.960 --> 00:04:38.160
A single commercial adjective cannot adequately describe

114
00:04:38.160 --> 00:04:40.560
your legal and technical relationship with a provider.

115
00:04:40.560 --> 00:04:41.600
It really can't.

116
00:04:41.600 --> 00:04:44.400
You have to look at the actual contract mechanics,

117
00:04:44.400 --> 00:04:47.120
which leaves us with a pretty unsettling thought to ponder.

118
00:04:47.680 --> 00:04:50.160
If a physical trial is literally the only way

119
00:04:50.160 --> 00:04:51.600
to measure departure costs,

120
00:04:52.480 --> 00:04:54.240
how many of the everyday digital tools

121
00:04:54.240 --> 00:04:57.280
your business relies on are essentially roach motels?

122
00:04:57.280 --> 00:04:58.480
Roach motels.

123
00:04:58.480 --> 00:05:02.080
Yeah, like incredibly easy to check your data into,

124
00:05:02.080 --> 00:05:05.280
but technically and financially impossible to leave.
