Privacy rights need infrastructure,
not more pop-ups.
Europe has strong rights on paper. In practice, people are still asked to manage those rights through repetitive, service-controlled interfaces. ADPC exists because meaningful consent, refusal, withdrawal and objection require a communication layer that fits human life and modern digital systems.
Current consent infrastructure
is structurally broken.
Cookie banners were never designed to become the main infrastructure for digital rights. Three structural failures explain why the status quo cannot hold.
The banner model is structurally weak
Cookie banners ask too much of individuals, create inconsistent records, encourage manipulative design, and make rights difficult to remember or revise. Every service solves the same problem separately, at scale.
Rights communication is not human-compatible
Privacy choices are cognitive, contextual and sometimes collective. People need memory support, accessible interfaces, age-appropriate explanations, and the possibility of trusted assistance. Banners offer none of this.
Rights stop at the interface layer
Rights exist in law, but they are not embedded in digital architecture. Without a user-side communication layer, consent and objection remain dependent on interfaces controlled by the same actors seeking data access.
Six reasons ADPC is different.
ADPC was designed around the actual requirements of EU data-protection law, not as a workaround or a market convenience.
Rights-first
ADPC starts from EU data-protection logic rather than advertising-market convenience. Consent, refusal, withdrawal and objection are first-class concepts, not afterthoughts.
Bidirectional
Both services and user-side tools participate in the exchange. Services express what they request; user-side software communicates back. Neither party is the sole gatekeeper.
Purpose-sensitive
ADPC can communicate specific choices for specific purposes, not only a global binary signal. Users keep different preferences for analytics, advertising, personalisation and more.
Opt-in compatible
Unlike signals designed purely for opt-out markets, ADPC supports consent as well as refusal, withdrawal and objection, matching the full grammar of EU data-protection law.
Implementation-ready
ADPC is publicly specified and already connected to existing website and CMP workflows. There is a working browser extension, WordPress integration and documented CMP-side support.
Future-ready
ADPC extends beyond websites to IoT, mixed reality, children’s protection with guardian support, AI-assisted privacy management and rights-aware AI-based systems.
A better rights layer is also
better market infrastructure.
A common communication layer can reduce duplicated compliance costs, improve legal certainty, support SMEs and startups, and make trustworthy digital services easier to build. For the EU, this is also a question of digital sovereignty: the technical grammar of rights expression should reflect European law and values.
ADPC does not solve every privacy problem. It does solve a critical architectural problem: how rights-relevant requests and decisions can be communicated in a reusable, machine-readable, human-compatible way.
Reduced compliance costs, legal certainty, and a reusable layer that scales across services, devices and jurisdictions.
A concrete path from GDPR rights to interoperable implementation, aligned with proposed Article 88b and EU digital sovereignty goals.
Set preferences once. Exercise rights without clicking through hundreds of banners. Trust that choices are respected and auditable.
ADPC is the practical path
from rights to implementation.
Read how the protocol works, explore its technical specification, or find out how Article 88b creates the legal pathway for rights infrastructure like ADPC.