The most important security property of WorkWithPDF is how it is built: your files are processed in your browser, and their contents are not uploaded to our servers. This page explains what that means in practice, what does leave your device, and the limits you should know about.
1. In-Browser File Processing
All PDF operations — merging, splitting, compressing, converting, redacting, signing, annotating — run inside your browser using JavaScript libraries and Web Workers. Your files are loaded into browser memory, processed there, and the result is offered to you as a download. Results are also kept in your browser's storage (the Origin Private File System or IndexedDB) on your device until you clear the workspace or your browser data.
No file content or file name is included in any network request during a tool operation. You can verify this independently at any time:
- Open your browser DevTools (F12 on most browsers)
- Go to the Network tab
- Process any file with any tool
- Observe that no request contains your file data
2. What Leaves Your Device
The following data is sent over the network when you use WorkWithPDF:
- Page load requests — HTML, JavaScript, and CSS are fetched from our host, Vercel. Like most web hosts, Vercel logs these requests, including your IP address and browser user agent.
- Analytics — Vercel Analytics (cookieless) and Google Analytics 4 record page views and general device and browser information. When you run a tool, a small usage event (tool name, browser type, page and output counts, and an error category if something failed) is sent to our server. See our Privacy Policy for full details.
That is what our site sends during normal use. None of it includes the contents of your documents.
3. Redaction — Visual Cover Only
The Redact PDF tool draws solid black rectangles over the areas you choose, including matches found by its scan for emails, phone numbers, and similar patterns. It does not yet remove the text underneath. The covered text is still in the output file, and anyone who receives it may be able to select, copy, search, or extract that text.
Treat the output as a visual cover, not a true redaction. Before you share a redacted file, try selecting or searching for the covered text to check what is still there. For legal, medical, financial, or other regulated documents, use a dedicated redaction tool that removes the underlying content.
4. No User Accounts
WorkWithPDF has no user accounts and no sign-in. That means there are no passwords, user records, or login sessions on our side to protect or to leak. Our own site does not set cookies; Google Analytics sets its own cookies, as described in our Privacy Policy.
5. Data in Transit
All network traffic between your browser and our servers uses HTTPS. This applies to page loads and analytics requests.
6. Infrastructure
WorkWithPDF is hosted on Vercel. Static assets are served from a global CDN. We do not operate server-side storage for user documents — because document contents are not uploaded to us, there is no document store on our side to secure or breach.
7. Browser Storage
The copy of your results that lives in your browser's storage is only as secure as your device and browser profile. If you use a shared or public computer, use the Clear workspace option (or clear your browser's site data) when you are done. The site also keeps a few small items in local storage — your invoice draft and a short log of recent tool events. These stay on your device.
8. Responsible Disclosure
If you discover a security vulnerability in WorkWithPDF, please report it privately to gaurav@stipple.sh before disclosing it publicly. We will acknowledge receipt within 2 business days and aim to resolve confirmed issues within 30 days. We do not operate a formal bug bounty program at this time but will credit researchers who report valid issues.
9. Contact
Security questions or reports: gaurav@stipple.sh
Stipple AI Pty Ltd, Australia