<aside> <img src="notion://custom_emoji/a9e82583-b24a-4a1a-acd2-b871fcb71bd8/30835fe7-dd4a-8049-a134-007aabf37e08" alt="notion://custom_emoji/a9e82583-b24a-4a1a-acd2-b871fcb71bd8/30835fe7-dd4a-8049-a134-007aabf37e08" width="40px" />

Purpose

Presenting the ANCR Working Group case study highlighting the core privacy and interoperability risks identified in the DPV:27560 Privacy Impact Report, as actionable, testable requests for ISO/IEC WG5.

Core claim and standard ISO/IEC profile path

Human consent online requires inspectable-before-identification accountability and exchangeable evidence — otherwise “consent records” become surveillance record information structures not suitable for AI governance.

March 9th, 2026

</aside>

gprc-image1-.png

<aside> <img src="notion://custom_emoji/a9e82583-b24a-4a1a-acd2-b871fcb71bd8/30835fe7-dd4a-8049-a134-007aabf37e08" alt="notion://custom_emoji/a9e82583-b24a-4a1a-acd2-b871fcb71bd8/30835fe7-dd4a-8049-a134-007aabf37e08" width="40px" />

IPR / licensing note (Kantara ANCR)

This work is presented as an ANCR Working Group contribution and should be understood in the context of Kantara ANCR working group IPR / RF-RAND style contribution rules (royalty-free by default with opt-out to RAND where declared).

For export/share: include a short licensing statement such as “Contributed under Kantara ANCR WG IPR policy (RF by default with opt-out to RAND where declared).”

</aside>

WG5 framing: why this is the 27560:2026 challenge (and not “just a consent UI issue”)

The current 27560:2026 risk pattern (identifier-first controller-side recordkeeping that can be labelled as a “receipt”) is the same structural failure mode that appears across age assurance, AI/agentic orchestration, IoT, and most digital identity + privacy use cases: systems demand identification before accountability and before an inspectable notice state exists, then treat internal processing records as consent evidence.

ANCR’s Digital Notice + Consent profile addresses this by anchoring consent to an international, cross-border governance baseline and an evidence-grade exchange:

This report provides the detailed problem statement, risk analysis, and closeable editor requests supporting the 27560-1 ANCR profile path.

Executive summary

ISO/IEC CD 27560:2026 defines a PII processing record information structure (and receipt structure) that aims to standardise controller recordkeeping and receipts across lawful bases (including consent). As currently framed, it enables interoperability, but also enables an evidence-laundering failure mode: identification-first controller logs can be labelled as “consent receipts” even where the choice to consent is not provided, and when notice was not inspectable/standardised (machine readable) before identification and processing.

Machine-readable standard policy, is a key digital privacy technology for implementing human centric digital policy meant for computers and open networked environments. Human readable is not proportionate or reciprocal.

ANCR (Anchored Notice and Consent Receipt) is a consent record information structure exchange: it specifies a bilateral, testable sequence and artefacts so that notice, authorization/consent (when consent is the legal basis), and evidence can be exchanged consistently across services and jurisdictions.

What changed (and why this matters)

The consent receipt lineage was defined for cross-border governance and interoperable fairness — first in the 1980 OECD Privacy Guidelines (transborder flows), and then in Convention 108+. It was never meant to be a jurisdiction-specific “PII processing record” framework.

When a consent record information structure is treated as a controller-side processing record, the structure shifts from “human meaningful choice” to “controller evidence-of-processing” — which, in digital identification terms, becomes a surveillance record information structure.

Digital Consent (what it is)

Digital consent is a technical pattern that imitates human consent. That means it must remain intrinsically understandable to a human at the point of decision, not merely representable as a controller-side data structure after the fact.

Key distinction: