Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Objective

This ANCR Record specification provides a methodology to audit a notice and produce a consent receipt.  The objective of this documents is to

  1. Provide a set of instructions for recording a notice and its purpose specification
  2. To then compare the conformance of the record with a set of rules or regulations referred to here as a code of practice. 

Methodology

This method describes, how to audit a notice to generate an ANCR Record using ISO/IEC 29100 receipt format, which is published in the ISO/IEC 29184 Annex D, 

The resulting audit is then used for assessing conformance with an ISO/IEC 29184 Online Privacy Notice and Consent control.  In order to demonstrate how the ANCR Notice Record for assessing conformance when creating a digital identifier and processing personal data.

Instructions 

  1. Read a notice 
    1. collect down the PII Controller Name 
    2. collect down the PII Controller Address
    3. collect contact information 
    4. collect link to privacy policy 
    5. collect any links to privacy access information 
  2. Indicate in which concentric manner data has been 
  3. Capture the legal justifications for processing 
  4.  Capture the Notice
    1.  indicate what the expected consent type is  prior to the notice
    2. indicate if personal identifiers are collected prior to presenting the notice
  5. Indicate the legal justification from the 6 categories - 
  6. indicate the personal data is sensitive 
  7. capture purpose description 
  8. capture the authorization scope
    1. frequency 
    2. duration
  • This audits a notice for information that is required for capture, creations , or use of identifiers.
  • For meaningful consent in Canada we also capture
  • A - is there notice of risk and harms, and if there is a privacy information service point / api for dynamic data controls


Field Name

Type

PII(Y)

Field Label

Description 

Required/Optional

version

string


Schema Version

The version of specification used to which the receipt conforms. To refer to this version of the specification, the string "v1" or the IRI "https://w3id.org/OPN/v1" should be used.

Required

profile

string


OPN Privacy Profile URI

Link to the controller's profile in the OPN registry. 

Required

Notice Receipt

string 


Type of Notice Receipt

Label Notice Receipt 

Required

id

string


Receipt ID

A unique number for each Notice Receipt. SHOULD use UUID-4 [RFC 4122].

Required

timestamp

integer


Timestamp

Date and time of when the notice was generated and provided. The JSON value MUST be expressed as the number of seconds since 1970-01-01 00:00:00 GMT (Unix epoch).

Required

key

string


Signing Key

The Controller’s profile public key. Used to sign notice icons, receipts and policies for higher assurance.

Optional

language

string


Language

Language in which the consent was obtained. MUST use ISO 639-1:2002 [ISO 639] if this field is used. Default is 'EN'.

Required

controllerID

string


Controller Identity

The identity (legal name) of the controller.

Required




Controller Address

jurisdiction

string


Legal Jurisdiction

The jurisdiction(s) applicable to this notice

Required

controllerContact

string


Controller Contact

Contact name of the Controller. Contact could be a telephone number or an email address or a twitter handle.

Required

notice

string


Link to Notice

Link to the notice the receipt is for 

Optional

policy

string


Link to Policy

Link to the policies relevant to this notice e.g. privacy policy active at the time notice was provided

Required

context

string


Context

Method of notice  presentation, sign, website pop-up etc

Optional




Receipt TypeThe human understandable label for a record or receipt for data processing.  This is used to extend the schema with  profile for the type of legal processing - and is Used to identify data privacy rights and controls 



Notice Text 



Accountable Person Role





  • No labels