WEBVTT

1
00:00:00.000 --> 00:00:03.080
This audio adaptation was generated with Notebook LM.

2
00:00:03.080 --> 00:00:06.100
Welcome to our deep dive into the October 2026 edition

3
00:00:06.100 --> 00:00:07.640
of the Law Right newsletter.

4
00:00:07.640 --> 00:00:11.240
So picture this, you log in and realize a platform

5
00:00:11.240 --> 00:00:12.640
you use every day is just, you know,

6
00:00:12.640 --> 00:00:14.300
quietly feeding your private posts

7
00:00:14.300 --> 00:00:16.640
into this massive AI brain.

8
00:00:16.640 --> 00:00:18.240
- Yeah, which is a pretty terrifying thought.

9
00:00:18.240 --> 00:00:20.960
- Right, and then suddenly this alarming headline pops up.

10
00:00:20.960 --> 00:00:23.400
It claims your legal right to say no

11
00:00:23.400 --> 00:00:24.960
is about to be completely erased.

12
00:00:24.960 --> 00:00:26.760
- Which naturally makes people wanna panic, right?

13
00:00:26.760 --> 00:00:28.240
Like just hit delete.

14
00:00:28.240 --> 00:00:30.440
- Exactly, do you delete your account?

15
00:00:30.440 --> 00:00:32.640
Or is there, you know, a better way to respond?

16
00:00:32.640 --> 00:00:35.560
Today we are navigating the highly complex rules

17
00:00:35.560 --> 00:00:38.040
of using your personal data to train AI.

18
00:00:38.040 --> 00:00:39.920
- It is incredibly easy to see a headline like that

19
00:00:39.920 --> 00:00:41.480
and just assume the battle for your privacy

20
00:00:41.480 --> 00:00:44.480
has already been lost, but I mean,

21
00:00:44.480 --> 00:00:46.080
panic usually leads to the wrong moves.

22
00:00:46.080 --> 00:00:48.200
- Yeah, so let's unpack this alarm.

23
00:00:48.200 --> 00:00:51.360
If this leak draft is just like advocacy noise,

24
00:00:51.360 --> 00:00:52.800
what is the actual signal here?

25
00:00:52.800 --> 00:00:53.640
- Right.

26
00:00:53.640 --> 00:00:55.320
- If a listener is worried about their data today,

27
00:00:55.320 --> 00:00:58.440
what real world rules actually protect them right now?

28
00:00:58.440 --> 00:01:00.640
- Well, let's start with the panic itself.

29
00:01:00.640 --> 00:01:02.920
On September 21st, 2026,

30
00:01:02.920 --> 00:01:05.800
the privacy advocacy group NYOB

31
00:01:05.800 --> 00:01:08.200
published a very strong criticism.

32
00:01:08.200 --> 00:01:09.040
- Okay.

33
00:01:09.040 --> 00:01:10.160
- It was criticism of a

34
00:01:10.160 --> 00:01:12.360
council presidency compromise draft,

35
00:01:12.360 --> 00:01:16.880
specifically draft number 1253526,

36
00:01:16.880 --> 00:01:17.920
dated September 3.

37
00:01:18.920 --> 00:01:22.880
What's fascinating here is that PDF published by NYOB

38
00:01:22.880 --> 00:01:25.120
is purely a negotiation document.

39
00:01:25.120 --> 00:01:26.240
- Wait, hold on, let me jump in.

40
00:01:26.240 --> 00:01:28.760
So a draft is really just a proposal.

41
00:01:28.760 --> 00:01:29.600
- Exactly.

42
00:01:29.600 --> 00:01:32.640
Their statement is just an advocacy position

43
00:01:32.640 --> 00:01:34.200
on ongoing talks.

44
00:01:34.200 --> 00:01:36.280
It has not adopted legislation

45
00:01:36.280 --> 00:01:38.680
and it is certainly not a court ruling.

46
00:01:38.680 --> 00:01:39.960
- Oh, I see.

47
00:01:39.960 --> 00:01:42.040
That means we shouldn't act like our legal productions

48
00:01:42.040 --> 00:01:44.000
have already vanished just because, you know,

49
00:01:44.000 --> 00:01:46.560
some politicians are having a brainstorm in Brussels.

50
00:01:46.560 --> 00:01:47.800
- Precisely.

51
00:01:47.800 --> 00:01:50.280
The current debate in Brussels has to be separated

52
00:01:50.280 --> 00:01:53.480
from the laws that are actually governing your data today.

53
00:01:53.480 --> 00:01:55.760
We just can't mistake policy advocacy

54
00:01:55.760 --> 00:01:57.880
for a sudden change in your legal rights.

55
00:01:57.880 --> 00:02:00.160
- Which means we need to look at the current reality

56
00:02:00.160 --> 00:02:01.360
of the GDPR.

57
00:02:01.360 --> 00:02:04.080
How does objecting actually work right now?

58
00:02:04.080 --> 00:02:06.280
Because I think most of us just assume

59
00:02:06.280 --> 00:02:09.480
clicking no works the exact same way everywhere.

60
00:02:09.480 --> 00:02:10.520
- It definitely doesn't.

61
00:02:10.520 --> 00:02:12.760
Under article 21 of the GDPR,

62
00:02:12.760 --> 00:02:14.000
you really have to distinguish

63
00:02:14.000 --> 00:02:15.640
between two types of objections.

64
00:02:15.640 --> 00:02:16.480
- Okay, how so?

65
00:02:16.480 --> 00:02:18.520
- Well, if a company uses your data

66
00:02:18.520 --> 00:02:21.560
for direct marketing and you object,

67
00:02:21.560 --> 00:02:24.160
that processing stops automatically, boom, done.

68
00:02:24.160 --> 00:02:25.800
- Right, so that one's just binary.

69
00:02:25.800 --> 00:02:28.480
- Exactly, but objecting to your data being used

70
00:02:28.480 --> 00:02:30.280
for AI training is usually based

71
00:02:30.280 --> 00:02:33.800
on what the law calls your particular situation.

72
00:02:33.800 --> 00:02:38.800
- Particular situation, that sounds a bit subjective.

73
00:02:39.720 --> 00:02:42.160
- It is legally distinct and it actually triggers

74
00:02:42.160 --> 00:02:44.720
a balancing exercise between your rights

75
00:02:44.720 --> 00:02:46.720
and the company's legitimate interests.

76
00:02:46.720 --> 00:02:48.720
- Well, hold on, a balancing exercise.

77
00:02:48.720 --> 00:02:52.640
Who gets to decide if a tech giant's legitimate interest

78
00:02:52.640 --> 00:02:53.480
outweighs my privacy?

79
00:02:53.480 --> 00:02:55.400
'Cause I feel like I know who usually wins that fight.

80
00:02:55.400 --> 00:02:56.240
- Yeah, I get that.

81
00:02:56.240 --> 00:02:59.240
But it's not a blank check for tech companies, thankfully.

82
00:02:59.240 --> 00:03:01.320
If we connect this to the bigger picture,

83
00:03:01.320 --> 00:03:04.080
we have to look at a recent EU data protection document.

84
00:03:04.080 --> 00:03:05.040
- Right.

85
00:03:05.040 --> 00:03:09.560
- Specifically, EDPB opinion 28/2024.

86
00:03:10.480 --> 00:03:13.560
This opinion demands a highly concrete assessment

87
00:03:13.560 --> 00:03:14.920
of legitimate interests.

88
00:03:14.920 --> 00:03:16.200
- So they can't just make something up?

89
00:03:16.200 --> 00:03:17.840
- No, they can't just wave a hand.

90
00:03:17.840 --> 00:03:19.720
They have to actually prove the necessity

91
00:03:19.720 --> 00:03:22.680
of using your data and pass that balancing test.

92
00:03:22.680 --> 00:03:24.280
- Here's where it gets really interesting, though.

93
00:03:24.280 --> 00:03:26.840
What if my data is just sitting publicly

94
00:03:26.840 --> 00:03:27.840
on a public forum?

95
00:03:27.840 --> 00:03:28.960
- Like an open profile.

96
00:03:28.960 --> 00:03:31.600
- Yeah, does the company just get a free pass to scrape it

97
00:03:31.600 --> 00:03:33.920
because I didn't hide it behind a private firewall?

98
00:03:33.920 --> 00:03:34.840
- Not at all.

99
00:03:34.840 --> 00:03:37.920
Public data is not unrestricted material.

100
00:03:37.920 --> 00:03:41.080
Just because your data is publicly accessible online,

101
00:03:41.080 --> 00:03:44.440
absolutely does not remove the conditions of the GDPR.

102
00:03:44.440 --> 00:03:45.280
- Oh, wow.

103
00:03:45.280 --> 00:03:46.120
Okay.

104
00:03:46.120 --> 00:03:49.560
- EDPB 28/2024 makes it very clear

105
00:03:49.560 --> 00:03:52.320
that an AI model trained with personal data

106
00:03:52.320 --> 00:03:54.840
is not automatically anonymous.

107
00:03:54.840 --> 00:03:57.360
- So practically speaking,

108
00:03:57.360 --> 00:03:59.840
if deleting my account doesn't actually remove

109
00:03:59.840 --> 00:04:02.680
my pass post from an AI's training data,

110
00:04:02.680 --> 00:04:05.480
what should you, the listener, actually do?

111
00:04:05.480 --> 00:04:08.520
- The Law Right newsletter offers very specific advice here.

112
00:04:08.520 --> 00:04:11.600
First, you need to understand that a request for erasure,

113
00:04:11.600 --> 00:04:12.960
like deleting your account,

114
00:04:12.960 --> 00:04:16.200
is entirely different from an objection.

115
00:04:16.200 --> 00:04:18.800
- Because deleting it doesn't prove the AI model

116
00:04:18.800 --> 00:04:21.520
was retrained to forget you, right?

117
00:04:21.520 --> 00:04:22.360
- Exactly.

118
00:04:22.360 --> 00:04:23.760
Think of it this way.

119
00:04:23.760 --> 00:04:25.560
Deleting your account is like taking your cake

120
00:04:25.560 --> 00:04:27.120
out of the bakery window.

121
00:04:27.120 --> 00:04:27.960
- Okay.

122
00:04:27.960 --> 00:04:29.720
- But an objection is stopping them

123
00:04:29.720 --> 00:04:32.720
from using your secret recipe in the first place.

124
00:04:32.720 --> 00:04:35.200
AI models don't automatically unlearn data

125
00:04:35.200 --> 00:04:37.000
just because the source file is deleted.

126
00:04:37.000 --> 00:04:38.240
- Uh-huh.

127
00:04:38.240 --> 00:04:40.000
Okay, so pulling the cake from the window

128
00:04:40.000 --> 00:04:42.760
doesn't delete the recipe from their files.

129
00:04:42.760 --> 00:04:45.080
What's the actual right move then?

130
00:04:45.080 --> 00:04:47.880
- First, identify the relevant privacy notice.

131
00:04:47.880 --> 00:04:51.520
You wanna find their stated purpose and legal basis.

132
00:04:51.520 --> 00:04:54.320
Then make a precisely targeted request

133
00:04:54.320 --> 00:04:57.200
objecting to that specific AI training.

134
00:04:57.200 --> 00:04:58.920
- Instead of just hitting delete account

135
00:04:58.920 --> 00:05:00.200
and hoping for the best.

136
00:05:00.200 --> 00:05:01.520
- Exactly.

137
00:05:01.520 --> 00:05:03.920
And make sure to keep dated copies of your request

138
00:05:03.920 --> 00:05:05.440
and their response.

139
00:05:05.440 --> 00:05:06.680
- So let me get this straight.

140
00:05:06.680 --> 00:05:10.160
When I explain my particular situation for the subjection,

141
00:05:10.160 --> 00:05:12.000
should I be sending them evidence

142
00:05:12.000 --> 00:05:15.600
because it feels like a hilarious and terrifying Catch-22

143
00:05:15.600 --> 00:05:17.760
if I have to send sensitive documents

144
00:05:17.760 --> 00:05:19.080
just to prove my identity?

145
00:05:19.080 --> 00:05:20.360
- It is a Catch-22.

146
00:05:20.360 --> 00:05:21.960
- Right, you'd basically just be handing them

147
00:05:21.960 --> 00:05:23.080
more data to train on.

148
00:05:23.080 --> 00:05:25.920
- Which is exactly why the newsletter explicitly warns

149
00:05:25.920 --> 00:05:29.360
against needlessly supplying new sensitive documents

150
00:05:29.360 --> 00:05:30.840
just to prove your point.

151
00:05:30.840 --> 00:05:33.920
You do not wanna accidentally give them more personal data

152
00:05:33.920 --> 00:05:35.440
in your attempt to protect it.

153
00:05:35.440 --> 00:05:37.920
- Okay, so the core message for you today.

154
00:05:37.920 --> 00:05:40.960
Take a breath, understand the specific processing

155
00:05:40.960 --> 00:05:44.600
and current laws, and don't panic over proposed draft.

156
00:05:44.600 --> 00:05:45.440
- Definitely.

157
00:05:45.440 --> 00:05:47.880
- Your legal protections haven't vanished overnight.

158
00:05:47.880 --> 00:05:48.720
- And looking ahead,

159
00:05:48.720 --> 00:05:50.760
it really raises a fascinating question.

160
00:05:50.760 --> 00:05:53.080
We spend so much time talking about the mechanics

161
00:05:53.080 --> 00:05:57.080
of opting out, but we rarely consider the downstream effects

162
00:05:57.080 --> 00:05:58.560
on the technology itself.

163
00:05:58.560 --> 00:06:01.960
- Which leaves you with a final provocative thought to ponder.

164
00:06:01.960 --> 00:06:04.720
If our personal data ultimately shapes the minds

165
00:06:04.720 --> 00:06:06.720
and behaviors of future AI,

166
00:06:06.720 --> 00:06:09.200
how might the AI's understanding of humanity

167
00:06:09.200 --> 00:06:12.200
become totally skewed if millions of users

168
00:06:12.200 --> 00:06:14.720
successfully exercise their right to object?

169
00:06:14.720 --> 00:06:16.440
- Yeah, by removing their unique voices

170
00:06:16.440 --> 00:06:17.640
from the training pool.

171
00:06:17.640 --> 00:06:18.520
- Exactly.

172
00:06:18.520 --> 00:06:20.840
Do we inadvertently leave the future of AI

173
00:06:20.840 --> 00:06:22.280
to be shaped only by those

174
00:06:22.280 --> 00:06:24.920
who just don't care about their privacy?

175
00:06:24.920 --> 00:06:26.480
It's definitely something to think about

176
00:06:26.480 --> 00:06:27.760
the next time you see a headline

177
00:06:27.760 --> 00:06:29.160
about your digital rights.
