Consent receipt management systems and related methods
First Claim
1. A computer-implemented data processing method for optimizing consent for a transaction, the method comprising:
- providing, by one or more processors, to a first plurality of data subjects, a first user interface having a first set of user interface attributes to each respective data subject of the first plurality of data subjects, the first user interface being a first user interface for initiating a transaction between an entity and each respective data subject of the first plurality of data subjects;
providing, by one or more processors, to a second plurality of data subjects, a second user interface having a second set of user interface attributes to each respective data subject of the second plurality of data subjects, the second user interface being a second user interface for initiating a transaction between the entity and each respective data subject of the second plurality of data subjects;
receiving, by one or more processors, one or more first requests to initiate the transaction from at least a first portion of the first plurality of data subjects;
receiving, by one or more processors, one or more second requests to initiate the transaction from at least a second portion of the second plurality of data subjects;
analyzing, by one or more processors, the one or more first requests and the one or more second requests to identify one or more common attributes among the first set of user interface attributes and the second set of user interface attributes, wherein the one or more common attributes comprise;
a time of day at which the first plurality of data subjects was provided the first user interface; and
a time of day at which the second plurality of data subjects was provided the second user interface;
analyzing, by one or more processors, the one or more common attributes of the first user interface and the second user interface to determine, based on the one or more first requests and the one or more second requests, at least one attribute that increases a likelihood that a particular data subject will submit a request to initiate the transaction;
storing an indication of the one or more common attributes in computer memory; and
generating a custom consent interface for initiating the transaction based at least in part on the and the at least one attribute, wherein generating the custom consent interface comprises determining a layout of the custom interface based at least in part on the at least one attribute.
2 Assignments
0 Petitions
Accused Products
Abstract
In particular embodiments, a consent receipt management system is configured to track and analyze one or more attributes of a user interface via which data subjects are requested to provide consent (e.g., consent to process, collect, and/or store personal data) in order to determine which of the one or more attributes are more likely to result in a successful receipt of consent from a data subject. For example, the system may be configured to analyze one or more instances in which one or more data subjects provided or did not provide consent in order to identify particular attributes and/or factors that may increase a likelihood of a data subject providing consent.
749 Citations
16 Claims
-
1. A computer-implemented data processing method for optimizing consent for a transaction, the method comprising:
-
providing, by one or more processors, to a first plurality of data subjects, a first user interface having a first set of user interface attributes to each respective data subject of the first plurality of data subjects, the first user interface being a first user interface for initiating a transaction between an entity and each respective data subject of the first plurality of data subjects; providing, by one or more processors, to a second plurality of data subjects, a second user interface having a second set of user interface attributes to each respective data subject of the second plurality of data subjects, the second user interface being a second user interface for initiating a transaction between the entity and each respective data subject of the second plurality of data subjects; receiving, by one or more processors, one or more first requests to initiate the transaction from at least a first portion of the first plurality of data subjects; receiving, by one or more processors, one or more second requests to initiate the transaction from at least a second portion of the second plurality of data subjects; analyzing, by one or more processors, the one or more first requests and the one or more second requests to identify one or more common attributes among the first set of user interface attributes and the second set of user interface attributes, wherein the one or more common attributes comprise; a time of day at which the first plurality of data subjects was provided the first user interface; and a time of day at which the second plurality of data subjects was provided the second user interface; analyzing, by one or more processors, the one or more common attributes of the first user interface and the second user interface to determine, based on the one or more first requests and the one or more second requests, at least one attribute that increases a likelihood that a particular data subject will submit a request to initiate the transaction; storing an indication of the one or more common attributes in computer memory; and generating a custom consent interface for initiating the transaction based at least in part on the and the at least one attribute, wherein generating the custom consent interface comprises determining a layout of the custom interface based at least in part on the at least one attribute. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A computer-implemented data processing method for optimizing consent for a transaction, the method comprising:
-
providing, by one or more processors, to a plurality of data subjects, a user interface for initiating a transaction between an entity and each respective data subject of the plurality of data subjects; at least partially in response to providing the user interface to the plurality of data subjects, receiving, by one or more processors, one or more requests to initiate the transaction from at least a first portion of the plurality of data subjects; analyzing, by one or more processors, the one or more requests to identify one or more first factors associated with at least a first portion of the one or more requests, wherein the one or more first factors comprise a time of day at which each of the plurality of data subjects viewed the user interface; analyzing, by one or more processors, the one or more first factors of the user interface to determine at least one factor of the one or more first factors that increase a likelihood that a particular data subject will submit a request to initiate the transaction; storing an indication of the at least one factor in computer memory; and generating a new user interface for initiating the transaction based at least in part on the at least one factor, wherein generating the new user interface comprises determining a layout of the new user interface based at least in part on the at least one factor. - View Dependent Claims (9, 10, 11, 12)
-
-
13. A consent receipt analysis, processing, and custom interface generation system comprising;
-
one or more processors; computer memory; and a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising; providing, by one or more processors, to a first plurality of data subjects, a first user interface having a first set of user interface factors to each respective data subject of the first plurality of data subjects, the first user interface being a first user interface for initiating a first transaction between an entity and each respective data subject of the first plurality of data subjects; providing, by one or more processors, to a second plurality of data subjects, a second user interface having a second set of user interface factors to each respective data subject of the second plurality of data subjects, the second user interface being a second user interface for initiating a second transaction between the entity and each respective data subject of the second plurality of data subjects; receiving, by one or more processors, one or more first requests to initiate the first transaction from at least a first portion of the first plurality of data subjects; receiving, by one or more processors, one or more second requests to initiate the second transaction from at least a second portion of the second plurality of data subjects; analyzing, by one or more processors, the one or more first requests and the one or more second requests to identify one or more common factors among the first set of user interface factors and the second set of user interface factors, wherein the one or more common factors comprise; a time of day at which the first user interface was provided to the first plurality of data subjects; a time of day at which the second user interface was provided to the second plurality of data subjects; analyzing, by one or more processors, the one or more common factors of the first user interface and the second user interface to determine, based on the one or more first requests and the one or more second requests, at least one factor that increases a likelihood that a particular data subject will submit a request to initiate the first transaction or the second transaction; storing an indication of the at least one factor in computer memory; and generating a custom consent interface for initiating a third transaction based at least in part on the at least one factor, wherein generating the custom consent interface comprises determining a layout of the custom consent interface based at least in part on the at least one factor. - View Dependent Claims (14, 15, 16)
-
Specification