Additional information for data control & accountability providence can be nested in the receipt to provide a higher level of automated privacy assurance to better mitigate risk and liability. (ref - PasE: CG Project -)
This document presents a framework update to the ANCR WG and Consent Receipt community completing of some of key issues and solutions that address them since MVCR v0.8 (when spec was frozen) for review by ANCR WG.
...
- The ISO/IEC SC 27 Committee in April 2020 to start an ISO Working Draft based on the Consent Notice Receipt
- The Consent Notice Receipt was published in appendix D, of ISO/IEC 29184 (June 6,2020) titled 'Online privacy notice and consent'
- this establishes the Consent Notice Receipt as an authoritative data governance tool to provide transparency over the control and interoperability of data processing by services between jurisdictions
- V1.1 to V 1.2 Notice; regarding 'well known issues and developments' (WKID) Updates,
- delegation (on-behalf)
- proof of notice receipt
- Consent Notice Receipt (Human Definition)
- a receipt to prove awareness of any policy or notice regarding surveillance; a physical sign, a blinking light, T&C's, privacy policies, cookie notices, online consent forms etc, any notice or notification to inform people about the active state of processing and accountability.
- Consent is a human centric term which is technically a multi-permissoned active state at any one point of time reflecting hidden and personal capabilities per context, biological, social, legal, but more importantly, the physical environment which dictates security and controls considerations for the individual.
- generated from the notice and or sign presented to the Individual in the individuals physical context indicating the system permissions/data protection and controls scopes/ relevant to the person and context.
- the consent notice receipt MUST function to link privacy rights information and access into the processing context, using a receipt for proof and post interaction access to those rights.
- a key challenge was the legal ontology for Purpose Specification
- to address this, Kantara CISWG members supported
- the launch of the W3C Data Privacy Vocabulary Group on the eve of the GDPR @ ODI in London in conjunction with MIT Media Labs
- updating / replacing the MVCR Appendix with the contributions of the Personal Data Categories from Jason Cronk (revised by the Open Consent Group), now an agreed and adopted category basis for semantic control interoperability
- Purpose category, referencing an industry or sector code of conduct. Often referred to as a trust framework, pr code of conduct for practices that are nuanced as like a digital identity governance scheme for (micro)credentials and certification. Codes of conduct are often championed at a national and international to be approved by Data Protection and Privacy Regulators for an industry and sector.
- to address this, Kantara CISWG members supported
- Legal Justifications for Processing
- For people the purpose is used to make choices and decisions it is used to inform people so they can grant consent or assent in some way for a specified purpose.
- Behind this purpose specification is the legitimacy of the processing which is technically broken down into recognized legal reasons for surveillance
- Now greatly simplified with the GDPR setting an international standard and ISO 29184, as a set of standard legal justifications,.
- Consent
- Contract
- Legitimate Interest
- In the Pubic's Interest
- for the Vital Interest of the Individual
- for a required legal obligation
- with a conformity assessment built in, any notice can be extended to provide a consent notice receipt to a person - where by standards are used to specifying the legal justification, purpose, data categories, so that the rights available for person are accessible and viewable in context. (the objective of the CR receipt format ) Regardless of service and terms
...
In all contexts, notifications a inform the lifecycle of inform the active state of the relationship according to the legal justification for processing and its relationship, and receipts render this lifecycle making transparent active state to which rights apply in context, and what the performance of those rights ares legally expected by people.
Additional information for data control & accountability providence can be nested in the receipt to provide a higher level of automated privacy assurance to better mitigate risk and liability. (ref - PasE: CG Project -)