Abstract

This document is a product of the CISWG Work Group. It records the scenarios and use cases governing the development of consent receipt and guiding associated implementations and deployments.

A Scenario specifying a receipt data schema

Status

This document is currently under active development. Its latest version can always be found here. See the Change History at the end of this document for its revision number.

Editors

Mark Lizar

Intellectual Property Notice

The CISWG Work Group operates under Option ABC and the publication of this document is governed by the policies outlined in this option.

Table of Contents

Introduction and Instructions

This document is a product of the CISWG Work Group. It records the scenarios and use cases governing the development of the Consent Receipt Schema (CRS) and guiding associated implementations and deployments.

Please use the scenario template near the end of this document in adding new scenarios and subordinate use cases. Change the status keyword in each scenario and use case title as appropriate, linking to the meeting minutes page explaining the status change:

• Pending: Initial status when first submitted
• Accepted: Needs to be accounted for in Consent Receipt Schema V1 and/or its associated compliant implementations
• Deferred: Relevant to the problem space; may be considered in future versions
• Rejected: Out of scope

Edit the descriptions of technical issues and scope questions to reflect (or point to) group decisions about how to handle them.

Scenario: unique-title (Pending)

Submitted by: Mark Lizar

The goal of this scenario is to create a specification for a receipt schema and a demonstrator for creating, providing and using a minimum viable consent receipt. 

Initial Audience

1. Open Notice & Kantara Community
2. The Usable Privacy Project
3. Mozilla
4. Internet Society

Background

Economic Performance of Consent:

A receipt you get when you buy something has many uses, it can be submitted to a third party, either to show a budget and costs, or to report on what was purchased and for how much.  It is a great tool for reducing friction, saves time, money.  Like a transaction receipt, consents can also be submitted to a third party, it can be compared, counted, and like purchasing preferences, consent preferences can also be collected.  

Experience of Consent

Better managed preferences result in better user experience. 

Governance of Consent:

A receipt can also be used for governance, for instance, the Tax authorities can use a receipt to check and see if the sales are hidden, the purchaser can use a receipt to be sure of the cost of goods and compare the change provided and the receipt against the price advertised to make sure of compliance.  

 A receipt can be taken and used with third parties like a token to access other services.

Objective

 Specify the existing fields for a consent transaction receipt and list them as a basic template for consent receipts. (Note: This entails formally defined attributes, published and open for comment.)

Develop scenario covering the life cycle of a minimum viable consent receipt for building a demonstrator.  This would involve

1. Create a consent receipt generator, --> Common Terms, Legal.TXT
2. Create a consent receipt button,  --> Embed Code, publish legal.txt
3. Provision a consent to a service user
4. Service user, uses the receipt  to achieve the use case specified.  

The demonstrator includes 3 stages, 1. Pre-Consent, 2. Consent 3. Post-Consent

1. Pre-Consent
   1. a website/server with form for a company to generate a legal.txt file
   2. Publishing legal.txt
   3. An embed code is created for company to put behind their consent buttons on the website
2. Consent
   1. A service user selects the consent '+ receipt' option to collect a receipt
      1. The id used by the service user to provision consent is used to send the receipt. 
         1. With no pre arranged application, a modal box will appear  asking for slection of identifier to use with the receipt
            1. this could be social login, email, etc
         2. the receipt is then accepted and stored by the digital identity being used for the consent
3. Post - Consent
   1. TOSSOS - Receipts are used to compare policy changes using TOSSOS
   2. TOS;Dr - Receipts are used to look up TOS;Dr rating
   3. Out of Scope
      1. Browser Plugin - Receipts are captured and used automatically  to make policy responsive and to customise experience, reduces steps in stage 2. streamling user experience. 
         1. Would require a receipt viewing capability, preferably on aggregate and current view as well. (by identity would be useful too)

Use Case: Demonstrator Scenario 1, Stage 1: Pre-Consent (Pending)

Submitted by: Mark Lizar

The primary focus is to create the first legal.txt (which I think at the time of this writing is already done) and develop a process for an organisation to distribute a consent receipt. 

Scope of Work for Stage 1

• Focus first on creating a legal.txt file with the existing schema
• Create webpage with Minimum Viable Consent Form
• Create Legal.txt
• Publish Legal.TXT
• Create Embed Code for Consent to be used by other organisations
• Optional
  • Create a Common Terms option on first page for use in creating legal.txt file
    • link existing policies to layered notice

Use Case: Demonstrator Scenario 1, Stage 2: Consent (Pending)

When a consent is provisioned using the button 

- a receipt is created  at the point of consent, the identity used to provision the consent is used to deliver the consent receipt

-  

Use Case: Demonstrator Scenario 1, Stage 3: Post-Consent (Pending)

The consent rec

Issue: unique-title

(Provide technical commentary on the issues brought up by this use case.)

Change History