Status of Document

In progress 19-12-2013

Introduction: 

This is the minimum viable consent  schema (legals.txt) page for the Common Consent Receipt Scenario.  

(draft) A minimum viable consent receipt is comprised of data that is required for explicit consent online across all jurisdictions. This receipt is comprised of a legals.txt file and a stamp produces at the point of consent which creates a consent receipt.  The consent receipt is then delivered to the individual for later use. 

 The Legal.txt contains the fields which are legally required on for use of services (see table below).

• Privacy Policy
• Purpose
• Consent
• Contact
• Address

•  Online terms of service policy for use of services (if there is one)

(Note: `Depending on the jurisdiction, the type of personal data provided, the devices used and the context their may be addition notice requirements and limitations. For example a cookie policy).    

This schema is being developed to evaluate the consent receipt as a transparency and interoperability tool for personalisation and customisation.  A tool that works to extend existing policy frameworks with a common consent receipt.

This Schema is required to  Demonstrate Two basic things: 

1. The minimum legally required information is published in a legals.txt, in common format, using best practices for the internet. 
2. Provide consenting individuals with a usable record of a consent at the point of consent.  Exploring the receipts use to manage and standardise consent preferences during and post consent, 

Common Consent Schema

The consent receipt schema below is split into two parts

• Part 1: Publishing Legals.txt

  • Common Consent Schema for legals.txt

  • Legal Reference Table for Receipt Fields

  • Legal Reference Table

• Part 2: Generating Receipt
  • Consent Receipt
• Human Language Common Consent Receipt
• Annex
  • Proposed/Possible fields
    
    

Part 1

Minimum Viable (Common) LEGALS.TXT

Legal References For Legals.txt

(Note this document is updated from a google spreadsheet)

Based on the above information there may be more consent or notice specific requirements, but, at this time these are out of scope of the minimum viable consent receipt.  (note: We have started a list of possible fields below to consider adding to future schema's)  

Part 2 - Consent Receipt Fields 

This is a list of fields that is stamped on the receipt at the time of providing consent, in addition to the legals.txt data. 

This is the schema for what someone will receive as the consent receipt.  This is generated by combining the legals.txt with information from the website at the point the consent was provisioned. E.g. time/date, web address, ip address, and consent preferences. 

Human language Expression 

-------------------------------

Open Notice Consent Receipt,  with ID http://example.com/notice243a34fad, 

- date/time stamp

written by http://www.example.com ,

which is based somewhere in somewhere in a Country

has 

  a privacy notice at http://www.example.com/privacy.html and 

  a terms of service at http://www.example.com/terms.html. 

Contact information: Email, Skype, Twitter, FB, Phone, Customer Service,

Address of Data Controller, Address of Data, Nationality of Company

Preferences : 

Authority:

**********

By providing this information this company openly publishes its policy and with the contact information provided is able to answer and deal with minimum obligations for consent across X jurisdictions

Depending on

• the jurisdiction
• the type of personal information provided
• the context
• the device
• the preferences selected by the individual

x -  jurisidictions

-----------

Annex A: Proposed Fields: 

Comments