Privacy policy
Last updated 27 July 2026
PDF Editor for Chrome is a Chrome extension that edits PDF documents. It has no server component. It collects no data, and it transmits nothing.
What happens to your documents
A PDF you open is read into the memory of the editor tab, rendered and edited there, and written back out when you save. The file never leaves your computer, is never uploaded, and is never sent to the developer or to any third party. When you close the tab, it is gone from memory.
When you ask the extension to open a PDF that lives on a website, your browser fetches that file from the site it is already on — the same request your browser would make if you clicked the link. Nothing is routed through anywhere else.
What is stored on your device
| What | Where | Why |
|---|---|---|
| Signatures you explicitly choose to save | Local extension storage, on this device only | So you can reuse a signature on later documents. Not synced. |
| Editor preferences (zoom, panel layout) | Local extension storage, on this device only | So the editor opens the way you left it. |
Both are removed when you uninstall the extension, or when you clear its data from
chrome://extensions.
What is not collected
No personally identifiable information, no health, financial or payment information, no authentication details, no personal communications, no location, no browsing history, no analytics, no telemetry, no crash reporting, and no advertising identifiers. There are no cookies, no accounts and no sign-in.
Permissions
| Permission | What it is used for |
|---|---|
activeTab |
When you click the toolbar icon, the popup checks whether the tab you were on is a PDF, so it can offer to edit it. Read at that moment only, and never stored. |
contextMenus |
Adds the “Open in PDF Editor for Chrome” and “Edit this PDF” right-click entries. |
storage |
Keeps your saved signatures and editor preferences on this device. |
Access to *.pdf pages |
Adds an “Edit in PDF Editor for Chrome” button to pages that are PDFs. The script runs only on
URLs ending in .pdf, reads no page content and sends nothing anywhere.
|
| Access to a website (optional) | Requested only when you ask to edit a PDF hosted on that site, and only for that site, so the file can be fetched and opened. Decline and you can still drag the file into the editor. |
| Feature permissions (optional) |
The extension declares a further set it does not hold — downloads,
clipboardRead, notifications, alarms,
idle, unlimitedStorage, scripting and
tabs. None is granted at install. Each is asked for only if you switch
on the feature that needs it — saving through the downloads shelf, pasting from the
clipboard, an export-finished notification, autosaved local drafts — and each can
be declined without losing anything else, or withdrawn later from
chrome://extensions. None collects or transmits anything.
|
Third parties
There are none. No data is sold, shared or transferred to anyone. The extension bundles two open-source libraries — pdf.js and pdf-lib — which run locally inside the extension and make no network requests of their own.
Children
The extension is not directed at children and, since it collects nothing, it collects nothing from them either.
Changes
If this policy ever changes, the revised version will be posted at this address with a new date above, and the change will be described in the extension's release notes.
Contact
Questions about this policy: privacy@pdf-editor-chrome.example.com
PDF Editor for Chrome is free software. This policy covers the extension published on the Chrome Web Store and nothing else.