ProtoConsent

User‑side, purpose‑based consent for the web.

ProtoConsent is a browser extension to control how websites may use your data, expressed in terms of purposes, from inside your browser.

No central server, no tracking, no sharing of personal data — everything stays in your browser by default.

Browser‑level, purpose‑based controls

No backend, local‑only storage

Early-alpha research prototype

View the code on GitHub Read the technical overview →

ProtoConsent complements existing consent and tracking solutions. It is not a production consent platform or legal product.

ProtoConsent doesn’t invent new tracking or blocking mechanisms. It builds on existing browser APIs, but organises everything around user‑defined, purpose‑based preferences instead of vendors or individual trackers.

Why ProtoConsent?

Moving purpose‑based controls into the browser

Today, consent banners often put all the work on the user and all the power on each individual website. ProtoConsent explores a different approach: giving users a single place to manage data‑use purposes across sites, and enforcing those choices at the browser level.

Give users one place to express their data‑purpose choices across sites.
Complement existing consent and tag setups instead of replacing them.
Turn abstract “tracking” into concrete, per‑purpose decisions.
Enforce choices with browser‑level rules, not one more on‑page script.

How it works

What ProtoConsent actually does

ProtoConsent is a browser extension that lets users define how different data‑use purposes should be treated on each site, then applies those rules locally in the browser. All preferences and enforcement happen on the user’s device.

Per‑site purpose profiles: choose how to treat functional, analytics, advertising, personalisation and advanced tracking for each domain.
Local‑only storage: no backend service and no external preference store.
Network‑level enforcement: uses browser extension APIs (such as declarative network rules) to block or allow requests related to specific purposes.
Composable with CMPs: designed to sit alongside existing consent mechanisms and tag configurations.

What you can do today

Early alpha, meant for exploration

ProtoConsent is an early alpha, meant for exploration and feedback, not production use yet (baseline v0.1.0). It’s best suited for people comfortable installing early-stage browser extensions and reading code.

Install the extension locally and define purpose profiles on a few test sites.
See how declarative rules apply to real network requests in the browser.
Use the code and data model as a starting point for experiments or internal demos.
Open issues or pull requests to discuss purpose categories or enforcement strategies.

Alpha · code‑first Feedback welcome Open to collaboration

Who it’s for today

Product, data & privacy teams

Explore what browser‑level, purpose‑based controls could look like in practice, beyond today’s consent banners and tracking settings. Use the prototype to discuss future consent flows, analytics and ads choices, and browser signals with stakeholders.

Developers & implementation engineers

Inspect the extension’s architecture, rules, and data model. Experiment with how browser APIs can express and enforce purpose‑based preferences for analytics, advertising, personalisation and third‑party services, and how sites or SDKs might consume those signals.

Researchers & open‑web standards folks

Use ProtoConsent as a sandbox to test ideas around browser‑mediated consent, purpose labelling, and open‑web preference signals. Connect those experiments with ongoing work on web privacy, permissions, and consent‑related standards.

Get involved

If you work around privacy, consent UX, tracking, or browser internals and feel like taking a look or sharing thoughts, I’d really appreciate it.

Star or fork the GitHub repo.
Open an issue with feedback or questions.
Reach out by email at ProtoConsent@gmail.com with “ProtoConsent” in the subject.