Your files, your eyes only. We never even get a look.

Where the processing actually happens

A normal "upload a file, get a result" website works by sending your file over the internet to that company's server, doing the work there, and sending a result back. That's how most free PDF/image tools you've used work — and it's also how your file ends up (at least briefly) sitting on someone else's computer.

PDFForYou doesn't do that. When you open a tool page, your browser downloads the code that does the work — JavaScript libraries like pdf.js (renders PDF pages), pdf-lib (reads and writes PDF files), and the Canvas API (image processing) — all running as part of the web page itself, using your device's own processor. When you click "Choose a file," that file is read directly into your browser's memory via the File API. It is never attached to a network request, never sent to any server, and the tool would work exactly the same way with your Wi-Fi turned off after the page has loaded.

How to verify this yourself

You don't have to take our word for it — this is checkable:

Open your browser's Network tab (right-click the page → Inspect → Network) before uploading a file to any tool. Use the tool normally. You'll see the page's own scripts and fonts load once, but no new network request appears when you select or process a file — because nothing is sent anywhere.

Try it offline. Load a tool page fully, then disconnect from the internet (airplane mode, unplug your router) and use the tool. It still works, because everything it needs is already running in your browser.

What this means for you

Files you process — PDFs, photos, whatever they contain — never exist anywhere except your own device, for the entire time you're using the tool. There's no server-side copy to worry about, no upload to wait on, and no privacy policy question about how long a company keeps your file, because there's no upload in the first place.