Security
Security starts with where documents go
DocuVerse Editor opens documents inside your own app. There is no service of ours that sees your files, so there is no service of ours to trust with them.
User’s device
By design
How DocuVerse protects documents
On the device
Documents open inside your app, in the user’s browser or on your own server. There is no DocuVerse service in between.
In the browser’s sandbox
In the browser, DocuVerse stays inside the same sandbox as your page. It sees only the files your app gives it.
No calls home
The software makes no network requests of its own: no analytics, no crash reports, no licence server. It works offline.
Your storage, your rules
Your app decides where documents are saved and who can open them. DocuVerse never stores them.
Safe with damaged files
Broken or unusual files open as far as possible, without bringing down your app.
Password-protected PDFs
Encrypted PDFs open only with their user or owner password, and the password never leaves the device.
For developers
Your part
The software runs in your app, so a few choices are yours. These keep it safe.
- 1Keep
docuverse(npm) orDocuVerse(NuGet) up to date, so you get fixes as soon as they are released. - 2Serve the engine file from your own site, next to your app.
- 3Treat files from strangers as untrusted. On a server, convert them in a separate process with limited permissions, and set limits on file size and time.
- 4Decide where saved documents go, and describe it in your own privacy policy.
Found a problem?
Report a vulnerability
If you think you’ve found a security problem in DocuVerse Editor, please tell us privately first, so we can fix it before it’s public.
- We confirm that we got your report
- We keep you updated while we work on a fix
- With your permission, we thank you by name in the release notes
Write to
Subject
Include
Please
| Version | Security fixes |
|---|---|
| 0.1.x | Supported (the latest release) |