Web Standards at Brave: Global Privacy Control

20211202_rev01 · COMPARED WITH 20211005_rev01 · ARCHIVE SNAPSHOT, DATE APPROXIMATE

Full text changes — 20211005_rev01 to 20211202_rev01

11[WebStandards@Brave](https://brave.com/web-standards-at-brave/)
22
3By Peter Snyder (@pes10k), Senior Privacy Researcher at Brave, and Implementation by Anton Lazarev, Research Engineer at Brave
3By the Brave Web Standards Team
44
5_By Peter Snyder, Senior Privacy Researcher at Brave, and Implementation by Anton Lazarev, Research Engineer at Brave_
6
57GPC 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
68
79One 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]().
810
911As part of our privacy-in-Web-Standards work, we're proud to have been involved in the design for the "Global Privacy Control" (GPC) proposal. The GPC proposal allows Web users to signal that they do not want to be tracked online, and where relevant, assert legal privacy rights, as described in legislation like the EU's GDPR and California's CCPA. GPC is meant as an _additional_ privacy tool for browser vendors and Web users; it does not take the place of any existing privacy protections Brave provides.
1012
41431. 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). [↩︎]()
4244
43452. i.e., identify users by their browser configuration and characteristics, instead of through stored identifiers like cookies. [↩︎]()
4446
4547## Related articles
4648
47## [#3: WebBundles Harmful to Content Blocking, Security Tools, and the Open Web](https://brave.com/web-standards-at-brave/3-web-bundles/)
49## [Encrypting DNS Zone Transfers](https://brave.com/web-standards-at-brave/5-encrypting-dns-zone-transfers/)
4850
51Brave, 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.
52
53[Read this article →](https://brave.com/web-standards-at-brave/5-encrypting-dns-zone-transfers/)
54
55## [WebBundles Harmful to Content Blocking, Security Tools, and the Open Web](https://brave.com/web-standards-at-brave/3-web-bundles/)
56
4957Google 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.
5058
5159[Read this article →](https://brave.com/web-standards-at-brave/3-web-bundles/)
5260
53## [#2: Brave, Fingerprinting, and Privacy Budgets](https://brave.com/web-standards-at-brave/2-privacy-budgets/)
61## [Brave, Fingerprinting, and Privacy Budgets](https://brave.com/web-standards-at-brave/2-privacy-budgets/)
5462
5563This 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.
5664
5765[Read this article →](https://brave.com/web-standards-at-brave/2-privacy-budgets/)
5866
5967## Ready to Brave the new internet?