The short version
Almost all of DocZap's PDF and image tools run entirely inside your web browser. When you drop a file into most of DocZap's 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 this way, because it never reaches us. Two tools — PDF to Word and Word to PDF — are the exception, and are covered separately below.
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.
The two tools that aren't client-side
PDF to Word and Word to PDF are the exceptions to everything above. Real conversion between PDF and editable Word documents isn't something a browser can do on its own, so these two tools send your file to a small conversion service DocZap runs, get the converted file back, and return it to you. That service does not log requests, does not persist files beyond the length of the conversion, and deletes both the uploaded file and the converted output the moment the response is sent. No one at DocZap looks at, or has a practical way to look at, the contents of a file passing through it. Every other tool on this site, including PDF to Excel, stays entirely client-side.
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.
Advertising
DocZap displays ads served by Google AdSense. Google and its advertising partners may use cookies and similar technologies to serve ads based on your prior visits to this and other websites. You can opt out of personalized advertising by visiting Google's Ads Settings, or aboutads.info/choices for other providers. Ad cookies are unrelated to, and have no access to, the contents of any file you process with a DocZap tool.
Cookies
Aside from the advertising cookies described above, 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 further — for example, if another tool needs server-side processing — this page will be updated first, and that tool will clearly state what happens to your file before you use it.
Questions
If you have questions about this policy, visit our Contact page.