SPECWORK · ANCR Extension for ISO/IEC TS 27560:2023

Identify the controller before anyone identifies you.

A receipt is the ordinary evidence of an exchange. Online, the evidence runs one way: the person is identified exhaustively, and the organisations doing the identifying leave no record in the person's hands. The ANCR extension fixes the missing half. It specifies a notice receipt that anchors who is accountable and which notice applied, without creating a single new identifier about the individual.

Release 1 at a glance

One receipt, held by the person

Anchored Notice Receipt

ancr-notice-receipt-2.0
receipt_idrcpt_7f3a…c1e9
notice_idntc_example_store
notice_version_referencev2026-09-07
controller_identification_record_idcir_8b12…04aa
presented_at2026-09-07T10:14:02Z
notice_typeonline_notice
pii_principal_idnot required
account_idnot required
anchored_notice_receipttrue
public rule setcode of practice, ref.
privacy_access_pointoperable without login

Verify: resolve notice_version_reference, compare notice_hash and published_at with the notice retrieved now. Issued by either party.

Field names as specified in Release 1. The person holds this record. It identifies the controller, not the person.

Why this exists

The problem the extension answers

Privacy notices, physical signs and codes of conduct state what a controller undertakes. None of them carries the version in effect at a particular disclosure, and none of them gives the person a record of the event. Consent management tools capture a permission for the organisation's own files and hand the person nothing that can be checked later.

The ANCR extension turns the disclosure event into evidence that both sides hold. It profiles and extends ISO/IEC TS 27560:2023, the international consent record structure, so that a Notice Receipt binds to an immutable notice version, that version resolves to a hash and a publication time, and every issuance and material change is logged. A question about what was presented, and when, becomes answerable from records.

Why now

Where the standards work stands

ISO/IEC JTC 1/SC 27/WG 5 has registered PWI 26689 on notice and consent evidence, and ISO/IEC JTC 1/SC 44/WG 1 has registered PWI 27138 on an Internet Transparency Code of Practice profile. Both need a machine readable notice record and receipt to point at. Release 1 is offered as prior art and as an implementation reference for both, and Annex F crosswalks it clause by clause to the registered scope of PWI 26689.

Working Group approval of Release 1 is what moves it toward a Kantara Initiative Recommendation and onward as a liaison contribution to SC 27/WG 5. That approval depends on review comments, implementer feedback and disposition of the open items. This is the moment to take part.

Who this is for. Implementers of wallets, identity providers and consent tooling who want a receipt their users can keep. Regulators and supervisory staff who need transparency they can test rather than read. National body delegates in SC 27 and SC 44 mirror committees. Researchers in privacy engineering, data protection law and human computer interaction. Anyone who has ever been asked to log in before being told who is collecting their data.

Review

Review Release 1 before the Working Group votes on it.

Comments go on GitHub pull request #34 or to the Working Group list. Line numbers are stable against the tag, so a comment against line 512 points at text that does not move.

Open the release on GitHub

About the extension

A notice receipt profile of the consent record standard.

The extension specifies a machine readable online Notice Record and a corresponding Notice Receipt that together provide durable evidence of notice disclosure. It is lawful basis agnostic. Where the lawful basis is consent, the authorization is a specialisation of the TS 27560:2023 consent receipt.

Sequence

Controller first

Controller identification shall precede any demand for personal identification, and the artefacts in clause 7 shall be inspectable independently of any personal identifier. An implementation that demands personal identification before a resolvable Controller Identification Record and its bound notice version are available does not conform. That single rule is the core of the document and the reason TCIEG supports it.

Co-regulated identity

Two rule sets, one identifier

Identification online is governed by two rule sets at the same time: the controller's own rules in service terms and technical design, and the public rules in treaty, law and standards. Self regulation on its own leaves the identifier privately defined. State regulation on its own lacks artefacts that can be inspected at the moment of interaction. The extension supplies the record structure through which the public rule set becomes machine readable, inspectable and enforceable, and makes the difference between identification that is transparent and identification that is surveillance testable in the record itself.

Identity and identification are kept distinct throughout. Identity is what the person owns and expresses. Identification is the process a controller runs to discover, link or assert claims about a person. Consent is a human expression; permissions are managed by systems. Where the two are conflated, an interface permission gets presented as consent.

Clause 6.2

The artefact set

Controller Identification Record

The accountability anchor. Publicly accessible and resolvable before any demand for personal identification, carrying the privacy access point and the public rule reference.

controller_identification_record_id, privacy_access_point, derogation_reference

Notice Record

The versioned notice content, expressing the public rule set in operational form. Each version is a Notice Version Object with an integrity hash and a publication time.

notice_id, notice_url, notice_version_id, notice_hash, published_at

Notice Receipt

The disclosure evidence, held bilaterally. Classified as an Anchored Notice Receipt when bound to the CIR and the notice version. Generable and verifiable without an account or a principal identifier.

receipt_id, notice_version_reference, presented_at, notice_type, schema_version

Notice Event Log

The lifecycle evidence. Issuance and material change at minimum, with hooks for withdrawal and objection, and processing events recorded separately from notice lifecycle events.

event type registry, append only state changes, reconstruction at a stated time

Two factor online notice

Clause 6.1

The extension supports a two factor online notice pattern for durable evidence of disclosure. Factor one is presentation, using ISO/IEC 29184 aligned controls such as layered presentation and timing. Factor two is the evidence receipt, generated as proof that a specific notice version was presented or available at a specific time. The two factors are counted within a single notice event. The pattern originates in the Minimum Viable Consent Receipt, the specification from which the ANCR co-regulation perspective developed.

Clause 5.1, criteria C1 to C8

Conformance

C1 SequenceA resolvable Controller Identification Record is available before any demand for personal identification.
C2 Minimum notice disclosureThe required elements are resolvable at the time of the disclosure event.
C3 Anonymity by defaultThe Anchored Notice Receipt is generable and verifiable without an account_id or a pii_principal_id.
C4 Public rule referenceThe Notice Record states the code of conduct, code of practice or legal instrument relied upon.
C5 EvidenceA Notice Event Log entry exists for issuance and each material change, and each receipt binds to a notice version whose hash matches the notice retrieved at assessment.
C6 Reciprocal and proportionate disclosureThe technology and controls disclosure set is published and bound to the version in effect.
C7 Non-exclusionAt least one privacy access point works without the person holding, presenting or authenticating a digital identification credential.
C8 Authorization stateWhere relied upon, a single Authorization State Object exists, each change is logged, and the state at a stated past time is reconstructable.

Conformance is asserted per notice version, not per organisation. Conformance to TS 27560:2023 alone does not constitute conformance to the extension, because clause 7 specifies artefacts the base specification does not.

How the receipt got here

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 adopted into ISO as the hosted consent receipt and consent record reference, citing the Kantara specification.

  3. ISO/IEC TS 27560:2023

    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 traceable and not just issued.

  5. ANCR Extension for ISO/IEC TS 27560:2023, Release 1

    Extends TS 27560:2023 into a receipt exchange profile for anchored, inspectable notice evidence. v1.0 Release Candidate, 7 September 2026.

Working areas

Four strands, one record structure.

The extension governs the record structure. Everything else in the working group either measures it, expresses it in another vocabulary, or carries it into the standards bodies that need it.

Specification text and schema

The extension

The markdown source in the Kantara repository is the authoritative copy. Release 1 runs to 1,036 lines: clauses 1 to 8, twenty seven terms, twelve mandatory requirements, conformance criteria C1 to C8 and Annexes A to F. The receipt schema identifier is ancr-notice-receipt-2.0 and is versioned separately from the document under a major, minor, patch rule in clause 7.3.4.

Open work after v1.0 includes a JSON Schema for the receipt, the CIR, the event log entry and the Authorization State Object; conformance test procedures for C1 to C8 beyond inspection; an integrity mechanism for an anonymous receipt in place of the per principal HMAC in TS 27560:2023 Annex E; and a field recording which consent construction is in use. Each of these is a place where an implementer can contribute directly.

TPI and the ANCR TPI-R profile

Transparency Performance Indicators

TPI-R is an external assessment methodology that measures how well a live deployment realises the transparency artefacts a standard specifies. It captures the practice, tests the captured information against the requirement, then measures whether the information performs, which for a transparency artefact means whether it can be used for rights access. Four indicators cover timing, required elements, accessibility and security integrity, each rated from -3 (non-operable transparency) to +1 (dynamic, in context transparency).

The ANCR TPI-R variant adds conformance indicators that test the presence and integrity of the CIR, the Notice Receipt, the Anchored Notice Receipt and the Notice Event Log. Annex E of the extension maps each indicator to the clauses that provide its evidence. A TPI-R score is a compliance signal for a deployment; conformance to the document itself is defined by clause 8 and criteria C1 to C8.

Convention 108+ legal model, v0.3

ANCR DPV Model Extension

A vocabulary and legal model expressed in DPV style. It maps the fields the extension specifies into DPV terms, anchors them to the modernised Convention 108, and states acceptance criteria that can be tested against a record or a receipt rather than against a policy document. It covers Convention 108+ legal bases and compatibility of further processing, principles and rights, transparency requirements with timing and custody conditions, the DPV expression of the CIR field set, an information set I1 to I16 for dynamic data and AI systems, and an AI transparency profile anchored to the EU AI Act and ISO/IEC 22989.

It is not a second record structure. Where the two diverge, the extension governs and the DPV companion is corrected. Terms are published under a provisional ANCR controlled namespace so a draft proposal is not mistaken for a registered DPV namespace.

SC 27/WG 5 and SC 44/WG 1

Standards submissions

Working group outputs are submitted to ISO/IEC JTC 1/SC 27/WG 5 as liaison contributions under PWI 26689, Notice and Consent Records. The version circulated as N 5211 on 16 July 2026 is the direct ancestor of Release 1, and the five priority comments raised against N 5211 are carried forward for disposition by the Working Group. Plenary and Council of Europe liaison decks sit alongside the specification in the repository.

Release 1 also records, in Annex B.3, where it meets ISO/IEC PWI 27138 in SC 44/WG 1, an Internet Transparency Code of Practice profile through privacy by design, established on 3 September 2026 and aligned to ISO/IEC 29100, 29184 and TS 27560:2023.

Build

Have a wallet, a notice tool or a test bed?

The open items after v1.0 are implementation work. A JSON Schema, a test procedure or a reference receipt generator would each move the release forward.

Bring an implementation

Release 1

v1.0 Release Candidate, now under Working Group review.

Released 7 September 2026 and put to the ANCR Working Group for candidate review and approval, and on approval for progression toward a Kantara Initiative Recommendation. It continues the lineage of the version circulated to SC 27/WG 5 as N 5211.

Record of the release

TitleANCR Extension for ISO/IEC TS 27560:2023. Anchored Notice and Consent Receipts for operational transparency.
Revisionv1.0 Release Candidate. Supersedes external review draft v0.5 (31 August 2026), the v0.4 baseline, and N 5211 (16 July 2026).
Tagancr-ext-release-1. Line numbers are stable against this tag.
EditorKantara Initiative ANCR Working Group. The editor is named in the release on GitHub.
Schemaancr-notice-receipt-2.0, unchanged from v0.5.
IPRKantara Initiative patent and copyright terms: reciprocal royalty free, with opt out to RAND. Kantara is chartered to contribute the completed work to ISO/IEC SC 27/WG 5.
CommentsPull request #34, or by reply to the Working Group list.

What changed

From v0.5 to Release 1

Seven of the thirteen open items carried into external review are closed. Additions include Annex F, the clause level crosswalk to PWI 26689 as registered by SC 27 Resolution 2026/32; Annex B.3 on the SC 44/WG 1 work item; a normative profiling rule in Annex C for jurisdictions whose lawful basis enumeration differs from the table; the hash input rule in 7.2.4 so that notice_hash is computed over the exact octet stream at notice_url; definitions of full receipt and reference receipt; informative citations for the TPI Conformity Specification and the WG 5 work items; and an assessment statement in clause 5.

Profile B2 is renamed to personal data control record structure. Three passages moved from 7.2.2 into the Introduction and now state the mechanism rather than the outcome, so 7.2.2 carries provisions only. The Introduction opens with the receipt analogy, states the one way evidence asymmetry, and names the missing artefact as the identification and tracking of the controller.

Clause 8

Mandatory requirements

  1. CIR publication. The CIR is publicly accessible and resolvable before any demand for personal identification.

  2. Anonymity by default. No pii_principal_id is required for an Anchored Notice Receipt.

  3. Version binding. Receipts bind to an immutable notice version; historic versions are retained; each version carries an integrity hash and a publication time.

  4. Material change. A material change creates a new notice version and a Notice Event Log entry.

  5. Notice classification. Every receipt populates notice_type from the vocabulary in 7.3.3.

  6. Reciprocal and proportionate disclosure. The technology and controls disclosure set is published and version bound.

  7. Non-exclusion. At least one privacy access point works without a digital identification credential.

  8. Co-regulation conformance. An implementation asserting co-regulated identification satisfies C1 to C8 for each notice version relied upon.

  9. Purpose recorded, bound to the legal authority, the controller and the notice version in effect.

  10. Processing events recorded separately from notice lifecycle events.

  11. Authorization state carried once, by a single Authorization State Object, with changes appended and past state reconstructable.

  12. Schema version stated on every receipt.

Carried forward after v1.0

Open items

ItemStatus
JSON Schema for the receipt, the CIR, the event log entry and the Authorization State ObjectDeferred to a companion artefact. Contributions welcome.
Conformance test procedures for C1 to C8Assessment is by inspection, with normative procedures for C5 and C8 only.
LICENSE and IPR file in the directoryRepository action. The IPR position is stated in the Foreword.
Integrity mechanism for an anonymous receiptOpen. Replaces the per principal HMAC of TS 27560:2023 Annex E.
ISO/IEC 29184 normative reliance versus informative citationPosition stated in the 2.2 NOTE, unchanged.
A field recording which consent construction is in useProposed for Working Group decision at v1.0 approval; a minor schema increment under 7.3.4.
Five priority comments raised against N 5211Carried forward for disposition by the Working Group; not treated as resolved by this revision.

Annex D, informative

Four stage exchange

  1. Anchored Notice Receipt, proof of notice

    Bilateral evidence that a specific notice version was disclosed. Minimum binding identifiers: receipt_id, notice_id, notice_version_reference, controller_identification_record_id, presented_at.

  2. Authorization receipt, basis dependent

    Expresses consent, contract acknowledgement or another authorization state, linked to the stage one receipt.

  3. Notice credential, protocol facing

    A context-specific micro-credential: the authorization as a credential or signed assertion for API or device enforcement, without resharing the full receipt.

  4. Portable token

    Reuse of authorization state across controllers and jurisdictions, traceable to stage one and carrying a status pointer so relying parties can check the notice version and authorization remain active.

Comment

Read the line numbered copy and comment against it.

The review copy and changelog are attached to the release. Comments citing a line number against the tag are the easiest for the Working Group to dispose of.

Comment on pull request #34

Resources

The documents this work stands on.

Standards the extension profiles, the instruments it aligns to, and the working group materials that carry it.

Kantara ANCR WG

Working group

Normative chain

Standards profiled

Where the extension is cited

Work items served

Alignment targets

Legal instruments

Background and argument

TCIEG writing

People and roles

Who does what, and where you would fit.

The specification is a Kantara Initiative working group output. TCIEG runs this community programme to bring implementers, regulators and delegates into that work and to carry it into ISO/IEC. The two are separate bodies with separate rules, and that separation is deliberate.

Owner of the specification

Kantara ANCR Working Group

The Anchored Notice and Consent Receipt Working Group builds inspectable, implementation ready artefacts for notice and consent receipt exchange under the Kantara Initiative, a global non profit commons for trustworthy digital identity and personal data. The working group approves releases, disposes of comments and decides what is submitted to ISO/IEC. Its flagship artefact is the Consent Receipt and its evolution into the ISO/IEC TS 27560 Notice Receipt Extension. The editor of the extension is named in the release record.

Participation follows Kantara operating procedures and the Kantara IPR policy, reciprocal royalty free with opt out to RAND. Membership is through the working group wiki. Working group calls run twice a month.

Community programme, SPECWORK

TCIEG

The Transparency & Consent Interoperability Expert Group works on operational transparency: a transparency code of practice, the Transparency Stack, and co-regulated identity through this extension. In SPECWORK, TCIEG coordinates review, brings implementations to the table, prepares liaison material, and connects the extension to the SC 27/WG 5 and SC 44/WG 1 work items where its members hold editing and delegate roles. TCIEG does not own the specification and does not vote in the Kantara working group on its own behalf.

Named so you can pick one

Roles the work needs

RoleWhat it involves
ReviewerRead the line numbered copy, comment against line numbers on pull request #34 or the list, and follow disposition.
ImplementerBuild a receipt generator, a CIR resolver, a Notice Version Object verifier or a Notice Event Log, and report what the text did not tell you.
AssessorApply the ANCR TPI-R profile to a live deployment and feed the findings back into Annex E and the TPI Conformity Specification.
Schema contributorDraft the JSON Schema companion for the receipt, the CIR, the event log entry and the Authorization State Object.
Legal model contributorExtend the DPV companion to a jurisdiction, or draft a lawful basis profile under the Annex C profiling rule.
National body delegateTake the work into your SC 27 or SC 44 mirror committee and into PWI 26689 or the SC 44/WG 1 work item.
Regulator or supervisory staffTell the working group which artefacts you would rely on in an inquiry and how they would need to be presented.

Meetings and milestones

Where the work is in time.

Working group calls run twice a month. Dates below are from the release record and the working group materials; the wiki carries the live calendar and joining details.

Milestones reached

Recent

May 2026Internet Transparency Code of Practice introduced at CPDP Brussels on the Council of Europe panel, Transparency by Default.
16 Jul 2026ANCR Notice Receipt Extension circulated to ISO/IEC JTC 1/SC 27/WG 5 as document N 5211.
20 Aug 2026Working group calls begin on a twice monthly cadence.
31 Aug 2026External review draft v0.5, with the DPV companion at v0.3. Two blocking decisions settled and four breaking changes applied to the receipt schema.
3 Sep 2026Fifth ISO/IEC JTC 1/SC 44 plenary establishes the preliminary work item on an Internet Transparency Code of Practice profile through privacy by design.
7 Sep 2026Release 1, v1.0 Release Candidate, published and put to the ANCR Working Group for candidate review and approval.
Oct 2026SC 27/WG 5 sends the revision of ISO/IEC TS 27560:2023 forward to DIS.
22 Oct 2026The SC 44/WG 1 work item is registered as ISO/IEC PWI 27138.

What review feeds into

Ahead

Review periodComments on pull request #34 and the working group list, with disposition of the five N 5211 priority comments and the open items.
Approval voteWorking group decision on Release 1, including ratification of the ANCR TPI-R variant as the assessment profile and the consent construction field.
RecommendationProgression toward a Kantara Initiative Recommendation under Kantara operating procedures.
LiaisonCirculation of the approved version to SC 27/WG 5 as a liaison contribution in continuity with N 5211, and to the SC 44/WG 1 work item as an implementation reference.

Join a call. Calls are open to working group participants. Membership is a short form on the Kantara wiki, and TCIEG will walk anyone through it. Working group wiki and calendar

Join the work

Pick a route in. There are five.

The extension is open by requirement, not by courtesy. Its IPR terms are reciprocal royalty free, its source is public, and every open item after v1.0 is a piece of work someone could pick up this month.

I build things

Implementers

Start with clause 7 and Annex A. Build any one of the four artefacts and try to make criterion C3 hold: generate and verify an Anchored Notice Receipt with no account and no principal identifier. Then draft the JSON Schema for what you built. Report the gaps on pull request #34 and bring the code to a call.

I review specifications

Reviewers

Download the line numbered review copy attached to Release 1. Comment against line numbers, since they are stable on the tag. Priority areas: the Annex A.0 deviation, the 7.2.2 lawful basis default, the 7.2.4 hash input rule, and the five N 5211 comments carried forward. Join the working group through the wiki so your comments are on record for disposition.

I supervise or regulate

Supervisory and regulatory staff

The question the working group needs answered: in an inquiry, which of the four artefacts would you rely on, and in what form? Criteria C1, C5 and C7 were written with inquiry evidence in mind. TCIEG will arrange a briefing and a walkthrough of the TPI-R assessment method against a live site, and can route formal input through the Council of Europe liaison.

I sit on a national committee

National body delegates

Two places to act. In SC 27/WG 5, PWI 26689 on notice and consent evidence is drafting its new work item proposal, and Annex F of the extension is the clause by clause crosswalk to its registered scope. In SC 44/WG 1, the Internet Transparency Code of Practice profile work item needs a machine readable notice and receipt to profile. Contact TCIEG to coordinate a national position or to receive the liaison decks.

I research

Researchers

Open questions with a research shape: an integrity mechanism for an anonymous receipt that replaces the per principal HMAC; usability of two factor online notice; measurement validity of the TPI ordinal scale; and jurisdiction profiling of lawful basis enumerations under Annex C. The DPV companion is a natural home for legal model contributions. Cite Release 1 by its tag.

The same for everyone

Steps

  1. Join the Kantara ANCR Working Group

    Membership is through the working group wiki. It puts you under the group's IPR terms so your contributions can be used.

  2. Read Release 1

    Use the line numbered copy. The changelog explains what moved and why.

  3. Comment or contribute

    Pull request #34 for comments; GitHub issues for change proposals. Include the target file and version, a rationale in terms of interoperability, implementability or conformance, and any privacy or security impact.

  4. Join a call

    Twice a month. Bring an implementation, a use case or a question.

Tell TCIEG

So we can connect you

Write to us with your name, your organisation and how you would like to take part: review Release 1, bring an implementation, contribute to the JSON Schema or the DPV legal model, or arrange a briefing. Nothing is collected on this page.

Email TCIEG

SPECWORK, a TCIEG programme supporting the Kantara Initiative ANCR Working Group. The specification is a Kantara working group output published under Kantara IPR terms. This page is maintained by TCIEG and is not a Kantara publication. About SPECWORK