browserpdf
← All tools

Privacy Policy

Last updated: August 5, 2026

Short version: every tool runs entirely in your browser. We cannot see your files (no upload, no server-side processing). We use basic Cloudflare traffic analytics, and, only if you accept the cookie banner, Google Analytics; neither ever includes document contents.

What we don't collect (your files)

We do not operate a backend for file processing. There is no upload endpoint. PDFs and other documents you open in any tool are read, processed, and downloaded again entirely within your browser tab. We never receive a copy of your files, their contents, extracted text, passwords you type into a tool, or any data derived from the document.

We do not require an account, and we do not ask for your name, email address, or other personal information just to use a tool.

What is stored locally on your device

The site may store a few preferences in your browser's localStorage only on your device (for example dark/light theme, language, and whether you've accepted or rejected the analytics cookie banner). Those values are not used to process your files and are not required for tools to run.

Traffic analytics (not your documents)

To operate and improve the site we use Cloudflare traffic analytics:

  • Edge / zone analytics that come with hosting on Cloudflare Workers (request counts, bandwidth, status codes, rough geography, popular paths). This is standard hosting telemetry.
  • Cloudflare Web Analytics (cookieless measurement of page views and performance, when enabled for this site). That may load a small Cloudflare script (for example from static.cloudflareinsights.com) to report aggregate page metrics.

These analytics are about site traffic (which HTML pages load, roughly from where). They are not about the PDF, Word, Excel, or image files you open inside a tool. There is no analytics packing of file bytes, extracted text, or tool form fields, because that work never leaves your tab.

We do not use social media pixels, advertising conversion trackers, or cross-site fingerprinting. The only other measurement tool is the consent-gated Google Analytics described next. See also Cloudflare's privacy policy.

Google Analytics (only with your consent)

If you click Accept on the cookie banner shown on your first visit, we load Google Analytics to understand aggregate site traffic. Until you make a choice, and if you click Reject, Google Analytics runs in a reduced mode that sets no cookies and does not identify you individually.

  • Delivery. Google Analytics loads through Cloudflare's Google Tag Gateway, which proxies it through our own domain rather than loading it directly from Google's servers, and strips your IP address before forwarding the request, so Google does not receive it.
  • What it can see. Pages visited, approximate location (derived without your raw IP), device and browser type, and how you arrived at the site. It cannot see the files you open in any tool, since that processing never leaves your browser tab.
  • Cookies. Once accepted, Google Analytics sets cookies to distinguish returning visitors. These are the only cookies this site sets; everything else (theme, language, your consent choice) uses localStorage, not cookies.
  • Changing your mind. Click Cookie preferences in the footer of any page at any time to change your choice.

See Google's privacy policy for how Google handles data it receives.

Third-party infrastructure

Loading this site involves a small number of third parties whose technical logs we do not fully control:

  • Hosting provider (Cloudflare). Static assets and the Worker are served via Cloudflare. Cloudflare keeps ordinary access logs (IP, requested path, timestamp, user agent) and provides the aggregate analytics described above. Document contents are not part of that. See Cloudflare's privacy policy.
  • jsDelivr (CDN). Open-source libraries (pdf.js, Tesseract.js, pdf-lib, and similar) load from jsDelivr. Your browser requests those library files from jsDelivr subject to jsDelivr's privacy policy. We pin versions and verify hashes before execution; we do not control jsDelivr's own logs. Your document files are never sent to jsDelivr.

Neither pathway is used to inspect what you do with a file after the page has loaded.

Children's privacy

This site does not knowingly collect personal information from anyone, including children, because it does not collect personal information at all.

Open-source code

Every claim in this policy follows from how the site is built, not a promise layered on top of it, so you don't have to take our word for it: the source code is published on GitHub, where you can verify directly that no upload endpoint exists. Reusing the code yourself, as opposed to using this hosted Service, is governed by a separate license, not this policy; see the Terms of Service for a summary and LICENSE.md in the repository for the complete terms.

Changes to this policy

If this policy changes, we'll update the date at the top of this page. Since the core fact (nothing is uploaded) is a property of how the site is built rather than a promise we could quietly break, we don't expect this policy to change often.

Contact

Questions about this policy can be sent to info@browserpdf.app.