Web Standards at Brave: Global Privacy Control

20250702_rev01 · COMPARED WITH 20250104_rev01 · ARCHIVE SNAPSHOT, DATE APPROXIMATE

Full text changes — 20250104_rev01 to 20250702_rev01

1919**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.
2020
2121## Brave's Implementation of the "Global Privacy Control"
2222
2323Brave 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.
2424
25Brave does not require users to change anything to start using the GPC to assert their privacy rights. For versions of Brave that have GPC implemented, the feature is on by default. To disable GPC in Brave, please see [this support article](https://support.brave.com/hc/en-us/articles/360017989132-How-do-I-change-my-Privacy-Settings).
25Brave does not require users to change anything to start using the GPC to assert their privacy rights. For versions of Brave that have GPC implemented, the feature is on by default. To disable GPC in Brave, please see [this support article](https://support.brave.app/hc/en-us/articles/360017989132-How-do-I-change-my-Privacy-Settings).
2626
2727We believe that anyone choosing to use Brave has already made an unambiguous expression that they do not want their data to be sold or shared online. Legislation like the [CCPA recognizes that the decision to use privacy-focused tools like Brave is itself an expression of user preference](https://oag.ca.gov/sites/all/files/agweb/pdfs/privacy/ccpa-fsor-appendix-e.pdf) for privacy. Requiring users in Brave to take an additional step to enable GPC therefore seems both unnecessary and disrespectful to our users (who have already made their preference clear!).
2828
2929## Brave, GPC, and The Inevitability of a Private-by-Default Web
3030
3131Since we started, Brave has argued that a healthy, sustainable, vibrant Web requires a privacy-preserving, privacy-by-default Web; business models that depend on tracking will soon look as antiquated as Flash, Java Applets or "made for IE" badges.