smartopian
commented
7 years ago A new abstract.
"Abstract: A Consent Receipt is the focus for an open standard, because it is a machine readable record of a consent that is converted into a (re usable) human readable format. The OECD Guidelines Council of Europe Convention, and European Union Data Protection Directive[8] relied on FIPs as core principles. All three organizations revised and extended the original U.S. statement of FIPs Due to the international and cross domain use of a consent receipt this document refers to the 1980 OECD Guidelines consent international transfer of personal data focusing on consent using the ISO 29100 lexicon A Consent Receipt is a record of consent used by a PII Controller (or Data Controller) as their authority to collect, use and disclose a PII Principal’s (or Data Subjects) personally identifiable information (PII). The Consent Receipt will be provided to the PII Principal that gave the consent. This specification defines the requirements for the creation of a consent record and the provision of a human readable receipt provided to the PII Principal. The receipt includes links to existing privacy notices & policies as well as a description of what information will be collected, the purposes for that collection and relevant information about how that information will be used or disclosed.
Although, this specification uses the ISO 29100 lexicon, its use of this language is non prescriptive and the terms should be replaced according to the jurisdiction that regulates its provision. The specification is based on privacy and data protection principles as set out in various data protection laws, regulations and international standards."
TomCJones
andrewhughes3000
iainh1
dturnerx
We need to be clear that the CR spec is not the authoritative source for definitions and be clear that implementers must follow the appropriate definitions according to their relevant jurisdictions.