0PN demonstration, operated by Open Consent Group Ltd
One age check, step by step
Each step creates a record and shows who holds it. Both branches can be run.
1Arrival
Until the notice is presented, this page sets no identifier and calls no third party. Your browser reports:
2Notice
The notice comes before any request. The page fetches it, recomputes its hash and compares that with the published value.
Notice as published
3Receipt
You receive evidence of the notice. It carries no identifier for you, and none is needed to issue it.
4Choice
Decline or proceed. A refusal is recorded. No request goes to the provider, and you keep your receipt.
5Processing
The simulated provider gets a method class and nothing else, so it does not learn which service is asking. Each party logs its own events, apart from the notice event log. The event types are proposed and are not adopted.
| Party | Event | Bound to notice |
|---|
6Change
Changes here are simulated for this run only. The published notice and log do not change.
7Challenge or withdrawal
A challenge goes to the provider, the party accountable for the result. A withdrawal goes to the relying party. Each is a new event linked to the receipt, which is never altered.
8Inquiry
An authority asks four questions. Each is answered from three record sets, kept distinct: the processing record, the notice and consent record, and your receipt.
| Question | Answer | Answered from |
|---|
Processing record
Notice and consent record
Your receipt
This page does not specify age assurance methods or decide whether a check is lawful. It makes no conformance claim. Where each field comes from. Controller Identity Record. Notice event log.