BlendPDF

Privacy Policy — Open in BlendPDF

Browser extension · Last updated 20 August 2026

The extension collects nothing. No analytics SDK, no telemetry, no error reporting, no account, no identifier of any kind. Nothing you do in the extension is reported to anyone.

This policy is deliberately specific, because the extension's main claim is a privacy claim and a vague policy would undermine it.

What runs on your device only

These never touch the network:

The PDF is read into memory, processed by bundled copies of pdf-lib (editing) and pdf.js (drawing previews), and written straight back to your disk. Both ship inside the extension; neither fetches anything. You can confirm this yourself: open DevTools on the extension popup, watch the Network tab, and run any local action. There will be no requests.

When the extension does use the network

Three cases, all of them started by you:

  1. Downloading a PDF you right-clicked. The extension fetches that URL so it has the bytes. The request goes to whichever site hosts the PDF — the same request your browser would make if you clicked the link.
  2. Opening a BlendPDF tool. The extension opens a normal tab at blendpdf.com.
  3. Sending a file to BlendPDF. The staged file is placed into the tool page's upload box. From that point the file is handled by BlendPDF under its own privacy policy: files are processed and deleted from BlendPDF's servers within one hour, most immediately after processing. Several BlendPDF tools — merge, split, rotate, reorder, delete pages, page numbers, watermark — run in your browser and do not upload at all.

The extension tells you at the moment of handoff that the file is going to BlendPDF.

What is stored, and for how long

DataWhereHow long
A PDF staged for handoffLocal IndexedDB, on your machineDeleted as soon as the file is delivered, and in all cases within 10 minutes
Anything elseNothing else is stored

There is no cloud storage, no sync, and no server belonging to this extension. Uninstalling removes the local database.

URL parameters

Links the extension opens on blendpdf.com carry utm_source=extension and the tool name, so the site's owner can see how many visits came from the extension. This is a first-party counter on their own site, contains nothing about you or your file, and is disclosed here rather than hidden. The handoff identifier in the URL is a random one-time value that means nothing outside your own browser, and it is removed from the address bar on arrival.

Permissions, and why each one exists

PermissionWhy
contextMenusAdds the right-click entries on PDF links
activeTabReads the PDF from the tab you invoked the menu on. Granted per click, not standing
scriptingRuns a single fetch inside that tab, which is the only way to read blob: PDFs a web app generated
downloadsSaves the merged, rotated or trimmed PDF you produced locally
unlimitedStorageHolds the staged file locally, in IndexedDB, between the click and the tab opening — PDFs exceed the default quota. The storage permission is deliberately not requested: the extension never calls chrome.storage
host_permissions (blendpdf.com)Lets the content script place your file into the tool page
optional_host_permissionsNot granted at install. Requested for one specific site, at the moment you use it, and only if the PDF could not be read any other way. You can decline and the tool page still opens

The extension does not request access to all websites.

Third parties

None. No SDKs, no CDNs, no remote code — Manifest V3 forbids remote code and this extension bundles every dependency. The only external service involved is blendpdf.com, and only when you choose to send a file there.

Contact

Questions about the extension: open an issue on its repository. Questions about how BlendPDF handles an uploaded file: see the BlendPDF privacy policy.