The short version
DocZap's PDF and image tools run entirely inside your web browser. When you drop a file into any of DocZap's 25 tools, that file is read, processed, and rebuilt using JavaScript and WebAssembly running on your own device. It is never uploaded to DocZap's servers, or any third party's servers, at any point. We have no ability to see, store, or access the contents of any file you process here, because it never reaches us.
Your files, specifically
Every tool — Merge, Split, Compress, Sign, Redact, Protect, and all the rest — uses open-source libraries (pdf-lib, pdf.js, jsPDF, Tesseract.js, and a WebAssembly build of QPDF) that run locally in your browser tab. Your file is processed in your device's memory and discarded when you close or reload the tab. Nothing is written to any server, cached remotely, or logged anywhere by us.
Analytics
We use Vercel Analytics to understand how many people visit DocZap and which pages they use. It doesn't use cookies, doesn't track you across other websites, and doesn't collect any personally identifying information — it reports aggregated counts like page views and general visitor location (country-level), not individual browsing profiles. It has no visibility into any file you process with a DocZap tool, since that processing never involves a network request in the first place.
Cookies
DocZap does not set tracking cookies. There are no accounts, no login sessions, and no saved preferences that would require one.
Fonts
The typefaces used on this site are self-hosted and bundled at build time, rather than loaded from Google's servers at runtime — so visiting DocZap doesn't send a request to Google just to render text.
Server logs and hosting
DocZap is hosted on Vercel. Like any website, basic connection information (such as IP address and request timing) is briefly processed by our hosting provider to serve you the page, the same as visiting any other site on the internet. This is standard web infrastructure logging, entirely separate from — and unrelated to — the contents of any file you process with a DocZap tool, which never becomes part of that traffic.
Changes to this policy
If DocZap's data practices ever change — for example, if a future tool requires server-side processing — this page will be updated first, and that tool will clearly state what happens to your file before you use it. As of this writing, every tool on DocZap is 100% client-side.
Questions
If you have questions about this policy, visit our Contact page.