ANCR Working Group

ANCR Working Group logo

ANCR Working Group, Kantara Initiative

The Anchored Notice and Consent Receipt (ANCR) Working Group builds inspectable, implementation-ready artefacts for notice and consent receipt exchange. Our flagship artefact is the Consent Receipt, and its evolution into the ISO/IEC TS 27560 Notice Receipt Extension.

Announcement: Co-Regulated Digital Identification (CRDI)

The ANCR Notice Receipt Extension now specifies co-regulated digital identification (CRDI): a model in which identification is governed by two concurrent rule sets at once, the controller’s own rules, and the public rules of treaty, law, and standards. The public rule set is expressed as inspectable record structure and is verifiable before identification occurs. Accountable controller identification and machine-readable notice come first; personal identification follows. This makes the difference between identification that is transparent and identification that is surveillance testable in the record itself.

The Consent Receipt is Kantara’s foundational transparency artefact: a machine-readable record, handed to a person at the point of notice, that captures who is processing their data, for what purpose, under what legal basis, and how to exercise their rights. It turns consent from an unverifiable claim into inspectable evidence.

Lineage:

  1. Kantara Consent Receipt, the original specification that established the receipt as the unit of consent evidence.
  2. ISO/IEC 29184:2020 (Annex B), the Consent Receipt was adopted into ISO as the hosted consent-receipt / consent-record reference, explicitly citing the Kantara Consent Receipt specification.
  3. ISO/IEC TS 27560:2023, became the international consent record information structure.
  4. ANCR (Anchored Notice and Consent Receipt), anchors the receipt to a verifiable controller identity and a notice event, so the record is not just issued but traceable.
  5. Notice Receipt Extension, extends ISO/IEC TS 27560:2023 into a receipt-exchange profile for anchored, inspectable notice evidence. Published as Release 1 and under Working Group review.

Release 1, now open for Working Group review

The ANCR Extension for ISO/IEC TS 27560:2023 is published as Release 1, the v1.0 Release Candidate, released 7 September 2026 and put to the Working Group for candidate review and approval.

Release 1 is 1,036 lines: clauses 1 to 8, twenty seven terms, twelve mandatory requirements, conformance criteria C1 to C8, and Annexes A to F. Annex A maps field by field to ISO/IEC TS 27560:2023 and A.0 states the single deviation from the base with its rationale. Annex F is a clause level crosswalk to the registered scope of the SC 27/WG 5 preliminary work item Gap analysis for standards on privacy notices and consent and ways to address potential gaps, registered by SC 27 Resolution 2026/32.

The five priority comments raised against the version circulated to ISO/IEC JTC 1/SC 27/WG 5 as N 5211 are carried forward for disposition by the Working Group and are not treated as resolved by this revision.

Where to find the spec:

Submission index

The following working-group outputs correspond to the documents submitted for ISO/IEC JTC 1/SC 27/WG 5, under the preliminary work item registered by SC 27 Resolution 2026/32:

  • 27560 Notice Receipt Extension, the receipt-exchange profile extending ISO/IEC TS 27560:2023 (the N-doc that carries the Consent Receipt into the standard).
  • WG5 / CoE Liaison materials, the plenary and Council of Europe liaison decks.

The canonical version for the submission is fixed by tag. Release 1 is tagged ancr-ext-release-1, so a clause or line number cited against it points at a text that does not move.

Other working areas

  • Transparency Performance Indicators (TPI), the ANCR transparency-scheme and conformity work: TPI
  • DPV (Transparency Code of Practice legal model), evidence-first DPV-style extension material: ancr-dpv

Participate

Notes

  • This site is published from the ancr-ts-27560-extension/docs/ folder (GitHub Pages / Jekyll). Pages outside that folder are linked to the GitHub repository tree, which always resolves.