Prune Privacy Policy
Effective date: 2026-11-04
Short version: Prune does not collect any data. It has no analytics, no telemetry, no accounts and no remote code. Nothing is sent to the developer or to any third party. All link cleaning happens locally in your browser.
What Prune does with web addresses
To remove tracking parameters, Prune has to look at the addresses (URLs) your browser requests. It checks them against its rule list inside your browser and changes them there. These addresses are not sent anywhere.
Network requests made by Prune
Prune makes only one kind of request on its own: at most every six hours, it downloads the checksum of its rule list from https://erencanucarr.github.io/prune-rules/, and downloads the rule list itself only if the checksum has changed. If that fails, it uses the copy of the rules that ships with the extension.
The rule list combines Prune's own rules with the ClearURLs community rule list, which is synced automatically from the ClearURLs project.
These are ordinary file downloads from GitHub Pages. They contain no information about you or your browsing. Like any web server, GitHub can see your IP address and browser version for those requests; GitHub's privacy statement applies to them. If you enter your own rule URLs under Settings (only https addresses are accepted), the rules are downloaded from there instead.
What is stored on your device
- Settings and the downloaded rule list.
- Counters: how many addresses were checked and how many were cleaned (numbers only).
- Log of cleaned URLs (optional, off by default): if you turn it on, Prune keeps the address before and after cleaning, the rule that matched and the time. It is limited to the number of entries you set (100 by default).
- Toolbar badge: a per-tab count of cleaned addresses and the tab's current address, kept in temporary session storage that the browser clears when it closes.
This data stays in your browser's extension storage. Prune never uploads it. You can export your settings or log to a file yourself; that file is saved only where you choose.
Deleting your data
Use Settings → Reset to restore all defaults, the Reset button in the popup to clear the counters, or Reset on the Log page to delete the log. Removing the extension deletes all of its stored data.
Permissions
| Permission | Why Prune needs it |
|---|---|
declarativeNetRequest, declarativeNetRequestWithHostAccess | Let Chrome itself remove tracking parameters, skip tracking redirects and block tracking domains. |
declarativeNetRequestFeedback | Read which of Prune's own rules matched, to count cleaned links (badge and statistics) and fill the optional local log. Nothing leaves the device. |
webRequest | A fallback used only when Chrome's rule engine is unavailable: Prune then cleans requests itself. |
Host access <all_urls> | Tracking parameters appear on links to any website, so cleaning must work everywhere. |
webNavigation | Notice when a page adds tracking parameters to its address after it has loaded. |
scripting | Replace such an address in the page, and copy a clean link to the clipboard. |
contextMenus | Add a right-click menu entry that copies a link without its tracking parameters. |
storage | Save settings, counters, the rule list and the optional log locally; the rule list can exceed the default quota. |
downloads | Save your settings or log to a file when you click Export. |
alarms | Run a periodic local self-check that cleaning still works. |
Prune also runs small scripts on Google and Yandex search pages to stop them from rewriting result links into tracking redirects.
Two of Prune's pages (the one used when skipping a tracking redirect and the "site blocked" page) are web-accessible, as Chrome requires for redirecting to them. A side effect is that a website could detect that Prune is installed.
Changes and contact
If this policy changes, the new version will be published on this page with a new date. Questions? Open an issue at github.com/erencanucarr/prune/issues.