Privacy you can check
Do not trust us. Check that nothing is uploaded.
Every PlumPDF tool runs inside your browser, so your files stay on your device. That is easy to say, so here are three ways to see it for yourself, the first one right on this page.
Live check
Pick any file. This page reads every byte of it and works out its fingerprint, the way a tool would, while it lists every request the page makes. Nothing about the file is sent anywhere.
You are offline. Everything still works, which is the point.
This list comes from your browser's own record of the page's requests. For an independent view, use the network panel (below), which also shows how many bytes each request sent.
Test 1: turn the internet off
Open any tool, for example Compress PDF, so the page and its tool have loaded. Then switch on airplane mode or turn off Wi-Fi.
Now add a file and run the tool. It still works and you can still download the result. A site that uploads files cannot do that, because it needs the internet to reach its server.
Some tools fetch a helper the first time you use them, such as the image encoders or the text recognition models. Use a tool once while online and it keeps working offline after that.
Test 2: watch the network
On a computer, open the browser's developer tools (press F12, or Cmd+Option+I on a Mac) and choose the Network tab. Safari needs "Show features for web developers" switched on in its Advanced settings first.
Keep the panel open, then use a tool. You will see the tool's own code arrive from plumpdf.com and, if analytics are allowed, a few small analytics requests. None of them is the size of your file, and none of them goes out when the file is processed.
Click any request to see what it sent. Analytics requests carry the page address, the tool name and counts, never a file or its contents.
Test 3: the browser's own lock
Every PlumPDF page tells your browser which addresses it may contact, in a Content Security Policy. The page may only connect to plumpdf.com itself and to two analytics services, Google Analytics and Microsoft Clarity. Your browser blocks any other connection, whatever the code tries.
You can read the policy yourself: in the Network tab, click the page itself and look for Content-Security-Policy in the page source or the response.
What analytics can see
Analytics tell us which tools are used and whether they worked, so we know what to improve. They see the page address, the tool, counts such as how many files, and fixed error codes. They never see a file, its contents or its exact size, and file names are hidden from Clarity's session recordings.
In the EEA, the UK, Switzerland, Iceland, Liechtenstein and Norway, analytics cookies stay off until you allow them. Anywhere, you can decline them in Cookie settings at the bottom of every page. The analytics services are then told not to use cookies or identify you, though they may still count a page view without them. Every tool works the same either way, and your files never reach them.
What no website can promise
Browser extensions you install can read the pages you visit, on any site. If a file is very sensitive, use a browser profile without extensions, or test offline as above.
Your downloaded results are ordinary files on your device. Delete them when you no longer need them, as you would any file.