See exactly what happens, per purpose and per site
Why ProtoConsent?
Moving purpose-based controls into the browser
The gap between clicking “accept” and what actually happens to your data is invisible. Users have no consistent way to enforce or verify their choices across sites. ProtoConsent closes that gap: one place to manage data-use purposes, with enforcement and visibility at the browser level.
Give users one place to express their data-purpose choices across sites.
See what enforcement does: blocked requests, GPC signals, and site declarations, all visible in real time.
Turn abstract “tracking” into concrete, per-purpose decisions.
Enforce choices with browser-level rules, not one more on-page script.
Per-site profiles with purpose toggles, real-time overview dashboard, and blocked domains by purpose.
What it does
Consent you can enforce and verify
Per-site profiles and purpose toggles: choose what each site may do with your data across six purposes.
Two operating modes: Blocking mode blocks requests directly. Monitoring mode delegates blocking to your existing tools and adds purpose attribution via the Proto dashboard.
Conditional privacy signal (GPC): sent only when your choices justify it, per site, with legal weight under CCPA/CPRA.
Cookie banner management: consent banners handled via cosmetic hiding and scroll unlock based on your purpose preferences. No DOM interaction, no click simulation.
Enhanced protection out of the box: curated blocklists from public sources, cosmetic filtering, CNAME detection, URL parameter stripping, and regional filters for 36 languages. Enabled by default and kept up to date automatically.
Inter-extension API: other privacy extensions can query the user's consent state via the browser messaging protocol, enabling composable privacy tools.
Site declarations and SDK: websites can publish their data practices or read user preferences and adapt. Both optional, both open.
ProtoConsent is a working browser extension with purpose-based enforcement,
a conditional GPC signal, site declarations, and an SDK. Install it from the Chrome Web Store, Firefox Add-ons, or the Edge Add-ons Store; you can also load it locally from GitHub on Chromium-based browsers.
Integrate the SDK: read user preferences from your pages. See the developer guide.
via Chrome Web Store Opera Addons In reviewAlso works on Vivaldi, Arc, and any Chromium-based browser.
Open source (GPL-3.0+)SDK: MITFeedback welcomeOpen to collaboration
Who it's for
End users
Control how every website uses your data from a single popup. See exactly what gets blocked, per purpose and per site. Everything works locally in your browser.
Website owners & publishers
Declare your site's data practices with a single JSON file. ProtoConsent displays it to users alongside their preferences, with clear visual indicators for each purpose.
Developers
Read user consent preferences directly from the browser with the SDK. Or publish a .well-known/protoconsent.json to declare your practices. Both paths are straightforward.
Privacy & compliance teams
See how purpose-based controls work in practice. Use ProtoConsent to align consent flows, GPC signals, and analytics choices with your privacy strategy.
Live test
Your preferences for this site
This section queries the ProtoConsent extension in real time using the SDK protocol.
If the extension is installed, your current preferences for protoconsent.org are shown below.
Get involved
ProtoConsent is free and open source: GPL-3.0+ for the extension, MIT for the SDK, CC BY-SA 4.0 for documentation. Contributions, feedback, and adoption are all welcome.
Publish a .well-known/protoconsent.json on your site to declare your data practices. Check it with the validator.
Integrate the SDK (MIT) to read user preferences from your pages.
Open an issue or pull request on GitHub with feedback, bug reports, or ideas.
via Chrome Web Store
Opera Addons In review
Also works on Vivaldi, Arc, and any Chromium-based browser.