Brave Software Web Standards at Brave: Global Privacy Control changes — 20220205_rev01

17

13

**First**, anything that makes it clearer to the surveillance-economy that users don't want, don't approve of, and don't consent to being followed and tracked on the Web is a good step (and something that Brave has been promoting since we started).

18

14

19

15

**Second**, similar consent mechanisms being pushed by the AdTech industry are incompatible with the kinds of privacy protections which Brave includes. For example, the Orwellian-named "consent management platforms" often require your browser to execute code from tracking companies, just to ask them to not track you. Brave blocks these network requests to tracking companies, which the tracking companies often interpret as "no preference expressed yet".

20

16

21

17

Good solutions to improving Web privacy cannot require browsers to interact with companies that have already lost users' trust; the "Global Privacy Control" proposal is a strong framework to begin building better privacy protections on.

22

18

23

**Third**, Brave is interested in working with responsible, ethical, privacy-respecting publishers who want to respect user privacy _without requiring users to click through intentionally confusing dialogs and "consent forms"_. We're especially interested in working with publishers who want to respect user privacy both where the law requires it (e.g., [GDPR](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation), [CCAP](https://en.wikipedia.org/wiki/California_Consumer_Privacy_Act)), as well as in areas where the law hasn't yet caught up to recognize privacy as a right (and pervasive, non-consensual tracking as wrong). We're excited by the publishers we've worked alongside during the "Global Privacy Control" proposal, and we hope others will follow their lead.

19

**Third**, Brave is interested in working with responsible, ethical, privacy-respecting publishers who want to respect user privacy _without requiring users to click through intentionally confusing dialogs and "consent forms"_. We're especially interested in working with publishers who want to respect user privacy both where the law requires it (e.g., [GDPR](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation), [CCPA](https://en.wikipedia.org/wiki/California_Consumer_Privacy_Act)), as well as in areas where the law hasn't yet caught up to recognize privacy as a right (and pervasive, non-consensual tracking as wrong). We're excited by the publishers we've worked alongside during the "Global Privacy Control" proposal, and we hope others will follow their lead.

24

20

25

21

## Brave's Implementation of the "Global Privacy Control"

26

22

27

23

Brave is currently testing an implementation of the GPC proposal in our [Nightly desktop](https://brave.com/download-nightly/) and [Android beta channels](https://play.google.com/store/apps/details), and expect to implement it in our iOS browser as the proposal goes through the standardization process.

28

24

29

25

Importantly, Brave does not require users to change anything to start using the GPC to assert your privacy rights. For versions of Brave that have GPC implemented, the feature is on by default and unconfigurable. We've decided to implement GPC in this way for several reasons.

+[WebStandards@Brave](https://brave.com/web-standards-at-brave/)
+By the Brave Web Standards Team
 _By Peter Snyder, Senior Privacy Researcher at Brave, and Implementation by Anton Lazarev, Research Engineer at Brave_
 GPC launches today from a [consortium of privacy-respecting organizations](https://globalprivacycontrol.org/press-release/20201007.html), to protect consumer privacy and provide consumers with greater control of their data
 One of Brave's core goals is to improve privacy on the Web. The main way Brave improves Web privacy is by building strong, on-by-default privacy protections in the Brave browser. However, Brave also works to improve privacy on the Web in general, particularly by advocating for privacy in the W3C [1]().
 **First**, anything that makes it clearer to the surveillance-economy that users don't want, don't approve of, and don't consent to being followed and tracked on the Web is a good step (and something that Brave has been promoting since we started).
 **Second**, similar consent mechanisms being pushed by the AdTech industry are incompatible with the kinds of privacy protections which Brave includes. For example, the Orwellian-named "consent management platforms" often require your browser to execute code from tracking companies, just to ask them to not track you. Brave blocks these network requests to tracking companies, which the tracking companies often interpret as "no preference expressed yet".
 Good solutions to improving Web privacy cannot require browsers to interact with companies that have already lost users' trust; the "Global Privacy Control" proposal is a strong framework to begin building better privacy protections on.
+**Third**, Brave is interested in working with responsible, ethical, privacy-respecting publishers who want to respect user privacy _without requiring users to click through intentionally confusing dialogs and "consent forms"_. We're especially interested in working with publishers who want to respect user privacy both where the law requires it (e.g., [GDPR](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation), [CCAP](https://en.wikipedia.org/wiki/California_Consumer_Privacy_Act)), as well as in areas where the law hasn't yet caught up to recognize privacy as a right (and pervasive, non-consensual tracking as wrong). We're excited by the publishers we've worked alongside during the "Global Privacy Control" proposal, and we hope others will follow their lead.
+**Third**, Brave is interested in working with responsible, ethical, privacy-respecting publishers who want to respect user privacy _without requiring users to click through intentionally confusing dialogs and "consent forms"_. We're especially interested in working with publishers who want to respect user privacy both where the law requires it (e.g., [GDPR](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation), [CCPA](https://en.wikipedia.org/wiki/California_Consumer_Privacy_Act)), as well as in areas where the law hasn't yet caught up to recognize privacy as a right (and pervasive, non-consensual tracking as wrong). We're excited by the publishers we've worked alongside during the "Global Privacy Control" proposal, and we hope others will follow their lead.
 ## Brave's Implementation of the "Global Privacy Control"
 Brave is currently testing an implementation of the GPC proposal in our [Nightly desktop](https://brave.com/download-nightly/) and [Android beta channels](https://play.google.com/store/apps/details), and expect to implement it in our iOS browser as the proposal goes through the standardization process.
 Importantly, Brave does not require users to change anything to start using the GPC to assert your privacy rights. For versions of Brave that have GPC implemented, the feature is on by default and unconfigurable. We've decided to implement GPC in this way for several reasons.
 - * *
 . Brave also advocates for, and improves privacy in, proposed Web standards, as members of the [W3C](https://www.w3.org/) and co-chairs the W3C's [privacy review interest group](https://www.w3.org/Privacy/IG/) (PING). [↩︎]()
 . i.e., identify users by their browser configuration and characteristics, instead of through stored identifiers like cookies. [↩︎]()
+## Related articles
+## [Encrypting DNS Zone Transfers](https://brave.com/web-standards-at-brave/5-encrypting-dns-zone-transfers/)
+Brave, along with a team of DNS experts from the industry and open source communities, recently helped publish an IETF standard (RFC 9103) to fix a long-standing privacy and security hole in the DNS.
+[Read this article →](https://brave.com/web-standards-at-brave/5-encrypting-dns-zone-transfers/)
+## [WebBundles Harmful to Content Blocking, Security Tools, and the Open Web](https://brave.com/web-standards-at-brave/3-web-bundles/)
+Google is proposing a new standard called WebBundles. This standard allows websites to "bundle" resources together, and will make it impossible for browsers to reason about sub-resources by URL. While we appreciate the problems the WebBundles and related proposals aim to solve, we believe there are other, better ways of achieving the same ends without compromising the open, transparent, user-first nature of the Web.
+[Read this article →](https://brave.com/web-standards-at-brave/3-web-bundles/)
+## [Brave, Fingerprinting, and Privacy Budgets](https://brave.com/web-standards-at-brave/2-privacy-budgets/)
+This post first summarizes what browser fingerprinting is, and common defenses. Second, the post presents problems with "dynamic privacy approaches", and why Brave is skeptical they are effective for protecting against fingerprinting. Third, the post presents Brave's fingerprinting protections, current, upcoming and longer-term.
+[Read this article →](https://brave.com/web-standards-at-brave/2-privacy-budgets/)
+## Ready to Brave the new internet?
+Brave is built by a team of privacy focused, performance oriented pioneers of the web. Help us fix browsing together.
+[Download Brave](https://laptop-updates.brave.com/download/BRV001)

Web Standards at Brave: Global Privacy Control

Full text changes — 20211202_rev01 to 20220205_rev01