1
00:00:00,000 --> 00:00:03,760
You know, I think we all know that feeling. You sign up for something specific,

2
00:00:03,760 --> 00:00:04,160
maybe a

3
00:00:04,160 --> 00:00:10,960
local library newsletter or a beta test for some software, and then just a few

4
00:00:10,960 --> 00:00:11,840
months down the line,

5
00:00:11,840 --> 00:00:15,680
your main email address, the one you use for everything, starts getting absolutely

6
00:00:15,680 --> 00:00:16,080
hammered

7
00:00:16,080 --> 00:00:21,780
with junk. Pyramid schemes, weird offers, it's annoying, sure. But what's worse,

8
00:00:21,780 --> 00:00:22,240
honestly,

9
00:00:22,240 --> 00:00:26,670
is that sinking feeling when a big company you trusted, maybe even shopped with,

10
00:00:26,670 --> 00:00:27,520
announces a data

11
00:00:27,520 --> 00:00:31,660
breach, and suddenly your personal email is out there floating around on the dark

12
00:00:31,660 --> 00:00:32,400
web, that's not

13
00:00:32,400 --> 00:00:36,760
just spam anymore, is it? That's like a permanent dent in your identity's armor. It

14
00:00:36,760 --> 00:00:37,520
really is. It's

15
00:00:37,520 --> 00:00:42,390
that moment, the cost of all this digital convenience really hits you. You traded a

16
00:00:42,390 --> 00:00:42,960
piece of your

17
00:00:42,960 --> 00:00:46,620
permanent online identity just to log into some service. So our mission today is

18
00:00:46,620 --> 00:00:47,280
basically to

19
00:00:47,280 --> 00:00:50,540
give you, the listener, a really solid tool to take back control. We're doing a

20
00:00:50,540 --> 00:00:51,280
deep dive into

21
00:00:51,280 --> 00:00:55,010
anonymous email forwarding, and we're focusing specifically on the documentation

22
00:00:55,010 --> 00:00:55,520
from a key

23
00:00:55,520 --> 00:01:01,200
player in this space, Addy.io. Exactly. This isn't about constantly cycling through

24
00:01:01,200 --> 00:01:01,760
new email

25
00:01:01,760 --> 00:01:05,800
addresses, which is just exhausting. It's about building an impenetrable shield

26
00:01:05,800 --> 00:01:06,480
around the one

27
00:01:06,480 --> 00:01:11,390
you already have. We want to give you a really clear, step-by-step guide to how

28
00:01:11,390 --> 00:01:12,160
these email

29
00:01:12,160 --> 00:01:17,560
aliases work. Make this whole privacy thing feel accessible, so you understand not

30
00:01:17,560 --> 00:01:18,560
just how to use

31
00:01:18,560 --> 00:01:23,840
it, but why it's fundamentally better than just using those throwaway email sites.

32
00:01:23,840 --> 00:01:24,320
Yeah, the goal

33
00:01:24,320 --> 00:01:28,360
is for you to finish this deep dive feeling confident enough to actually set this

34
00:01:28,360 --> 00:01:28,720
up, like

35
00:01:28,720 --> 00:01:32,090
right away. Put that protective layer in place. Okay, but before we get into the

36
00:01:32,090 --> 00:01:32,800
nuts and bolts,

37
00:01:32,800 --> 00:01:36,960
we really want to thank the supporter of this deep dive, Safe Server. They handle

38
00:01:36,960 --> 00:01:37,360
the hosting

39
00:01:37,360 --> 00:01:41,290
for this kind of software and can support your digital transformation. You can find

40
00:01:41,290 --> 00:01:41,520
more

41
00:01:41,520 --> 00:01:47,900
information at www.safeserver.de. All right, let's start right at the beginning.

42
00:01:47,900 --> 00:01:48,800
When we say email

43
00:01:48,800 --> 00:01:52,140
alias here, what are we actually talking about? Because, you know, a lot of people

44
00:01:52,140 --> 00:01:52,800
just think of

45
00:01:52,800 --> 00:01:58,240
an alias as like an extra address tacked onto their Gmail or Outlook account. Right,

46
00:01:58,240 --> 00:01:58,800
and that's the

47
00:01:58,800 --> 00:02:03,940
key difference here. In this context, an alias isn't just another inbox. It's a

48
00:02:03,940 --> 00:02:05,200
dedicated forwarding

49
00:02:05,200 --> 00:02:09,970
address. It acts as a protective layer, a true middleman, really. It shields your

50
00:02:09,970 --> 00:02:10,640
real email

51
00:02:10,640 --> 00:02:14,600
address, the recipient from the websites you interact with. So when you sign up for

52
00:02:14,600 --> 00:02:15,200
something,

53
00:02:15,200 --> 00:02:19,930
you give them the alias if they get breached. Your actual email address is safe. It's

54
00:02:19,930 --> 00:02:21,040
never exposed.

55
00:02:21,040 --> 00:02:25,640
Okay, that's clear. And the guide we looked at, it lays out a pretty simple three-step

56
00:02:25,640 --> 00:02:26,320
process to get

57
00:02:26,320 --> 00:02:30,440
going, right? Even if this sounds kind of complex at first. Exactly. Step one is

58
00:02:30,440 --> 00:02:31,600
just registering.

59
00:02:31,600 --> 00:02:35,440
You pick a username, let's say John Doe for the example. Now what's crucial here is

60
00:02:35,440 --> 00:02:35,920
that this

61
00:02:35,920 --> 00:02:43,200
username creates a unique sub-domain structure for you. Something like at JohnDoe.Ananaddy.com.

62
00:02:43,200 --> 00:02:46,960
See that asterisk? That's really important. It signifies a wild card. It means you

63
00:02:46,960 --> 00:02:47,280
don't have

64
00:02:47,280 --> 00:02:51,070
to go and manually create every single alias you might ever want to use beforehand.

65
00:02:51,070 --> 00:02:52,400
Oh, okay. And

66
00:02:52,400 --> 00:02:56,380
I guess this is where the first bit of discipline comes in for anonymity. You

67
00:02:56,380 --> 00:02:57,680
absolutely must use a

68
00:02:57,680 --> 00:03:02,070
username that has zero connection to your real name, your professional life, any

69
00:03:02,070 --> 00:03:02,640
other online

70
00:03:02,640 --> 00:03:08,060
handles you use. Precisely. If you use JohnDoe everywhere else, well, you've just

71
00:03:08,060 --> 00:03:08,800
handed over

72
00:03:08,800 --> 00:03:12,470
a perfect digital fingerprint linking all these new aliases. You really want

73
00:03:12,470 --> 00:03:13,680
something random here.

74
00:03:14,400 --> 00:03:18,800
A string of characters, baby. Got it. Totally random username. So we've got the

75
00:03:18,800 --> 00:03:19,120
domain

76
00:03:19,120 --> 00:03:24,470
structure set up. Step two is actually creating the aliases. How's this better than

77
00:03:24,470 --> 00:03:25,120
a disposable

78
00:03:25,120 --> 00:03:29,320
email? It's the on-the-fly creation. This is the magic bit. Let's say you're

79
00:03:29,320 --> 00:03:30,240
signing up for that

80
00:03:30,240 --> 00:03:35,220
view.js blog you mentioned. You don't need to log into your adi.io dashboard first.

81
00:03:35,220 --> 00:03:35,760
Nope. You

82
00:03:35,760 --> 00:03:41,280
just invent an alias right there in the signup form, like viewjs at johndoe.anitadi.com.

83
00:03:41,280 --> 00:03:41,440
The

84
00:03:41,440 --> 00:03:45,350
system is smart enough to see that new alias when the first email arrives, and it

85
00:03:45,350 --> 00:03:46,000
automatically

86
00:03:46,000 --> 00:03:49,790
creates it in your account instantly. Zero friction when you need it. Okay. That is

87
00:03:49,790 --> 00:03:50,320
smooth,

88
00:03:50,320 --> 00:03:54,080
removes all the hassle, and the huge benefit, the real payoff. Even though that

89
00:03:54,080 --> 00:03:55,280
email lands in my

90
00:03:55,280 --> 00:03:59,610
normal inbox, my Gmail or whatever, and I can hit reply, the sender never sees my

91
00:03:59,610 --> 00:04:00,640
real address.

92
00:04:00,640 --> 00:04:04,720
Never. It's completely masked by the forwarding service. Your reply goes back

93
00:04:04,720 --> 00:04:05,360
through them using

94
00:04:05,360 --> 00:04:10,330
the alias address. Which leads perfectly into step three, right? Management.

95
00:04:10,330 --> 00:04:11,680
Control. This is where

96
00:04:11,680 --> 00:04:15,140
the power to fight spam and track breaches comes in. Exactly. This is where you

97
00:04:15,140 --> 00:04:16,160
leverage having all

98
00:04:16,160 --> 00:04:19,850
those unique aliases. Okay, let's play it out. I signed up for that Vue.js

99
00:04:19,850 --> 00:04:21,520
newsletter with Vue.js

100
00:04:21,520 --> 00:04:28,000
at jondo.inonity.com. Suddenly, that specific alias starts getting bombarded with

101
00:04:28,000 --> 00:04:28,800
crypto scams

102
00:04:28,800 --> 00:04:33,800
from some totally random company. Right. That tells you immediately. Vue.js either

103
00:04:33,800 --> 00:04:34,640
got hacked,

104
00:04:34,640 --> 00:04:38,680
or they sold your address. Maybe both. Now in your dashboard, you have two main

105
00:04:38,680 --> 00:04:39,840
ways to deal with it.

106
00:04:39,840 --> 00:04:43,200
Tactically different. First, you can just deactivate the alias, flick a switch.

107
00:04:43,200 --> 00:04:44,000
That

108
00:04:44,000 --> 00:04:49,360
tells the system to silently intercept any more emails sent to Vue.js at jondo.inonity.com

109
00:04:49,360 --> 00:04:54,480
and just discard them. Poof. Gone. The center gets no notification. Silent discard.

110
00:04:54,480 --> 00:04:55,040
I can see the

111
00:04:55,040 --> 00:04:58,910
appeal less noise, but why would I want the second option? The guide says you can

112
00:04:58,910 --> 00:04:59,600
also delete the

113
00:04:59,600 --> 00:05:03,450
alias. Deleting makes the system reject the email with an error, right? Like

114
00:05:03,450 --> 00:05:04,720
address doesn't exist.

115
00:05:04,720 --> 00:05:08,150
Why tell a spammer as anything? That's a great question. It really depends on your

116
00:05:08,150 --> 00:05:09,120
strategy.

117
00:05:09,120 --> 00:05:13,410
Deactivation, the silent discard, is good if you think maybe the sender will try

118
00:05:13,410 --> 00:05:14,320
again. Or maybe

119
00:05:14,320 --> 00:05:18,450
you want the original source, Vue.js, to think the address is still valid even

120
00:05:18,450 --> 00:05:20,000
while you ignore them.

121
00:05:20,000 --> 00:05:25,440
But deleting, that sends a clear bounce message. For automated spam systems, that

122
00:05:25,440 --> 00:05:26,160
often triggers

123
00:05:26,160 --> 00:05:29,910
them to remove the address from their lists entirely. It saves bandwidth,

124
00:05:29,910 --> 00:05:31,360
processing power,

125
00:05:31,360 --> 00:05:36,080
it's more aggressive, but it's definitive. Cleans up their lists, potentially.

126
00:05:36,080 --> 00:05:39,180
How would that make sense? Different tactics for different situations. But either

127
00:05:39,180 --> 00:05:39,440
way,

128
00:05:39,440 --> 00:05:44,720
the main point is crystal clear. Because I used a unique alias just for Vue.js,

129
00:05:44,720 --> 00:05:49,000
the second that alias gets unrelated junk, I know exactly who leaked or sold my

130
00:05:49,000 --> 00:05:50,240
data instantly.

131
00:05:50,240 --> 00:05:50,960
No guesswork.

132
00:05:50,960 --> 00:05:55,120
That's the real power. It turns a data breach from this vague scary thing into

133
00:05:55,120 --> 00:05:55,520
something

134
00:05:55,520 --> 00:05:57,360
actionable. You have concrete information.

135
00:05:57,360 --> 00:06:01,320
And making this even easier day to day, the notes mention some handy tools. Open

136
00:06:01,320 --> 00:06:02,320
source ones.

137
00:06:02,320 --> 00:06:06,990
Oh yeah. They've got native mobile apps, open source for iOS and Android. So you

138
00:06:06,990 --> 00:06:07,360
can manage

139
00:06:07,360 --> 00:06:10,940
things on the go. But maybe even more useful is the browser extension. Works on

140
00:06:10,940 --> 00:06:11,360
pretty much

141
00:06:11,360 --> 00:06:17,350
everything. Firefox, Chrome, Edge, Safari, Brave. And that lets you generate a new

142
00:06:17,350 --> 00:06:18,560
unique alias with

143
00:06:18,560 --> 00:06:22,400
just like a couple of clicks right when you're on a signup form. No need to think

144
00:06:22,400 --> 00:06:22,960
of a name

145
00:06:22,960 --> 00:06:27,840
or copy paste anything. Super convenient. Okay. So we've tackled controlling who

146
00:06:27,840 --> 00:06:28,640
emails us and

147
00:06:28,640 --> 00:06:33,280
figuring out where leaks happen, but there's still this potential issue of, well,

148
00:06:33,280 --> 00:06:34,000
who I am.

149
00:06:34,000 --> 00:06:39,120
If I have hundreds of aliases, but they're all under at jondo.anonaddy.com, aren't

150
00:06:39,120 --> 00:06:40,000
I still linking

151
00:06:40,000 --> 00:06:43,120
everything back to that one John Doe username? If that service got compromised,

152
00:06:43,120 --> 00:06:43,760
wouldn't everything

153
00:06:43,760 --> 00:06:47,200
be linked? How do I blend in more? That's definitely the next level of thinking

154
00:06:47,200 --> 00:06:51,550
about privacy. And yeah, anonymity options are key. The service handles this mainly

155
00:06:51,550 --> 00:06:52,640
in two ways.

156
00:06:52,640 --> 00:06:57,120
First, they offer random unique aliases that use a shared domain. So instead of dot

157
00:06:57,120 --> 00:06:58,720
at johndoe.anonaddy.com,

158
00:06:58,720 --> 00:07:05,440
it might look like by 481904 at anonaddy.me. Total gibberish. Anonaddy.me. That's

159
00:07:05,440 --> 00:07:06,000
the important part.

160
00:07:06,000 --> 00:07:11,520
The domain. Exactly. Because that .me domain or similar shared ones they offer is

161
00:07:11,520 --> 00:07:12,320
used by

162
00:07:12,320 --> 00:07:18,480
everyone on the service who chooses that option. So an alias like by 481904 at anonaddy.me

163
00:07:18,480 --> 00:07:19,440
cannot

164
00:07:19,440 --> 00:07:23,340
be traced back specifically to your johndoe account. You just look like any other

165
00:07:23,340 --> 00:07:23,840
user.

166
00:07:23,840 --> 00:07:28,150
That's real anonymity from external observers. Okay. That covers external privacy.

167
00:07:28,150 --> 00:07:28,480
But what if

168
00:07:28,480 --> 00:07:31,960
I just want to organize things better for myself, keep work and personal stuff

169
00:07:31,960 --> 00:07:32,960
separate? Right. And

170
00:07:32,960 --> 00:07:36,800
that's the second option, usually on the paid plans. You can add additional usernames.

171
00:07:36,800 --> 00:07:37,360
So johndoe

172
00:07:37,360 --> 00:07:41,830
might be your personal one. But you could add, say, janeworkerb as another username

173
00:07:41,830 --> 00:07:42,160
under your

174
00:07:42,160 --> 00:07:49,120
account. Then all your work-related signups use aliases like client A at jane-worker-b.anonaddy.com.

175
00:07:49,600 --> 00:07:53,100
It compartmentalizes everything logically. Only you know those usernames are linked

176
00:07:53,100 --> 00:07:53,680
to the same

177
00:07:53,680 --> 00:07:58,330
account. Nice. Okay, let's shift gears to maybe the most advanced feature mentioned.

178
00:07:58,330 --> 00:07:59,200
Encryption.

179
00:07:59,200 --> 00:08:03,540
GPG open PGP. That sounds complicated for a beginner. What does this actually do

180
00:08:03,540 --> 00:08:03,840
beyond

181
00:08:03,840 --> 00:08:08,150
just hiding my email address? Isn't that enough? It adds another very powerful

182
00:08:08,150 --> 00:08:09,360
layer of security.

183
00:08:09,360 --> 00:08:15,210
Think of it as your ultimate privacy blanket. Basically, you generate a GPG key

184
00:08:15,210 --> 00:08:16,400
pair, a public

185
00:08:16,400 --> 00:08:20,850
and a private key. You upload your public key to the alias service. From then on,

186
00:08:20,850 --> 00:08:21,760
every single email

187
00:08:21,760 --> 00:08:25,780
forwarded to you through the alias service gets instantly encrypted using that

188
00:08:25,780 --> 00:08:26,720
public key before

189
00:08:26,720 --> 00:08:31,410
it even hits your main inbox. But why? If it's going to my secure Gmail or Outlook

190
00:08:31,410 --> 00:08:32,000
anyway,

191
00:08:32,000 --> 00:08:35,120
it doesn't matter. Aren't they already protecting my emails? Well, this protects

192
00:08:35,120 --> 00:08:35,920
you from inbox

193
00:08:35,920 --> 00:08:40,660
snooping. If the email content arrives encrypted, only you with your private key

194
00:08:40,660 --> 00:08:41,760
stored securely on

195
00:08:41,760 --> 00:08:45,300
your own device can decrypt and read it. It means your email provider, Google,

196
00:08:45,300 --> 00:08:46,720
Microsoft, whoever,

197
00:08:46,720 --> 00:08:50,310
literally cannot read the content of those forwarded messages, even if their

198
00:08:50,310 --> 00:08:50,720
policies

199
00:08:50,720 --> 00:08:54,690
allow scanning or if they suffer an internal breach. You can even choose to encrypt

200
00:08:54,690 --> 00:08:55,360
the subject

201
00:08:55,360 --> 00:09:00,290
line too, which often leaks sensitive info. It's maximum obfuscation. Okay, I

202
00:09:00,290 --> 00:09:01,440
understand the why.

203
00:09:01,440 --> 00:09:05,280
But practically speaking, does this add a ton of friction? Like, do I have to

204
00:09:05,280 --> 00:09:06,160
manually decrypt

205
00:09:06,160 --> 00:09:10,850
every single email? This is only for the super paranoid, technically savvy user.

206
00:09:10,850 --> 00:09:11,760
That's a fair point.

207
00:09:11,760 --> 00:09:15,650
There's definitely an initial setup step, generating the keys, configuring your

208
00:09:15,650 --> 00:09:16,400
email client.

209
00:09:16,400 --> 00:09:22,480
But modern email clients, like Thunderbird or dedicated GPG tools, can handle the

210
00:09:22,480 --> 00:09:22,960
decryption

211
00:09:22,960 --> 00:09:27,050
pretty seamlessly. Once it's set up, it's mostly automatic. You unlock your key

212
00:09:27,050 --> 00:09:27,920
maybe once per

213
00:09:27,920 --> 00:09:32,260
session. For people really serious about privacy, that initial setup is a small

214
00:09:32,260 --> 00:09:33,120
price to pay for

215
00:09:33,120 --> 00:09:37,050
knowing nobody but them can read their mail. That helps put it in perspective. And

216
00:09:37,050 --> 00:09:37,600
there was this

217
00:09:37,600 --> 00:09:42,110
tiny detail in the docs about replying when using GPG. Something about stripping

218
00:09:42,110 --> 00:09:42,960
the public key. Why

219
00:09:42,960 --> 00:09:48,980
is that important? Oh yes, that's crucial. It's about preventing accidental self-docsing.

220
00:09:48,980 --> 00:09:49,120
Your

221
00:09:49,120 --> 00:09:54,000
public GPG key often contains metadata embedded within it, typically your real name

222
00:09:54,000 --> 00:09:54,800
and your real

223
00:09:54,800 --> 00:09:58,300
email address. If the alias service didn't automatically remove your public key

224
00:09:58,300 --> 00:09:58,720
when you

225
00:09:58,720 --> 00:10:03,520
replied from alias, you'd be broadcasting your hidden real email address with every

226
00:10:03,520 --> 00:10:04,400
reply.

227
00:10:04,400 --> 00:10:09,080
It completely undermines the alias. Stripping the key is a vital little detail that

228
00:10:09,080 --> 00:10:09,520
shows they

229
00:10:09,520 --> 00:10:13,200
understand operational security. That kind of attention to detail is definitely

230
00:10:13,200 --> 00:10:13,840
reassuring.

231
00:10:13,840 --> 00:10:18,400
Okay, before we wrap up, let's quickly touch on the practical side. They offer a

232
00:10:18,400 --> 00:10:19,120
free plan,

233
00:10:19,120 --> 00:10:23,600
right? Seems pretty generous. It really is, especially for a privacy-focused tool.

234
00:10:23,600 --> 00:10:28,640
The free tier gives you unlimited standard aliases, the ETA, at your username, dot

235
00:10:28,640 --> 00:10:29,760
whatever kind,

236
00:10:29,760 --> 00:10:34,220
and lets you forward to one main recipient address. The main limits are bandwidth

237
00:10:34,220 --> 00:10:34,240
10

238
00:10:34,240 --> 00:10:39,600
millibies a month, which they figure is about 140 average emails. And you get 10 of

239
00:10:39,600 --> 00:10:40,080
those shared

240
00:10:40,080 --> 00:10:45,140
domain aliases, the anonymous dot at anonymity.me type. If you need more bandwidth

241
00:10:45,140 --> 00:10:45,760
or want to

242
00:10:45,760 --> 00:10:49,420
forward to multiple real addresses or use custom domains, then you look at the paid

243
00:10:49,420 --> 00:10:49,920
plans.

244
00:10:49,920 --> 00:10:53,700
And for people who are naturally wary of trusting any third party, especially with

245
00:10:53,700 --> 00:10:54,640
privacy,

246
00:10:54,640 --> 00:10:58,400
the whole thing is open source. Correct. Full transparency, you can audit the code

247
00:10:58,400 --> 00:10:59,200
yourself.

248
00:10:59,200 --> 00:11:02,570
And if you're technically inclined, you can even self-host the entire application

249
00:11:02,570 --> 00:11:02,800
on your

250
00:11:02,800 --> 00:11:07,040
own server. Take complete control. They also mentioned their infrastructure primary

251
00:11:07,040 --> 00:11:07,280
server

252
00:11:07,280 --> 00:11:10,960
in the Netherlands running on wind power back up in Poland. That level of

253
00:11:10,960 --> 00:11:12,080
transparency is good to

254
00:11:12,080 --> 00:11:17,080
see. So putting it all together, this knowledge really is quite powerful. You can

255
00:11:17,080 --> 00:11:17,840
basically build

256
00:11:17,840 --> 00:11:22,730
this flexible digital shield, pinpoint data leaks the moment they happen, kill spam

257
00:11:22,730 --> 00:11:23,360
with surgical

258
00:11:23,360 --> 00:11:27,530
precision, and even use strong encryption. So literally only you can read your

259
00:11:27,530 --> 00:11:28,400
emails. That's

260
00:11:28,400 --> 00:11:32,350
a huge step up in control. It absolutely is. It moves you from being just a passive

261
00:11:32,350 --> 00:11:32,800
target

262
00:11:32,800 --> 00:11:37,430
online to someone actively managing and protecting your digital identity. It's very

263
00:11:37,430 --> 00:11:37,920
empowering.

264
00:11:37,920 --> 00:11:42,230
Now, one interesting thing we noticed reviewing the source material. While it's all

265
00:11:42,230 --> 00:11:42,880
about privacy

266
00:11:42,880 --> 00:11:47,230
protection, they do have terms and conditions designed to prevent abuse. For

267
00:11:47,230 --> 00:11:47,600
instance, they

268
00:11:47,600 --> 00:11:52,160
explicitly say, don't create multiple free accounts. And interestingly, they warn

269
00:11:52,160 --> 00:11:52,480
against

270
00:11:52,480 --> 00:11:56,560
using aliases to create large numbers of accounts on other websites. That sounds

271
00:11:56,560 --> 00:11:57,600
like an anti-botting

272
00:11:57,600 --> 00:12:02,000
rule. That does raise an interesting point for you, the listener, to think about.

273
00:12:02,000 --> 00:12:02,400
We've spent

274
00:12:02,400 --> 00:12:05,930
this whole deep dive talking about the technical ways to boost your privacy and

275
00:12:05,930 --> 00:12:06,720
security using

276
00:12:06,720 --> 00:12:11,430
these tools. But where's the line? Where does legitimate, necessary privacy

277
00:12:11,430 --> 00:12:12,720
protection end,

278
00:12:12,720 --> 00:12:16,560
and potentially abusing the service according to their rules begin? Something to

279
00:12:16,560 --> 00:12:17,040
definitely

280
00:12:17,040 --> 00:12:21,920
mull over as you start using aliases yourself. A very interesting thought to end on.

281
00:12:21,920 --> 00:12:22,160
We really

282
00:12:22,160 --> 00:12:26,080
hope this deep dive has brought clarity to anonymous email forwarding and shown you

283
00:12:26,080 --> 00:12:26,240
how

284
00:12:26,240 --> 00:12:30,190
to take back control of your inbox. And thanks once more to our supporter, Safe

285
00:12:30,190 --> 00:12:31,040
Server. They're

286
00:12:31,040 --> 00:12:37,040
dedicated to hosting and digital transformation. Find out more at www.safeserver.de.