Date
May 20, 2014
...
Intro to the Specification
...
: Consent Receipt Specification v.01
The purpose of this specification is the MVC specification (or the consent receipt header) is to standardise the recordation of consent and the
collection the collection of consent specific policy links. As well as to make standard a link to withdraw consent.
The first section (or header) of the consent receipt provides the basic needed information to record that a consent
was provided, and the policies under which it was provided. This header is what we have called in the past the MVC.
The second part of the consent receipt is intended to draw out from the policies the minimum legal require for consent
Purpose
Jurisdiction and Contact Information legal requirements for consent and to display these. Either by a direct link to the policy section with the legal notice requirement or by scraping the policy. All of the notice requirements for consent by jurisdiction and industry are to found in a reference document called the "Consent Notice Map". (needs link)
(Note: The theory being that the header provides the sources of information needed for the rest of the receipt )
Section 2:
- Purpose
- Contact of the Data Controller
- Jurisdiction for Data Controller
- Jurisdiction data is stored in
- Jurisdiction of the data subject
Section 3 Extensions
two types of extensions are predicted to be here.
- notice requirement extensions for jurisdictions, industry specific, or type of personal inforamtion
- Preference management tools - e.g. DNT, Withdraw Consent, Block Use of Data use, (Note: these vary by jurisdiction)
Consent Receipt Demo Button Review Terms
...
(From work to date)
Discussion Items
| Time | Item | Who | Notes |
|---|---|---|---|
Action Items
...