March 2025 - Wg-ancr - mailman.kantarainitiative.org

Clarifying the Consent Receipt Use Case in 27560
by Mark Lizar 31 Mar '25

31 Mar '25

HI Everyone, Now that 27560 is going to be open, I have looked into recent work on 27560, and 29184, so I could try and locate where the consent receipt use case has gone awry exactly, in addition, to provide Transparency Report Specific references to support the use of Consent Receipts, to enable Controller compliance. Its clear the Consent Receipt use case to regulate digital identity trust and address surveillance capitalism is still a big deal, and something that perhaps the ANCR WG can support, to educate the industry on a way for human data control and interoperability with consent and identity management. Aka the Consent Receipt. To this end, I have drafted some comments/ update to the Consent Receipt use case, to the W3C DPV, Group and to provide the legal references to request updates to the proposed 27560. Would these comments be supported by ANCR. WG? Best, Marl Core Consent Receipt Use Case - Permission for Identification (or self-identifying with consent) As the researcher, developer and editor of the Consent Receipt, and editor of the Transparency Performane Report at the ANCR WG. I would like to clarity the core use case for the consent receipt, to demonstrate how to decentralised the govern of digital identification and surveillance with enforceable privacy, transparency, and consent regulation. To this end, I would request a review of notice and consent in DPV (and 27560), with regards to the associated guidance found in particular Associating Identity with Consent <https://harshp.com/research/publications/038-comparison-notice-requirements…> “Additionally, GDPR encourages using an identifier so that controllers can demonstrate the individual’s given consent (Art.7-1), enable them to withdraw it (Art.7-3), and provide them with a history of their consent events (Art.15).”https://harshp.com/research/publications/038-comparison-notice-req… Referencing Guidelines 05/2020 on consent under Regulation 2016/679 ( point to the guidance which has a different interpretation that what is provided here) “64. >>>> Furthermore, there may be situations where a data controller is processing personal data that does not require the identification of a data subject (for example, with pseudonymized data). In such cases, Article 11.1 may also be relevant as it states that a data controller shall not be obliged to maintain, acquire, or process additional information to identify the data subject solely to comply with the GDPR.” In Article 29 Working Party: Guidelines on transparency under Regulation 2016/679 “106. At the same time, the duty to demonstrate that valid consent has been obtained by a controller should not in itself lead to excessive amounts of additional data processing. This means that controllers should have enough data to show a link to the processing (to show consent was obtained) but shouldn’t be collecting any more information than necessary.” The context of the use case The consent receipt version 1.1 , which was adopted as ISO/IEC 27560, was developed through five years of research and two years of drafting and volunteer community work, originating from Hackathons and Campaigns to stop the biggest lie on the internet: whcich is “Our Data Is Collected without Consent.” Which is now showing to cause significant harms on society (References available upon request) The Issue being addressed If an individual must first be identified to access rights to stop being surveilled online, then privacy is not a right; it is a consumer protection with limited capacity to see and control who can surveil PII principals. This is referred to as the surveillance capitalism use case, which the MVCR and Consent Receipt work solves. Key Points: Without this, people can be surveilled, their data scraped (like with AI), and then they have to opt-out of being tracked, referencing a ‘Consumer Protection’ Paradigm where privacy isn't a fundamental right, and consent is required to surveil people. The consent receipt is the solution to this challenge. Using a standard interaction pattern, well-known in society for trust, that requires fair and proportionate transparency (as explained in Guidance for use of GDPR). It's very simple: Put up a sign, provide a notice, and ask for permission—fundamental components of human etiquette, being polite, and reducing frictions. How does it work; How does this consent receipt work so PII principals can provide permission before being surveilled. A Controller presents their identity in a standard notice (layer 1 of online interaction). This generates a notified record when the PII principal interacts with it. That notified processing activity is mirrored as a consent receipt. A controller digital identifier is provided to the PII principal, instead of a PII principal identifier being taken secretly from the data subject. The data subject can use the receipt (in a secure private space like a digital wallet) to interact with the Controller, send more PII, provide permission to be digitally identified, and self-identify. Consent can be withdrawn with a click. Please consider that at this time, 27560, which is called a consent record, uses a PII principal identifier is in the record header (with an unknown 3rd party ID - for un-notified tracking of people), indicating that this is not consent but a USA-style consumer protection record. Which has significant, security and privacy implications, AS USA Law only affords US citizens consumer rights not afforded to EU or Canadians, under USA Foreign Intelligence Surveillance Laws. As you can imagine, without a real consent receipt and transparency before surveillance, it provides people with much weaker consumer protection, and leaves Canadians open, without rights, or data sovereignty, having a geo-political impact to the international market. Please update text, here especially,https://harshp.com/research/publications/038-comparison-notice-r…

1 1

ANCR WG call reminder - tomorrow 26, march / 12pm EST
by gigi.agassini＠gmail.com 25 Mar '25

25 Mar '25

Dear ANCR WG, This is a kind reminder for our meeting tomorrow, at 12:00pm EST to review: Time Topic 3m WG Admin 10m TPR out for comments for 45d 15m Update homepage 15m Update WG slides (see attached in minutes link)) 5m Blog post 3m Change time of the bi-weekly meeting 8m Any other business 1m Adjourn meeting link: https://us06web.zoom.us/j/87282263538?pwd=K0RwY1g1b3pKeHdBcXpjeExVZUFpQT09 Minutes: https://kantara.atlassian.net/wiki/spaces/WA/pages/942374923/ANCR+WG+2025032 6?force_transition=7e127725-7d77-46d6-9b44-6fa9c5db3c52 Looking forward to seeing you all tomorrow. Kindest Regards, Gigi

1 0

Invitation - Thursday Breakfast Club 7:00 - 7:45 am
by Mark Lizar 25 Mar '25

25 Mar '25

Hello All, We happy to Invite you to 0PN Breakfast Club @ the 0PN Lab, We are resuming the Thursday Breakfast Club, focusing on all the great work that is coming out with regards to Operational Privacy Notice from the ANCR WG, W3C and ISO. This week we invite back the regulars, who might be interested in talking more about the work going on. With a plan to open up invitation to the breakfast club in April. This week there are Announcements and some big news. To find out more, and help spread the word, you are welcome to join the 0PN Breakfast club, where we will report on these initiatives, share the latest gossip, news and research in this field. Call Details: 7:00 - 8:00 am Dropin @ Join on Microsoft Teams <https://teams.microsoft.com/l/meetup-join/19:meeting_NzVlMTM0YzQtYmQwYy00Zm…> See you there, Mark Lizar Check out The Breakfast Club <https://coda.io/d/_dFkt_pKxozn/The-0PN-Breakfast-Club_sucLUgUu> for more information, and even common on the very new Charter. Agenda Topics 1. The Consent receipt from Kantara, now represented in standard at ISO, is to be made open and free to access in 2025! This means it can be used to make international operational transparency open source. #1 0PN project for April. 2. This week the ANCR WG is releasing the Transparency Performance Assessment Report (TPR) for review by Kantara / wider Identity Management Community. The report is the first tool for digital identity management industry to see regulated transparency and Consent for digital identity management is valid. * The TPR can assess consent, security, and sovereignty for compliance with the many consent laws that are becoming enforceable in 2025. 3. ANCR WG is going to be working on terms for the Transparency Report, and discussing how to address misinformation in digital identity management technology, for the next few WG calls, (Tomorrow and ever second Wed) 4. W3C DPV v2.1 was just released, and its getting quite good for mapping the laws to vocabulary, that can be used to operationalised notice, and we are looking at how to use this for Montreal / Consent. Note: - the call will be recorded for the transpcript so that we can support some great blog content. So if you have any news, or updates to report on, please prep them prior to the call.

1 0

Transparency Performance Reporting Public Review and Comment Period Open
by Salvatore D'Agostino 25 Mar '25

25 Mar '25

Hi ANCR, RIUP, and PEMC. We have a Kantara Recommendation that is now out for public comment. PCIPR20250317 - ANCR Transparency Performance Reporting - General Information - Kantara Initiative<https://kantara.atlassian.net/wiki/spaces/GI/pages/925663233/PCIPR20250317+…> Here is the link to the document as well as the reporting forms. Congratulations to the WG for this effort and thanks for your time in review and comments. Sincerely, Sal IDmachines 4 Lamson Place Cambridge, MA 02139-2612 +1 617.201.4809 @idmachines https://idmachines.com<https://idmachines.com/> Please note our new address. Email, phones, other contacts remain the same. Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. If you have received this email in error, please delete it and advise the sender.

1 0

FW: TPR Draft Recommendation: Public Comments
by Salvatore D'Agostino 20 Mar '25

20 Mar '25

Hip, hip… From: Amanda Gay <amanda(a)kantarainitiative.org> Sent: Thursday, March 20, 2025 4:13 PM To: Salvatore D'Agostino <sal(a)idmachines.com> Subject: TPR Draft Recommendation: Public Comments Hi Sal: Everything is prepped for the Public Comment/IPR Period--which will start tomorrow at 1PM! Since 45 days out from today was a Sunday, I didn't send it out today. The Public Comment Period will run from March 21 to May 5. Here's an advance copy of the document for your review. Thanks again for your hard work and continued patience! Best, -Amanda -- Amanda Gay | Work Groups and Membership <https://lh7-rt.googleusercontent.com/docsz/AD_4nXfHwJ-rzpysEzGWLZ07DoUVltjG…> Phone: +1 571-475-8895 LinkedIn: @KantaraInitiative

1 0

FW: [KI-LC] Call to Update Group Slides for 2025
by Salvatore D'Agostino 19 Mar '25

19 Mar '25

Hello WG, Please take a look through the Kantara presentation deck wrt to wg activity, we will need to update, let’s talk about that over the next few meetings. We can create a pair of draft slides as placeholder to get started. Comments here in thread as well? Kind regards, Sal From: Alec L via LC <lc(a)kantarainitiative.org> Sent: Wednesday, March 19, 2025 9:45 AM To: Kantara Leadership Council <lc(a)kantarainitiative.org> Subject: [KI-LC] Call to Update Group Slides for 2025 Hi all, With EIC and Identiverse coming up, it's time for each group to refresh our presentation slides with their 2024 achievements and 2025 plans. This activity helps Kay accurately represent your group's work and attract new members and participation The shared presentation can be found here: https://docs.google.com/presentation/d/1j__6HOA8BuDWPcYsY3Q7DETpGmbNZ34s/ed… Please update your group's section before our next monthly meeting, Apr 15, 2025 @ 10ET Thanks, - Alec Alec Laws CTO Engineering | IDENTOS Inc. <https://cdn2.hubspot.net/hubfs/53/tools/email-signature-generator/icons/pho…> (647)-822-1529<tel:(647)-822-1529> <https://cdn2.hubspot.net/hubfs/53/tools/email-signature-generator/icons/ema…> alec(a)identos.ca<mailto:alec@identos.ca> <https://uploads-ssl.webflow.com/650c9dbaffb52efc03fda0ca/656f37e5c28b666130…> <https://twitter.com/identos_inc> <https://www.linkedin.com/company/identos-inc/>

1 0

Cannot host call
by Salvatore D'Agostino 12 Mar '25

12 Mar '25

Hi WG, Sorry for this but timing isn't working today as I have to pick up Sarah who has just had a procedure, and she comes out at 12:30. Also, Gigi is on vacation this week. The TPR document should be formatted with appreciation from Amanda and Kantara this week and be ready to share for public comment, clearly, we all want to be able to cross that milestone, and that it happens shortly. There are drafts of blog post associated with the TPR to share with Kantara and promoting this. Best, Sal

3 2

Updates: 27560 Comment & ANCR Controller Draft is Posted
by Mark Lizar 04 Mar '25

04 Mar '25

Dear WG, The 2 Updates, 1. posted an initial spec outline for the Controller_notice_ Id record draft <https://kantara.atlassian.net/wiki/x/OADaNQ?atlOrigin=eyJpIjoiYTU3NDA5ZTRjY…> taken from the appendix of ANCR Transparency Reporting specification. It should also contain a link to the google doc in active development. ( Feel free to jump in and comment/ contribute/discuss and edit. if you have ideas for what should be included, or would like to get involved in drafting, please let me know 2. I have also tried to submit late comments - referencing the controller notice id record to 27560, but due to technical account issue (@ standards council of Canada) it was not submitted on time. Even so comments were eventually submitted, so the editors hopefully will get a chance to review them. And, yes, it does recommend the use of the ANCR PII controller_idenitty_ record, (with a Link) to be used in the record information structure, as well as minimumal changes to update to to a notice record and receipt record and information structure, (so as to be suitable for (all use case) including the original Surveillance/Terms and Condition / Cookie use cases). So fingers crossed, the ANCR / Kantara Work might actually work out in the end by not only interoperate in the next edition,with 27560, 29184, 29100, and DPV, but also be useable for ‘operational personal data security/surveillance access and control.’ Which would make the effort definitely worthy while in the end Best, Mark PS. Key Comment Summary #1 comment (imo) is recommending to swap the PII_principal identifier from the record header with with the pii_controller_record_id, (as specified in the ANCR WG) #2 Second most important, is a recommendation of a generic use case for getting permission to identify the pii_principal in the consent record header. (which demo’s how privacy is used for identify management) In the context of providing and withdrawal of consent using a consent receipt for a secondary purpose of use (for any lawful basis) PSS - In essence completing the work to propose a standard that can make a real consent record and receipt 10 years after the v1 was drafted. - comments received or not - is a big milestone in my book.

1 0

ANCR PII Controller Notice Identification Record Draft v0.8
by Info 03 Mar '25

03 Mar '25

Dear WG, I posted an initial spec outline for the Controller_notice_ Id record draft <https://kantara.atlassian.net/wiki/x/OADaNQ?atlOrigin=eyJpIjoiYTU3NDA5ZTRjY…> currently found in the TPR appendix. It contains a link to the google doc in active development. Feel free to jump in and comment on the website posted version if you have ideas for what should be included, or let me know if you want to actively draft or edit, and we can co-ordinate, as we generally aim to work on this doc in a session on Monday afternoons, for the short period of time it will take to draft. Kind Regards, Mark 0PN Director Zero Privacy Needed

1 0