See machine-readable
privacy choices in action.
ADPC is easiest to understand when you see the exchange: a service requests, a user-side tool presents and remembers, and the service respects the resulting choice. The demonstrations below show how ADPC works across different environments.
Available and planned
demonstrations
Some demos are available now. Others are in development. Each clearly states its status, requirements, and known limitations.
Web demo
A service exposes ADPC consent requests via a well-known resource. A user-side client reads the request, presents a summary, and sends back the signed choice.
Browser extension demo
A user-side browser extension detects ADPC-capable sites, presents the consent request in a readable interface, and sends the user’s decision as an HTTP header.
WordPress demo
ADPC request configuration, discovery headers, incoming signal logs, and CMP mapping in a working WordPress installation.
IoT demo
Device discovery, simplified plain-language explanation, consent approval, and withdrawal for connected devices in a home or enterprise environment.
Mixed-reality demo
Contextual rights prompts in immersive environments. Privacy choices appear in-world when a service requires data, without breaking the experience.
AI assistant demo
An AI assistant explains the consent request in plain language, helps the user review the implications, and relays the confirmed decision back to the service.
Demonstrations and production use
Research prototypes and production implementations are different things. Each demo is clearly labelled.
Status declared
Every demo clearly states whether it is a research prototype, a reference implementation, or a production-ready deployment.
Limitations documented
Known limitations, requirements, and next development steps are published alongside each demo so you can evaluate it accurately.
Source code published
All demos link to their source code on GitHub so developers can inspect, fork, and contribute to the implementation.
Test, report, improve
Use the demos to understand the protocol, test implementation ideas, evaluate usability, and contribute feedback to the specification.