MVCR Use Case(s): Simple Consent Receipt

MVCR (Minimum Viable Consent Receipt) for an Open Consent Model

A proof of concept that explains the consent receipt and is presented as an open common consent meta-format for consent.
It is a starting point for being able to track consents and their basic requirements for people online.
The MVCR consent receipt is meant to be a bridge for policy, and personal data control architecture
- providing legacy consent implementations with a way to evolve, be compliant, and enable new Consent 2.0 witha
Objective
- 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.
- do this in a way that enables the receipt to be usable (systematically read)

Specific Use Case for:
- non-sensitive PII, -
- e.g.no third party sharing,
- no-PII payload,
- with output into a json field with pdf version (or html version)
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