1
00:00:00,000 --> 00:00:03,760
Welcome back to the Deep Dive, your essential shortcut to being well-informed.

2
00:00:03,760 --> 00:00:07,840
Before we jump into today's material, we really have to take a moment and thank the

3
00:00:07,840 --> 00:00:12,370
supporter that makes these deep dives possible, SafeServer. SafeServer cares for

4
00:00:12,370 --> 00:00:12,800
the hosting of

5
00:00:12,800 --> 00:00:17,390
this software and supports digital transformation. They ensure innovative projects,

6
00:00:17,390 --> 00:00:17,840
especially those

7
00:00:17,840 --> 00:00:21,130
focused on security and privacy like what we're discussing today, have the

8
00:00:21,130 --> 00:00:22,480
resources they need.

9
00:00:22,480 --> 00:00:26,240
You can find out more and support their mission at www.safeserver.de.

10
00:00:27,440 --> 00:00:30,720
So today, we're embarking on a pretty fascinating deep dive into something,

11
00:00:30,720 --> 00:00:35,520
well, incredibly common, editing PDFs. But this isn't just about any tool. We're

12
00:00:35,520 --> 00:00:36,160
looking at

13
00:00:36,160 --> 00:00:39,360
BentopPDF. And the core of our discussion, really, it revolves around a

14
00:00:39,360 --> 00:00:40,880
revolutionary concept,

15
00:00:40,880 --> 00:00:44,800
something that fundamentally changes how you should think about document security.

16
00:00:44,800 --> 00:00:48,320
I mean, think about it. Every day, you or maybe your colleagues, you upload highly

17
00:00:48,320 --> 00:00:48,640
sensitive

18
00:00:48,640 --> 00:00:53,790
information contracts, health records, financial reports to online services, often

19
00:00:53,790 --> 00:00:54,480
just for simple

20
00:00:54,480 --> 00:00:59,370
stuff like merging two documents or making a file smaller. And that upload, that

21
00:00:59,370 --> 00:01:00,000
tiny moment when

22
00:01:00,000 --> 00:01:03,500
the file leaves your local machine and hits some remote server, that is the moment

23
00:01:03,500 --> 00:01:04,240
of maximum

24
00:01:04,240 --> 00:01:09,010
vulnerability. Our mission today, really, is to thoroughly unpack this concept of

25
00:01:09,010 --> 00:01:09,920
privacy-first

26
00:01:09,920 --> 00:01:15,210
client-side processing. We're going to show you why this seemingly simple technical

27
00:01:15,210 --> 00:01:15,520
detail,

28
00:01:15,520 --> 00:01:19,920
this architecture, is actually the key to enterprise-level security for pretty much

29
00:01:19,920 --> 00:01:23,800
anyone needing to manipulate documents on the fly. It all boils down to one

30
00:01:23,800 --> 00:01:24,800
question. What

31
00:01:24,800 --> 00:01:28,610
of your sensitive files never actually left your computer? Okay, let's unpack this

32
00:01:28,610 --> 00:01:29,280
then. For the

33
00:01:29,280 --> 00:01:33,270
listener who might not be, you know, deep into network architecture, what is the

34
00:01:33,270 --> 00:01:34,160
default risk?

35
00:01:34,160 --> 00:01:38,320
The risk inherent in, say, 99 percent of online PDF tools, what we're calling the

36
00:01:38,320 --> 00:01:39,360
server-side model.

37
00:01:39,360 --> 00:01:43,010
Right. So what's happening in that standard model is pretty straightforward. When

38
00:01:43,010 --> 00:01:43,840
you hit upload,

39
00:01:43,840 --> 00:01:48,720
your document gets packaged up, travels across the internet to the provider's

40
00:01:48,720 --> 00:01:49,440
server farm,

41
00:01:49,440 --> 00:01:53,920
somewhere out there. That server then runs the code, you know, merging, splitting,

42
00:01:53,920 --> 00:01:54,400
compressing,

43
00:01:54,400 --> 00:01:59,690
whatever it is, and then it sends the finished file back to you. The key risk, the

44
00:01:59,690 --> 00:02:00,880
fundamental risk,

45
00:02:00,880 --> 00:02:05,560
is that your file, even for a short time, maybe two seconds, it resided on a

46
00:02:05,560 --> 00:02:06,720
machine owned and

47
00:02:06,720 --> 00:02:11,040
operated by someone else, a third party. So even if the company says, oh, we

48
00:02:11,040 --> 00:02:12,320
deleted it immediately,

49
00:02:12,320 --> 00:02:16,460
they still possessed it, even for a moment. And that window of possession, that's

50
00:02:16,460 --> 00:02:17,040
the danger zone.

51
00:02:17,040 --> 00:02:20,960
It's a vulnerability. It could be server hacks, maybe internal data breaches, or

52
00:02:20,960 --> 00:02:21,520
even just

53
00:02:21,520 --> 00:02:26,190
unauthorized data logging by the company itself. Once it leaves your device, you've

54
00:02:26,190 --> 00:02:26,560
basically

55
00:02:26,560 --> 00:02:31,350
outsourced the control. Precisely. And that's exactly why the central innovation

56
00:02:31,350 --> 00:02:32,000
here, the real

57
00:02:32,000 --> 00:02:37,190
aha moment with bent-out PDF, is this absolute commitment to being 100% client-side.

58
00:02:37,190 --> 00:02:37,520
It's like

59
00:02:37,520 --> 00:02:41,060
the processing factory is brought right to your desktop. The file never leaves your

60
00:02:41,060 --> 00:02:42,080
device, never.

61
00:02:42,080 --> 00:02:45,920
Okay, now I get the security argument that makes sense. But if the processing is

62
00:02:45,920 --> 00:02:46,960
happening locally,

63
00:02:46,960 --> 00:02:51,340
right there in my browser, doesn't that raise some immediate, maybe skeptical

64
00:02:51,340 --> 00:02:52,560
questions, like about

65
00:02:52,560 --> 00:02:58,280
speed and capability? Traditionally, we rely on these massive server farms because,

66
00:02:58,280 --> 00:02:58,720
well, they have

67
00:02:58,720 --> 00:03:03,360
more computational power, right? So what gives this tool the ability to handle

68
00:03:03,360 --> 00:03:04,800
potentially massive,

69
00:03:04,800 --> 00:03:10,480
complex PDF tasks locally and instantly? That is the critical question, absolutely.

70
00:03:10,480 --> 00:03:10,960
And it's really

71
00:03:10,960 --> 00:03:14,950
where modern technological progress meets privacy policy. This isn't just some

72
00:03:14,950 --> 00:03:16,160
philosophical choice.

73
00:03:16,160 --> 00:03:20,100
It's a technological leap because BentaPDS leverages the power of modern web

74
00:03:20,100 --> 00:03:21,040
technologies,

75
00:03:21,040 --> 00:03:24,800
specifically these really high-powered JavaScript engines that are in every browser

76
00:03:24,800 --> 00:03:25,760
now and

77
00:03:25,760 --> 00:03:30,290
foundational open source libraries that are highly optimized for the browser. Your

78
00:03:30,290 --> 00:03:30,960
local machine,

79
00:03:30,960 --> 00:03:34,510
your web browser, they're now robust enough to handle that computation. We're just

80
00:03:34,510 --> 00:03:34,960
not limited

81
00:03:34,960 --> 00:03:39,520
by dial-up error browsers anymore, you know? Ah, okay. So here's where it gets

82
00:03:39,520 --> 00:03:40,320
really interesting,

83
00:03:40,320 --> 00:03:45,080
then, because they've eliminated that whole round trip time, the upload delay, the

84
00:03:45,080 --> 00:03:46,240
download delay.

85
00:03:46,240 --> 00:03:50,800
The local processing actually feels instantaneous, is that right? Exactly. The

86
00:03:50,800 --> 00:03:52,080
speed advantage is,

87
00:03:52,080 --> 00:03:56,160
frankly, tremendous because often that processing delay you think you're

88
00:03:56,160 --> 00:03:57,600
experiencing with online

89
00:03:57,600 --> 00:04:03,360
tools, it's actually masked by the latency, the lag of internet transmission. And

90
00:04:03,360 --> 00:04:04,240
here's the crucial

91
00:04:04,240 --> 00:04:07,580
business advantage that stems directly from this architecture because they don't

92
00:04:07,580 --> 00:04:08,480
have the massive

93
00:04:08,480 --> 00:04:12,790
infrastructure costs, right? No huge bandwidth bills, no storage liabilities, none

94
00:04:12,790 --> 00:04:13,360
of the massive

95
00:04:13,360 --> 00:04:17,130
legal exposure that comes with holding user data. They can afford to offer this

96
00:04:17,130 --> 00:04:18,000
what sounds like an

97
00:04:18,000 --> 00:04:22,500
enterprise-grade toolkit as completely free, forever free. Spot on. It's a

98
00:04:22,500 --> 00:04:23,360
foundational

99
00:04:23,360 --> 00:04:26,860
promise. They make no signups, no limits on use, unlimited processing, lightning

100
00:04:26,860 --> 00:04:27,200
speed.

101
00:04:27,200 --> 00:04:31,100
And it all stems from that simple technical fact, they never touch your data. That

102
00:04:31,100 --> 00:04:32,560
transition from

103
00:04:32,560 --> 00:04:37,290
a kind of complex technical security detail to a really practical massive user

104
00:04:37,290 --> 00:04:39,040
advantage, that's

105
00:04:39,040 --> 00:04:43,440
extremely compelling. Now, let's talk about formal security compliance. If a large

106
00:04:43,440 --> 00:04:44,320
institution,

107
00:04:44,320 --> 00:04:48,840
say a hospital or maybe a university, wants to use this, they need, like ironclad

108
00:04:48,840 --> 00:04:49,520
assurance,

109
00:04:49,520 --> 00:04:53,920
it meets global standards. How does this client-side model inherently comply with

110
00:04:53,920 --> 00:04:58,720
regulations like HIPAA, CCPA, GDPR? Yeah, this raises a profoundly important

111
00:04:58,720 --> 00:04:59,440
question, especially

112
00:04:59,440 --> 00:05:04,190
for any C-suite executive or maybe a researcher listening. The short answer is

113
00:05:04,190 --> 00:05:04,640
compliance is

114
00:05:04,640 --> 00:05:08,300
achieved by default simply because they have zero access to the user's data. So the

115
00:05:08,300 --> 00:05:08,960
lack of data

116
00:05:08,960 --> 00:05:12,870
possession itself is the ultimate compliance officer. That's kind of neat. Precisely.

117
00:05:12,870 --> 00:05:14,080
I mean,

118
00:05:14,080 --> 00:05:18,240
if we look at, say, HIPAA, which is all about safeguarding sensitive patient health

119
00:05:18,240 --> 00:05:18,800
information

120
00:05:18,800 --> 00:05:23,960
in the US, if a standard server-side tool touches that patient data, that company

121
00:05:23,960 --> 00:05:24,720
instantly becomes

122
00:05:24,720 --> 00:05:29,350
a business associate. And that means they assume massive legal liability for any

123
00:05:29,350 --> 00:05:30,400
breach. They often

124
00:05:30,400 --> 00:05:35,010
need millions in security measures. But because BentoPDF never sees the file, never

125
00:05:35,010 --> 00:05:35,680
stores it,

126
00:05:35,680 --> 00:05:41,440
never transmits it, that entire liability barrier just vanishes instantly. And that's

127
00:05:41,440 --> 00:05:42,000
why the source

128
00:05:42,000 --> 00:05:46,920
is confirmed. The tool meets GDPR for EU data, CCPA for California privacy rights,

129
00:05:46,920 --> 00:05:47,120
and those

130
00:05:47,120 --> 00:05:51,050
Apto safeguards. They don't have to try really hard to secure your data. They

131
00:05:51,050 --> 00:05:51,600
simply never have

132
00:05:51,600 --> 00:05:55,950
it in the first place. Right. That distinction, the complete absence of liability,

133
00:05:55,950 --> 00:05:56,640
that must be why

134
00:05:56,640 --> 00:06:00,600
institutions are, well, probably quite quick to adopt solutions like this. Okay, so

135
00:06:00,600 --> 00:06:01,200
even if they

136
00:06:01,200 --> 00:06:04,360
don't see the document contents, what about tracking? How do they even know if the

137
00:06:04,360 --> 00:06:04,640
site

138
00:06:04,640 --> 00:06:09,620
is popular or being used? They seem to maintain privacy really vigilantly there too.

139
00:06:09,620 --> 00:06:10,160
They state

140
00:06:10,160 --> 00:06:14,160
very clearly they do not track personal information. They use something called

141
00:06:14,160 --> 00:06:15,600
simple analytics,

142
00:06:15,600 --> 00:06:20,720
but solely for anonymous visit counts. So they can tell, you know, a certain number

143
00:06:20,720 --> 00:06:21,120
of people

144
00:06:21,120 --> 00:06:24,550
visited the site on a given day, but they state clearly, we never know who you are.

145
00:06:24,550 --> 00:06:25,760
It seems to

146
00:06:25,760 --> 00:06:30,440
fulfill their need for basic internal metrics without compromising user anonymity

147
00:06:30,440 --> 00:06:31,040
at all.

148
00:06:31,040 --> 00:06:34,960
And this commitment to transparency, it's beautifully reinforced by the project

149
00:06:34,960 --> 00:06:35,520
being open

150
00:06:35,520 --> 00:06:39,920
source, right? If they claim the files never leave the device, any skeptical

151
00:06:39,920 --> 00:06:40,800
developer can actually

152
00:06:40,800 --> 00:06:44,720
go look at the code and verify that. Absolutely. And the sources highlight this.

153
00:06:44,720 --> 00:06:45,440
The projects on

154
00:06:45,440 --> 00:06:50,610
GitHub, it shows strong community backing over 1.6 thousand stars, 103 forks last I

155
00:06:50,610 --> 00:06:51,280
checked,

156
00:06:51,280 --> 00:06:55,440
all under an Apache 2.0 license. This allows anyone, security firms, curious

157
00:06:55,440 --> 00:06:55,920
developers,

158
00:06:55,920 --> 00:07:00,390
even competitors, to inspect the code base, to confirm that privacy promise is

159
00:07:00,390 --> 00:07:00,720
actually

160
00:07:00,720 --> 00:07:04,360
baked into the code, that there are no secret uploads or transmissions happening.

161
00:07:04,360 --> 00:07:04,880
That level

162
00:07:04,880 --> 00:07:09,450
of verifiable trust, it's paramount in today's security landscape. And we see that

163
00:07:09,450 --> 00:07:10,320
trust reflected

164
00:07:10,320 --> 00:07:14,390
in the user community, don't we? The testimonials are incredibly telling, and they

165
00:07:14,390 --> 00:07:15,040
specifically

166
00:07:15,040 --> 00:07:20,560
focus on that privacy guarantee. I love Sarah L.'s observation. She calls it a lifesaver

167
00:07:20,560 --> 00:07:20,880
for my

168
00:07:20,880 --> 00:07:25,900
freelance work, specifically because she knows her confidential documents never get

169
00:07:25,900 --> 00:07:26,720
uploaded.

170
00:07:26,720 --> 00:07:32,160
That's peace of mind. And Dr. Brickson, the researcher, explicitly says the client-side

171
00:07:32,160 --> 00:07:36,490
processing model is exactly what my institution recommends. That's a powerful

172
00:07:36,490 --> 00:07:37,360
endorsement,

173
00:07:37,360 --> 00:07:40,480
especially from sectors facing huge penalties for breaches.

174
00:07:41,120 --> 00:07:46,000
And we even get a little bit of satirical feedback, which actually emphasizes their

175
00:07:46,000 --> 00:07:49,840
commitment to not tracking. We saw things like one-star reviews from something

176
00:07:49,840 --> 00:07:50,640
called AdTracker

177
00:07:50,640 --> 00:07:54,550
Pro complaining the site is broken because their ad blocker didn't block a single

178
00:07:54,550 --> 00:07:55,040
tracker.

179
00:07:55,040 --> 00:07:55,440
Right.

180
00:07:55,440 --> 00:07:59,280
And another user calling it useless for my data profile. It's kind of a humorous

181
00:07:59,280 --> 00:07:59,920
way to signal,

182
00:07:59,920 --> 00:08:03,950
look, we reject the data harvesting business model that funds so many competing

183
00:08:03,950 --> 00:08:04,880
tools out there.

184
00:08:04,880 --> 00:08:08,710
That really grounds the benefits in reality. Okay, so let's talk about the tool

185
00:08:08,710 --> 00:08:09,120
itself.

186
00:08:09,840 --> 00:08:14,160
If they manage this level of security, do they have to sacrifice features?

187
00:08:14,160 --> 00:08:16,480
The Allianz says this is a comprehensive toolkit.

188
00:08:16,480 --> 00:08:20,240
Oh, far from it. This is a robust, really mature platform.

189
00:08:20,240 --> 00:08:24,400
The sources indicate Bento PDF offers a massive feature set over 50 tools.

190
00:08:24,400 --> 00:08:29,920
50. It covers virtually every organizational security and conversion need

191
00:08:29,920 --> 00:08:33,760
you might have for PDFs. It's not just some niche security solution.

192
00:08:33,760 --> 00:08:36,720
It's like an entire office suite just delivered privately.

193
00:08:36,720 --> 00:08:40,960
Wow. Okay. 50 tools. That is massive functionality for a free,

194
00:08:40,960 --> 00:08:44,720
private tool. To avoid just reading a checklist, maybe let's focus on some of

195
00:08:44,720 --> 00:08:47,760
the more advanced security and modification tools.

196
00:08:47,760 --> 00:08:51,280
Can you highlight a few key features that professionals would really rely on?

197
00:08:51,280 --> 00:08:55,280
Certainly. Let's maybe look at three critical security-focused tools.

198
00:08:55,280 --> 00:08:56,560
Let's start with Flatten PDF.

199
00:08:56,560 --> 00:09:00,960
Wait. Okay. Flatten PDF. Why is flattening so critical, especially for, say,

200
00:09:00,960 --> 00:09:04,720
legal or institutional forms? What exactly does it prevent?

201
00:09:04,720 --> 00:09:08,720
Right. Flattening is essential because standard PDFs often contain dynamic

202
00:09:08,720 --> 00:09:12,400
elements. I think form fields you can type into, interactive buttons, maybe

203
00:09:12,400 --> 00:09:17,040
annotations people added. When you sign or submit a document officially,

204
00:09:17,040 --> 00:09:20,800
you need those fields to become static, unchangeable, part of the permanent

205
00:09:20,800 --> 00:09:25,360
content. Flattening takes those dynamic bits and basically converts them into an

206
00:09:25,360 --> 00:09:29,680
uneditable image layer within the PDF. It permanently locks the document's

207
00:09:29,680 --> 00:09:34,160
content. It prevents manipulation, accidental changes later on, or even

208
00:09:34,160 --> 00:09:38,160
potentially malicious scripts that could be embedded in form fields after the

209
00:09:38,160 --> 00:09:42,320
document has been approved or submitted. It's a key step for document integrity.

210
00:09:42,320 --> 00:09:46,720
Ah, that makes perfect sense. Locking it down. Okay, now you also mentioned tools

211
00:09:46,720 --> 00:09:51,440
for content removal and document hygiene, specifically redact content and

212
00:09:51,440 --> 00:09:54,160
sanitize PDF. Are those basically the same thing?

213
00:09:54,160 --> 00:09:59,440
Good question. They serve different but related security functions. Redact

214
00:09:59,440 --> 00:10:04,160
content is about permanently removing sensitive visual information. So if you

215
00:10:04,160 --> 00:10:08,160
use the redaction tool to black out, say, a social security number or a client

216
00:10:08,160 --> 00:10:12,000
name, the underlying data isn't just covered up with a black box like some

217
00:10:12,000 --> 00:10:15,520
simple tools do. It is surgically and permanently removed from the file

218
00:10:15,520 --> 00:10:18,800
structure itself. It leaves only blank space where that data was. Okay,

219
00:10:18,800 --> 00:10:23,200
permanently gone. Permanently gone. Now, sanitize PDF, on the other hand, is more

220
00:10:23,200 --> 00:10:26,800
about container hygiene. You have to remember, a PDF is essentially a

221
00:10:26,800 --> 00:10:30,400
sophisticated container format. It can harbor hidden stuff, potentially

222
00:10:30,400 --> 00:10:33,760
unwanted or even malicious elements, things like executable scripts,

223
00:10:33,760 --> 00:10:36,880
embedded file attachments you didn't know were there, or maybe navigation

224
00:10:36,880 --> 00:10:41,520
history that you don't want distributed. Sanitize cleans all of that out. It

225
00:10:41,520 --> 00:10:45,440
strips the document down to its core valuable content. You could think of

226
00:10:45,440 --> 00:10:48,880
sanitize as doing a deep cleaning of the file's internal structure, ensuring

227
00:10:48,880 --> 00:10:52,160
you're only sharing the visible information and absolutely nothing else

228
00:10:52,160 --> 00:10:55,920
hidden inside. That's a crucial distinction. Wow, it sounds like a really

229
00:10:55,920 --> 00:10:59,680
necessary step before sending almost any external document to a third party,

230
00:10:59,680 --> 00:11:03,760
honestly. Besides security, the source has

231
00:11:03,760 --> 00:11:06,720
mentioned some complex organizational tools too, like

232
00:11:06,720 --> 00:11:10,000
alternate and mix pages, which sounds complicated,

233
00:11:10,000 --> 00:11:15,360
and posterized PDF. What are those about? Yeah, alternate and mix is actually a

234
00:11:15,360 --> 00:11:18,720
really powerful feature, especially if you're merging reports where

235
00:11:18,720 --> 00:11:22,320
you need to interleave pages from two different documents. So you want page one

236
00:11:22,320 --> 00:11:24,400
from the original, page one from the revision,

237
00:11:24,400 --> 00:11:27,920
page two from the original, page two from the revision, and so on. It automates

238
00:11:27,920 --> 00:11:32,080
that interleaving process. Posterized PDF, well as the name suggests,

239
00:11:32,080 --> 00:11:36,480
it prepares a very large PDF, like a big blueprint or maybe a scientific poster,

240
00:11:36,480 --> 00:11:40,080
by automatically splitting it into smaller standard letter-sized pages.

241
00:11:40,080 --> 00:11:43,280
It adds overlap marks so you can easily print it on a standard desktop printer

242
00:11:43,280 --> 00:11:46,640
and then assemble the full poster. The toolkit is clearly designed for power

243
00:11:46,640 --> 00:11:50,160
users, but also seems built for organizations needing control.

244
00:11:50,160 --> 00:11:53,360
And speaking of organizations, the deployment flexibility is worth noting

245
00:11:53,360 --> 00:11:57,040
too. How can large institutions use this private tool

246
00:11:57,040 --> 00:12:00,960
and still guarantee like 100% internal network control?

247
00:12:00,960 --> 00:12:03,920
Right, because it is open source, organizations can run it completely

248
00:12:03,920 --> 00:12:05,840
offline, entirely within their own network

249
00:12:05,840 --> 00:12:08,400
perimeter using Docker. It's quite straightforward.

250
00:12:08,400 --> 00:12:11,680
The sources even provide the command to show how simple it is. You can run it

251
00:12:11,680 --> 00:12:17,040
locally on, say, port 3000 using docker run udp3000.a0

252
00:12:17,040 --> 00:12:21,680
bentop ddf.latest. This means that privacy promise,

253
00:12:21,680 --> 00:12:24,720
it extends from the individual user right up to the enterprise level. They can

254
00:12:24,720 --> 00:12:28,400
guarantee those sensitive files never ever leave the corporate internet. And for

255
00:12:28,400 --> 00:12:31,920
that internal company use or maybe educational institutions, they even offer

256
00:12:31,920 --> 00:12:35,600
something called Simple Mode. They do, yeah. Simple Mode is designed

257
00:12:35,600 --> 00:12:38,720
specifically to maximize focus and reduce any

258
00:12:38,720 --> 00:12:42,560
internal friction or confusion. When you activate it, it hides all the

259
00:12:42,560 --> 00:12:46,240
branding, the marketing stuff, the SAQs, testimonials, even the footer. It just

260
00:12:46,240 --> 00:12:49,440
creates this clean, distraction-free environment that looks and

261
00:12:49,440 --> 00:12:52,560
feels like a dedicated internal company tool.

262
00:12:52,560 --> 00:12:56,000
It's actually a pretty elegant solution for enterprise adoption, making it look

263
00:12:56,000 --> 00:12:58,960
less like a public website. That's really thoughtful detail.

264
00:12:58,960 --> 00:13:03,360
Okay, so as we wrap up this deep dive, the crucial takeaway for you, the listener,

265
00:13:03,360 --> 00:13:06,160
the learner, is this complete paradigm shift here.

266
00:13:06,160 --> 00:13:09,760
Benta PDF really proves that you no longer have to trade security for

267
00:13:09,760 --> 00:13:12,960
functionality or vice versa. It offers genuine

268
00:13:12,960 --> 00:13:16,160
enterprise-level PDF capability, we're talking over 50 tools,

269
00:13:16,160 --> 00:13:20,160
but with consumer-level privacy. And it achieves this by moving the file

270
00:13:20,160 --> 00:13:22,400
processing entirely off the vulnerable server

271
00:13:22,400 --> 00:13:26,400
and onto your secure local browser. It's fast, it's free, and it's verifiable

272
00:13:26,400 --> 00:13:30,320
because it's open source. And this, well, frankly, revolutionary

273
00:13:30,320 --> 00:13:33,680
architecture prompts a final thought for reflection perhaps.

274
00:13:33,680 --> 00:13:37,760
If complex multi-functional tools like this can operate entirely client-side

275
00:13:37,760 --> 00:13:42,960
without compromising speed or security, in fact, actually enhancing both what

276
00:13:42,960 --> 00:13:47,280
other types of common digital tasks. Maybe things like simple video editing,

277
00:13:47,280 --> 00:13:51,200
or detailed photo manipulation, or even light data analysis.

278
00:13:51,200 --> 00:13:55,200
What else could, and perhaps should, be migrated off remote servers and brought

279
00:13:55,200 --> 00:13:58,720
back to the local browser? It really raises the bar, I think, for

280
00:13:58,720 --> 00:14:01,840
what we should demand from every web service we use in terms of

281
00:14:01,840 --> 00:14:05,280
privacy and control. That's certainly something to maul over

282
00:14:05,280 --> 00:14:07,600
the next time you hover over that upload button somewhere.

283
00:14:07,600 --> 00:14:10,640
Thank you for joining us on this deep dive, and a huge thank you once again to

284
00:14:10,640 --> 00:14:13,760
our dedicated supporter, SafeServer. They provide hosting and

285
00:14:13,760 --> 00:14:18,000
support to digital transformation. Find out more at www.safeserver.de.

286
00:14:18,000 --> 00:14:20,800
We'll see you next time.