PDF tools
Compress · Merge · Split · Edit · Sign · Convert
All PDF processing uses pdf.js and pdf-lib running in your browser. Your PDF is parsed and re-serialized locally — the bytes never leave the tab.
Privacy proof, not just promises
How we protect your files
Most tools tell you to trust them. We'd rather show you. The live log below is reading your browser's Network tab right now — every request the page has made, and a counter that proves zero of them carried your file.
Live network activity
Live network activity on this page
Files uploaded
0
never
Bytes sent of your data
0 B
since page load
Simulated tool actions
0
local only
Waiting for activity…
Try this yourself: open your browser's Network tab, filter by Fetch/XHR, then use any TryDocsy tool. You'll see static assets load once — and zero requests carrying your file.
The proof checklist
Six claims, each with a 30-second way to check it yourself. The live demo above proves the first one in real time.
01Your file is never uploaded.
Open DevTools → Network tab → filter by Fetch/XHR. Use any tool with a real file. You'll see zero requests carrying the file contents.
02Tools keep working without internet.
Load any tool once, then disconnect from Wi-Fi (or enable airplane mode). The tool still opens, processes, and downloads your file.
03No analytics on what you upload.
Our analytics count anonymous page views only — never file names, contents, or even which tool you opened. Page-view tracking is on by default and you can block it with any standard ad-blocker.
04Source code is auditable.
Open DevTools → Sources tab → the bundled JavaScript is plain, minified, but unminified-enough to grep. The processing logic for every tool lives under /lib and /app.
05No account, no sign-in, no email.
Try to find a signup flow — there isn't one. Nothing ties your usage to an identity, so there is nothing to leak.
06Downloads happen straight to your device.
The "Download" button uses a Blob URL — your file is constructed in memory and offered to your browser's save dialog without ever leaving the tab.
Where the privacy comes from
Each tool category runs on a different in-browser engine. Here's what does the work — and what is never sent over the network.
Image tools
Compress · Resize · Crop · Remove BG · Metadata Remover
Image processing uses the Canvas API and on-device AI (ONNX Runtime Web for background removal). Your photo is decoded, transformed, and re-encoded in browser memory.
OCR tools
Image-to-text · PDF-to-text
OCR runs Tesseract.js, a WebAssembly build of Tesseract, on your device. The recognition model is loaded once and then runs entirely client-side.
Form tools
Signature Resizer · Passport Photo · Auto-Fill · Document Checker
Forms never send the data you fill in. The auto-fill helper reads from values you paste into the page, processes them locally, and offers the result as a Blob download.
Questions people ask when they're skeptical (good)
Aren't page assets network requests too?
Yes — and that's the point. The live demo above shows every request the page itself makes (HTML, CSS, JS, fonts) and labels them clearly. Zero of those requests carry your file. The distinction matters: a server-based tool would show a Fetch/XHR row containing the file's bytes during processing — TryDocsy never does.
Can I really use TryDocsy offline?
After your first visit, yes. The service worker caches the page shell and tool bundles, so the tools keep working in airplane mode. This is also the strongest external proof that nothing is uploaded — a tool that needed to send your file to a server could not function without a network.
Does TryDocsy use my files for analytics or AI training?
Never. Our analytics (if loaded) count anonymous page views only. Your files, file names, and tool choices are not collected, not transmitted, and not used to train any model. There is no account to tie usage to.
What if a future tool needs server processing?
The promise is that no tool on TryDocsy will ever upload your file by default. If a feature genuinely cannot run in-browser, it will be opt-in, clearly labelled, and documented on this page so you can choose to use it — or not.
How do I audit the code myself?
Open DevTools → Sources → search the bundled JS for the file-upload logic. There isn't any for the actual processing pipeline. Every tool's logic lives under /lib (image-helpers, pdf-editor, ocr, etc.) and is reachable from the page's source map.
Convinced? Try a tool.
Pick anything — compress a PDF, strip EXIF, sign a doc. Watch the Network tab as you do.
Still reading? See the Privacy Policy, the Trust page, or get in touch.