Last updated: 4 August 2026
PDF Workbench does not collect, store, transmit or share any data about you or your documents. This page explains what that means and how you can check it for yourself.
Nothing. There is no analytics, no telemetry, no crash reporting, no advertising identifier and no account system. We do not know how many times you open the extension or which files you work with.
Your PDFs and images are read directly by the extension page in your browser and held in memory for as long as that tab is open. They are processed on your own machine and written back to your computer when you click Save. They are never uploaded, because there is no server to upload them to. Closing the tab discards everything.
chrome://extensions, click Details, and look at the permission list —
it is empty. It cannot read your browsing history, your tabs or the pages you
visit, because it never asked to.fetch(),
no XMLHttpRequest and no WebSocket in the code. You can
confirm this with the Network tab in Chrome DevTools while using it.None. No data is shared with anyone, because none is gathered. The extension bundles two open source libraries — pdf-lib and Mozilla's pdf.js — and both are included in the package itself. No code is loaded from a remote server at any point.
The extension does not request the storage permission and does not keep
settings between sessions. Options such as the watermark text are held in memory only
and are gone once you close the tab.
The extension is a general-purpose file utility and is not directed at children. Since no data is collected from anyone, none is collected from children either.
If a future version of PDF Workbench ever changes how data is handled, this page will be updated before that version is published, and the change will be described in the extension's listing.
Questions about this policy, or anything about the extension: open an issue on GitHub. Issues are public, so please do not include anything confidential.