Browser privacy · Chrome 6.11

BP Tracker Blocker: Block Trackers, Ads and Analytics

BP Tracker Blocker helps block known trackers and ads while keeping the controls needed to review activity or allow a trusted website. The Chrome edition also brings tracking cookie, popup, autoplay video and page element controls into the same dashboard.

Reviewed against Chrome 6.11, August 2026. These screenshots and feature descriptions refer to this Chrome release. Firefox and Edge versions and controls may differ.

For setup instructions, follow the BP Tracker Blocker Chrome tutorial.

Chrome 6.11 Home dashboard with current-site tracker, ad, cookie, popup, autoplay and element counters
Home summarizes protection for the current website and activity from its last load.

Six protection categories in Chrome

Use Home to inspect the active page, Allow for exceptions, Settings to tune protection, and Help for guidance. Counters describe local activity, not guaranteed detection of every unwanted request.

TrackersKnown analytics, social pixels, attribution and session replay requests matched by blocking rules.
AdsAdvertising requests and matching patterns, with controls for blocked ad spaces.
Tracking cookiesProvider and cookie-name patterns, with optional Chrome cookie access for removal.
PopupsControls for consent overlays, notification prompts and other unwanted overlays.
Autoplay videosPause unwanted autoplay while keeping website-specific exceptions.
Blocked elementsHide a selected page element and manage the resulting local rule.

Control popups and autoplay separately

Choose which popup categories to hide in Settings. Video controls can stop unwanted autoplay without requiring all protection to be disabled.

Allow autoplay on a trusted website when needed. A video exception is narrower than pausing protection for the whole site.

Chrome 6.11 popup categories and autoplay video exceptions
Popup and video controls are separate settings.
Chrome 6.11 tracking cookie patterns, subscriptions and editable blocking rules
Review cookie patterns, built-in rules and subscription sources from Settings.

Tracking cookies, EasyPrivacy and custom rules

Chrome cookie access is optional. Grant it only if you want matching tracking cookies removed; this is distinct from blocking network requests.

Built-in rules, custom wildcard patterns and compatible subscriptions such as EasyPrivacy supply matching rules. Subscription text is processed into browser rules, not executed as remote code.

Inspect a matching rule before editing it. Broad wildcard patterns can affect services a website needs.

Allow trusted services and troubleshoot a broken page

Allow keeps paused websites and allowed items separate. Prefer a precise service exception when one resource is needed; use a website pause only when the broader exception is appropriate.

Home also provides Block element and Report a problem. Review the report dialog before sending: a report intentionally sends diagnostic information and is separate from normal local activity storage.

Chrome 6.11 Allow controls for paused websites and allowed items with support guidance
Remove temporary exceptions when they are no longer needed.
Chrome 6.11 local privacy settings with fingerprinting preferences and protection controls
Privacy preferences complement the six protection categories.

Local-first privacy with explicit reporting

Settings, custom rules, allowlists, subscription sources and recent activity are stored locally. There is no automatic telemetry; sending a problem report is a separate action you choose.

Optional fingerprinting controls address supported browser signals. Do Not Track is a preference signal, not a promise that a website will comply. Subscription updates contact the configured list providers.

A tracker blocker does not change your IP address or make browsing anonymous. Blocking can change page behavior, so test important workflows and review exceptions.

BP Tracker Blocker FAQ

Does it block every tracker or ad?

No. Coverage depends on the rules, enabled protections and website behavior. Review current-page activity and use precise exceptions when needed.

Is cookie access required?

Cookie access is optional in Chrome and used for matching cookie removal. It is separate from network blocking.

What if a website stops working?

Inspect the affected category and allow the required item. If necessary, pause that trusted website while troubleshooting, then remove unneeded exceptions.

Are Firefox and Edge identical to Chrome?

Do not assume so. This overview covers Chrome 6.11; consult the other browser listings for their own release details.

Scroll to Top