# US 11,030,274 B2 · Data processing user interface monitoring systems and related methods

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,030,274 B2
- Document ID: US11030274B2
- Status: Granted
- Kind: B2
- Application number: 16/832,451
- Filed: 2020-03-27
- Published: 2020-07-16
- Granted: 2021-06-08
- Earliest claimed: 2016-06-10
- Assignees: OneTrust, LLC
- Applicants: OneTrust, LLC
- Inventors: Jonathan Blake Brannon; Casey Hill; Kevin Jones; Richard A. Beaumont
- Web page: https://patentgrep.com/patent/US11030274B2

## CPC

- G06F 16/972: {Access to data in other repository systems, e.g. legacy data or dynamic Web page generation}
- G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
- G06F 16/951: Indexing; Web crawling techniques
- G06F 16/9574: {of access to content, e.g. by caching}
- G06F 16/9577: {Optimising the visualization of content, e.g. distillation of HTML documents}
- G06F 21/554: {involving event detection and direct action}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 40/174: Form filling; Merging
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

In various embodiments, a system may be configured to analyze data for a particular consent capture point to identify a change in consent capture rate from the capture point. The system may, for example, be configured to automatically detect that the system has stopped receiving consent records from a particular capture point. In such embodiments, the system may be configured to generate an alert, and transmit the alert to any suitable individual (e.g., privacy team member, IT department member, etc.) regarding the capture point. The system may, for example, enable an entity to identify one or more capture points that may have become non-functional (e.g., as a result of one or more changes to the capture point).

## Claims

### Claim 1

A consent receipt management system comprising:
one or more processors; and
computer memory that stores a plurality of consent records, each of the plurality of consent records being electronically associated with:
a respective transaction of a plurality of transactions involving a particular data subject of a plurality of data subjects and an entity; and
a respective data subject of the plurality of data subjects, wherein the consent receipt management system is configured for:
receiving, at a particular consent capture point, a plurality of requests from the one or more data subjects to initiate a particular transaction of the plurality of transactions, the particular transaction involving collection or processing of personal data associated with the one or more data subjects by the entity as part of a processing activity undertaken by the entity that each of the one or more data subjects is consenting to as part of the transaction;
monitoring the particular consent capture point to determine a consent record rate for the particular consent capture point;
analyzing the consent record rate to identify a particular change in the consent record rate;
determining, based at least in part on the particular change in the consent record rate, that the particular consent capture point is not functioning properly; and
in response to identifying the particular change in the consent record rate, taking one or more automated actions, wherein the one or more automated actions comprise flagging one or more pieces of computer code associated with the particular consent capture point for modification.

### Claim 2 (depends on 1)

The consent receipt management system of claim 1, wherein the one or more automated actions further comprise
generating an electronic alert and transmitting the electronic alert to an individual responsible for the particular consent capture point.

### Claim 3 (depends on 1)

The consent receipt management system of claim 1, wherein the particular change in the consent record rate comprises a reduction in the consent record rate to zero.

### Claim 4 (depends on 1)

The consent receipt management system of claim 1, wherein the particular change in the consent record rate comprises a reduction in the consent record rate below a particular threshold level.

### Claim 5 (depends on 4)

The consent receipt management system of claim 4, wherein the system is further configured for, in response to the reduction in the consent record rate below the particular threshold level, automatically implementing a modified consent capture interface at the particular consent capture point.

### Claim 6 (depends on 5)

The consent receipt management system of claim 5, wherein the particular consent capture point comprises a particular domain.

### Claim 7 (depends on 1)

The consent receipt management system of claim 1, wherein the system is further configured for, in response to determining that the particular consent capture point is not functioning properly, generating an alert that the entity is capturing data that at least one of the one or more data subjects has not consented to as part of the transaction.

### Claim 8

A computer-implemented data processing method for monitoring consent record rate change of a particular capture point, the method comprising:
providing, by one or more processors, a user interface at a particular capture point for initiating a transaction between an entity and a data subject;
receiving, by one or more processors, one or more requests to initiate a respective transaction between the entity and a respective data subject;
monitoring, by one or more processors, the particular capture point to determine a rate of one or more consent records generated at the particular capture point, each of the one or more consent records being generated in response to each of the one or more requests to initiate each respective transaction;
identifying, by one or more processors, a change in the rate of the one or more consent records generated at the particular capture point;
determining, by one or more processors, based at least in part on the change in the rate of the one or more consent records generated at the particular capture point, that the particular capture point is not functioning properly;
in response to determining that the particular capture point is not functioning properly, generating, by one or more processors, an electronic alert and transmitting the electronic alert to an individual responsible for the particular capture point; and
in response to determining that the particular capture point is not functioning properly, flagging, by one or more processors, one or more pieces of computer code associated with the particular capture point for modification.

### Claim 9 (depends on 8)

The computer-implemented data processing method of claim 8, where the transaction involves a collection or processing of personal data associated with the data subject by the entity.

### Claim 10 (depends on 8)

The computer-implemented data processing method of claim 8, the method further comprising, in response to determining that the particular capture point is not functioning properly, determining, by one or more processors, that the entity has captured at least one piece of data under the transaction that does not have an associated consent record of the one or more consent records.

### Claim 11 (depends on 8)

The computer-implemented data processing method of claim 8, wherein the particular capture point comprises a particular webpage.

### Claim 12 (depends on 8)

The computer-implemented data processing method of claim 8, the method further comprising, in response to determining that the particular capture point is not functioning properly, automatically initiating a risk analysis for the transaction.

### Claim 13

A computer-implemented data processing method for managing a consent capture point, the method comprising:
providing, by one or more processors, at the consent capture point, a user interface for initiating a transaction between an entity and one or more data subjects;
receiving, by one or more processors, from the one or more data subjects, at the consent capture point, one or more requests to initiate the transaction between the entity and the one or more data subjects, each of the one or more requests providing consent, from the one or more data subjects, to the collection or processing of personal data associated with the one or more data subjects as part of the transaction;
in response to receiving each of the one or more requests, generating, by one or more processors, one or more consent records, each of the one or more consent records storing an indication of the consent to the collection or processing of the personal data associated with the one or more data subjects as part of the transaction;
analyzing, by one or more processors, the one or more consent records to determine a consent record rate for the consent capture point;
monitoring, by one or more processors, the consent record rate for the consent capture point to identify a particular change to the consent record rate;
determining, by one or more processors, based at least in part on the particular change to the consent record rate, that the consent capture point is not functioning properly;
in response to identifying that the capture point is not functioning properly, automatically executing, by one or more processors, one or more automated actions, wherein the one or more automated actions comprise flagging one or more pieces of computer code associated with the consent capture point for modification.

### Claim 14 (depends on 13)

The computer-implemented data processing method of claim 13, wherein the one or more automated actions are selected from the group consisting of:
generating an electronic alert and transmitting the electronic alert to an individual responsible for the consent capture point; and
automatically initiating a consent interface consent conversion test at the consent capture point.

### Claim 15 (depends on 13)

The computer-implemented data processing method of claim 13, wherein the particular change to the consent record rate comprises a reduction in the consent record rate below a particular threshold level.

### Claim 16 (depends on 13)

The computer-implemented data processing method of claim 13, the method further comprising, in response to determining that the consent capture point is not functioning properly, determining, by one or more processors, that the entity has captured at least one piece of data under the transaction that does not have an associated consent record of the one or more consent records.

### Claim 17 (depends on 13)

The computer-implemented data processing method of claim 13, wherein the consent capture point is selected from the group consisting of:
a particular domain;
a particular webpage;
a particular electronic form; and
a particular mobile application.