US 2019/0096020 A1 · CONSENT RECEIPT MANAGEMENT SYSTEMS AND RELATED METHODS

Abstract

A consent receipt management system may, for example, be configured to track data on behalf of an entity that collects and/or processes persona data related to: (1) who consented to the processing or collection of personal data; (2) when the consent was given (e.g., a date and time); (3) what information was provided to the consenter at the time of consent (e.g., a privacy policy, what personal data would be collected following the provision of the consent, for what purpose that personal data would be collected, etc.); (4) how consent was received (e.g., one or more copies of a data capture form, webform, etc. via which consent was provided by the consenter); (5) when consent was withdrawn (e.g., a date and time of consent withdrawal if the consenter withdraws consent); and/or (6) any other suitable data related to receipt or withdrawal of consent.

Claims20

Dependent claims

A consent receipt management system comprising:

one or more processors;
and
computer memory, wherein the consent receipt management system is configured for:
receiving a request to initiate a transaction between an entity and a data subject, the transaction involving collection or processing of personal data associated with the data subject by the entity as part of a processing activity undertaken by the entity that the data subject is consenting to as part of the transaction;
in response to receiving the request:
identifying a transaction identifier associated with the transaction;
generating, a unique consent receipt key for the transaction;
and
determining a unique subject identifier for the data subject;
electronically storing the unique subject identifier, the unique consent receipt key, and the transaction identifier in computer memory;
electronically associating the unique subject identifier, the unique consent receipt key, and the transaction identifier;
generating a consent record for the transaction, the consent receipt comprising at least the unique subject identifier and the unique consent receipt key;
and
electronically transmitting the consent record to the data subject.

11 more elements

A computer-implemented data processing method for managing a consent receipt under a transaction, the method comprising:

providing a user interface for initiating a transaction between an entity and a data subject;
receiving a request to initiate a transaction between the entity and the data subject;
in response to the request:
initiating the transaction;
and
generating, using one or more consent receipt generation means, a unique consent receipt key;
receiving, from the data subject, a unique subject identifier
electronically storing the unique subject identifier, the unique consent receipt key, and a unique transaction identifier associated with the transaction in computer memory using one or more electronic storage means;
electronically associating the unique subject identifier, the unique consent receipt key, and the unique transaction identifier;
and
in response to receiving the request, transmitting a consent receipt to the data subject, the consent receipt comprising at least the unique subject identifier and the unique consent receipt key.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application

16/104,628Filed 17 Aug 2018

Priority

10 Jun 2016

Published

28 Mar 2019

Term ends

Not estimatedThe source records don’t support an estimate.

Classification10 codes

G06Q 50/265
Government or public services: personal security, identity or safety
G06F 15/76
Digital computers in general ; Data processing equipment in general: architectures of general purpose stored program computers
G06F 21/552
Detecting local intrusion or implementing counter-measures: involving long-term monitoring or reporting
G06F 21/6245
To a system of files or objects, e.g. local or distributed file system or database: protecting personal data, e.g. for financial or medical purposes

Family

Application62/348,695Us provisional application · filed 10 Jun 2016

Application62/353,802Us provisional application · filed 23 Jun 2016

Application62/360,123Us provisional application · filed 8 Jul 2016

Application15/254,901Continuation in part · filed 1 Sep 2016

Application15/619,455Continuation in part · filed 10 Jun 2017

Application62/537,839Us provisional application · filed 27 Jul 2017

Application62/541,613Us provisional application · filed 4 Aug 2017

Application62/547,530Us provisional application · filed 18 Aug 2017

Application15/853,674Continuation in part · filed 22 Dec 2017

Application15/996,208Continuation in part · filed 1 Jun 2018

Application16/054,672Continuation in part · filed 3 Aug 2018