Privacy Policy
Marginalize Chrome ExtensionEffective 2026-05-23
Publisher: Nexudeit
Short version
Marginalize does not collect, transmit, sell, or share any personal data, browsing history, page content, or analytics. Everything happens locally in your browser. The only network requests the Extension makes on its own initiative are to public filter-list URLs that you can review and change at any time.
1. What data we collect
None that leaves your browser. Specifically:
- We do not collect your browsing history.
- We do not collect URLs you visit.
- We do not collect page content, form data, cookies, or credentials.
- We do not use third-party analytics, telemetry, crash reporting, or A/B testing.
- We do not sell, share, or transmit any usage data.
- We do not assign you a user ID, advertising ID, or similar identifier.
2. What is stored locally
The Extension uses Chrome’s
chrome.storage.local API to save settings and statistics on your own device only. Stored items include:- Whether protection is on or off.
- A list of hostnames where you paused the Extension.
- Your custom filter rules and cosmetic selectors (whatever you type in Settings).
- The list of filter-list URLs you have configured.
- The parsed cosmetic-selector list and dynamic network rules derived from those filter lists.
- Aggregate counts of how many requests have been blocked today and in total (counters only — no per-site breakdown).
- The timestamp of the most recent filter list update.
This data never leaves your device. You can wipe it at any time by uninstalling the Extension or by clearing site data for the extension in
chrome://settings/cookies.3. Outgoing network requests
The Extension makes outbound requests only to fetch the filter lists you have configured. By default that is:
https://easylist.to/easylist/easylist.txthttps://easylist.to/easylist/easyprivacy.txt
These requests are sent from your browser directly to the filter-list provider. The provider sees your IP address and a normal
User-Agent string the same way they would for any web request. The Extension does not add identifying headers, cookies, or query parameters. You can remove or replace these URLs in Settings → Filter Lists, or disable updates entirely.4. Permissions and why we need them
- declarativeNetRequest / declarativeNetRequestFeedback — to block network requests against the filter rules and to count blocks for the badge.
- storage — to remember your settings and statistics locally.
- alarms — to schedule periodic filter updates.
- scripting — to inject the cosmetic stylesheet into pages.
- tabs — to identify the current site for the popup’s per-site toggle and to read the active tab’s hostname.
- webNavigation — reserved for future support of pre-render rule application.
- <all_urls> host permission — required for the content script to inject cosmetic rules and the anti-popunder defenses on the sites you visit.
5. What page content the Extension can see
Because the Extension injects scripts into web pages it visits, those scripts technically run in the same JavaScript context as the page. The bundled scripts do not read, copy, or transmit page content. Their job is to patch
window.open, monitor click events for hijack overlays, and apply CSS hiding rules. No data from the page is sent anywhere.6. Children
The Extension is not directed at children under 13 and does not knowingly collect any data, including from children. (See section 1: it does not collect data from anyone.)
7. Third parties
The Extension downloads filter lists from third-party providers. Those providers have their own privacy policies which govern what they do with the incoming request. We recommend reviewing EasyList’s policies before relying on their lists.
8. Changes to this Policy
If this Privacy Policy changes in a way that materially affects your privacy, the change will be noted by an updated “Effective” date and, if relevant, an in-extension notice. We will not start collecting any data without your explicit, opt-in consent.
9. Contact
Privacy questions: [email protected]. Publisher: Nexudeit.