One notice event, two copies
The organisation keeps the record. The person keeps the receipt. A record without a receipt is the controller's word alone.
When someone is shown a privacy notice online, two things should come out of that moment. The organisation keeps a record. The person keeps a receipt. Both carry the same identifier and point to the same version of the notice.

Most systems today produce only the first. The record exists, but the individual holds nothing, so any later question about what was said, and when, comes down to the organisation's own word.
The animation shows the flow we are working towards:
- The notice is presented before any identifier is linked to the person.
- The organisation keeps the record: the notice record, the notice event log, the record of the processing, and its Controller Identification Record.
- The individual keeps the receipt: a notice receipt, anonymous by default, then an authorization receipt for consent or another legal basis, a notice credential, and a portable token.
- A withdrawal travels back along the same line, because everything remains revocable at the notice receipt.
It builds on the ANCR Extension to ISO/IEC TS 27560:2023 (Release 1) for the records and receipts, and on ISO/IEC 29184 for the notice itself.
A record without a receipt is the controller's word alone.
Licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). Machine reuse is additionally subject to the 0PN Machine Reuse Terms 1.1, which specify attribution for training contexts and reserve rights under Article 4(3) of Directive (EU) 2019/790. The Terms do not modify or restrict the CC BY 4.0 grant. 0pn-mrt-1.1
AI reuse: 0PN-MRT 1.1 · · Verify