Skip to content
BlockZeee
  • Features
  • Compare
  • Privacy
  • FAQ
Get BlockZeee — Free
Legal & Privacy

Privacy Policy &
Limited Use Disclosure

We built BlockZeee on a single principle: your data is none of our business. Here's exactly what that means.

Effective: March 30, 2026 Last updated: October 27, 2026 Applies to all browsers

Contents

  1. Overview
  2. Data Handling
  3. How the Extension Works
  4. Browser Permissions
  5. Third-Party Services
  6. Children's Privacy
  7. Changes to This Policy
  8. Contact
  9. Limited Use Disclosure

1 Overview

The short version: BlockZeee processes settings and site information locally to provide its protections. It does not upload browsing reports, cookie contents, or hardware profiles to us. Optional filter downloads and links make ordinary web requests, whose recipients receive connection information such as your IP address; Section 3 explains these requests.

BlockZeee ("the extension," "we," "us") is a browser extension available for Chrome and Firefox. Its sole purpose is to block ads, trackers, and fingerprinting scripts locally on your device using declarativeNetRequest rules and content scripts.

This Privacy Policy describes our data practices. If you have questions, contact us at the address in Section 8.

2 Data Handling

BlockZeee has no account, usage-analytics, or remote-reporting feature. It handles information locally for its protections:

  • The extension has no account or sign-in form. Optional cookie cleanup accesses site cookies locally to delete eligible cookies; it does not upload cookie contents.
  • The current tab domain is used in memory for protection controls and cleanup. Site exceptions and reported domains that you save remain in local extension storage.
  • Aggregate block counters and per-tab report summaries are maintained locally and can appear in an export you request.
  • The extension does not upload identity or hardware profiles. Websites and the filter-list provider can receive ordinary network information from your browser requests.
  • We do not use analytics, telemetry, or crash-reporting services.
  • The extension does not upload these local records to a BlockZeee backend.

Preferences, aggregate counters, site exceptions, user-reported domains, and downloaded filter rules are stored in your browser's local storage using chrome.storage.local. Per-tab domain and block-count reports are held in extension memory. The extension does not transmit these records to us. If you choose Export, it creates a local file containing those settings and reports.

The optional Blocklist Auto-Sync feature, described in Section 3, periodically fetches a public filter list from a third-party server. It sends no browsing history or extension reports. As with any web request, the provider can see your network IP address and ordinary connection information.

3 How the Extension Works

Protection decisions and reports run in your browser using two mechanisms:

  • declarativeNetRequest rules — Bundled and downloaded rules instruct the browser to block or modify matching requests. The browser evaluates these rules and, where supported, exposes matched-rule information for local statistics.
  • Content scripts — Local scripts inspect page structure, links, selected browser APIs, and video-player/request information to apply your enabled protections. They do not upload this information to BlockZeee.

Fingerprint Protection — beyond blocking known fingerprinting scripts, BlockZeee actively alters what a small set of fingerprinting-relevant browser APIs report back to the sites you visit: canvas and WebGL reads (toDataURL, getImageData, readPixels) return slightly noised pixel data instead of your device's exact rendering signature, and WebGL vendor/renderer queries return a generic, non-identifying value. These changes happen on-device and can be turned off via the "Fingerprint Protection" toggle. They cover selected API signals and do not prevent every fingerprinting technique; the extension does not upload hardware profiles to us.

UTM Stripping — BlockZeee rewrites the page you're currently on to remove known tracking parameters (utm_*, fbclid, gclid, and 30+ others) from its address and from every link on the page, so a cleaned URL is what gets bookmarked, shared, or followed. Redirect Unwrapping recognizes common tracking-redirect links (e.g., Google, Facebook, and LinkedIn click-through URLs) and sends you to their real destination directly, bypassing the tracking hop. Both happen locally in your browser; no URLs are sent anywhere to perform this rewriting. Toggle "UTM Stripping" and "Redirect Unwrapping" individually in Settings to turn either off.

Cookie Consent Auto-Dismiss — enabled by default, this feature detects GDPR/cookie-consent banners from common consent-management platforms (OneTrust, Cookiebot, TrustArc, Quantcast, and others) and automatically rejects non-essential cookies on your behalf — clicking each platform's "Reject All" / "Necessary Only" / "Decline" control where one exists — so you don't have to click through a consent dialog on every new site. If a banner has no such control, BlockZeee removes it without clicking anything, rather than granting consent by default. It never clicks "Accept" on your behalf. Consent controls are inspected and acted on locally. Local aggregate counters can record that a banner was handled; consent results are not uploaded as browsing reports. You can turn this off at any time via the "Cookie Consent Auto-Dismiss" toggle in the extension's Settings — turning it off means BlockZeee will no longer interact with consent banners at all, leaving them for you to answer yourself.

BlockZeee has no license-check, telemetry, or browsing-report upload endpoint. It makes the disclosed filter-data downloads and page navigations described below.

Blocklist Auto-Sync is enabled by default and can be turned off in Advanced settings. While protection and this feature are enabled, the extension fetches the public EasyPrivacy list from https://easylist.to/easylist/easyprivacy.txt on install or browser startup and on a daily alarm. Requests omit cookies and referrers; a locally cached ETag may be sent to avoid an unchanged download. The provider receives ordinary network information such as your IP address, but no browsing history, extension reports, or account identifiers are attached. Downloaded text is parsed only into a restricted set of blocking rules and is never executed. Turning this feature off removes its downloaded blocking rules and stops further downloads. Master pause also stops downloads and active blocking; local choices are retained for resume.

On a fresh installation, the extension opens its welcome page at blockzeee.com with a browser-family parameter so it can show the right pinning instructions. Following welcome, help, review, or store links makes an ordinary browser navigation to that site.

4 Browser Permissions

The extension requests the following permissions and uses them as described:

  • declarativeNetRequest / declarativeNetRequestFeedback — Used for browser-enforced network rules and matched-rule statistics where the browser makes them available. Other protections inspect page links and player requests locally as described above.
  • storage — Stores your on/off toggle and any settings locally on your device only.
  • cookies — Used by Cookie Auto-Clean: after a tab closes, BlockZeee can delete cookies for its domain unless the site is exempt or another open tab still uses the cookie's domain. This happens on-device; cookie contents are not transmitted or retained by the extension. This feature is unavailable in the Safari build.
  • scripting — Required to inject content scripts for DOM-level ad removal (e.g., video-site ad elements).
  • alarms — Used to schedule the optional Blocklist Auto-Sync fetch (see Section 3) every 24 hours. Does not run if Blocklist Auto-Sync is disabled.
  • Host permissions (<all_urls>) — Allow page protection scripts, supported header changes, tab-domain identification, and cookie cleanup across sites. Content scripts inspect page structure and selected browser/player APIs to apply the enabled protections. Tab domains are used in memory for local reports and cleanup; no browsing history is sent to us.

5 Third-Party Services

The extension contains no third-party analytics SDK or telemetry endpoint. Its optional EasyPrivacy data download contacts easylist.to, which receives ordinary connection information, including your IP address, as described in Section 3. Welcome, help, review, and store links open normal browser pages whose sites have their own data practices.

The extension is distributed through browser extension stores (Chrome Web Store, Firefox Add-ons, etc.). Those stores have their own privacy policies governing your relationship with them as a platform; BlockZeee has no control over or responsibility for those policies.

6 Children's Privacy

The local data handling described in this policy applies to all users. BlockZeee is not directed at children as its primary audience and does not provide accounts or remote behavioral profiles. Please contact us about concerns involving a child's information.

7 Changes to This Policy

If we ever change this policy in a material way, we will update the "Last updated" date at the top of this page and, where required by platform policies, notify users through the extension's store listing. The current version of this policy is always available at the URL where you are reading it.

We will describe any change to local data handling or transmission here and obtain consent when required before enabling new uses.

8 Contact

Questions, concerns, or requests regarding this policy can be directed to:

BlockZeee Privacy
Email: privacy@blockzeee.com

We will respond to all privacy-related inquiries within 5 business days.


9 Chrome Web Store — Limited Use Disclosure

In compliance with the Chrome Web Store Developer Program Policies, this section formally discloses how BlockZeee handles user data obtained through Chrome APIs.

Limited Use Compliance Statement

BlockZeee v3.7.69 · Browser Extension · Updated October 27, 2026

BlockZeee's use of information received from Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically:

Browsing reports uploaded to BlockZeee
None
Data sold to third parties
Never
Data used for advertising
Never
Reports uploaded to third parties
Never
Data used for creditworthiness
Never
Extension's core function
Ad & tracker blocking

Optional filter downloads and user-opened links make normal web requests (see Section 3). Recipients receive connection metadata such as your IP address; extension reports are not attached.

Page and tab information is used for the enabled protections and local reports. Preferences, saved site exceptions, aggregate counters, and filter caches persist locally as described in Section 2. Export creates a local file at your request. Removing the extension clears its browser-local storage; exported files remain under your control.

Formal Limited Use Statement

BlockZeee will not use or transfer user data for purposes unrelated to the extension's single, stated purpose: blocking advertisements, trackers, and fingerprinting scripts in the user's browser.

BlockZeee will not use or transfer user data to determine creditworthiness or for lending purposes.

BlockZeee will not sell user data to third parties.

BlockZeee will not use or transfer user data for personalized advertising.

These commitments apply permanently and are not subject to future change without explicit, prominent disclosure and user consent.

© 2026 BlockZeee  ·  Privacy Policy  ·  Back to Home