This change affects only the default settings Brave users who wish to retain current, more aggressive but occasionally-website-breaking behavior can do so by setting the “trackers and ads blocked” setting in Shields to the “aggressive” setting. disable Brave’s privacy protections) to use certain sites, leaving those Brave users exposed to the worst kinds of privacy harm. Second, this change aims to reduce how often Brave users have to “drop shields” (i.e. First, recent privacy protections in Brave protect users from the kinds of tracking first-party subresources can carry out (e.g. This change is being made for two reasons. Brave will continue blocking third-party requests as it currently does, using the crowdsourced information gathered by EasyList, EasyPrivacy, uBlock Origin and similar projects.

In order to improve privacy and Web compatibility, Brave will by default not apply network level filter list blocking to same-site 1 subresources, starting in version 1.30, or the Beta and Nightly versions at time of this posting 2. This post was written by Peter Snyder, Director of Privacy and Senior Privacy Researcher. This work was done by Research Engineer Anton Lazarev.

Brave block website