Privacy policy
Last updated 3 August 2026. Applies to the Palisade browser extension.

The short version
Palisade sends nothing about you anywhere. There is no account, no sign-in, no telemetry, no analytics, and no error reporting. Nobody, including me, receives any information about which sites you visit.

What it handles, and why
To block an ad you have to look at the request first, so the extension necessarily sees things about your browsing. Chrome asks extensions to disclose that even when the data never leaves the machine, which for Palisade it does not. Here is all of it.

Addresses of pages and requests. Every request your browser makes is checked against the filter lists. On Firefox the check happens inside the extension. On Chrome the browser does it internally from rules the extension compiled in advance, and the extension is told only which rule matched.

Page content. The content script reads the ids, classes and, for some filters, the text of elements on the page so it can work out what to hide. It looks at page structure to make that decision and nothing else. It does not read what you type, does not touch form fields or passwords, and does not copy page content anywhere.

A short request log. If the logger is on, recent decisions are kept in memory so the logger window has something to show. It is capped, it is per tab, it is cleared when you navigate or close the tab, and it is gone when the browser restarts. It is never written to disk and never sent anywhere.

Your own settings. Your filters, your per-site choices, which lists you enabled and the running counters are stored locally through the browser's extension storage. They stay on the device unless you export them yourself. If you have browser sync switched on for extensions, your browser may sync them under its own privacy policy, not mine.

Network requests it makes
Exactly one kind: downloading filter lists from the people who publish them, on a schedule you control in the settings, and only for lists you have enabled. Those are plain text files. As of this version the publishers are:

easylist.to
ublockorigin.github.io
pgl.yoyo.org
malware-filter.gitlab.io
raw.githubusercontent.com
Those requests carry no identifier of any kind. Like any download, the server will see the IP address the request came from. Nothing is added to it.

What it never does
No selling or sharing of data, because none is collected in the first place.
No advertising, no profiling, no "acceptable ads" arrangement, no paid allowlist.
No remote code. Everything that runs is in the package you installed. Filter lists are data that the bundled code reads; they are never executed as code.
Removing everything
Uninstalling the extension deletes all of it. There is nothing held anywhere else to delete, and no request to make of anyone.

Contact
Open an issue at https://github.com/TiltedLunar123/palisade/issues

Changes
Any change to this policy will be a commit in that repository, so the history is public and dated.