WEBVTT

1
00:00:00.000 --> 00:00:03.720
This video adaptation was generated with Notebook LM.

2
00:00:03.720 --> 00:00:05.400
Welcome to This Explainer.

3
00:00:05.400 --> 00:00:07.960
Today we're diving into the pretty complex reality

4
00:00:07.960 --> 00:00:10.520
of your data rights when it comes to AI training.

5
00:00:10.520 --> 00:00:11.920
We're looking at all of this strictly

6
00:00:11.920 --> 00:00:14.680
from the perspective of October 7th, 2026,

7
00:00:14.680 --> 00:00:17.000
pulling insights directly from the Law Right Newsletter,

8
00:00:17.000 --> 00:00:18.720
edition 007.

9
00:00:18.720 --> 00:00:21.560
Look, it is a truly chaotic time for digital rights right now.

10
00:00:21.560 --> 00:00:23.000
So let's cut through all that noise

11
00:00:23.000 --> 00:00:26.000
and look at the actual grounded legal facts.

12
00:00:26.000 --> 00:00:27.840
Here's our agenda for today.

13
00:00:27.840 --> 00:00:30.560
One, a fictional AI scenario.

14
00:00:30.560 --> 00:00:33.320
Two, Brussels drafts an advocacy.

15
00:00:33.320 --> 00:00:35.520
Three, how Article 21 works.

16
00:00:35.520 --> 00:00:38.360
Four, assessing anonymity and interests.

17
00:00:38.360 --> 00:00:41.080
And five, practical steps to take.

18
00:00:41.080 --> 00:00:43.320
Okay, let's jump right into Section 1,

19
00:00:43.320 --> 00:00:46.480
a fictional AI scenario distinguishing illustration

20
00:00:46.480 --> 00:00:47.880
from reality.

21
00:00:47.880 --> 00:00:51.520
So which data, which actor, and which use?

22
00:00:51.520 --> 00:00:53.920
Just imagine for a second that a platform announces

23
00:00:53.920 --> 00:00:57.120
it's going to use your posts to train a new AI model.

24
00:00:57.120 --> 00:00:59.520
You log in, you find an object button,

25
00:00:59.520 --> 00:01:00.400
and you click it.

26
00:01:00.400 --> 00:01:01.960
Boom, done, right?

27
00:01:01.960 --> 00:01:04.400
But then weeks later, headlines are screaming

28
00:01:04.400 --> 00:01:06.800
that your right to say no is completely vanishing

29
00:01:06.800 --> 00:01:08.200
under new laws.

30
00:01:08.200 --> 00:01:10.120
What's the actual reality here?

31
00:01:10.120 --> 00:01:12.480
Should you immediately fire off an angry letter

32
00:01:12.480 --> 00:01:15.200
or maybe just delete your entire account?

33
00:01:15.200 --> 00:01:16.400
Well, hold on a second.

34
00:01:16.400 --> 00:01:18.800
Before you do anything, you really need to identify

35
00:01:18.800 --> 00:01:20.880
exactly what processing is proposed

36
00:01:20.880 --> 00:01:23.040
and what specific rules govern it.

37
00:01:23.040 --> 00:01:25.120
Now, that's an area we just talked about.

38
00:01:25.120 --> 00:01:26.200
It's completely fictional.

39
00:01:26.200 --> 00:01:28.160
It's not a real event, and it's not a measurement

40
00:01:28.160 --> 00:01:30.360
of any individual legal conclusion.

41
00:01:30.360 --> 00:01:34.040
But it perfectly highlights a really fundamental necessity.

42
00:01:34.040 --> 00:01:35.600
You just can't make big decisions

43
00:01:35.600 --> 00:01:37.960
about your data based on assumptions.

44
00:01:37.960 --> 00:01:41.320
Moving on to Section 2, Brussels drafts an advocacy,

45
00:01:41.320 --> 00:01:43.320
separating proposals from law.

46
00:01:44.360 --> 00:01:47.120
If you've been following the news around late 2026,

47
00:01:47.120 --> 00:01:49.600
you've probably seen the organization NYOB

48
00:01:49.600 --> 00:01:51.800
strongly criticize a European draft

49
00:01:51.800 --> 00:01:53.920
concerning personal data and AI.

50
00:01:53.920 --> 00:01:55.040
But here's the thing.

51
00:01:55.040 --> 00:01:57.760
We have to actively separate legislative noise

52
00:01:57.760 --> 00:01:59.680
from actual binding law.

53
00:01:59.680 --> 00:02:01.080
There's September 21st statement,

54
00:02:01.080 --> 00:02:03.080
that is purely an advocacy position

55
00:02:03.080 --> 00:02:04.800
on ongoing negotiations.

56
00:02:04.800 --> 00:02:06.920
Remember, complaints contain allegations.

57
00:02:06.920 --> 00:02:09.120
They are not court rulings, and they aren't proof

58
00:02:09.120 --> 00:02:11.920
that a reform has actually taken effect.

59
00:02:11.920 --> 00:02:15.000
The actual PDF document that sparked all this debate,

60
00:02:15.000 --> 00:02:18.560
officially numbered 12535/26,

61
00:02:18.560 --> 00:02:20.920
is a council presidency compromise draft

62
00:02:20.920 --> 00:02:22.400
from September 3rd.

63
00:02:22.400 --> 00:02:25.120
The absolutely crucial word there is draft.

64
00:02:25.120 --> 00:02:27.800
It's just a negotiation document published by NYOB,

65
00:02:27.800 --> 00:02:29.880
not adopted legislation.

66
00:02:29.880 --> 00:02:32.720
An ongoing debate in Brussels does not, by itself,

67
00:02:32.720 --> 00:02:34.520
magically erase the existing rights

68
00:02:34.520 --> 00:02:35.840
governing your data today.

69
00:02:37.040 --> 00:02:40.200
All right, Section 3, how Article 21 works,

70
00:02:40.200 --> 00:02:43.080
the bedrock of current GDPR law.

71
00:02:43.080 --> 00:02:45.560
So what exactly are those existing rights?

72
00:02:45.560 --> 00:02:48.480
Well, the GDPR remains our absolute starting point here,

73
00:02:48.480 --> 00:02:50.120
specifically Article 21.

74
00:02:50.120 --> 00:02:53.440
It separates objections into two very distinct camps.

75
00:02:53.440 --> 00:02:55.760
First, you have an objection based on your particular

76
00:02:55.760 --> 00:02:57.960
situation under Article 6 grounds.

77
00:02:57.960 --> 00:02:59.640
Think of this as a balancing test.

78
00:02:59.640 --> 00:03:02.320
It's subject to exceptions, and the controller has to stop

79
00:03:02.320 --> 00:03:05.120
unless they demonstrate compelling legitimate grounds.

80
00:03:05.120 --> 00:03:08.400
Now, contrast that with a direct marketing objection.

81
00:03:08.400 --> 00:03:10.800
With direct marketing, there is no balancing act.

82
00:03:10.800 --> 00:03:13.400
The processing strictly and immediately stops.

83
00:03:13.400 --> 00:03:15.520
They just don't work the same way.

84
00:03:15.520 --> 00:03:19.200
And hey, this brings up a really massive point of confusion.

85
00:03:19.200 --> 00:03:22.160
Erasure and objection are fundamentally different

86
00:03:22.160 --> 00:03:23.440
legal requests.

87
00:03:23.440 --> 00:03:26.360
Simply rage-deleting your account does not automatically prove

88
00:03:26.360 --> 00:03:28.400
that previous data use has been reversed,

89
00:03:28.400 --> 00:03:31.760
or that a massive AI model was somehow untrained.

90
00:03:31.760 --> 00:03:35.000
An unverified technical assurance simply isn't proof.

91
00:03:35.000 --> 00:03:37.440
You need a proper response detailing exactly

92
00:03:37.440 --> 00:03:40.000
what your request actually changes.

93
00:03:40.000 --> 00:03:42.560
This takes us to Section 4, assessing anonymity

94
00:03:42.560 --> 00:03:44.960
and interests, the institutional interpretation

95
00:03:44.960 --> 00:03:46.840
from the EDPB.

96
00:03:46.840 --> 00:03:50.040
How are the big institutions actually navigating all this?

97
00:03:50.040 --> 00:03:52.840
The European Data Protection Board is crystal clear

98
00:03:52.840 --> 00:03:55.360
in opinion 28/2024.

99
00:03:55.360 --> 00:03:57.960
Relying on legitimate interests requires a

100
00:03:57.960 --> 00:04:00.440
concrete case-specific assessment.

101
00:04:00.440 --> 00:04:03.320
It comes down to three incredibly strict criteria,

102
00:04:03.320 --> 00:04:05.120
assessing the specific interest,

103
00:04:05.120 --> 00:04:07.360
evaluating the necessity of the processing,

104
00:04:07.360 --> 00:04:10.000
and doing that balancing test against user rights.

105
00:04:10.000 --> 00:04:12.800
You literally can't just assume legitimate interests

106
00:04:12.800 --> 00:04:15.120
automatically authorize a data grab.

107
00:04:15.120 --> 00:04:19.200
Then, of course, we have the persistent myth of anonymity.

108
00:04:19.200 --> 00:04:22.440
The EDPB provides a vital reality check here.

109
00:04:22.440 --> 00:04:24.520
An AI model trained with personal data

110
00:04:24.520 --> 00:04:27.840
does not automatically become anonymous just by its nature.

111
00:04:27.840 --> 00:04:31.240
You need a concrete assessment to actually establish that.

112
00:04:31.240 --> 00:04:34.280
Here's another super critical takeaway from the EDPB.

113
00:04:34.280 --> 00:04:38.400
Public accessibility does not erase GDPR conditions.

114
00:04:38.400 --> 00:04:40.920
Just because your data can be read online by anyone

115
00:04:40.920 --> 00:04:42.840
does not mean it magically transforms

116
00:04:42.840 --> 00:04:45.240
into unrestricted material for reuse,

117
00:04:45.240 --> 00:04:47.280
totally exempt from data protection laws.

118
00:04:47.280 --> 00:04:49.800
The rules still completely apply.

119
00:04:49.800 --> 00:04:52.360
Finally, section five, practical steps to take,

120
00:04:52.360 --> 00:04:54.200
the law-right approach.

121
00:04:54.200 --> 00:04:57.120
Let's bring this all down to earth with some practical actions,

122
00:04:57.120 --> 00:04:58.680
straight from the newsletter article.

123
00:04:58.680 --> 00:05:00.640
Now, while this advice belongs to the author

124
00:05:00.640 --> 00:05:03.080
and creates no universal legal duties,

125
00:05:03.080 --> 00:05:04.560
it's an incredibly solid framework

126
00:05:04.560 --> 00:05:07.280
for where things stand in October 2026.

127
00:05:07.280 --> 00:05:10.440
Step one, identify the exact privacy notice.

128
00:05:10.440 --> 00:05:12.920
Step two, state your request precisely

129
00:05:12.920 --> 00:05:14.560
and keep a dated acknowledgement.

130
00:05:14.560 --> 00:05:16.640
You want to explain your particular situation

131
00:05:16.640 --> 00:05:19.080
rather than just assuming it's for direct marketing.

132
00:05:19.080 --> 00:05:21.920
And step three, assess any incomplete responses

133
00:05:21.920 --> 00:05:24.680
against the actual processing taking place.

134
00:05:24.680 --> 00:05:27.800
There's also some really grounded advice here for businesses.

135
00:05:27.800 --> 00:05:30.200
First, you've got to map the exact information

136
00:05:30.200 --> 00:05:31.680
supplied to AI tools.

137
00:05:31.680 --> 00:05:34.760
Second, carefully check what the actual service does

138
00:05:34.760 --> 00:05:37.440
versus what the contractual promises claim.

139
00:05:37.440 --> 00:05:39.880
And most importantly, businesses have to remember

140
00:05:39.880 --> 00:05:42.200
that a reform currently under discussion

141
00:05:42.200 --> 00:05:44.440
absolutely does not replace the immediate need

142
00:05:44.440 --> 00:05:47.400
to comply with the law as it stands today.

143
00:05:47.400 --> 00:05:48.960
So as we wrap up this explainer,

144
00:05:48.960 --> 00:05:51.440
I want to leave you with a bit of a provocative question

145
00:05:51.440 --> 00:05:52.640
to chew on.

146
00:05:52.640 --> 00:05:54.840
Are you effectively separating legal facts

147
00:05:54.840 --> 00:05:57.960
from advocacy noise in your own data decisions?

148
00:05:57.960 --> 00:05:59.800
Untangling ongoing draft proposals

149
00:05:59.800 --> 00:06:01.600
from the precise legal realities

150
00:06:01.600 --> 00:06:03.120
governing your data right now

151
00:06:03.120 --> 00:06:05.720
is literally the most powerful tool you have.

152
00:06:05.720 --> 00:06:06.840
Thanks so much for joining me.

153
00:06:06.840 --> 00:06:08.080
Keep your focus on the facts

154
00:06:08.080 --> 00:06:10.120
and I will catch you in the next explainer.
