DATA PROCESSING SYSTEMS FOR FULFILLING DATA SUBJECT ACCESS REQUESTS AND RELATED METHODS

BACKGROUND

Over the past years, privacy and security policies, and related operations have become increasingly important. Breaches in security, leading to the unauthorized access of personal data (which may include sensitive personal data) have become more frequent among companies and other organizations of all sizes. Such personal data may include, but is not limited to, personally identifiable information (PII), which may be information that directly (or indirectly) identifies an individual or entity. Examples of PII include names, addresses, dates of birth, social security numbers, and biometric identifiers such as a person's fingerprints or picture. Other personal data may include, for example, customers' Internet browsing habits, purchase history, and even their preferences (e.g., likes and dislikes, as provided or obtained through social media).

Many organizations that obtain, use, and transfer personal data, including sensitive personal data, have begun to address these privacy and security issues. To manage personal data, many companies have attempted to implement operational policies and processes that comply with legal and organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example, a right to obtain a confirmation of whether a particular organization is processing their personal data, a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected), and other such rights. Some regulations require organizations to comply with requests for such information (e.g., Data Subject Access Requests) within relatively short periods of time (e.g., 30 days).

Existing systems for complying with such requests can be inadequate for producing and providing the required information within the required timelines. This is especially the case for large corporations, which may store data on several different platforms in differing locations. Accordingly, there is a need for improved systems and methods for complying with data subject access requests.

SUMMARY

In general, embodiments of the present invention provide methods, apparatus, systems, computing devices, computing entities, and/or the like for adjusting the priority of a data subject access request. In accordance with various aspects, a method is provided that comprises: receiving a data subject access request associated with a data subject, wherein processing the data subject access request involves a data network comprising a plurality of data assets and a plurality of data processing activities; applying an initial prioritization level to the data subject access request, wherein the initial prioritization level identifies where in an order of a plurality of data subject access requests found in a fulfillment data subject access request queue that the data subject access request is to be fulfilled; obtaining, by computing hardware monitoring data processing through the data network, metadata associated with the data subject access request, wherein the metadata comprises a condition associated with at least one of a particular data asset of the plurality of data assets or a particular data processing activity of the plurality of data processing activities involved in processing data for fulfilling the data subject access request; determining, by the computing hardware and based on the metadata, that the condition affects at least one of an amount of computing resources or an amount of time needed for processing the data for fulfilling the data subject access request; adjusting, by the computing hardware, the initial prioritization level based on the condition to generate an adjusted prioritization level for the data subject access request; generating, by the computing hardware, an updated order of the plurality of data subject access requests found in the fulfillment data subject access request queue based on the adjusted prioritization level, wherein the adjusted prioritization level identifies where in the updated order that the data subject access request is to be fulfilled; generating, by the computing hardware, a graphical user interface by configuring the plurality of data subject access requests on the graphical user interface based on the updated order and configuring a display mechanism for the data subject access request to identify the adjusted prioritization level; and providing the graphical user interface for display on a computing device.

In some aspects, the method further comprises processing, by the computing hardware, the plurality of data subject access requests to fulfill each of the plurality of data subject access requests according to the updated order of the plurality of data subject access requests found in the fulfillment data subject access request queue. In some aspects, processing the plurality of data subject access requests comprises, for each data subject access request of the plurality of data subject access requests: scanning a plurality of data inventories for the data network to identify personal data for the data subject associated with the data subject access request; and performing at least one of providing the personal data for viewing by a requestor who submitted the data subject access request, deleting the personal data from the plurality of data inventories, or update the personal data stored in the plurality of data inventories.

In some aspects, the metadata further comprises at least one of: (1) a type of the data subject access request; (2) a location from which the data subject access request is being made; (3) a country of residency of the data subject; or (4) a status of the data subject and adjusting the initial prioritization level is further based on the metadata. In some aspects, the data subject access request was submitted by the data subject and the method further comprises: verifying an identity of the data subject; and responsive to verifying the identity of the data subject, processing the data subject access request to fulfill the data subject access request. In some aspects, the method further comprises, responsive to adjusting the initial prioritization level of the data subject access request, modifying a completion date for fulfillment of the data subject access request. In some aspects, the method further comprises: responsive to adjusting the initial prioritization level of the data subject access request, generating a prioritization message to indicate that the initial prioritization level of the data subject access request has been adjusted; and electronically communicating the prioritization message to at least one individual.

In accordance with various aspects, a system comprising a non-transitory computer-readable medium storing instructions and a processing device communicatively coupled to the non-transitory computer-readable medium is provided. Accordingly, the processing device is configured to execute the instructions and thereby perform operations comprising: applying an initial prioritization level to a data subject access request associated with a data subject, wherein: processing the data subject access request involves a data network comprising a plurality of data assets and a plurality of data processing activities, and the initial prioritization level identifies where in an order of a plurality of data subject access requests found in a fulfillment data subject access request queue that the data subject access request is to be fulfilled; monitoring data processing through the data network; obtaining, based on monitoring the data network, metadata associated with the data subject access request, wherein the metadata comprises a condition associated with at least one of a particular data asset of the plurality of data assets or a particular data processing activity of the plurality of data processing activities involved in processing data for fulfilling the data subject access request; adjusting the initial prioritization level based on the condition to generate an adjusted prioritization level for the data subject access request; generating an updated order of the plurality of data subject access requests found in the fulfillment data subject access request queue based on the adjusted prioritization level, wherein the adjusted prioritization level identifies where in the updated order that the data subject access request is to be fulfilled; and providing a graphical user interface for display, the graphical user interface comprising the plurality of data subject access requests on the graphical user interface based on the updated order and configuring a display mechanism for the data subject access request to identify the adjusted prioritization level.

In some aspects, the operations further comprise processing the plurality of data subject access requests to fulfill each of the plurality of data subject access requests according to the updated order. In some aspects, processing the plurality of data subject access requests comprises, for each data subject access request of the plurality of data subject access requests: scanning a plurality of data inventories for the data network to identify personal data for the data subject associated with the data subject access request; and performing at least one of providing the personal data for viewing by a requestor who submitted the data subject access request, deleting the personal data from the plurality of data inventories, or update the personal data stored in the plurality of data inventories.

In some aspects, the operations further comprise, responsive to adjusting the initial prioritization level of the data subject access request, modifying a completion date for fulfillment of the data subject access request. In some aspects, the operations further comprise: responsive to adjusting the initial prioritization level of the data subject access request, generating a prioritization message to indicate that the initial prioritization level of the data subject access request has been adjusted; and electronically communicating the prioritization message to at least one individual.

In accordance with various aspects, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium having program code that is stored thereon, the program code executable by one or more processing devices for performing operations comprising: applying an initial prioritization level to a data subject access request associated with a data subject, wherein: processing the data subject access request involves a data network comprising a plurality of data assets and a plurality of data processing activities, and the initial prioritization level identifies where in an order of a plurality of data subject access requests found in a fulfillment data subject access request queue that the data subject access request is to be fulfilled; monitoring the data network; identifying, based on monitoring the data network, a condition associated with at least one of a particular data asset of the plurality of data assets or a particular data processing activity of the plurality of data processing activities involved in processing data for fulfilling the data subject access request; adjusting the initial prioritization level based on the condition to generate an adjusted prioritization level for the data subject access request; generating an updated order of the plurality of data subject access requests found in the fulfillment data subject access request queue based on the adjusted prioritization level, wherein the adjusted prioritization level identifies where in the updated order that the data subject access request is to be fulfilled; and providing a graphical user interface for display, the graphical user interface comprising the plurality of data subject access requests on the graphical user interface based on the updated order and configuring a display mechanism for the data subject access request to identify the adjusted prioritization level.

In some aspects, the data subject assess request comprises information comprising at least one of: (1) a type of the data subject access request; (2) a location from which the data subject access request is being made; (3) a country of residency of the data subject; or (4) a status of the data subject and adjusting the initial prioritization level is further based on the information. In some aspects, the operations further comprise: verifying an identity of the data subject; and responsive to verifying the identity of the data subject, processing the data subject access request to fulfill the data subject access request. In some aspects, the operations further comprise, responsive to adjusting the initial prioritization level of the data subject access request, modifying a completion date for fulfillment of the data subject access request.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a data subject access request processing and fulfillment system are described below. In the course of this description, reference will be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 depicts a data subject request processing and fulfillment system according to particular embodiments.

FIG. 2A is a schematic diagram of a computer (such as the data model generation server 110, or data model population server 120 of FIG. 1) that is suitable for use in various embodiments of the data subject request processing and fulfillment system shown in FIG. 1.

FIG. 2B is a flow chart depicting exemplary steps executed by a Data Subject Access Request Routing Module according to various embodiments.

FIGS. 3-43 are examples of user interfaces that demonstrate the operation of various embodiments.

FIGS. 44-49 depict various examples of exemplary screen displays and user interfaces that a user of various embodiments of the system may encounter (FIGS. 47 and 48 collectively show four different views of a Data Subject Request Queue).

FIG. 50 is a flowchart showing an example of a processes performed by a Data Subject Access Request Prioritization Module according to various embodiments.

DETAILED DESCRIPTION

Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings. It should be understood that the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

Overview and Technical Contributions Provided by Various Embodiments

An entity that handles (e.g., collects, receives, transmits, stores, processes, shared, and/or the like) sensitive and/or personal information associated with particular individuals, such as personally identifiable information (PH) data, may be subject to various laws and regulations regarding the handling of such personal data. The term “personal data” is used throughout the disclosure. However, those of ordinary skill in the art should recognize that various embodiments of the disclosure are applicable to other forms of data. The applicable laws and regulations may vary based on the jurisdiction in which the entity handling the personal data is operating, the jurisdiction in which the entity (e.g., individual) associated with the personal data (“data subject”) is located, and/or the jurisdiction in which the personal data is handled. In many jurisdictions, an entity that handles personal data may be required to track the personal data they handle, by maintaining and/or readily generating information that indicates what personal data is handled, where the personal data is stored, how the personal data is processed, how the personal data is collected, etc. The entity may be required to have this information available (or have to ability to obtain this information) so that it can readily service one or more data subject access requests (DSARs).

A DSAR may be a request from a data subject or other requestor (e.g., authorized individual on behalf of a data subject) to access personal data, delete personal data, receive information about the handling of personal data, and/or the like. The entity handling the personal data may also, or instead, be required to have this information available (or have the ability to obtain this information) to comply with various aspects of one or more applicable laws, regulations, and/or standards. The entity may also, or instead, want or be able to have this information available (or have to ability to obtain this information) to perform one or more other functions, such as mine one or more legacy systems for personal data (e.g., to ensure that legacy systems comply with current laws, regulations, and/or standards), create one or more maps of where personal data may be stored, identify personal data that may need to be modified (deleted due to age or other factors, updated, supplemented, and/or the like).

As the quantity of personal data increases over time, and/or as the number of data assets found in a data network that may be potentially handling personal data increases, as well as the number of data processing activities involved in handling personal data increases, determining how and/or where particular personal data is being and/or has been handled (e.g., collected, received, transmitted, stored, processed, shared, and/or the like) across the data network can be difficult. A data asset may be a component such as a computing system, computing device, data source, software application, and/or the like that can be used within the data network for handling personal data. A data processing activity may involve an action, operation, and/or the like that is performed within the data network and may involve personal data. For example, a data processing activity may involve transferring personal data stored in a first data asset to a second data asset. As a result, identifying and retrieving personal data for various DSARs across the data network when multiple data assets, data processing activities, and/or the like are involved can become quite challenging due to the sheer volume of personal data that an entity may be handling, as well as due to the number of data assets, data processing activities, and/or the like used by the entity in handling the personal data. Yet, even more challenging may be identifying and retrieving specific personal data for various DSARs from a large volume of personal data found across multiple data assets, involving multiple data processing activities, and/or the like that enables the entity to process (e.g., fulfill) the DSARs within required timelines.

Further adding to the challenge of fulfilling these DSARs is that conditions within the data network involving the data assets and/or data processing activities used in handling the personal data may constantly change that can directly affect the processing of the DSARs. For example, a data asset used in storing personal data may be taken “offline” for maintenance purposes. Data traffic within the data network may be congested, resulting in a data processing activity taking longer to complete. The volume of DSARs to be processed through the data network may significantly increase, resulting in a need for more processing capacity and/or processing time in fulfilling the DSARs. Therefore, conditions within the data network can affect prioritizing the processing of certain DSARs to ensure time requirements for fulfilling the DSARs are met.

Accordingly, various embodiments of present disclosure overcome many of the technical challenges associated with processing (e.g., fulfilling) of DSARs as described above. Specifically, various embodiments of the disclosure involve a data subject access request processing and fulfillment system that is adapted to receive DSARs associated with particular data subjects, and to facilitate the timely processing of valid DSARs by an appropriate respondent. In particular embodiments, the data subject access request processing and fulfillment system receives DSARs via one or more user interfaces such as, for example, one or more webforms that each may respectively be accessed via an appropriate link, button, and/or the like on a respective web page. In other embodiments, the system may receive DSARs through any other suitable mechanism such as, for example, via a computer software application (e.g., a messaging application such as Slack, Twitter), via a chat bot, via generic API input from another system, and/or through entry by a representative who receives the information via suitable paper forms and/or over the phone.

In particular embodiments, the data subject access request processing and fulfillment system may include a webform creation tool that is adapted to allow a user to create customized webforms for receiving DSARs from various different data subject types and for routing the requests to appropriate systems and/or individuals for processing. The webform creation tool may, for example, allow the user to specify the language that the form will be displayed in, what particular information is to be requested from the requestor (e.g., data subject) and/or provided by the requestor, what systems and/or individuals any DSARs that are received via the webform are routed to, and/or the like. Accordingly, such capabilities may enable the user to design webforms that enable the collection of needed information from a requestor submitting a DSAR and the submission of the DSAR to the proper system and/or personnel for processing of the DSAR in an efficient and timely manner. In some embodiments, once the user has completed the design of the webform, the webform creation tool may generate code for the webform that may then be inserted (e.g., cut and pasted) into a particular web page.

The system may be further adapted to facilitate efficient and timely processing of DSARs that are received via the webforms, or any other suitable mechanism. For example, the data subject access request processing and fulfillment system may be adapted to execute one or more of the following operations (steps) for each particular DSAR received via the webforms (or other suitable mechanism) described above. Firstly, before processing the DSAR, the data subject access request processing and fulfillment system may confirm that the DSAR was actually submitted by the particular data subject of the DSAR (or, in the alternative, by an individual authorized to make the DSAR on the data subject's behalf, such as a parent, guardian, power-of-attorney holder, and/or the like). Depending on the embodiment, various processes may be used to confirm the identity of the entity/individual submitting the DSAR. For example, in particular embodiments, if the system receives the DSAR via a third-party computer system, the system may validate authentication via API secret, or by requiring a copy of one or more particular legal documents (e.g., a particular contract between two particular entities). In some embodiments, the system may validate the identity of an individual by, for example, requiring the individual (e.g., data subject) to provide particular account credentials, by requiring the individual to provide particular out-of-wallet information, through biometric scanning of the individual (e.g., finger or retinal scan), or via any other suitable identity verification technique. Next, the data subject access request processing and fulfillment system may deny the DSAR if the DSAR was not submitted by the particular data subject (or authorized individual). If the DSAR was submitted by the particular data subject (or authorized individual), then the data subject access request processing and fulfillment system may advance the processing of the DSAR. For instance, in particular embodiments, advancing the processing of the DSAR may involve one or more of routing the DSAR to one or more correct individual(s) or groups internally for handling, facilitating the assignment of the DSAR to one or more other individuals for handling of one or more portions of the DSAR, facilitating the suspension of processing of the data subject's data (e.g., personal data) by an organization, and/or changing the policy according to which of the data subject's data is retained and/or processed by the system. Such capabilities may enable the data subject access request processing and fulfillment system to ensure the DSAR is processed in an efficient and timely manner. In addition, in particular embodiments, the system may perform any one or more of the above operations involved in processing the DSAR automatically to further introduce efficiency and timeliness. Further, in particular embodiments, the system may generate a receipt for the DSAR that the requestor can use as a transactional record of their submitted request.

In particular embodiments, the data subject access request processing and fulfillment system may be adapted to provide a graphical user interface (e.g., a DSAR request-processing dashboard) that is adapted to allow a user (e.g., a privacy officer of an organization that is receiving DSARs) to monitor the progress of any of the DSARs. Here, for example, the DSAR request-processing dashboard may display, for each DSAR, an indication of how much time is left (e.g., quantified in days and/or hours) before a legal and/or internal deadline to fulfill the request. The system may also display, for each DSAR, a respective user-selectable indicium that, when selected, may facilitate one or more of the following: (1) verifying the request; (2) assigning the request to another individual; (3) requesting an extension to fulfill the request; (4) rejecting the request; and/or (5) suspending the request.

As previously and elsewhere noted in this application, in particular embodiments, any one or more of the above operations (steps) may be executed by the system automatically. For example, in some embodiments, the system may be adapted to automatically verify the identity of the DSAR requestor and then automatically fulfill the DSAR request by obtaining the requested data (e.g., personal data) via a suitable data model and communicating the data to the requestor. As another particular example, the system may be configured to automatically route the DSAR to the correct individual for handling based at least in part on one or more pieces of information provided (e.g., in the webform).

In various embodiments, the system may be adapted to prioritize the processing of a DSAR based on metadata associated with the DSAR and/or the data subject of the DSAR. Such a capability may enhance the system's ability to process (e.g., fulfill) DSARs in an expedited manner due to one or more factors associated with the DSARs. Accordingly, such a capability may help to ensure an entity is processing (e.g., fulfill) DSARs within the required timelines. For example, the system may be adapted for: (1) in response to receiving a DSAR, obtaining metadata regarding at least one of the DSAR or the data subject; (2) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (3) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.

In some instances, the metadata may be directly related to the DSAR and/or the data subject of the DSAR. For example, metadata that may be used to determine whether to adjust the priority of a particular DSAR may include: (1) the type of DSAR submitted; (2) a location from which the DSAR is being made; (3) a country of residency of the data subject and, for example, that county's tolerance for enforcing DSAR violations; (4) current sensitivities to world events; (5) a status of the requestor and/or data subject (e.g., especially loyal customer); and/or (6) any other suitable metadata directly related to the DSAR and/or data subject.

In other instances, the metadata may be related to factors that involve processing the DSAR. For example, metadata that may be used to determine whether to adjust the priority of a particular DSAR may include: (1) a data asset found within a data network that is involved in handling personal data needed to fulfill the DSAR; (2) a data processing activity that may be performed within the data network in fulfilling the DSAR; (3) conditions occurring within the data network that may affect a data asset and/or a data processing activity involved in fulfilling the DSAR; and/or (4) any other suitable metadata related to factors that involve processing the DSAR.

Accordingly, various embodiments of disclosure provided herein facilitate effective, efficient, timely, accurate, and faster processing (e.g., fulfilling) of DSARs involving personal data found in large volumes of data handled in a data network that may involve a significant number of data assets and/or data processing activities in handling the personal data. In addition, various embodiments of the disclosure provided herein can facilitate the identification and/or documentation of personal data present within large volumes of data, spread over various data sources, as well as facilitate the retrieval of personal data for DSARs. In addition, various embodiments of the disclosure provided herein can facilitate the prioritization of DSARs based on various factors that may affect the processing of the DSARs. Such capabilities can ensure that the DSARs are processed in a manner so that they are fulfilled over required timelines. Further, various embodiments of the disclosure can carry out data processing involved in many DSARs that cannot be feasibly performed by a human, especially when such data processing involves large volumes of data. This is especially advantageous when the processing (fulfilling) of DSARs must be carried out over required timelines. In doing so, various embodiments of the present disclosure make major technical contributions to improving the computational efficiency and reliability of various automated systems and procedures using in processing (fulfilling) DSARs. This in turn translates to more computationally efficient data networks. Further detail is now provided for different aspects of various embodiments of the disclosure.

Exemplary Technical Platforms

As will be appreciated by one skilled in the relevant field, the present invention may be, for example, embodied as a computer system, a method, or a computer program product. Accordingly, various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, particular embodiments may take the form of a computer program product stored on a computer-readable storage medium having computer-readable instructions (e.g., software) embodied in the storage medium. Various embodiments may take the form of web-implemented computer software. Any suitable computer-readable storage medium may be utilized including, for example, hard disks, compact disks, DVDs, optical storage devices, and/or magnetic storage devices.

Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatuses (e.g., systems), and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by a computer executing computer program instructions. These computer program instructions may be loaded onto a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus to create means for implementing the functions specified in the flowchart block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner such that the instructions stored in the computer-readable memory produce an article of manufacture that is configured for implementing the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of mechanisms for performing the specified functions, combinations of steps for performing the specified functions, and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and other hardware executing appropriate computer instructions.

Example System Architecture

FIG. 1 is a block diagram of a data subject access request processing and fulfillment system 100 according to a particular embodiment. In various embodiments, the data subject access request processing and fulfillment system 100 is part of a privacy compliance system (also referred to as a privacy management system), or other system, which may, for example, be associated with a particular entity (e.g., organization) and be configured to aid in compliance with one or more legal or industry regulations related to the collection and storage of personal data within a data network.

As may be understood from FIG. 1, the data subject access request processing and fulfillment system 100 includes one or more computer networks 115, a Data Model Generation Server 110, a Data Model Population Server 120, an Intelligent Identity Scanning Server 130 (which may automatically validate a DSAR requestor's identity), One or More Databases 140 or other data structures, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), One or More Third Party Servers 160, and a DSAR Processing and Fulfillment Server 170. In particular embodiments, the one or more computer networks 115 facilitate communication between the Data Model Generation Server 110, Data Model Population Server 120, Intelligent Identity Scanning Server 130, One or More Databases 140, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), One or More Third Party Servers 160, and DSAR Processing and Fulfillment Server 170. Although in the embodiment shown in FIG. 1, the Data Model Generation Server 110, Data Model Population Server 120, Intelligent Identity Scanning Server 130, One or More Databases 140, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), and One or More Third Party Servers 160, and DSAR Processing and Fulfillment Server 170 are shown as separate servers, it should be understood that in other embodiments, the functionality of one or more of these servers and/or computing devices may, in different embodiments, be executed by a larger or smaller number of local servers, one or more cloud-based servers, or any other suitable configuration of computers.

The one or more computer networks 115 may include any of a variety of types of wired or wireless computer networks such as the Internet, a private intranet, a public switch telephone network (PSTN), or any other type of network. For example, the communication link between the DSAR Processing and Fulfillment Server 170 and the One or More Remote Computing Devices 150 may be implemented via a Local Area Network (LAN) or via the Internet. In other embodiments, the One or More Databases 140 may be stored either fully or partially on any suitable server or combination of servers described herein.

FIG. 2A illustrates a diagrammatic representation of a computer 200 that can be used within the data subject access request processing and fulfillment system 100, for example, as a client computer (e.g., one or more remote computing devices 150 shown in FIG. 1), or as a server computer (e.g., DSAR Processing and Fulfillment Server 170 shown in FIG. 1). In particular embodiments, the computer 200 may be suitable for use as a computer within the context of the data subject access request processing and fulfillment system 100 that is configured for routing and/or processing DSARs and/or generating one or more data models used in automatically fulfilling those requests.

In particular embodiments, the computer 200 may be connected (e.g., networked) to other computers in a LAN, an intranet, an extranet, and/or the Internet. As noted above, the computer 200 may operate in the capacity of a server or a client computer in a client-server network environment, or as a peer computer in a peer-to-peer (or distributed) network environment. The Computer 200 may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any other computer capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that computer. Further, while only a single computer is illustrated, the term “computer” shall also be taken to include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

An exemplary computer 200 includes a processing device 202, a main memory 204 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), static memory 206 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 218, which communicate with each other via a bus 232.

The processing device 202 represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device 202 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device 202 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, and/or the like. The processing device 202 may be configured to execute processing logic 226 for performing various operations and steps discussed herein.

The computer 200 may further include a network interface device 208. The computer 200 also may include a video display unit 210 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 212 (e.g., a keyboard), a cursor control device 214 (e.g., a mouse), and a signal generation device 216 (e.g., a speaker).

The data storage device 218 may include a non-transitory computer-accessible storage medium 230 (also known as a non-transitory computer-readable storage medium or a non-transitory computer-readable medium) on which is stored one or more sets of instructions (e.g., software instructions 222) embodying any one or more of the methodologies or functions described herein. The software instructions 222 may also reside, completely or at least partially, within main memory 204 and/or within processing device 202 during execution thereof by computer 200—main memory 204 and processing device 202 also constituting computer-accessible storage media. The software instructions 222 may further be transmitted or received over a network 115 via a network interface device 208.

While the computer-accessible storage medium 230 is shown in an exemplary embodiment to be a single medium, the term “computer-accessible storage medium” should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The terms “computer-accessible storage medium”, “computer-readable medium”, and like terms should also be understood to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the computer and that cause the computer to perform any one or more of the methodologies of the present invention. These terms should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc.

Systems for Managing Data Subject Access Requests

Various embodiments may involve a data subject access request processing and fulfillment system 100 and/or one or more other systems for managing data subject access requests (DSARs). In operation, the system may use one or more computer processors, which are operatively coupled to memory, to execute one or more software modules (which may be included in the Instructions 222 referenced above) such as a Data subject Access Request Routing Module 1000 and a Data Subject Access Request Prioritization Module 5000. An overview of the functionality and operation of each of these modules is provided below.

Data Subject Access Request Routing Module 1000

As shown in FIG. 2B, a Data Subject Access Request (DSAR) Routing Module 1000, according to particular embodiments, is adapted for executing the steps of: (1) at Step 1050, presenting a first webform on a first website adapted to receive DSARs and to route the requests to a first designated individual (e.g., an individual who is associated with a first sub-organization of a particular organization—e.g., an employee of the first sub-organization) for processing (in various embodiments, a “presenting” a webform on a website” involves, for example: (A) providing a button, link, or other selectable indicium on the website that, when selected, causes the system to provide the webform for display on the website, or (B) providing the webform directly for display on the website); (2) at Step 1100, presenting a second webform on a second website adapted to receive DSARs and to route the requests to a second designated individual (e.g., an individual who is associated with a second sub-organization of a particular organization—e.g., an employee of the second sub-organization) for processing; (3) at Step 1150, receiving, via the first webform, a first DSAR and receiving, via the second webform, a second DSAR; (4) at Step 1200, at least partially in response to the receiving the first DSAR, automatically routing the first DSAR to the first designated individual for handling; (5) at Step 1250, at least partially in response to the receiving the second DSAR, automatically routing the second DSAR to the second designated individual for handling; and (6) at Step 1300, communicating, via a single user interface, a status of both the first DSAR and the second DSAR.

In particular embodiments: (1) the first website is a website of a first sub-organization of a particular parent organization; (2) the second website is a website of a second sub-organization of the particular parent organization; and (3) a single user interface is used to communicate a status of each of the first DSAR and the second DSAR (e.g., to an employee such as a privacy officer of the parent organization). As discussed in more detail below, this single user interface may display an indication, for each respective one of the first and second DSARs, of a number of days remaining until a deadline for fulfilling the respective DSAR.

In certain embodiments, the single user interface is adapted to facilitate the deletion or assignment of multiple DSARs to a particular individual for handling in response to a single command from a user (e.g., in response to a user first selecting multiple DSARs from the single user interface and then executing an assign command to assign each of the multiple requests to a particular individual for handling).

In particular embodiments, the system running the DSAR Routing Module 1000 may be adapted for generating an ID number (e.g., a transaction ID or suitable Authentication Token) for the first DSAR that can be used later, for example, by the DSAR requestor to access information related to the DSAR, such as personal information requested via the DSAR, the status of the DSAR request, and/or the like. To facilitate access, the system may be adapted for receiving the ID number from an individual and, at least partially in response to receiving the ID number from the individual, providing the individual with information regarding status of the DSAR and/or information previously requested via the DSAR.

In particular embodiments, the system may be adapted to facilitate the processing of multiple different types of DSARs. For example, the system may be adapted to facilitate processing: (1) a request for all personal data that an organization is processing for the data subject (a copy of the personal data in a commonly used, machine-readable format); (2) a request for all such personal data to be deleted; (3) a request to update personal data that the organization is storing for the data subject; (4) a request to opt out of having the organization use the data subject's personal information in one or more particular ways (e.g., per the organization's standard business practices), or otherwise change the way that the organization uses the data subject's personal information; and/or (5) a request related to the filing of a complaint.

In particular embodiments, the system may execute one or more steps (e.g., any suitable step or steps discussed herein) automatically. For example, the system may be adapted for: (1) receiving, from the first designated individual, a request to extend a deadline for satisfying the first DSAR; (2) at least partially in response to receiving the extension request, automatically determining whether the requested extension complies with one or more applicable laws or internal policies; and (3) at least partially in response to determining that the requested extension complies with the one or more applicable laws or internal policies, automatically modifying the deadline, e.g., in memory, to extend the deadline according to the extension request. The system may be further adapted for, at least partially in response to determining that the requested extension does not comply with the one or more applicable laws or internal policies, automatically rejecting the extension request. In various embodiments, the system may also, or alternatively, be adapted for: (1) at least partially in response to determining that the requested extension does not comply with the one or more applicable laws or internal policies, automatically modifying the length of the requested extension to comply with the one or more applicable laws or internal policies; and (2) automatically modifying the deadline, e.g., in memory, to extend the deadline according to the extension request.

In various embodiments, the system may be adapted for: (1) automatically verifying an identity of a particular data subject access requestor placing the first DSAR; (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically obtaining, via a particular data model, at least a portion of information requested in the first DSAR; and (3) after obtaining the at least a portion of the requested information, having the obtained information displayed to a user as part of a fulfillment of the first DSAR. The information requested in the first DSAR may, for example, comprise at least substantially all (e.g., most or all) of the information regarding the first data subject that is stored accordingly to the data model.

In various embodiments, the system is adapted for: (1) automatically verifying an identity of a particular data subject access requestor placing the first DSAR; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically facilitating an update of personal data that an organization associated with the first webform is processing regarding the particular data subject access requestor.

Similarly, in particular embodiments, the system may be adapted for: (1) automatically verifying an identity of a particular data subject access requestor placing the first DSAR; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically processing the DSAR made by the particular data subject access requestor to opt out of having the organization use the particular data subject access requestor's personal information in one or more particular ways.

The system may, in various embodiments, be adapted for: (1) providing a webform creation tool that is adapted for receiving webform creation criteria from a particular user, the webform creation criteria comprising at least one criterion that includes one or more of: (A) a language that the form will be displayed in; (B) what information is to be requested from data subjects who uses the webform to initiate a DSAR; and/or (C) what systems and/or who any DSARs that are received via the webform should be routed to; and (2) executing the webform creation tool to create webforms (e.g., both the first webform and the second webform).

In light of the discussion above, although the DSAR Routing Module 1000 is described as being adapted in various embodiments to route DSARs to particular individuals for handling, it should be understood that in some embodiments the module may be adapted to process at least part of, or all of, particular DSARs automatically (e.g., without input from a human user). In such cases, the system may or may not route such automatically-processed requests to a designated individual for additional handling or monitoring. In particular embodiments, the system may automatically fulfill all or a portion of a particular DSAR, automatically assign a transaction ID and/or authentication token to the automatically fulfilled DSAR, and then provide the completed DSAR for display on a system dashboard associated with a particular individual who may have otherwise been responsible for processing the DSAR (e.g., an individual to whom a webform receiving the DSAR would otherwise have routed the DSAR to). This may be helpful in allowing a human user to later track, and answer any questions about, the automatically-fulfilled DSAR.

It should also be understood that, although the system is described in various embodiments as receiving DSARs via multiple webforms, each of which is located on a different website, in other embodiments, the system may receive DSARs via only a single webform, or through any other suitable input mechanism besides a webform (e.g., through any suitable software application, request via SMS message, request via email, data transfer via a suitable API, and/or the like)

In various embodiments, the system may be adapted to access information needed to satisfy DSARs via one or more suitable data models. Such data models include those that are described in greater detail in U.S. patent application Ser. No. 15/996,208, filed Jun. 1, 2018, which, as noted above, is incorporated herein by reference in its entirety. These data models may provide information to the system that can be useful to the system in identifying the data assets and/or data processing activities found within a data network that are involved in handing personal data needed to satisfy the DSARs. In various embodiments, the system is adapted to build and access such data models as described in this earlier-filed U.S. patent application.

As an example, in fulfilling a DSAR to produce, modify, or delete, and/or the like any of a data subject's data (e.g., personal data) that is stored by a particular entity within a data network, the system may be adapted to access a suitable data model to identify the data (e.g., the personal data) of the data subject that is currently being stored in one or more data assets (e.g., computer systems) associated with the particular entity. After using the data model to identify the data, the system may automatically process the data accordingly (e.g., by modifying or deleting it, and/or sharing it with the DSAR requestor).

Data Subject Access Request Prioritization Module 5000

In various embodiments, the system may be adapted to prioritize the processing of DSAR's based on metadata about the DSAR and/or the data subject associated with the DSAR. For example, the system may be adapted for: (1) in response to receiving a DSAR, obtaining metadata regarding at least one of the DSAR and/or the data subject associated with the DSAR; (2) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (3) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.

As previously noted, in some instances, the metadata may be directly related to the DSAR and/or the data subject. For examples, metadata that may be used to determine whether to adjust the priority of a particular DSAR include: (1) the type of DSAR, (2) a location from which the DSAR is being made, (3) current sensitivities to world events, (4) a status of the requestor and/or data subject (e.g., especially loyal customer, important client, competitor, etc.), or (5) any other suitable metadata directly related to the DSAR and/or the data subject.

In various embodiments, in response to the system determining that the priority of a particular DSAR should be elevated, the system may automatically adjust the deadline for responding to the DSAR. For example, the system may update the deadline in the system's memory and/or modify the “Days Left to Respond” field (See FIG. 19) to include a fewer number of days left to respond to the request. Alternatively, or in addition, the system may use other techniques to convey to a respondent that the request should be expedited (e.g., change the color of the request, send a message to the respondent that they should process the request before non-prioritized requests, etc.)

In various embodiments, in response to the system determining that the priority of a particular DSAR should be lowered, the system may automatically adjust the deadline for responding to the DSAR by adding to the number of days left to respond to the request. In other embodiments, the system may be configured to prioritize more demanding requests (e.g., requests that may require more effort and/or computing resources to process), for example, to ensure that the requests can be fulfilled within legally defined deadlines or timelines.

In particular embodiments, the DSAR Prioritization Module 5000 is configured to receive a DSAR, obtain one or more pieces of metadata associated with the DSAR and/or data subject associated with the DSAR, analyze the one or more pieces of metadata to determine or adjust a prioritization level of the DSAR, and digitally store the determined or adjusted prioritization level of the DSAR in computer memory.

Turning to FIG. 50, when executing the DSAR Prioritization Module 5000, the system begins, at step S010, by receiving a DSAR. For instance, in particular embodiments, the system receives the request via a suitable web form or some other mechanism as previously discussed herein. In certain embodiments, the DSAR comprises a particular request to perform one or more actions for personal data stored by a particular organization regarding the data subject (e.g., the requestor). Here, the personal data may be stored in a data network that includes a number of data assets and/or data processing activities that may be involved in handling the personal data for the particular organization. For example, in some embodiments, the DSAR may include a request to view one or more pieces of personal data stored within the data network regarding the data subject. In other embodiments, the DSAR may include a request to delete one or more pieces of personal data stored within the data network regarding the data subject. In still other embodiments, the DSAR may include a request to update one or more pieces of personal data stored within the data network regarding the data subject. Additionally, as described above, data subjects may be entitled to certain rights related to the data subjects' personal data that is collected, stored, or otherwise processed by an organization, and the rights may be asserted or requested by a data subject as a DSAR. Accordingly, to fulfill the DSAR, the system can retrieve one or more pieces of personal data associated with the data subject to perform the requested operation to the retrieved one or more pieces of personal data associated with the data subject.

The system may further be configured to process the request by validating the identity of the requestor. The system may be configured to substantially automatically (e.g., automatically) authenticate and/or validate an identity of a requestor (e.g., data subject) using various techniques. These techniques may include, for example: (1) one or more credit-based and/or public- or private-information-based verification techniques; (2) one or more company verification techniques (e.g., in the case of a business-to-business DSAR); (3) one or more techniques involving integration with a company's employee authentication system; (4) one or more techniques involving a company's (e.g., organization's) consumer portal authentication process; (5) and/or the like.

In particular embodiments, when authenticating a data subject (e.g., validating the data subject's identity), the system may be configured to execute particular identity confirmation steps, for example, by interfacing with one or more external systems (e.g., one or more third-party data aggregation systems). For example, the system, when validating a data subject's identity, may begin by verifying that a person with the data subject's name, address, social security number, or other identifying characteristic (e.g., which may have been provided by the data subject as part of the DSAR) actually exists. In still other embodiments, the system may be configured to utilize one or more other third-party systems (e.g., such as LexisNexis, Idology, RSA, etc.), which may, for example, compile utility and phone bill data, property deeds, rental agreement data, and other public records for various individuals. After confirming the existence of a person with the one or more characteristics provided by the data subject, the system may be configured to confirm that the requestor making the DSAR is, in fact, the data subject.

In various embodiments, the system may apply an initial prioritization level to each DSAR. The prioritization level can be used to attribute an urgency, importance, and/or sensitivity in fulfilling each particular DSAR. Additionally, the prioritization level may be used to place the DSARs in an order of fulfillment (e.g., in a fulfillment data subject access request queue). The prioritization level applied to the DSAR after the system receives the request can be based on the data included in the DSAR itself, which may include, for example, an identity of the data subject, an identity of the particular organization receiving the DSAR, a requested deadline for receiving fulfillment of the DSAR, and/or the like. In some implementations, the prioritization level can be two levels (e.g., “standard” and “urgent” or “standard” and “sensitive”), and in some implementations, the system can include three or more different prioritization levels (e.g., “high,” “medium,” and “low”).

Continuing to step S020, the system is configured to obtain one or more pieces of metadata associated with the DSAR. For instance, depending on the embodiment, the one or more pieces of metadata may describe additional information related to the DSAR and/or the data subject associated with the DSAR. Examples of metadata that may relate to the priority (e.g., prioritization level) of a particular DSAR can include: (1) a request type associated with the DSAR; (2) a location from which the DSAR is being made; (3) current sensitivities to world events (e.g., a war occurring in a country where a particular organization has a server that stores data subject's information); (4) a status of the requestor issuing the DSAR and/or the data subject; (5) a time in which the DSAR was made; (6) and/or the like. Here, the metadata related to the request type may identify what the requestor is requesting from the particular organization. For example, the request type can be a request to advise the requestor of the personal data that the organization has stored related to the data subject (e.g., a subject's rights request) or a request to delete one or more pieces of personal data stored by the particular organization regarding the data subject (e.g., a data subject deletion request).

In addition, in particular embodiments, the metadata may include factors that may affect the processing of the DSAR. Examples of metadata that may be related to factors that can affect the processing of the DSAR can include: (1) a data asset found within the data network that is involved in handling personal data needed to fulfill the DSAR; (2) a data processing activity that may be performed in association with the data network in fulfilling the DSAR; (3) conditions occurring within the data network that may affect a data asset and/or a data processing activity involved in fulfilling the DSAR; and/or (4) any other suitable metadata related to one or more factors that involve processing the DSAR.

As a particular example, a particular data network maybe experiencing a high volume of data traffic. As a result, one or more data processing activities that are used in retrieving personal data needed to fulfill the DSAR may be delayed. In addition, one or more additional data assets (e.g., servers) may be needed to handle the high volume of data traffic. As a result, these additional data assets may be unavailable for processing the DSAR. In another example, a data asset used in storing personal data needed for fulfilling the DSAR may be currently unavailable (e.g., “offline”) or may be scheduled to become unavailable. Therefore, the system may not currently be able to process the DSAR. In another example, a data processing activity used in retrieving personal data needed to fulfill the DSAR may not currently be operating correctly (malfunctioning) and may therefore be unable to retrieve the personal data. Again, as a result, the system may not currently be able to process the DSAR.

In addition, in particular embodiments, the metadata may include other information such as, for example: (1) the requestor's IP address (e.g., or other location data); (2) the requestor's MAC address; (3) one or more regulations that apply to the request; (4) and/or the like. Further, in particular embodiments, the metadata may include the type of request (e.g., a request for data, a request to delete data, and/or a request to correct data).

In various embodiments, the metadata may be provided to the system as part of, or along with, the DSAR. However, in some embodiments, the metadata may be provided substantially automatically (e.g., automatically) subsequent to the system receiving the DSAR, or an individual of the particular organization (e.g., a privacy officer) may manually request the one or more pieces of metadata subsequent to receiving the DSAR. In some embodiments, the system may obtain one or more pieces of metadata from a third party (e.g., a web browser identifying current events in a particular location). Additionally, in some implementations, data of the DSAR and/or metadata can be provided to the system via a secure terminal or secure link between a computer system that includes the metadata (e.g., the computer system of the requestor) and a system to prevent interception of the data or unwarranted access to the additional information. Additionally, the data of the DSAR and/or metadata may be encrypted for the transmission of the data.

In some embodiments, the system may monitor the data network to obtain the metadata.

For instance, the system may monitor data processing through the data network to identify conditions within the data network with respect to various data assets and/or data processing activities used in processing personal data needed to fulfill the DSAR. For example, the system may monitor data processing through the data network to determine conditions for the various data assets and/or data processing activities. The conditions may include a particular data asset or data processing activity: (1) being unavailable; (2) being scheduled to become unavailable; performing too slowly; performing too quickly, and/or the like. In addition, the system may determine conditions for other factors of the data network such as the amount of data traffic currently being processed within the data network, the amount of processing capacity that is being used and/or that is available within the data network, the number of data processing activities that are queued to be run, and/or the like.

At step S030, the system is configured to analyze the one or more pieces of metadata to determine a prioritization level of the DSAR. For instance, in particular embodiments, the system may analyze one or more pieces of metadata to identify information related to an urgency for fulfilling the particular DSAR. For example, requests for deletion and production of data may be prioritized ahead of data correction requests. In another example, the system may prioritize requests that have a legal basis (e.g., any suitable request under the GDPR) over requests to which a data subject may not be legally entitled (e.g., but that the organization may still fulfil, but at a lower priority level behind other more pressing requests).

In other instances, the system may analyze the one or more pieces of metadata and determine that a condition exists for a data asset and/or data processing activity that prevents the system from currently processing the DSAR. In other instances, the system may analyze the one or more pieces of metadata and determine that a condition exists within the data network that affects an amount of computing resources and/or an amount of time needed for processing the personal data needed to fulfill the DSAR. Accordingly, the system may determine a prioritization level of the DSAR by taking such conditions into consideration.

In some implementations, a prioritization level is applied to the DSAR prior to the system receiving and/or analyzing the one or more pieces of metadata, as described above. This initial prioritization level may be applied based on data provided in the DSAR (e.g., an identification of the requestor). The system may then obtain one or more pieces of metadata, as described above, and determine whether the one or more pieces of metadata relate to a priority of fulfilling the DSAR. For instance, in particular embodiments, the system may perform the determination by analyzing the contents of the one or more pieces of metadata for information related to, for example: (1) a request type associated with the DSAR; (2) a location from which the DSAR is being made; (3) current sensitivities to world events (e.g., a war occurring in a country where a particular organization has a server that stores data subject's information); (4) a status of the requestor issuing the DSAR (e.g., customer) and/or the data subject; (5) a time in which the DSAR was made; (6) and/or the like. In particular embodiments, the system may perform the determination by analyzing the contents of the one or more pieces of metadata for information relating to, for example: (1) a data asset found within the data network that is involved in handling personal data needed to fulfill the DSAR; (2) a data processing activity that may be performed within the data network in fulfilling the DSAR; (3) conditions occurring within the data network that may affect a data asset and/or a data processing activity involved in fulfilling the DSAR; (4) and/or the like.

In response to the system determining that one or more pieces of metadata relate to the priority of fulfilling the DSAR, the system may analyze the metadata to determine whether the prioritization level of the DSAR should be adjusted. For example, if one of the pieces of metadata is related to a location from which the DSAR is being made and the content of the metadata identifies that the location is a different continent than the location the data servers that store the personal data for the particular organization (receiving the DSAR), then the system may determine that the urgency and sensitivity of this particular metadata necessitates an adjustment to the prioritization level of the DSAR. Specifically, the system may determine that the data transmission and rules involving storage of personal data in different continents indicates a greater risk and more attention required in fulfilling the DSAR. In continuing the above example, if the content of the metadata identified that the location from which the request is being made is the same continent where the data servers that store the personal data for the particular organization are located, then the system may determine that an adjustment to the prioritization level of the DSAR is not necessary.

In yet another example, if one of the pieces of metadata indicates that a condition exists in which personal data needed for fulfilling the DSAR is stored on a data asset that is currently unavailable, then the system may determine that an adjustment to the prioritization level of the DSAR is needed to lower it. In another example, if one of the pieces of metadata indicates that a condition exists in which the amount of time needed to process the DSAR is higher than expected and the timeline for fulfilling the DSAR is short, then the system may determine that an adjustment to the prioritization level of the DSAR is needed to increase it.

In response to determining that the prioritization level of the DSAR should be adjusted based on one or more pieces of metadata, the system may adjust the prioritization level of the DSAR for fulfillment. As described above, the system may adjust the prioritization level based on the analyzed content of the metadata that was determined to be related to the prioritization level of the DSAR. When the system determines that the urgency, importance, and/or sensitivity of one or more pieces of metadata necessitate an adjustment to the prioritization level, the system can increase the prioritization level of the DSAR from, for example, a “standard” prioritization level to an “urgent” prioritization level, or a “normal” prioritization level to a “high” prioritization level. Additionally, the system may determine that the content of the metadata reduces the urgency, importance, and/or sensitivity of DSAR, and the system can decrease the prioritization level of the DSAR from, for example, a “urgent” prioritization level to an “standard” prioritization level, or a “normal” prioritization level to a “low” prioritization level.

In various embodiments, the prioritization level may be stored by the system and presented (e.g., via a user interface to a privacy officer of the organization) as a prioritization indicator associated with the DSAR to show the prioritization level of the DSAR has been adjusted. For example, the system can store a listing of DSARs, and a column within a user interface presentation of the listing of DSARs can provide the prioritization indicator presented in one color (e.g., yellow) for a “standard” prioritization level and a different color (e.g., red) for an “urgent” prioritization level.

Further, in some embodiments, in response to adjusting the prioritization level of the DSAR, the system may modify a completion date for fulfillment of the DSAR (e.g., the completion data may be stored in a database of the system and presented in a user interface to a privacy officer of the organization). For example, when the system decreases the prioritization level of the DSAR, the system may move the completion date back by modifying the completion date to a modified completion date that is a later date than the initial completion date (e.g., modifying the completion date from Dec. 29, 2018, to Dec. 31, 2018). Likewise, in some embodiments, when the system increases the prioritization level of the DSAR, the system may move the completion date forward by modifying the completion date to a modified completion date that is an earlier date than the initial completion date (e.g., modifying the completion date from Dec. 29, 2018, to Dec. 27, 2018). In some embodiments, the completion date can be shown as “Days Left to Respond,” so the system may calculate the days left from a current date to the completion date, and the present the number of days left until the completion date from the current date.

In various embodiments, in response to adjusting the prioritization level of the DSAR, the system may generate a prioritization message (e.g., email or other type of electronic communication) to indicate that the prioritization level of the DSAR has been adjusted. Further, the system may electronically communicate the prioritization message to at least one privacy team member that is assigned to fulfill the DSAR (e.g., a privacy officer for the particular organization).

In some embodiments, a prioritization level is first applied to the DSAR subsequently to the system analyzing the one or more pieces of metadata associated with the DSAR and/or data subject. In such embodiments, the system may analyze the one or more pieces of metadata and in response, determine a prioritization level for the DSAR (i.e., the prioritization level is not adjusted in this instance because the prioritization level is not determined until after the one or more pieces of metadata are analyzed).

Finally, at step S040, the system is configured to digitally store the prioritization level of the DSAR in computer memory. Additionally, in embodiments where the prioritization level is adjusted, the system is configured to digitally store the adjusted prioritization level of the DSAR in computer memory. Accordingly, in particular embodiments, the system may access the stored prioritization level (or adjusted prioritization level) for each of a plurality of DSARs and place the DSARs in an order of fulfillment (e.g., in a fulfillment data subject access request queue).

The operation of various embodiments of the various software modules above is described in greater detail below. It should be understood that the various steps described herein may be executed, by the system, in any suitable order and that various steps may be omitted, or other steps may be added in various embodiments.

Operation of Example Implementation

FIGS. 3-43 are screen shots that demonstrate the operation of a particular embodiment.

FIGS. 3-6 show a graphical user interface (GUI) of an example webform construction tool. FIG. 3 shows a user working to design a webform called “Web form 1.” As may be understood from the vertical menu shown on the left-hand side of the screen, the webform construction tool allows users to design a webform by: (1) specifying the details of the form (via the “Form Details” tab); (2) defining the fields that will be displayed on the webform (via the “Webform Fields” tab); (3) defining the styling of the webform (via the “Form Styling” tab); and (4) defining various settings associated with the webform (via the “Settings” tab). As shown in FIGS. 4-6, the user may also specify text to be displayed on the webform (e.g., via a “Form Text” tab).

FIG. 4 shows that, by selecting the “Form Details” tab, the user may define which answers a requestor will be able to specify on the webform in response to prompts for information regarding what type of individual they are (customer, employee, etc.) and what type of request they are making via the webform. Example request types include: (1) a request for all personal data that an organization is processing for the data subject (a copy of the personal data in a commonly used, machine-readable format); (2) a request for all such personal data to be deleted; (3) a request to update personal data that the organization is storing for the data subject; (4) a request to opt out of having the organization use the data subject's personal information in one or more particular ways (e.g., per the organization's standard business practices); (5) a request for filing a complaint; and/or (6) other.

FIG. 5 shows that, by selecting the “Settings” tab, the user may specify various system settings, such as whether Captcha will be used to verify that information is being entered by a human, rather than a computer.

FIG. 6 shows that, by selecting the Form Styling tab, the user may specify the styling of the webform. The styling may include, for example: (1) a header logo; (2) header height; (3) header color; (4) body text color; (5) body text size; (6) form label color; (7) button color; (8) button text color; (9) footer text color; (10) footer text size; and/or any other suitable styling related to the webform.

In other embodiments, the system is configured to enable a user to specify, when configuring a new webform, what individual at a particular organization (e.g., company) will be responsible for responding to requests made via the webform. The system may, for example, enable the user to define a specific default sub-organization (e.g., within the organization) responsible for responding to DSARs submitted via the new webform. As such, the system may be configured to automatically route a new DSAR made via the new webform to the appropriate sub-organization for processing and fulfillment. In various embodiments, the system is configured to route one or more various portions of the DSAR to one or more different sub-organizations within the organization for handling.

In particular embodiments, the system may include any suitable logic for determining how the webform routes DSARs. For example, the system may be adapted to determine which organization or individual to route a particular DSAR to based, at least in part, on one or more factors that may include: (1) the data subject's current location; (2) the data subject's country of residence; (3) the type of request being made; (4) the type of systems that contain (e.g., store and/or process) the data subject's personal data (e.g., in ADP, Salesforce, etc.); and/or (5) any other suitable factors.

In particular embodiments, the system is configured to enable a user generating webforms to assign multiple webforms to multiple different respective suborganizations within an organization. For example, an organization called ACME, Inc. may have a website for each of a plurality of different brands (e.g., sub-organizations) under which ACME sells products (e.g., UNICORN Brand T-shirts, GRIPP Brand Jeans, etc.). As may be understood in light of this disclosure, each website for each of the particular brands may include an associated webform for submitting DSARs (e.g., accessible via as a webform directly on the website or a link on the website). Each respective webform may be configured to route a DSAR made via its associated brand website to a particular sub-organization and/or individual(s) within ACME for handling DSARs related to the brand.

As noted above, in particular embodiments, once the user has designed a particular webform for use on a particular web page, the webform construction tool may generate code (e.g., HTML code) that can be pasted into the particular web page to run the designed webform. For instance, in some embodiments, when pasted into the particular web page, the code may generate a selectable button on the web page that, when selected, causes display of the DSAR webform.

FIG. 7 shows a privacy webpage for a company (e.g., the ACME corporation). As shown in this figure, a requestor may submit a DSAR by selecting a “Submit a Privacy Related Request” button on the web page. Accordingly, FIG. 8 shows a webform that is displayed after a requestor selects the “Submit a Privacy Related Request” button on the privacy webpage of FIG. 7. As may be understood from this figure, the requestor may complete the webform by specifying which type of user they are, and what type of request they are making. In this instance, the webform also asks the requestor to provide enough personal information to confirm their identity (e.g., and fulfill the request). As shown in this figure, the user submitting the DSAR may be prompted to provide information such as, for example: (1) what type of requestor the user is (e.g., employee, customer, etc.); (2) what the request involves (e.g., requesting data, opting out, deleting data, updating data, and/or the like); (3) first name; (4) last name; (5) email address; (6) telephone number; (7) home address; (8) one or more other pieces of identifying information; (9) one or more details associated with the request; (10) and/or the like. FIG. 9 shows an example populated version of the webform.

As shown in FIG. 10, after a requestor completes the webform and selects a “submit” indicia, a message is displayed to the requestor indicating that their DSAR has been successfully submitted. In particular embodiments, a Request ID associated with the request is also displayed. In response to the requestor successfully submitting the request, an email (or other suitable communication) may be sent to the requestor confirming the request. An example of a suitable confirmation email is shown in FIG. 11.

In various embodiments, the system includes a dashboard that may be used by various individuals within an organization (e.g., one or more privacy officers of an organization) to manage multiple DSARs. As discussed above, the dashboard may display DSARs submitted, respectively, to a single organization, any of multiple different sub-organizations (divisions, departments, subsidiaries etc.) of a particular organization, and/or any of multiple independent organizations. For example, the dashboard may display a listing of DSARs that were submitted from a parent organization and from the parent organization's U.S. and European subsidiaries. This may be advantageous, for example, because it may allow an organization to manage all DSARs of all of its sub-organizations (and/or other related organizations) centrally.

FIGS. 12-23, 25-27, 29-34, and 41-43 depict various example user-interface screens of a DSAR request-management dashboard. As may be understood from FIG. 12, after an appropriate user (e.g., a privacy officer associated with a particular organization) logs into the system, the system may display a Data Subject Request Queue that may, for example, display a listing of all DSARs that the appropriate individual has been designated to process. As shown in FIG. 12, each DSAR may be represented by a respective row of information that may include, for example: (1) an ID number for the request; (2) the name of the data subject who is associated with the request; (3) the status of the request; (4) the number of days that are left to respond to the request (e.g., according to applicable laws and/or internal procedures); (5) an indication as to whether the deadline to respond to the request has been extended; (6) a creation date of the request; (7) an indication of the type of requestor that submitted the request (customer, employee, etc.); and/or (8) the name of the individual who has been assigned to process the request (e.g., the respondent). This screen may also include selectable “Edit” and “Filter” buttons that respectively facilitate acting on and filtering the various requests displayed on the page.

As shown in FIG. 13, in response to a respondent selecting the edit button while a particular DSAR is highlighted, the system displays a dropdown menu allowing the respondent to select between taking the following actions: (1) verify the request; (2) assign the request to another individual; (3) request an extension; (4) reject the request; or (5) suspend the request.

FIGS. 14 and 15 show a message that the system displays to the respondent in response to the respondent selecting the “verify” option. As shown in this figure, the system prompts the respondent to indicate whether they are sure that they wish to authenticate the request. The system also presents an input field where the respondent can enter text to be displayed to the requestor along with a request for the requestor to provide information verifying that they are the data subject associated with the request. After the respondent populates the input field, they may submit the request by selecting a “Submit” button.

In particular embodiments, the input field may enable the respondent to provide one or more supporting reasons for a decision to authenticate the request. The respondent may also upload one or more supporting documents (such as an attachment). The supporting documents or information may include, for example, one or more documents utilized in confirming the requestor's identity, etc.

In response to the respondent selecting the Submit button, the system changes the status of the request to “In Progress” and also changes the color of the request's status from orange to blue (or from any other suitable color to any different suitable color)—see FIG. 16. The system also generates and sends a message (e.g., an electronic or paper message) to the requestor asking them to submit information verifying the request. For example, the message may include the text that the respondent entered in the text box of FIG. 14.

As shown in FIGS. 17-19, in response to a respondent selecting the “Edit” button and then selecting the “Assign” indicia from the displayed dropdown menu, the system displays a Request Assignment interface that allows a respondent to indicate who the request should be assigned to. For example, the respondent may indicate that they will be handling the request, or assign the request to another suitable individual, who may, for example, then be designated as the respondent for the request. If the respondent assigns the request to another individual for handling, the respondent may also provide an email address or other correspondence information for the individual. In particular embodiments, the Request Assignment interface includes a comment box for allowing a respondent to add a message to the individual that the assignment will be assigned to regarding the assignment. In response to the respondent selecting the “Assign” button, the system assigns the request to the designated individual for handling. If the request has been assigned to another, designated individual, in particular embodiments, the system automatically generates and sends a message (e.g., an electronic message such as an email or SMS message) to the designated individual informing them of the assignment.

As shown in FIGS. 20-22, in response to a respondent selecting the “Edit” button and then selecting the “Reject” indicia from the displayed dropdown menu, the system displays a Reject Request interface. This interface includes a comment box for allowing a respondent to add a message to the requestor as to why the request was rejected. In response to the respondent selecting the “Submit” button, the system changes the status of the request to “Rejected” and changes the color of the request's status indicator to red (See FIG. 23). The system may also automatically generate a message (e.g., an electronic or paper message) to the requestor notifying them that their request has been rejected and displaying the text that the respondent entered into the Reject Request interface of FIG. 22. An example of such a message is shown in FIG. 24.

As shown in FIGS. 25-26, in response to a respondent selecting the “Edit” button and then selecting the “Request Extension” indicia from the displayed dropdown menu, the system displays a Request Extension interface. This includes a text box for allowing the respondent to indicate the number of days for which they would like to extend the current deadline for responding to the request. For example, the dialog box of FIG. 26 shows the respondent requesting that the current deadline be extended by 90 days. In response to the respondent entering a desired extension duration and selecting the “Submit” button, the system updates the deadline in the system's memory (e.g., in an appropriate data structure) to reflect the extension. For instance, in the example of FIG. 26, the system extends the deadline to be 90 days later than the current deadline. As shown in FIG. 27, the system also updates the “Days Left to Respond” field within the Data Subject Request Queue to reflect the extension (e.g., from 2 days from the current date to 92 days from the current date). As shown in FIG. 28, the system may also generate an appropriate message (e.g., an electronic message, such as an email, or a paper message) to the requestor indicating that the request has been delayed. This message may provide a reason for the delay and/or an anticipated updated completion date for the request.

In particular embodiments, the system may include logic for automatically determining whether a requested extension complies with one or more applicable laws or internal policies and, in response, either automatically grant or reject the requested extension. For example, if the maximum allowable time for replying to a particular request is 90 days under the controlling laws and the respondent requests an extension that would result in the fulfillment of the request 91 or more days from the date that the request was submitted, the system may automatically reject the extension request. In various embodiments, the system may also communicate to the respondent (e.g., via a suitable electronic message or text display on a system user interface) an explanation as to why the extension request was denied, and/or a maximum amount of time (e.g., a maximum number of days) that the deadline may be extended under the applicable laws or policies. In various embodiments, if the system determines that the requested extension is permissible under the applicable laws and/or policies, the system may automatically grant the extension.

In other embodiments, the system may be configured to automatically modify a length of the requested extension to conform with one or more applicable laws and/or policies. For example, if the request was for a 90-day extension, but only a 60 day extension is available under the applicable laws or regulations, the system may automatically grant a 60-day extension rather than a 90 day extension. The system may be adapted to also automatically generate and transmit a suitable message (e.g., a suitable electronic or paper communication) notifying them of the fact that the extension was granted for a shorter, specified period of time than requested.

As shown in FIGS. 29-34, a respondent may obtain additional details regarding a particular request by selecting (e.g., clicking on) the request on the Data Subject Request Queue screen. For instance, FIG. 29 depicts an exemplary user interface that may be included to assist in prioritizing the fulfillment of the DSARs. For example, the user interface can be presented to the privacy officer assigned to fulfill the DSARs. As shown in the Figure, the user interface may present a DSAR queue for fulfillment, which may include a prioritization column along with additional columns (e.g., ID column, a name of requestor column, etc.) for each DSAR to provide information for the particular organization to fulfill the DSAR. In the exemplary user interface, a prioritization indicator is included for each DSAR where the prioritization indicators include prioritization levels of “Low,” “Normal,” and “Urgent.” The privacy officer or other individual within a particular organization responsible for fulfilling the DSARs may arrange and organize their fulfillment of the DSARs based on the prioritization level provided. The DSARs may, for example, be sorted based on the prioritization levels (e.g., where the DSARs with an “Urgent” prioritization level are grouped at the top of the DSAR queue followed by the DSARs with a “Normal” prioritization level, and then the DSARs with a “Low” prioritization level) or the other columns. In some embodiments, the DSARs may be automatically re-sorted based on a change in the prioritization level for a DSAR. Additionally, the DSARs may be filtered based on the prioritization levels (e.g., where the DSARs with an “Urgent” prioritization level are only shown in the data subject request queue).

FIG. 30 shows a Data Subject Request Details screen that the system displays in response to a respondent selecting the “Donald Blair” request on the user interface screen of FIG. 35. As shown in FIG. 30, the Data Subject Request Details screen shows all correspondence between the organization and the requesting individual regarding the selected DSAR. As may be understood from FIG. 31, when a respondent selects a particular correspondence (e.g., email), the system displays the correspondence to the respondent for review or other processing.

As shown in FIG. 32, in various embodiments, the system may provide a selectable “Reply” indicia that allows the respondent to reply to particular correspondence from an individual. As may be understood from this figure, in response to the respondent selecting the “Reply” indicia, the system may display a dropdown menu of various standard replies. For example, the dropdown menu may provide the option of generating a reply to the requestor indicating that the request has been rejected, is pending, has been extended, or that the request has been completed.

As shown in FIG. 33, in response to the respondent selecting “Reply as Completed”, the system may generate a draft email to the requestor explaining that the request has been completed. The respondent may then edit this email and send the edited correspondence (e.g., via email) to the requestor by selecting a “Send as Complete” indicia. As shown in FIG. 34, the system may, in response, display an indicator adjacent the correspondence indicating that the correspondence included a reply indicating that the request was completed. This may be useful in allowing individuals to understand the contents of the correspondence without having to open it.

FIG. 35 shows an example email automatically generated by the system in response to the respondent selecting “Reply as Completed” on the screen shown in FIG. 32. As shown in FIG. 35, the correspondence may include a secure link that the requestor may select to access the data that was requested in the DSAR. In particular embodiments, the link is to a secure website, such as the website shown in FIG. 36, that provides access to the requested data (e.g., by allowing a user to download a .pdf file, or other suitable file, which includes the requested data). As shown in FIG. 36, the website may require multiple pieces of data to verify that the requestor is permitted to access the site. For example, in order to access the website, the requestor may be required to provide both the unique ID number of the request, and an authentication token, which the system may send to the user via email—See FIGS. 37 and 38.

FIGS. 39-43 are computer screen shots that depict additional user interfaces according to various embodiments.

Additional Concepts

Automatic Deletion of Data Subject Records Based on Detected Systems

In particular embodiments, in response a data subject submitting a request to delete their personal data from an organization's data network, the system may: (1) automatically determine where the data subject's personal data is stored; and (2) in response to determining the location of the data (which may be on multiple systems, data assets, and/or the like within the data network), automatically facilitate the deletion of the data subject's personal data from the various systems, data assets, and/or the like (e.g., by automatically assigning a plurality of tasks to delete data across multiple systems, data assets, and/or the like to effectively delete the data subject's personal data from the systems, data assets, and/or the like). In particular embodiments, the step of facilitating the deletion may comprise, for example: (1) overwriting the data in memory; (2) marking the data for overwrite; (2) marking the data as free (e.g., and deleting a directory entry associated with the data); and/or (3) any other suitable technique for deleting the personal data. In particular embodiments, as part of this process, the system uses an appropriate data model (see discussion above) to efficiently determine where all of the data subject's personal data is stored.

Automatic Determination of Business Processes that Increase Chance of Deletion Requests

In various embodiments, the system is adapted to store, in memory, a log of DSAR actions. The system may also store, in memory, additional information regarding the data subjects of each of the requests. The system may use this information, for example, to determine which business processes are most commonly associated with a data subject submitting a request to have their personal information deleted from the organization's data network (e.g., systems, data assets, and/or the like). The organization may then use this information to revise the identified business processes in an effort to reduce the number of deletion requests issued by data subjects associated with the business processes.

As a particular example, the system may analyze stored information to determine that a high number (e.g., 15%) of all participants in a company's loyalty program submit requests to have their personal information deleted from the company's data network. In response to making this determination, the system may issue an electronic alert to an appropriate individual (e.g., a privacy officer of the company), informing them of the high rate of members of the company's loyalty program issuing personal data delete requests. This alert may prompt the individual to research the issue and try to resolve it.

Automated Data Subject Verification

In various embodiments, before a data subject request can be processed, the data subject's identity may need to be verified. In various embodiments, the system provides a mechanism to automatically detect the type of authentication required for a particular data subject based on the type of DSAR being made and automatically issues a request to the data subject to verify their identity against that form of identification. For example, a subject rights request might only require two types of authentication, but a deletion request may require four types of authentication. The system may automatically detect which is type of authentication is required based on the DSAR and send an appropriate request to the data subject to verify their identity.

Stated more particularly, when processing a DSAR, the system may be configured to verify an identity of the data subject prior to processing the request (e.g., or as part of the processing step). In various embodiments, confirming the identity of the data subject may, for example, limit a risk that a third-party or other entity may gain unlawful or unconsented to access to the requestor's personal data. The system may, for example, limit processing and fulfillment of requests relating to a particular data subject to requests that are originated by (e.g., received from) the particular data subject. When processing a DSAR, the system may be configured to use various reasonable measures to verify the identity of the data subject who requests access (e.g., in particular in the context of online services and online identifiers). In particular embodiments, the system is configured to substantially automatically validate an identity of a data subject when processing the DSAR.

For example, in particular embodiments, the system may be configured to substantially automatically (e.g., automatically) authenticate and/or validate an identity of a data subject using any suitable technique. These techniques may include, for example: (1) one or more credit-based and/or public- or private-information-based verification techniques; (2) one or more company verification techniques (e.g., in the case of a business-to-business DSAR); (3) one or more techniques involving integration with a company's employee authentication system; (4) one or more techniques involving a company's (e.g., organization's) consumer portal authentication process; (5) etc. Various exemplary techniques for authenticating a data subject are discussed more fully below.

In particular embodiments, when authenticating a data subject (e.g., validating the data subject's identity), the system may be configured to execute particular identity confirmation steps, for example, by interfacing with one or more external systems (e.g., one or more third-party data aggregation systems). For example, the system, when validating a data subject's identity, may begin by verifying that a person with the data subject's name, address, social security number, or other identifying characteristic (e.g., which may have been provided by the data subject as part of the DSAR) actually exists. In various embodiments, the system is configured to interface with (e.g., transmit a search request to) one or more credit reporting agencies (e.g., Experian, Equifax, TransUnion, etc.) to confirm that a person with one or more characteristics provided by the data subject exists. The system may, for example, interface with such credit reporting agencies via a suitable plugin (e.g., software plugin). Additionally, there might be a verification on behalf of a trusted third-party system (e.g., the controller).

In still other embodiments, the system may be configured to utilize one or more other third-party systems (e.g., such as LexisNexis, Idology, RSA, etc.), which may, for example, compile utility and phone bill data, property deeds, rental agreement data, and other public records for various individuals. The system may be configured to interface with one or more such third-party systems to confirm that a person with one or more characteristics provided by the data subject exists.

After the step of confirming the existence of a person with the one or more characteristics provided by the data subject, the system may be configured to confirm that the person making the DSAR is, in fact, the data subject. The system may, for example, verify that the requestor is the data subject by prompting the requestor to answer one or more knowledge-based authentication questions (e.g., out-of-wallet questions). In particular embodiments, the system is configured to utilize one or more third-party services as a source of such questions (e.g., any of the suitable third-party sources discussed immediately above). The system may use third-party data from the one or more third-party sources to generate one or more questions. These one or more questions may include questions that a data subject should know an answer to without knowing the question ahead of time (e.g., one or more previous addresses, a parent or spouse name and/or maiden name, etc.).

FIG. 46 depicts an exemplary identity verification questionnaire. As may be understood from this figure, an identity verification questionnaire may include one or more questions whose responses include data that the system may derive from one or more credit agencies or other third-party data aggregation services (e.g., such as previous street addresses, close associates, previous cities lived in, etc.). In particular embodiments, the system is configured to provide these one or more questions to the data subject in response to receiving the DSAR. In other embodiments, the system is configured to prompt the data subject to provide responses to the one or more questions at a later time (e.g., during processing of the request). In particular other embodiments, the system is configured to substantially automatically compare one or more pieces of information provided as part of the DSAR to one or more pieces of data received from a third-party data aggregation service in order to substantially automatically verify the requestor's identity.

In still other embodiments, the system may be configured to prompt a requestor to provide one or more additional pieces of information in order to validate the requestor's identity. This information may include, for example: (1) at least a portion of the requestor's social security number (e.g., last four digits); (2) a name and/or place of birth of the requestor's father; (3) a name, maiden name, and/or place of birth of the requestor's mother; and/or (4) any other information which may be useful for confirming the requestor's identity (e.g., such as information available on the requestor's birth certificate). In other embodiments, the system may be configured to prompt the requestor to provide authorization for the company to check the requestor's social security or other private records (e.g., credit check authorization, etc.) to obtain information that the system may use to confirm the requestor's identity. In other embodiments, the system may prompt the user to provide one or more images (e.g., using a suitable mobile computing device) of an identifying document (e.g., a birth certificate, social security card, driver's license, etc.).

The system may, in response to a user providing one or more responses that matches information that the system receives from one or more third-party data aggregators or through any other suitable background, credit, or other search, substantially automatically authenticate the requestor as the data subject. The system may then continue processing the data subject's request, and ultimately fulfill their request.

In particular embodiments, such as embodiments in which the requestor includes a business (e.g., as in a business to business DSAR), the system may be configured to authenticate the requesting business using one or more company verification techniques. These one or more company validation techniques may include, for example, validating a vendor contract (e.g., between the requesting business and the company receiving the DSAR); receiving a matching token, code, or other unique identifier provided by the company receiving the DSAR to the requesting business; receiving a matching file in possession of both the requesting business and the company receiving the DSAR; receiving a signed contract, certificate (e.g., digital or physical), or other document memorializing an association between the requesting business and the company receiving the DSAR; and/or any other suitable method of validating that a particular request is actually made on behalf of the requesting business (e.g., by requesting the requesting business to provide one or more pieces of information, one or more files, one or more documents, etc. that may only be accessible to the requesting business).

In other embodiments, the system may be configured to authenticate a request via integration with a company's employee or customer (e.g., consumer) authentication process. For example, in response to receiving a DSAR that indicates that the data subject is an employee of the company receiving the DSAR, the system may be configured to prompt the employee to login to the company's employee authentication system (e.g., Okta, Azure, AD, etc.) In this way, the system may be configured to authenticate the requestor based at least in part on the requestor successfully logging into the authentication system using the data subject's credentials. Similarly, in response to receiving a DSAR that indicates that the data subject is a customer of the company receiving the DSAR, the system may be configured to prompt the customer to login to an account associated with the company (e.g., via a consumer portal authentication process). In a particular example, this may include, for example, an Apple ID (for DSARs received by Apple). In this way, the system may be configured to authenticate the requestor based at least in part on the requestor successfully logging into the authentication system using the data subject's credentials. In some embodiments, the system may be configured to require the requestor to login using two-factor authentication or other suitable existing employee or consumer authentication process.

Data Subject Blacklist

In various embodiments, a particular organization may not be required to respond to a DSAR that originates from (e.g., is received from) a malicious requestor. A malicious requestor may include, for example: (1) a requestor (e.g., an individual) that submits excessive or redundant DSARs; (2) a group of requestors such as researchers, professors, students, NGOs, etc. that submit a plurality of requests for reasons other than those reasons provided by policy, law, etc.; (3) a competitor of the company receiving the DSAR that is submitting such requests to tie up the company's resources unnecessarily; (4) a terrorist or other organization that may spam requests to disrupt the company's operation and response to valid requests; and/or (5) any other request that may fall outside the scope of valid requests made for reasons proscribed by public policy, company policy, or law. In particular embodiments, the system is configured to maintain a blacklist of such malicious requestors.

In particular embodiments, the system is configured to track a source of each DSAR and analyze each source to identify sources from which: (1) the company receives a large volume of requests; (2) the company receives a large number of repeat requests; (3) etc. These sources may include, for example: (1) one or more particular IP addresses; (2) one or more particular domains; (3) one or more particular countries; (4) one or more particular institutions; (5) one or more particular geographic regions; (6) etc. In various embodiments, in response to analyzing the sources of the requests, the system may identify one or more sources that may be malicious (e.g., are submitting excessive requests).

In various embodiments, the system is configured to maintain a database of the identified one or more sources (e.g., in computer memory). In particular embodiments, the database may store a listing of identities, data sources, etc. that have been blacklisted (e.g., by the system). In particular embodiments, the system is configured to, in response to receiving a new DSAR, cross reference the request with the blacklist to determine if the requestor is on the blacklist or is making the request from a blacklisted source. The system may then, in response to determining that the requestor or source is blacklisted, substantially automatically reject the request. In particular embodiments, the blacklist cross-referencing step may be part of the requestor authentication (e.g., verification) discussed above. In various embodiments, the system may be configured to analyze request data on a company by company basis to generate a blacklist. In other embodiments, the system may analyze global data (e.g., all data collected for a plurality of companies that utilize the data subject access request processing and fulfillment system) to generate the blacklist.

In particular embodiments, the system may be configured to fulfill DSARs for the purpose of providing a data subject with information regarding what data the company collects and for what purpose, for example, so the data subject can ensure that the company is collecting data for lawful reasons. As such, the system may be configured to identify requestors and other sources of data requests that are made for other reasons (e.g., one or more reasons that would not obligate the company to respond to the request). These reasons may include, for example, malicious or other reasons such as: (1) research by an academic institution by one or more students or professors; (2) anticompetitive requests by one or more competitors; (3) requests by disgruntled former employees for nefarious reasons; (4) etc.

In particular embodiments, the system may, for example, maintain a database (e.g., in computer memory) of former employees. In other embodiments, the system may, for example: (1) identify a plurality of IP addresses associated with a particular entity (e.g., academic organization, competitor, etc.); and (2) substantially automatically reject a DSAR that originates from the plurality of IP addresses. In such embodiments, the system may be configured to automatically add such identified IP addresses and/or domains to the blacklist.

In still other embodiments, the system is configured to maintain a listing of blacklisted names of particular individuals. These may include, for example, one or more individuals identified (e.g., by an organization or other entity) as submitting malicious DSARs.

FIG. 47 depicts a queue of pending DSARs. As shown in this figure, the first three listed DSARs are new and require verification before processing and fulfillment can begin. As shown in this figure, a user (e.g., such as a privacy officer or other privacy controller) may select a particular request, and select an indicia for verifying the request. The user may also optionally select to reject the request. FIG. 48 depicts an authentication window that enables the user to authenticate a particular request. In various embodiments, the user may provide an explanation of why the user is authenticating the request (e.g., because the requestor successfully completed one or more out-of-wallet questions or for any other suitable reason). The user may further submit one or more attachments to support the verification. In this way, the system may be configured to document that the authentication process was performed for each request (e.g., in case there was an issue with improperly fulfilling a request, the company can show that they are following procedures to prevent such improper processing). In other embodiments, the system may enable the user to provide similar support when rejecting a request (e.g., because the requestor is blacklisted, makes excessive requests, etc.).

Data Subject Access Request Fulfillment Cost Determination

In various embodiments, as may be understood in light of this disclosure, fulfilling a DSAR may be particularly costly. In some embodiments, a company may store data regarding a particular data subject in multiple different locations for a plurality of different reasons as part of a plurality of different processing and other business activities. For example, a particular data subject may be both a customer and an employee of a particular company or organization. Accordingly, in some embodiments, fulfilling a DSAR for a particular data subject may involve a plurality of different information technology (IT) professionals in a plurality of different departments of a particular company or organization. As such, it may be useful to determine a cost of a particular DSAR (e.g., particularly because, in some cases, a data subject is entitled to a response to their DSAR as a matter of right at no charge).

In particular embodiments, in response to receiving a DSAR, the system may be configured to: (1) assign the request to at least one privacy team member; (2) identify one or more IT teams required to fulfill the request (e.g., one or more IT teams associated with one or more business units that may store personal data related to the request); (3) delegate one or more subtasks of the request to each of the one or more IT teams; (4) receive one or more time logs from each individual involved in the processing and fulfillment of the DSAR; (5) calculate an effective rate of each individual's time (e.g., based at least in part on the individual's salary, bonus, benefits, chair cost, etc.); (6) calculate an effective cost of fulfilling the DSAR based at least in part on the one or more time logs and the effective rate of each of the individual's time; and (7) apply an adjustment to the calculated effective cost that accounts for one or more external factors (e.g., overhead, etc.) in order to calculate a cost of fulfilling the DSAR.

In particular embodiments, the system is configured to substantially automatically track an amount of time spent by each individual involved in the processing and fulfillment of the DSAR. The system may, for example, automatically track an amount of time between each individual opening and closing a ticket assigned to them as part of their role in processing or fulfilling the DSAR. In other embodiments, the system may determine the time spent based on an amount of time provided by each respective individual (e.g., the individual may track their own time and submit it to the system).

In various embodiments, the system is configured to measure a cost of each particular DSAR received, and analyze one or more trends in costs of, for example: (1) DSARs over time; (2) related DSARs; (3) etc. For example, the system may be configured to track and analyze cost and time-to-process trends for one or more social groups, one or more political groups, one or more class action groups, etc. In particular embodiments, the system may be configured to identify a particular group from which the system receives particularly costly DSARs (e.g., former and/or current employees, members of a particular social group, members of a particular political group, etc.).

In particular embodiments, the system may be configured to utilize DSAR cost data when processing, assigning, and/or fulfilling future DSARs (e.g., from a particular identified group, individual, etc.). For example, the system may be configured to prioritize requests that are expected to be less costly and time-consuming (e.g., based on past cost data) over requests identified as being likely more expensive. Alternatively, the system may prioritize more costly and time-consuming requests over less costly ones in the interest of ensuring that the system is able to respond to each request in a reasonable amount of time (e.g., within a time required by law, such as a thirty day period, or any other suitable time period).

Customer Satisfaction Integration with Data Subject Access Requests

In various embodiments, the system may be configured to collect customer satisfaction data, for example: (1) as part of a DSAR submission form; (2) when providing one or more results of a DSAR to the data subject; or (3) at any other suitable time. In various embodiments, the customer satisfaction data may be collected in the form of a suitable survey, free-form response questionnaire, or other suitable satisfaction data collection format (e.g., thumbs up vs. thumbs down, etc.).

FIG. 49 depicts an exemplary customer satisfaction survey that may be included as part of a DSAR submission form, provided along with the results of a DSAR, provided in one or more messages confirming receipt of a DSAR, etc. As shown in the figure, the customer satisfaction survey may relate to how likely a customer (e.g., a data subject) is to recommend the company (e.g., to which the data subject has submitted the request) to a friend (e.g., or colleague). In the example shown in FIG. 49, the satisfaction survey may relate to a Net Promoter score (NPS), which may indicate a loyalty of a company's customer relationships. Generally speaking, the Net Promoter Score may measure a loyalty that exists between a provider and a consumer. In various embodiments, the provider may include a company, employer, or any other entity. In particular embodiments, the consumer may include a customer, employee, or other respondent to an NPS survey.

In particular embodiments, the question depicted in FIG. 49 is the primary question utilized in calculating a Net Promoter Score (e.g., “how likely is it that you would recommend our company/product/service to a friend or colleague?”). In particular embodiments, the question is presented with responses ranging from 0 (not at all likely) to 10 (extremely likely). In particular embodiments, the question may include any other suitable scale. As may be understood from FIG. 49, the system may be configured to assign particular categories to particular ratings on the 10 point scale. The system may be configured to track and store responses provided by consumers and calculate an overall NPS score for the provider. The system may be further configured to generate a visual representation of the NPS score, including a total number of responses received for each particular score and category as shown in FIG. 49.

In various embodiments, the system may be configured to measure data related to any other suitable customer satisfaction method (e.g., in addition to NPS). By integrating a customer satisfaction survey with the DSAR process, the system may increase a number of consumers that provide one or more responses to the customer satisfaction survey. In particular embodiments, the system is configured to require the requestor to respond to the customer satisfaction survey prior to submitting the DSAR.

CONCLUSION

Although embodiments above are described in reference to various data subject access fulfillment systems, it should be understood that various aspects of the system described above may be applicable to other privacy-related systems, or to other types of systems, in general.

While this specification contains many specific embodiment details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. In addition, it should be understood that terms such as “in some embodiments”, “in various embodiments”, and “in certain embodiments” are intended to indicate that the stated features may be implemented in any suitable embodiment described herein.

Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for the purposes of limitation.

Number	Date	Country
62961054	Jan 2020	US
62360123	Jul 2016	US
62353802	Jun 2016	US
62348695	Jun 2016	US
62541613	Aug 2017	US
62537839	Jul 2017	US
62547530	Aug 2017	US

	Number	Date	Country
Parent	17383889	Jul 2021	US
Child	17710653		US

	Number	Date	Country
Parent	17710653	Mar 2022	US
Child	17837393		US
Parent	17149380	Jan 2021	US
Child	17383889		US
Parent	16410336	May 2019	US
Child	17149380		US
Parent	16055083	Aug 2018	US
Child	16410336		US
Parent	15996208	Jun 2018	US
Child	16055083		US
Parent	15853674	Dec 2017	US
Child	15996208		US
Parent	15619455	Jun 2017	US
Child	15853674		US
Parent	15254901	Sep 2016	US
Child	15619455		US

DATA PROCESSING SYSTEMS FOR FULFILLING DATA SUBJECT ACCESS REQUESTS AND RELATED METHODS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS REFERENCE TO RELATED APPLICATIONS

Provisional Applications (7)

Continuations (1)

Continuation in Parts (8)