Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

    • display the meta format that meets the minimum compliance obligations of an organisation that does not:
      • share with third parties,
      • does not collect sensitive data,
      • includes a self assertion that context specific requirements are included, this minimum viable consent receipt provides the minimum needed for a person to interact independently with an organizations to address any additional compliance or complaint requirements.
    • Notes:
      •  the MVCR is designed and intended to demonstrate the minimum online consent requirements with existing law illustrating the most common consent requirements across all jurisdictions in an independently usable form)
      • with these three components alone provides a tremendous improvement as a meta format,
  • Additional Operational Objectives to implement beyond the MVCR: (creating list here)
    1. re-consent

    2. withdrawing consent

    3. upgrading consent to the new consent data model

  • Technical Implementation
    • release an open simple version of the CR that is useful out of the box for a common and specific scenario, defined here as website registration for Kantara.
    • do this in a way that enables the receipt to be usable (systematically read)
    • Use the common consent receipt format being developed in technical meetings
    • Use the consent receipt generation tool being developed in technical meetings

Stage 1 MVCR Website Registration: : CIS-WG Implementation:

  • Specific Use Case for :the Kantara CISWG Registration
    •  non-sensitive PII, -
    • e.g.no third party sharing,
    • no-PII payload,
    • with output into a json format of the receipt download as a text file with  html version displayed on screen and pdf version available to send via email (evaluating different methods of delivery)
  • Components
    • includes a simple form for creating a static receipt
    • presents the receipt on a website, with pdf version, and digital cert version
    • documentation about what the receipt is potentially good for. 
  • Walkthrough
    • WG- Admin
      • fills out form for creating consent receipt code
      • this code is put on the website
    • Alice Experience
      • alice goes to sign up
      • alice gets receipt
  • Implementation Plan
    • get quote from Oliver for the demo
    • demo needs plan to be developed and moved to consent receipt. org
      • includes list of usability requirements, documentation, graphics

...