Security

The strongest protection for a document is not sending it anywhere. Every tool on BoringWork runs inside your browser: the PDF is read, changed and saved on your own computer or phone. There is no upload step, and we have no server that receives or stores files, so there is nothing on our side to leak, breach or delete.

You can check this yourself: open your browser’s developer tools, go to the Network tab, and use a tool. You’ll see no request carrying your file.

• PDFs are rendered with pdf.js (Apache 2.0) and written with pdf-lib (MIT), widely used open-source libraries that run in the page.
• PDF parsing runs in a Web Worker, separate from the rest of the page.
• No ads or trackers, and no fonts from other domains. The only third-party script is Google Analytics, loaded only if you allow it, and it never sees your files.
• The site is served over HTTPS only, with headers that block framing and content-type sniffing.
• When installed as an app, a service worker keeps an offline copy of our own site files. It never stores or sees your documents.

Because processing happens on your device, a few things are up to you:

• Keep your browser and operating system up to date.
• Be careful with browser extensions; they can read pages you visit.
• Store downloaded files somewhere safe, especially on shared computers.
• The Cover up tool is not redaction: the original content remains in the file underneath. Don’t use it to remove confidential information.

If you think you’ve found a security issue, please email officialprince52@gmail.com with the steps to reproduce it. We’ll acknowledge your report within 3 working days and keep you updated while we fix it.

When testing, please:

• only use files and data that are your own,
• don’t run denial-of-service, spam or social-engineering tests,
• give us reasonable time to fix the issue before sharing it publicly.

We won’t take legal action against good-faith research that follows these guidelines. Our contact details are also published in /.well-known/security.txt.

See the privacy policy for what data we handle (very little) and the cookie policy for what’s stored in your browser (four display preferences and an offline copy of the site).