US20230015047A1

US20230015047A1 - Data processing systems and methods for automatic discovery and assessment of mobile software development kits

Info

Publication number: US20230015047A1
Application number: US17/948,036
Authority: US
Inventors: Kevin Jones; Pratik Doshi; Jonathan Blake Brannon; Prabhu Kumar
Original assignee: OneTrust LLC
Current assignee: OneTrust LLC
Priority date: 2016-06-10
Filing date: 2022-09-19
Publication date: 2023-01-19
Also published as: US20220129581A1; US20210279363A1; US11222139B2; US11449633B2

Abstract

A mobile application privacy analysis system is described, where the system scans a mobile device to identify files associated with a particular SDK and generates a tokenized name for the SDK. The tokenized name includes tokens representing the SDK vendor and one or more functions of the SDK. Using the tokenized name, the system then determines corresponding categories for each functionality token and score for each such category. Based on the scores, the system determines the most significant category and assigns that category to the SDK for use in privacy analysis. The system may also, or instead, determine a vendor category using the vendor token and assign that category to the SDK. Weighting factors may be applied to the scores for the categories associated with the functionality tokens and vendor tokens.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/572,298, filed Jan. 10 2022, which is a continuation of U.S. patent application Ser. No. 17/326,901, filed May 21, 2021, now U.S. Pat. No. 11,222,139, issued Jan. 11, 2022, which claims priority from U.S. Provisional Patent Application Ser. No. 63/028,149, filed May 21, 2020, and is also a continuation-in-part of U.S. patent application Ser. No. 17/163,701, filed Feb. 1, 2021, now U.S. Pat. No. 11,113,416, issued Sep. 7, 2021, which is a continuation of U.S. patent application Ser. No. 16/915,097, filed Jun. 29, 2020, now U.S. Pat. No. 10,909,265, issued Feb. 2, 2021, which claims priority from U.S. Provisional Patent Application Ser. No. 62/868,373, filed Jun. 28, 2019, and is also a continuation-in-part of U.S. patent application Ser. No. 16/895,278, filed Jun. 8, 2020, now U.S. Pat. No. 11,200,341, issued Dec. 14, 2021, which is a continuation of U.S. patent application Ser. No. 16/552,765, filed Aug. 27, 2019, now U.S. Pat. No. 10,678,945, issued Jun. 9, 2020, which is a continuation-in-part of U.S. patent application Ser. No. 16/277,568, filed Feb. 15, 2019, now U.S. Pat. No. 10,440,062, issued Oct. 8, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/631,684, filed Feb. 17, 2018 and U.S. Provisional Patent Application Ser. No. 62/631,703, filed Feb. 17, 2018, and is also a continuation-in-part of U.S. patent application Ser. No. 16/159,634, filed Oct. 13, 2018, now U.S. Pat. No. 10,282,692, issued May 7, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/572,096, filed Oct. 13, 2017 and U.S. Provisional Patent Application Ser. No. 62/728,435, filed Sep. 7, 2018, and is also a continuation-in-part of U.S. patent application Ser. No. 16/055,083, filed Aug. 4, 2018, now U.S. Pat. No. 10,289,870, issued May 14, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/547,530, filed Aug. 18, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/996,208, filed Jun. 1, 2018, now U.S. Pat. No. 10,181,051, issued Jan. 15, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/537,839, filed Jul. 27, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/853,674, filed Dec. 22, 2017, now U.S. Pat. No. 10,019,597, issued Jul. 10, 2018, which claims priority from U.S. Provisional Patent Application Ser. No. 62/541,613, filed Aug. 4, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/619,455, filed Jun. 10, 2017, now U.S. Pat. No. 9,851,966, issued Dec. 26, 2017, which is a continuation-in-part of U.S. patent application Ser. No. 15/254,901, filed Sep. 1, 2016, now U.S. Pat. No. 9,729,583, issued Aug. 8, 2017, which claims priority from: (1) U.S. Provisional Patent Application Ser. No. 62/360,123, filed Jul. 8, 2016; (2) U.S. Provisional Patent Application Ser. No. 62/353,802, filed Jun. 23, 2016; (3) U.S. Provisional Patent Application Ser. No. 62/348,695, filed Jun. 10, 2016. The disclosures of all of the above patents and patent applications are hereby incorporated herein by reference in their entirety.

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, Internet browsing habits and history, purchase history, geolocation data, biometric data (e.g., fingerprint data, facial recognition data), user preferences, user activity on websites and/or social media (e.g., postings, likes and dislikes, social media data), and any other data that may be associated with and/or can be used to identify a particular user.
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 industry requirements. However, there is an increasing need for improved systems and methods to manage personal data in a manner that complies with such policies.
Applications configured on user devices, like smartphones, can present privacy issues. Such applications may obtain, use, and/or transfer personal data, including sensitive personal data, both knowingly and unknowingly to users of such devices and applications.
Developers and providers of applications (e.g., application vendors) may use software development kits (SDKs) to develop mobile applications. An SDK may include privacy-related functions and attributes and may install and/or use files that may be scattered throughout a mobile device's file system. Moreover, application developers and providers may be reluctant to be transparent about the particular SDKs used in the generation of an application. Due to the large number of files likely to be configured on a typical mobile device and the difficulty in identifying a particular application or development kit associated with each file, it can be challenging to determine that a particular SDK was used to generate a particular application configured on the mobile device. Additionally, scanning software (e.g., software tools used to analyze privacy impacts of software programs) may inaccurately assess the degree to which a software program transmits or otherwise processes such sensitive information when the identity of the SDK used to build the program is inaccessible to the scanning software.
Because there is an increasing need to manage the privacy impact of applications configured on user devices, there is also an increasing need to understand the privacy implications of the development tools used to generate such applications, with or without the cooperation of application developers and providers.

SUMMARY

In general, various aspects provide methods, apparatuses, systems, computing devices, computing entities, and/or the like for soliciting consent for various functionality provided through third-party SDKs found in mobile software applications and take action to block functionality when consent has not been provided. In accordance with one aspect, a method is provided that comprises: scanning, by computing hardware, at least one of a folder on a mobile device or a file stored on the mobile device to determine identifying information for a third-party development tool; (2) generating, by the computing hardware, a functionality token for the third-party development tool by: (A) querying, based on the identifying information for the third-party development tool, a database that stores a plurality of third-party identities in correlation with a plurality of respective identifying information of third-party development tools, (B) determining, based on a result of querying the database, a third-party identity corresponding to the third-party development tool, and (C) generating the functionality token based on the third-party identity; (3) determining, by the computing hardware, a functionality category for the functionality token; (4) assigning, by the computing hardware, a third-party development tool category to the third-party development tool based on the functionality category; and (5) linking, by the computing hardware, the third-party development tool category to the third-party development tool.
In some aspects, the method further comprises generating, by the computing hardware, a tokenized name for the third-party development tool using natural language processing on at least one of a filename for the file stored on the mobile device or content in the file stored on the mobile device; and the identifying information for the third-party development tool comprises the tokenized name. In other aspects, the method further comprises determining, by the computing hardware, based on the identifying information, a source of the third-party development tool, and assigning, by the computing hardware, the third-party development tool category based on the source. In some aspects the tokenized name comprises a source token, and the method comprises determining the source of the third-party development tool based on the source token.
In some aspects, scanning the at least one of the folder on the mobile device or the file stored on the mobile device comprises performing a filename search on the mobile device to determine the identifying information for the third-party development tool. In particular aspects, the functionality token comprise a first functionality token representing a first functionality type of the third-party development tool and a second functionality token representing a second functionality type of the third-party development tool. In some aspects, assigning, by the computing hardware, the third-party development tool category to the third-party development tool based on the functionality category comprises assigning the third-party development tool category based on a relative relevance weighting of the first functionality token and the second functionality token. In various aspects, the third-party development tool is a software development kit used to generate an application, the application being configured to operate on the mobile device.
In accordance with other aspects, a system is provided that comprises a non-transitory computer-readable medium storing instructions and a processing device communicatively coupled to the non-transitory computer-readable medium. The processing is configured to execute the instructions and thereby perform operations comprising : (1) scanning at least one of a folder on a mobile device or a file stored on the mobile device to determine identifying information for a third-party development tool; (2) generating a source token for the third-party development tool by: (A) querying, based on the identifying information for the third-party development tool, a database that stores a plurality of third-party identities in correlation with a plurality of respective identifying information of third-party development tools, (B) determining, based on a result of querying the database, a third-party identity corresponding to the third-party development tool, and (C) generating the source token based on the third-party identity; (3) identifying a third-party computing system from the source token; (4) assigning a third-party development tool category to the third-party development tool based on the third-party computing system; and (5) linking the third-party development tool category to the third-party development tool.
In some aspects, the operations further comprise generating a tokenized name for the third-party development tool using natural language processing on at least one of a filename for the file stored on the mobile device or content in the file stored on the mobile device. In other aspects, the identifying information for the third-party development tool comprises the tokenized name. In some aspects, the tokenized name comprises a first function token, and the operations further comprise assigning the third-party development tool category based on the first functionality token. In various aspects, the tokenized name comprises a second function token, and the operations further comprise assigning the third-party development tool category based on the first functionality token and the second functionality token. In a particular aspect, scanning the at least one of a folder on the mobile device or the file stored on the mobile device comprises determining the identifying information for the third-party development tool based on at least one of a package name, a file name, or a folder name. In particular aspects, the third-party development tool is a software development kit used to generate an application. In still other aspects, the third-party development tool category includes at least one of a targeting category, a functional category, or a location category.
In addition, in accordance with other aspects, a non-transitory computer-readable medium having program code that is stored thereon is provided. The program code is executable by one or more processing devices for performing operations comprising: (1) scanning at least one of a folder on a mobile device or a file stored on the mobile device to determine identifying information for a third-party development tool; (2) generating a tokenized name for the third-party development tool based on the identifying information, the tokenized name comprising a functionality token representing a function of the third-party development tool; (3) assigning a third-party development tool category to the third-party development tool based on the functionality token; and (4) linking the assigned third-party development tool category to the third-party development tool.
In some aspects, generating the tokenized name for the third-party development tool comprises using natural language processing on at least one of a filename for the file stored on the mobile device or content in the file stored on the mobile device. In such aspects, the identifying information for the third-party development tool may comprise the tokenized name. In any aspect described herein, scanning the at least one of the folder on the mobile device or the file stored on the mobile device comprises performing a filename search on the. mobile device to determine the identifying information for the third-party development tool.
In some aspects, the functionality token is a first functionality token, the tokenized name comprises a second functionality token, and the operations further comprise assigning the third-party development tool category based on the first functionality token but not on the second functionality token. In still other aspects, the functionality token comprise a first functionality token representing a first functionality type of the third-party development tool and a second functionality token representing a second functionality type of the third-party development tool, and assigning the third-party development tool category to the third-party development tool based on the functionality category comprises assigning the third-party development tool category based on a relative relevance weighting of the first functionality token and the second functionality token. In a particular aspect, the third-party development tool is a software development kit used to generate an application, the application being configured to operate on the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a data subject access request 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 model generation and population system according to particular embodiments.

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

FIG. 3 is a flowchart showing an example of steps performed by a Data Model Generation

Module according to particular embodiments.

FIGS. 4-10 depict various exemplary visual representations of data models according to particular embodiments.

FIG. 11 is a flowchart showing an example of steps performed by a Data Model Population Module.

FIG. 12 is a flowchart showing an example of steps performed by a Data Population Questionaire Generation Module.

FIG. 13 is a process flow for populating a data inventory according to a particular embodiment using one or more data mapping techniques.

FIGS. 14-25 depict exemplary screen displays and graphical user interfaces (GUIs) according to various embodiments of the system, which may display information associated with the system or enable access to, or interaction with, the system by one or more users (e.g., to configure a questionnaire for populating one or more inventory attributes for one or more data models, complete one or more assessments, etc.).

FIG. 26 is a flowchart showing an example of steps performed by an Intelligent Identity Scanning Module.

FIG. 27 is schematic diagram of network architecture for an intelligent identity scanning system 2700 according to a particular embodiment.

FIG. 28 is a schematic diagram of an asset access methodology utilized by an intelligent identity scanning system 2700 in various embodiments of the system.

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

FIGS. 30-31 depict exemplary screen displays and graphical user interfaces (GUIs) according to various embodiments of the system, which may display information associated with the system or enable access to, or interaction with, the system by one or more users (e.g., for the purpose of submitting a data subject access request or other suitable request).

FIGS. 32-35 depict exemplary screen displays and graphical user interfaces (GUIs) according to various embodiments of the system, which may display information associated with the system or enable access to, or interaction with, the system by one or more users (e.g., for the purpose of flagging one or more risks associated with one or more particular questionnaire questions).

FIG. 36 depicts a schematic diagram of a centralized data repository system according to particular embodiments of the present system.

FIG. 37 is a centralized data repository module according to various embodiments, which may, for example, be executed by the centralized data repository system of FIG. 36 .

FIG. 38 depicts a schematic diagram of a consent receipt management system according to particular embodiments.

FIGS. 39-54 are computer screen shots that demonstrate the operation of various embodiments.

FIG. 55 depicts a schematic diagram of an application privacy analysis system according to particular embodiments of the present system.

FIG. 56 depicts a schematic diagram of an application privacy analysis system according to particular embodiments of the present system.

FIG. 57 depicts a schematic diagram of a static application privacy analysis system according to particular embodiments of the present system.

FIG. 58 depicts a schematic diagram of a dynamic application privacy analysis system according to particular embodiments of the present system.

FIG. 59 is a flowchart showing an example of a process performed by a Privacy Analysis Module according to various embodiments.

FIG. 60 depicts a schematic diagram of an SDK discovery and assessment system according to various embodiments.

FIG. 61 is a flowchart showing an example of a process performed by a Mobile SDK Package Assessment 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

A data model generation and population system, according to particular embodiments, is configured to generate a data model (e.g., one or more data models) that maps one or more relationships between and/or among a plurality of data assets utilized by a corporation or other entity (e.g., individual, organization, etc.) in the context, for example, of one or more business processes. In particular embodiments, each of the plurality of data assets (e.g., data systems) may include, for example, any entity that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, web site, data-center, server, etc.). For example, a first data asset may include any software or device (e.g., server or servers) utilized by a particular entity for such data collection, processing, transfer, storage, etc.
As shown in FIGS. 4 and 5 , in various embodiments, the data model may store the following information: (1) the organization that owns and/or uses a particular data asset (a primary data asset, which is shown in the center of the data model in FIG. 4 ); (2) one or more departments within the organization that are responsible for the data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the data asset (e.g., or one or more other suitable collection assets from which the personal data that is collected, processed, stored, etc. by the primary data asset is sourced); (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to for other use, and which particular data is transferred to each of those data assets. As shown in FIGS. 6 and 7 , the system may also optionally store information regarding, for example, which business processes and processing activities utilize the data asset.
In particular embodiments, the data model stores this information for each of a plurality of different data assets and may include links between, for example, a portion of the model that provides information for a first particular data asset and a second portion of the model that provides information for a second particular data asset.
In various embodiments, the data model generation and population system may be implemented in the context of any suitable privacy management system that is configured to ensure compliance with one or more legal or industry standards related to the collection and/or storage of private information. In various embodiments, a particular organization, sub-group, or other entity may initiate a privacy campaign or other activity (e.g., processing activity) as part of its business activities. In such embodiments, the privacy campaign may include any undertaking by a particular organization (e.g., such as a project or other activity) that includes the collection, entry, and/or storage (e.g., in memory) of any personal data associated with one or more individuals. In particular embodiments, a privacy campaign may include any project undertaken by an organization that includes the use of personal data, or any other activity that could have an impact on the privacy of one or more individuals.
In any embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein. In particular embodiments, such personal data may include one or more cookies (e.g., where the individual is directly identifiable or may be identifiable based at least in part on information stored in the one or more cookies).
In particular embodiments, when generating a data model, the system may, for example: (1) identify one or more data assets associated with a particular organization; (2) generate a data inventory for each of the one or more data assets, where the data inventory comprises information such as: (a) one or more processing activities associated with each of the one or more data assets, (b) transfer data associated with each of the one or more data assets (data regarding which data is transferred to/from each of the data assets, and which data assets, or individuals, the data is received from and/or transferred to, (c) personal data associated with each of the one or more data assets (e.g., particular types of data collected, stored, processed, etc. by the one or more data assets), and/or (d) any other suitable information; and (3) populate the data model using one or more suitable techniques.
In particular embodiments, the one or more techniques for populating the data model may include, for example: (1) obtaining information for the data model by using one or more questionnaires associated with a particular privacy campaign, processing activity, etc.; (2) using one or more intelligent identity scanning techniques discussed herein to identify personal data stored by the system and map such data to a suitable data model, data asset within a data model, etc.; (3) obtaining information for the data model from a third-party application (or other application) using one or more application programming interfaces (API); and/or (4) using any other suitable technique.
In particular embodiments, the system is configured to generate and populate a data model substantially on the fly (e.g., as the system receives new data associated with particular processing activities). In still other embodiments, the system is configured to generate and populate a data model based at least in part on existing information stored by the system (e.g., in one or more data assets), for example, using one or more suitable scanning techniques described herein.
As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store personal data in a plurality of different locations which may include one or more known and/or unknown locations. By generating and populating a data model of one or more data assets that are involved in the collection, storage and processing of such personal data, the system may be configured to create a data model that facilitates a straightforward retrieval of information stored by the organization as desired. For example, in various embodiments, the system may be configured to use a data model in substantially automatically responding to one or more data access requests by an individual (e.g., or other organization). Various embodiments of a system for generating and populating a data model are described more fully below.
To ensure compliance with privacy regulations and/or standards, entities may determine the privacy and security impact of data and software installed on computing devices that such entities may control or interact with. Examples of such data and software may include cookies that may contain personal data and applications that may track a user's activity (“trackers”). In various embodiments, the disclosed systems may assess (e.g., score, categorize, etc.) such data and applications based on various privacy-related criteria and/or security-related criteria. In particular embodiments, the system may apply such assessment techniques to mobile devices and the data and software installed thereon.
In various embodiments, the system may identify one or more software development kits (SDKs) configured on a mobile device and/or used to generate an application configured on the mobile device. Using natural language processing (NLP) artificial intelligence techniques, the system may generate a tokenized name for the SDK that includes tokens representing the vendor of the SDK and various functions performed by applications generated using the SDK. The system may determine scores for one or more such tokens and determine a privacy category or score for the SDK based on the token scores. The security and privacy impact of the particular identified SDK may be assessed based, at least in part, on one or more privacy and security impact determinations (e.g., scores, categorization, etc.) associated with the SDK and/or the SDK vendor.

Technical Contributions of Various Embodiments

With the proliferation of mobile devices, the number of privacy-implicated activities performed on mobile devices and/or by software configured on mobile devices continues to grow. Therefore, determining the privacy implications of applications and other software executing on mobile devices is increasingly important. However, mobile device applications are often generated using software development kits (SDKs) that may install and/or use files that may be scattered throughout a mobile device's file system. As there are likely to be thousands of files (or more) configured on a typical mobile device, it can be very challenging to locate and identify files associated with a particular SDK or make a determination that a particular SDK was used to generate a particular application configured on the mobile device based on the filed installed on the device.
Accordingly, various embodiments of present disclosure overcome many of the technical challenges associated with determining particular SDKs used to generate applications configured on a mobile device. Specifically, various embodiments of the disclosure are directed to a computational framework configured for analyzing the many files (e.g., distributed across many folders within a file system) that may be configured on a mobile device and determining whether such files are associated with valid SDKs. The various embodiments may then tokenize the file names of identified SDKs to generate data structures representing various aspects of the identified SDKs. The system can evaluate these data structures (the tokenized SDK package names and/or one or more portions thereof) to determine a privacy category, privacy-related score, and/or a privacy assessment information for the package. For example, the various embodiments evaluate individual tokens of a package's tokenized name, determine a score for one or more of the tokens (including, in various embodiments, weighting such scores), and determine a category and/or score for the associated SDK based on the token scores. In this way, the various embodiments spare users from the time-consuming operations of manually searching folders and files on a mobile to device to identify files, determining whether an SDK is associated with each identified file, determining a function of an SDK that may be represented by a particular file if it is associated with an SDK, and determining the privacy-related implications (e.g., most relevant privacy category or a privacy-related score) of the SDK based on various functions of the SDK indicated by files that have been identified as being associated with the SDK. The various embodiments thus increase the efficiency with which users can evaluate the privacy impact of SDKs used to generate mobile device applications.
Accordingly, various embodiments of the disclosure provided herein are more effective, efficient, timely, accurate, and faster in determining a mobile device application's privacy implications and those of an SDK used to generate the application. In addition, various embodiments of the disclosure provided herein can facilitate the identification and/or documentation of (e.g., automated) processes and activities performed by an application that may be related to privacy and security. The system may use the determination of the privacy implications of a mobile device application and/or its associated SDK to determine an entity's compliance (and/or efforts to comply) with numerous regulations and requirements. Various embodiments of the disclosure can execute data processing related to determining the privacy implications of a mobile device application and/or its associated SDK that cannot be feasibly performed by a human, for example, by using such data processing to analyze the many files configured throughout the file system of a mobile device to identify a package and generate a tokenized package name which can then be used to calculate a privacy score and/or determine a suitable privacy category based on values determined for the tokens in a tokenized package name. This is especially advantageous when this data processing must be carried out over a reasonable timeframe to ensure that the privacy implications of a mobile device application and/or its associated SDK can be understood in a timely fashion. By facilitating such data processing, the various embodiments of the present disclosure improve the computational efficiency and reliability of various automated systems and procedures for determining the privacy implications of a mobile device application and/or its associated SDK, and therefore an extent of compliance with one or more particular regulations and/or requirements and/or extents of compliance between multiple regulations and/or requirements based on such privacy implications. 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, various embodiments 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 Model Generation and Population System 100 according to a particular embodiment. In various embodiments, the Data Model Generation and Population 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 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. In some embodiments, the Data Model Generation and Population System 100 is configured to: (1) generate a data model based on one or more identified data assets, where the data model includes a data inventory associated with each of the one or more identified data assets; (2) identify populated and unpopulated aspects of each data inventory; and (3) populate the unpopulated aspects of each data inventory using one or more techniques such as intelligent identity scanning, questionnaire response mapping, APIs, etc.
As may be understood from FIG. 1 , the Data Model Generation and Population 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, 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.), and One or More Third Party Servers 160. 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.), and One or More Third Party Servers 160. 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 are shown as separate servers, it should be understood that in other embodiments, one or more of these servers and/or computing devices may comprise a single server, a plurality of servers, one or more cloud-based servers, or any other suitable configuration.
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. The communication link between The Intelligent Identity Scanning Server 130 and the One or More Third Party Servers 160 may be, for example, 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. 2 illustrates a diagrammatic representation of a computer 200 that can be used within the Data Model Generation and Population System 100, for example, as a client computer (e.g., one or more remote computing devices 130 shown in FIG. 1 ), or as a server computer (e.g., Data Model Generation Server 110 shown in FIG. 1 ). In particular embodiments, the computer 200 may be suitable for use as a computer within the context of the Data Model Generation and Population System 100 that is configured to generate a data model and map one or more relationships between one or more pieces of data that make up the model.
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, 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 120 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 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 term “computer-accessible storage medium” 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 disclosed embodiments. The term “computer-accessible storage medium” should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc.

Exemplary System Platform

Various embodiments of a Data Model Generation and Population System 100 may be implemented in the context of any suitable system (e.g., a privacy compliance system). For example, the Data Model Generation and Population System 100 may be implemented to analyze a particular company or other organization's data assets to generate a data model for one or more processing activities, privacy campaigns, etc. undertaken by the organization. In particular embodiments, the system may implement one or more modules in order to at least partially ensure compliance with one or more regulations (e.g., legal requirements) related to the collection and/or storage of personal data. Various aspects of the system's functionality may be executed by certain system modules, including a Data Model Generation Module 300, Data Model Population Module 1100, Data Population Questionnaire Generation Module 1200, Intelligent Identity Scanning Module 2600, and Data Subject Access Request Fulfillment Module 2900. These modules are discussed in greater detail below.
Although these modules are presented as a series of steps, it should be understood in light of this disclosure that various embodiments of the Data Model Generation Module 300, Data Model Population Module 1100, Data Population Questionnaire Generation Module 1200, Intelligent Identity Scanning Module 2600, and Data Subject Access Request Fulfillment Module 2900 described herein may perform the steps described below in an order other than in which they are presented. In still other embodiments, the Data Model Generation Module 300, Data Model Population Module 1100, Data Population Questionnaire Generation Module 1200, Intelligent Identity Scanning Module 2600, and Data Subject Access Request Fulfillment Module 2900 may omit certain steps described below. In various other embodiments, the Data Model Generation Module 300, Data Model Population Module 1100, Data Population Questionnaire Generation Module 1200, Intelligent Identity Scanning Module 2600, and Data Subject Access Request Fulfillment Module 2900 may perform steps in addition to those described (e.g., such as one or more steps described with respect to one or more other modules, etc.).

Data Model Generation Module

In particular embodiments, a Data Model Generation Module 300 is configured to: (1) generate a data model (e.g., a data inventory) for one or more data assets utilized by a particular organization; (2) generate a respective data inventory for each of the one or more data assets; and (3) map one or more relationships between one or more aspects of the data inventory, the one or more data assets, etc. within the data model. In particular embodiments, a data asset (e.g., data system, software application, etc.) may include, for example, any entity that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, website, data-center, server, etc.). For example, a first data asset may include any software or device (e.g., server or servers) utilized by a particular entity for such data collection, processing, transfer, storage, etc.
In particular embodiments, a particular data asset, or collection of data assets, may be utilized as part of a particular data processing activity (e.g., direct deposit generation for payroll purposes). In various embodiments, a data model generation system may, on behalf of a particular organization (e.g., entity), generate a data model that encompasses a plurality of processing activities. In other embodiments, the system may be configured to generate a discrete data model for each of a plurality of processing activities undertaken by an organization.
Turning to FIG. 3 , in particular embodiments, when executing the Data Model Generation Module 300, the system begins, at Step 310, by generating a data model for one or more data assets and digitally storing the data model in computer memory. The system may, for example, store the data model in the One or More Databases 140 described above (or any other suitable data structure). In various embodiments, generating the data model comprises generating a data structure that comprises information regarding one or more data assets, attributes and other elements that make up the data model. As may be understood in light of this disclosure, the one or more data assets may include any data assets that may be related to one another. In particular embodiments, the one or more data assets may be related by virtue of being associated with a particular entity (e.g., organization). For example, the one or more data assets may include one or more computer servers owned, operated, or utilized by the entity that at least temporarily store data sent, received, or otherwise processed by the particular entity.
In still other embodiments, the one or more data assets may comprise one or more third party assets which may, for example, send, receive and/or process personal data on behalf of the particular entity. These one or more data assets may include, for example, one or more software applications (e.g., such as EXPENSIFY to collect expense information, QUICKBOOKS to maintain and store salary information, etc.).
Continuing to step 320, the system is configured to identify a first data asset of the one or more data assets. In particular embodiments, the first data asset may include, for example, any entity (e.g., system) that collects, processes, contains, and/or transfers data (e.g., such as a software application, “interne of things” computerized device, database, website, data-center, server, etc.). For example, the first data asset may include any software or device utilized by a particular organization for such data collection, processing, transfer, etc. In various embodiments, the first data asset may be associated with a particular processing activity (e.g., the first data asset may make up at least a part of a data flow that relates to the collection, storage, transfer, access, use, etc. of a particular piece of data (e.g., personal data)). Information regarding the first data asset may clarify, for example, one or more relationships between and/or among one or more other data assets within a particular organization. In a particular example, the first data asset may include a software application provided by a third party (e.g., a third party vendor) with which the particular entity interfaces for the purpose of collecting, storing, or otherwise processing personal data (e.g., personal data regarding customers, employees, potential customers, etc.).
In particular embodiments, the first data asset is a storage asset that may, for example: (1) receive one or more pieces of personal data form one or more collection assets; (2) transfer one or more pieces of personal data to one or more transfer assets; and/or (3) provide access to one or more pieces of personal data to one or more authorized individuals (e.g., one or more employees, managers, or other authorized individuals within a particular entity or organization). In a particular embodiment, the first data asset is a primary data asset associated with a particular processing activity around which the system is configured to build a data model associated with the particular processing activity.
In particular embodiments, the system is configured to identify the first data asset by scanning a plurality of computer systems associated with a particular entity (e.g., owned, operated, utilized, etc. by the particular entity). In various embodiments, the system is configured to identify the first data asset from a plurality of data assets identified in response to completion, by one or more users, of one or more questionnaires.
Advancing to Step 330, the system generates a first data inventory of the first data asset. The data inventory may comprise, for example, one or more inventory attributes associated with the first data asset such as, for example: (1) one or more processing activities associated with the first data asset; (2) transfer data associated with the first data asset (e.g., how and where the data is being transferred to and/or from); (3) personal data associated with the first data asset (e.g., what type of personal data is collected and/or stored by the first data asset; how, and from where, the data is collected, etc.); (4) storage data associated with the personal data (e.g., whether the data is being stored, protected and deleted); and (5) any other suitable attribute related to the collection, use, and transfer of personal data. In other embodiments, the one or more inventory attributes may comprise one or more other pieces of information such as, for example: (1) the type of data being stored by the first data asset; (2) an amount of data stored by the first data asset; (3) whether the data is encrypted; (4) a location of the stored data (e.g., a physical location of one or more computer servers on which the data is stored); etc. In particular other embodiments, the one or more inventory attributes may comprise one or more pieces of information technology data related to the first data asset (e.g., such as one or more pieces of network and/or infrastructure information, IP address, MAC address, etc.).
In various embodiments, the system may generate the data inventory based at least in part on the type of first data asset. For example, particular types of data assets may have particular default inventory attributes. In such embodiments, the system is configured to generate the data inventory for the first data asset, which may, for example, include one or more placeholder fields to be populated by the system at a later time. In this way, the system may, for example, identify particular inventory attributes for a particular data asset for which information and/or population of data is required as the system builds the data model.
As may be understood in light of this disclosure, the system may, when generating the data inventory for the first data asset, generate one or more placeholder fields that may include, for example: (1) the organization (e.g., entity) that owns and/or uses the first data asset (a primary data asset, which is shown in the center of the data model in FIG. 4 ); (2) one or more departments within the organization that are responsible for the first data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the first data asset (e.g., or one or more other suitable collection assets from which the personal data that is collected, processed, stored, etc. by the first data asset is sourced); (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the first data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the first data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the first data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to from the first data asset, and which particular data is transferred to each of those data assets.
As may be understood in light of this disclosure, the system may be configured to generate the one or more placeholder fields based at least in part on, for example: (1) the type of the first data asset; (2) one or more third party vendors utilized by the particular organization; (3) a number of collection or storage assets typically associated with the type of the first data asset; and/or (4) any other suitable factor related to the first data asset, its one or more inventory attributes, etc. In other embodiments, the system may substantially automatically generate the one or more placeholders based at least in part on a hierarchy and/or organization of the entity for which the data model is being built. For example, a particular entity may have a marketing division, legal department, human resources department, engineering division, or other suitable combination of departments that make up an overall organization. Other particular entities may have further subdivisions within the organization. When generating the data inventory for the first data asset, the system may identify that the first data asset will have both an associated organization and subdivision within the organization to which it is assigned. In this example, the system may be configured to store an indication in computer memory that the first data asset is associated with an organization and a department within the organization.
Next, at Step 340, the system modifies the data model to include the first data inventory and electronically links the first data inventory to the first data asset within the data model. In various embodiments, modifying the data model may include configuring the data model to store the data inventory in computer memory, and to digitally associate the data inventory with the first data asset in memory.
FIGS. 4 and 5 show a data model according to a particular embodiment. As shown in these figures, the data model may store the following information for the first data asset: (1) the organization that owns and/or uses the first data asset; (2) one or more departments within the organization that are responsible for the first data asset; (3) one or more applications that collect data (e.g., personal data) for storage in and/or use by the first data asset; (4) one or more particular data subjects that information is collected from for use by the first data asset; (5) one or more collection assets from which the first asset receives data (e.g., personal data); (6) one or more particular types of data that are collected by each of the particular applications (e.g., collection assets) for storage in and/or use by the first data asset; (7) one or more individuals (e.g., particular individuals, types of individuals, or other parties) that are permitted to access and/or use the data stored in or used by the first data asset; (8) which particular types of data each of those individuals are allowed to access and use; and (9) one or more data assets (destination assets) the data is transferred to for other use, and which particular data is transferred to each of those data assets. As shown in FIGS. 6 and 7 , the system may also optionally store information regarding, for example, which business processes and processing activities utilize the first data asset.
As noted above, in particular embodiments, the data model stores this information for each of a plurality of different data assets and may include one or more links between, for example, a portion of the model that provides information for a first particular data asset and a second portion of the model that provides information for a second particular data asset.
Advancing to Step 350, the system next identifies a second data asset from the one or more data assets. In various embodiments, the second data asset may include one of the one or more inventory attributes associated with the first data asset (e.g., the second data asset may include a collection asset associated with the first data asset, a destination asset or transfer asset associated with the first data asset, etc.). In various embodiments, as may be understood in light of the exemplary data models described below, a second data asset may be a primary data asset for a second processing activity, while the first data asset is the primary data asset for a first processing activity. In such embodiments, the second data asset may be a destination asset for the first data asset as part of the first processing activity. The second data asset may then be associated with one or more second destination assets to which the second data asset transfers data. In this way, particular data assets that make up the data model may define one or more connections that the data model is configured to map and store in memory.
Returning to Step 360, the system is configured to identify one or more attributes associated with the second data asset, modify the data model to include the one or more attributes, and map the one or more attributes of the second data asset within the data model. The system may, for example, generate a second data inventory for the second data asset that comprises any suitable attribute described with respect to the first data asset above. The system may then modify the data model to include the one or more attributes and store the modified data model in memory. The system may further, in various embodiments, associate the first and second data assets in memory as part of the data model. In such embodiments, the system may be configured to electronically link the first data asset with the second data asset. In various embodiments, such association may indicate a relationship between the first and second data assets in the context of the overall data model (e.g., because the first data asset may serve as a collection asset for the second data asset, etc.).
Next, at Step 370, the system may be further configured to generate a visual representation of the data model. In particular embodiments, the visual representation of the data model comprises a data map. The visual representation may, for example, include the one or more data assets, one or more connections between the one or more data assets, the one or more inventory attributes, etc.
In particular embodiments, generating the visual representation (e.g., visual data map) of a particular data model (e.g., data inventory) may include, for example, generating a visual representation that includes: (1) a visual indication of a first data asset (e.g., a storage asset), a second data asset (e.g., a collection asset), and a third data asset (e.g., a transfer asset); (2) a visual indication of a flow of data (e.g., personal data) from the second data asset to the first data asset (e.g., from the collection asset to the storage asset); (3) a visual indication of a flow of data (e.g., personal data) from the first data asset to the third data asset (e.g., from the storage asset to the transfer asset); (4) one or more visual indications of a risk level associated with the transfer of personal data; and/or (5) any other suitable information related to the one or more data assets, the transfer of data between/among the one or more data assets, access to data stored or collected by the one or more data assets, etc.
In particular embodiments, the visual indication of a particular asset may comprise a box, symbol, shape, or other suitable visual indicator. In particular embodiments, the visual indication may comprise one or more labels (e.g., a name of each particular data asset, a type of the asset, etc.). In still other embodiments, the visual indication of a flow of data may comprise one or more arrows. In particular embodiments, the visual representation of the data model may comprise a data flow, flowchart, or other suitable visual representation.
In various embodiments, the system is configured to display (e.g., to a user) the generated visual representation of the data model on a suitable display device.

Exemplary Data Models and Visual Representations of Data Models (e.g., Data Maps)

FIGS. 4-10 depict exemplary data models according to various embodiments of the system described herein. FIG. 4 , for example, depicts an exemplary data model that does not include a particular processing activity (e.g., that is not associated with a particular processing activity). As may be understood from the data model shown in this figure, a particular data asset (e.g., a primary data asset) may be associated with a particular company (e.g., organization), or organization within a particular company, sub-organization of a particular organization, etc. In still other embodiments, the particular asset may be associated with one or more collection assets (e.g., one or more data subjects from whom personal data is collected for storage by the particular asset), one or more parties that have access to data stored by the particular asset, one or more transfer assets (e.g., one or more assets to which data stored by the particular asset may be transferred), etc.
As may be understood from FIG. 4 , a particular data model for a particular asset may include a plurality of data elements. When generating the data model for the particular asset, a system may be configured to substantially automatically identify one or more types of data elements for inclusion in the data model, and automatically generate a data model that includes those identified data elements (e.g., even if one or more of those data elements must remain unpopulated because the system may not initially have access to a value for the particular data element). In such cases, the system may be configured to store a placeholder for a particular data element until the system is able to populate the particular data element with accurate data.
As may be further understood from FIG. 4 , the data model shown in FIG. 4 may represent a portion of an overall data model. For example, in the embodiment shown in this figure, the transfer asset depicted may serve as a storage asset for another portion of the data model. In such embodiments, the transfer asset may be associated with a respective one or more of the types of data elements described above. In this way, the system may generate a data model that may build upon itself to comprise a plurality of layers as the system adds one or more new data assets, attributes, etc.
As may be further understood from FIG. 4 , a particular data model may indicate one or more parties that have access to and/or use of the primary asset (e.g., storage asset). In such embodiments, the system may be configured to enable the one or more parties to access one or more pieces of data (e.g., personal data) stored by the storage asset.
As shown in FIG. 4 , the data model may further comprise one or more collection assets (e.g., one or more data assets or individuals from which the storage asset receives data such as personal data). In the exemplary data model (e.g., visual data map) shown in this figure, the collection assets comprise a data subject (e.g., an individual that may provide data to the system for storage in the storage asset) and a collection asset (e.g., which may transfer one or more pieces of data that the collection asset has collected to the storage asset).
FIG. 5 depicts a portion of an exemplary data model that is populated for the primary data asset GUSTO. GUSTO is a software application that, in the example shown in FIG. 5 , may serve as a human resources service that contains financial, expense, review, time and attendance, background, and salary information for one or more employees of a particular organization (e.g., GeneriTech). In the example of FIG. 5 , the primary asset (e.g., GUSTO) may be utilized by the HR (e.g., Human Resources) department of the particular organization (e.g., GeneriTech). Furthermore, the primary asset, GUSTO, may collect financial information from one or more data subjects (e.g., employees of the particular organization), receive expense information transferred from Expensify (e.g., expensing software), and receive time and attendance data transferred from Kronos (e.g., timekeeping software). In the example shown in FIG. 5 , access to the information collected and/or stored by GUSTO may include, for example: (1) an ability to view and administer salary and background information by HR employees, and (2) an ability to view and administer employee review information by one or more service managers. In the example shown in this figure, personal and other data collected and stored by GUSTO (e.g., salary information, etc.) may be transferred to a company banking system, to QUICKBOOKS, and/or to an HR file cabinet.
As may be understood from the example shown in FIG. 5 , the system may be configured to generate a data model based around GUSTO that illustrates a flow of personal data utilized by GUSTO. The data model in this example illustrates, for example, a source of personal data collected, stored and/or processed by GUSTO, a destination of such data, an indication of who has access to such data within GUSTO, and an organization and department responsible for the information collected by GUSTO. In particular embodiments, the data model and accompanying visual representation (e.g., data map) generated by the system as described in any embodiment herein may be utilized in the context of compliance with one or more record keeping requirements related to the collection, storage, and processing of personal data.
FIGS. 6 and 7 depict an exemplary data model and related example that is similar, in some respects, to the data model and example of FIGS. 4 and 5 . In the example shown in FIGS. 6 and 7 , the exemplary data model and related example include a specific business process and processing activity that is associated with the primary asset (GUSTO). In this example, the business process is compensation and the specific processing activity is direct deposit generation in GUSTO. As may be understood from this figure, the collection and transfer of data related to the storage asset of GUSTO is based on a need to generate direct deposits through GUSTO in order to compensate employees. GUSTO generates the information needed to conduct a direct deposit (e.g., financial and salary information) and then transmits this information to: (1) a company bank system for execution of the direct deposit; (2) QUICKBOOKS for use in documenting the direct deposit payment; and (3) HR File cabinet for use in documenting the salary info and other financial information.
As may be understood in light of this disclosure, when generating such a data model, particular pieces of data (e.g., data attributes, data elements) may not be readily available to the system. In such embodiment, the system is configured to identify a particular type of data, create a placeholder for such data in memory, and seek out (e.g., scan for and populate) an appropriate piece of data to further populate the data model. For example, in particular embodiments, the system may identify GUSTO as a primary asset and recognize that GUSTO stores expense information. The system may then be configured to identify a source of the expense information (e.g., Expensify).
FIG. 8 depicts an exemplary screen display 800 that illustrates a visual representation (e.g., visual data map) of a data model (e.g., a data inventory). In the example shown in FIG. 8 , the data map provides a visual indication of a flow of data collected from particular data subjects (e.g., employees 801). As may be understood from this figure, the data map illustrates that three separate data assets receive data (e.g., which may include personal data) directly from the employees 801. In this example, these three data assets include Kronos 803 (e.g., a human resources software application), Workday 805 (e.g., a human resources software application), and ADP 807 (e.g., a human resources software application and payment processor). As shown in FIG. 8 , the transfer of data from the employees 801 to these assets is indicated by respective arrows.
As further illustrated in FIG. 8 , the data map indicates a transfer of data from Workday 805 to ADP 807 as well as to a Recovery Datacenter 809 and a London HR File Center 811. As may be understood in light of this disclosure, the Recovery Datacenter 809 and London HR File Center 811 may comprise additional data assets in the context of the data model illustrated by the data map shown in FIG. 8 . The Recover Datacenter 809 may include, for example, one or more computer servers (e.g., backup servers). The London HR File Center 811 may include, for example, one or more databases (e.g., such as the One or More Databases 140 shown in FIG. 1 ). AS shown in FIG. 8 , each particular data asset depicted in the data map may be shown along with a visual indication of the type of data asset. For example, Kronos 803, Workday 805, and ADP 807 are depicted adjacent a first icon type (e.g., a computer monitor), while Recover Datacenter 809 and London HR File Center 811 are depicted adjacent a second and third icon type respectively (e.g., a server cluster and a file folder). In this way, the system may be configured to visually indicate, via the data model, particular information related to the data model in a relatively minimal manner.
FIG. 9 depicts an exemplary screen display 900 that illustrates a data map of a plurality of assets 905 in tabular form (e.g., table form). As may be understood from this figure, a table that includes one or more inventory attributes of each particular asset 905 in the table may indicate, for example: (1) a managing organization 910 of each respective asset 905; (2) a hosting location 915 of each respective asset 905 (e.g., a physical storage location of each asset 905); (3) a type 920 of each respective asset 905, if known (e.g., a database, software application, server, etc.); (4) a processing activity 925 associated with each respective asset 905; and/or (5) a status 930 of each particular data asset 905. In various embodiments, the status 930 of each particular asset 905 may indicate a status of the asset 905 in the discovery process. This may include, for example: (1) a “new” status for a particular asset that has recently been discovered as an asset that processes, stores, or collects personal data on behalf of an organization (e.g., discovered via one or more suitable techniques described herein); (2) an “in discovery” status for a particular asset for which the system is populating or seeking to populate one or more inventory attributes, etc.
FIG. 10 depicts an exemplary data map 1000 that includes an asset map of a plurality of data assets 1005A-F, which may, for example, be utilized by a particular entity in the collection, storage, and/or processing of personal data. As may be understood in light of this disclosure, the plurality of data assets 1005A-F may have been discovered using any suitable technique described herein (e.g., one or more intelligent identity scanning techniques, one or more questionnaires, one or more application programming interfaces, etc.). In various embodiments, a data inventory for each of the plurality of data assets 1005A-F may define, for each of the plurality of data assets 1005A-F a respective inventory attribute related to a storage location of the data asset.
As may be understood from this figure, the system may be configured to generate a map that indicates a location of the plurality of data assets 1005A-F for a particular entity. In the embodiment shown in this figure, locations that contain a data asset are indicated by circular indicia that contain the number of assets present at that location. In the embodiment shown in this figure, the locations are broken down by country. In particular embodiments, the asset map may distinguish between internal assets (e.g., first party servers, etc.) and external/third party assets (e.g., third party owned servers or software applications that the entity utilizes for data storage, transfer, etc.).
In some embodiments, the system is configured to indicate, via the visual representation, whether one or more assets have an unknown location (e.g., because the data model described above may be incomplete with regard to the location). In such embodiments, the system may be configured to: (1) identify the asset with the unknown location; (2) use one or more data modeling techniques described herein to determine the location (e.g., such as pinging the asset, generating one or more questionnaires for completion by a suitable individual, etc.); and (3) update a data model associated with the asset to include the location.

Data Model Population Module

In particular embodiments, a Data Model Population Module 1100 is configured to: (1) determine one or more unpopulated inventory attributes in a data model; (2) determine one or more attribute values for the one or more unpopulated inventory attributes; and (3) modify the data model to include the one or more attribute values.
Turning to FIG. 11 , in particular embodiments, when executing the Data Model Population Module 1100, the system begins, at Step 1110, by analyzing one or more data inventories for each of the one or more data assets in the data model. The system may, for example, identify one or more particular data elements (e.g., inventory attributes) that make up the one or more data inventories. The system may, in various embodiments, scan one or more data structures associated with the data model to identify the one or more data inventories. In various embodiments, the system is configured to build an inventory of existing (e.g., known) data assets and identify inventory attributes for each of the known data assets.
Continuing to Step 1120, the system is configured to determine, for each of the one or more data inventories, one or more populated inventory attributes and one or more unpopulated inventory attributes (e.g., and/or one or more unpopulated data assets within the data model). As a particular example related to an unpopulated data asset, when generating and populating a data model, the system may determine that, for a particular asset, there is a destination asset. In various embodiments, the destination asset may be known (e.g., and already stored by the system as part of the data model). In other embodiments, the destination asset may be unknown (e.g., a data element that comprises the destination asset may comprise a placeholder or other indication in memory for the system to populate the unpopulated inventory attribute (e.g., data element).
As another particular example, a particular storage asset may be associated with a plurality of inventory assets (e.g., stored in a data inventory associated with the storage asset). In this example, the plurality of inventory assets may include an unpopulated inventory attribute related to a type of personal data stored in the storage asset. The system may, for example, determine that the type of personal data is an unpopulated inventory asset for the particular storage asset.
Returning to Step 1130, the system is configured to determine, for each of the one or more unpopulated inventory attributes, one or more attribute values. In particular embodiments, the system may determine the one or more attribute values using any suitable technique (e.g., any suitable technique for populating the data model). In particular embodiments, the one or more techniques for populating the data model may include, for example: (1) obtaining data for the data model by using one or more questionnaires associated with a particular privacy campaign, processing activity, etc.; (2) using one or more intelligent identity scanning techniques discussed herein to identify personal data stored by the system and then map such data to a suitable data model; (3) using one or more application programming interfaces (API) to obtain data for the data model from another software application; and/or (4) using any other suitable technique. Exemplary techniques for determining the one or more attribute values are described more fully below. In other embodiments, the system may be configured to use such techniques or other suitable techniques to populate one or more unpopulated data assets within the data model.
Next, at Step 1140, the system modifies the data model to include the one or more attribute values for each of the one or more unpopulated inventory attributes. The system may, for example, store the one or more attributes values in computer memory, associate the one or more attribute values with the one or more unpopulated inventory attributes, etc. In still other embodiments, the system may modify the data model to include the one or more data assets identified as filling one or more vacancies left within the data model by the unpopulated one or more data assets.
Continuing to Step 1150, the system is configured to store the modified data model in memory. In various embodiments, the system is configured to store the modified data model in the One or More Databases 140, or in any other suitable location. In particular embodiments, the system is configured to store the data model for later use by the system in the processing of one or more data subject access requests. In other embodiments, the system is configured to store the data model for use in one or more privacy impact assessments performed by the system.

Data Model Population Questionnaire Generation Module

In particular embodiments, a Data Population Questionnaire Generation Module 1200 is configured to generate a questionnaire (e.g., one or more questionnaires) comprising one or more questions associated with one or more particular unpopulated data attributes, and populate the unpopulated data attributes based at least in part on one or more responses to the questionnaire. In other embodiments, the system may be configured to populate the unpopulated data attributes based on one or more responses to existing questionnaires.
In various embodiments, the one or more questionnaires may comprise one or more processing activity questionnaires (e.g., privacy impact assessments, data privacy impact assessments, etc.) configured to elicit one or more pieces of data related to one or more undertakings by an organization related to the collection, storage, and/or processing of personal data (e.g., processing activities). In particular embodiments, the system is configured to generate the questionnaire (e.g., a questionnaire template) based at least in part on one or more processing activity attributes, data asset attributes (e.g., inventory attributes), or other suitable attributes discussed herein.
Turning to FIG. 12 , in particular embodiments, when executing the Data Population Questionnaire Generation Module 1200, the system begins, at Step 1210, by identifying one or more unpopulated data attributes from a data model. The system may, for example, identify the one or more unpopulated data attributes using any suitable technique described above. In particular embodiments, the one or more unpopulated data attributes may relate to, for example, one or more processing activity or asset attributes such as: (1) one or more processing activities associated with a particular data asset; (2) transfer data associated with the particular data asset (e.g., how and where the data stored and/or collected by the particular data asset is being transferred to and/or from); (3) personal data associated with the particular data assets asset (e.g., what type of personal data is collected and/or stored by the particular data asset; how, and from where, the data is collected, etc.); (4) storage data associated with the personal data (e.g., whether the data is being stored, protected and deleted); and (5) any other suitable attribute related to the collection, use, and transfer of personal data by one or more data assets or via one or more processing activities. In other embodiments, the one or more unpopulated inventory attributes may comprise one or more other pieces of information such as, for example: (1) the type of data being stored by the particular data asset; (2) an amount of data stored by the particular data asset; (3) whether the data is encrypted by the particular data asset; (4) a location of the stored data (e.g., a physical location of one or more computer servers on which the data is stored by the particular data asset); etc.
Continuing to Step 1220, the system generates a questionnaire (e.g., a questionnaire template) comprising one or more questions associated with one or more particular unpopulated data attributes. As may be understood in light of the above, the one or more particulate unpopulated data attributes may relate to, for example, a particular processing activity or a particular data asset (e.g., a particular data asset utilized as part of a particular processing activity). In various embodiments, the one or more questionnaires comprise one or more questions associated with the unpopulated data attribute. For example, if the data model includes an unpopulated data attribute related to a location of a server on which a particular asset stores personal data, the system may generate a questionnaire associated with a processing activity that utilizes the asset (e.g., or a questionnaire associated with the asset). The system may generate the questionnaire to include one or more questions regarding the location of the server.
Returning to Step 1230, the system maps one or more responses to the one or more questions to the associated one or more particular unpopulated data attributes. The system may, for example, when generating the questionnaire, associate a particular question with a particular unpopulated data attribute in computer memory. In various embodiments, the questionnaire may comprise a plurality of question/answer pairings, where the answer in the question/answer pairings maps to a particular inventory attribute for a particular data asset or processing activity.
In this way, the system may, upon receiving a response to the particular question, substantially automatically populate the particular unpopulated data attribute. Accordingly, at Step 1240, the system modifies the data model to populate the one or more responses as one or more data elements for the one or more particular unpopulated data attributes. In particular embodiments, the system is configured to modify the data model such that the one or more responses are stored in association with the particular data element (e.g., unpopulated data attribute) to which the system mapped it at Step 1230. In various embodiments, the system is configured to store the modified data model in the One or More Databases 140, or in any other suitable location. In particular embodiments, the system is configured to store the data model for later use by the system in the processing of one or more data subject access requests. In other embodiments, the system is configured to store the data model for use in one or more privacy impact assessments performed by the system.
Continuing to optional Step 1250, the system may be configured to modify the questionnaire based at least in part on the one or more responses. The system may, for example, substantially dynamically add and/or remove one or more questions to/from the questionnaire based at least in part on the one or more responses (e.g., one or more response received by a user completing the questionnaire). For example, the system may, in response to the user providing a particular inventory attribute or new asset, generates additional questions that relate to that particular inventory attribute or asset. The system may, as the system adds additional questions, substantially automatically map one or more responses to one or more other inventory attributes or assets. For example, in response to the user indicating that personal data for a particular asset is stored in a particular location, the system may substantially automatically generate one or more additional questions related to, for example, an encryption level of the storage, who has access to the storage location, etc.
In still other embodiments, the system may modify the data model to include one or more additional assets, data attributes, inventory attributes, etc. in response to one or more questionnaire responses. For example, the system may modify a data inventory for a particular asset to include a storage encryption data element (which specifies whether the particular asset stores particular data in an encrypted format) in response to receiving such data from a questionnaire. Modification of a questionnaire is discussed more fully below with respect to FIG. 13 .

Data Model Population via Questionnaire Process Flow

FIG. 13 depicts an exemplary process flow 1300 for populating a data model (e.g., modifying a data model to include a newly discovered data asset, populating one or more inventory attributes for a particular processing activity or data asset, etc.). In particular, FIG. 13 depicts one or more exemplary data relationships between one or more particular data attributes (e.g., processing activity attributes and/or asset attributes), a questionnaire template (e.g., a processing activity template and/or a data asset template), a completed questionnaire (e.g., a processing activity assessment and/or a data asset assessment), and a data inventory (e.g., a processing activity inventory and/or an asset inventory). As may be understood from this figure the system is configured to: (1) identify new data assets; (2) generate an asset inventory for identified new data assets; and (3) populate the generated asset inventories. Systems and methods for populating the generated inventories are described more fully below.
As may be understood from FIG. 13 , a system may be configured to map particular processing activity attributes 1320A to each of: (1) a processing activity template 1330A; and (2) a processing activity data inventory 1310A. As may be understood in light of this disclosure, the processing activity template 1330A may comprise a plurality of questions (e.g., as part of a questionnaire), which may, for example, be configured to elicit discovery of one or more new data assets. The plurality of questions may each correspond to one or more fields in the processing activity inventory 1310A, which may, for example, define one or more inventory attributes of the processing activity.
In particular embodiments, the system is configured to provide a processing activity assessment 1340A to one or more individuals for completion. As may be understood from FIG. 13 , the system is configured to launch the processing activity assessment 1340A from the processing activity inventory 1310A and further configured to create the processing activity assessment 1340A from the processing activity template 1330. The processing activity assessment 1340A may comprise, for example, one or more questions related to the processing activity. The system may, in various embodiments, be configured to map one or more responses provided in the processing activity assessment 1340A to one or more corresponding fields in the processing activity inventory 1310A. The system may then be configured to modify the processing activity inventory 1310A to include the one or more responses, and store the modified inventory in computer memory. In various embodiments, the system may be configured to approve a processing activity assessment 1340A (e.g., receive approval of the assessment) prior to feeding the processing activity inventory attribute values into one or more fields and/or cells of the inventory.
As may be further understood from FIG. 13 , in response to creating a new asset record (e.g., which the system may create, for example, in response to a new asset discovery via the processing activity assessment 1340A described immediately above, or in any other suitable manner), the system may generate an asset inventory 1310B (e.g., a data asset inventory) that defines a plurality of inventory attributes for the new asset (e.g., new data asset).
As may be understood from FIG. 13 , a system may be configured to map particular asset attributes 1320B to each of: (1) an asset template 1330BA; and (2) an asset inventory 1310A. As may be understood in light of this disclosure, the asset template 1330B may comprise a plurality of questions (e.g., as part of a questionnaire), which may, for example, be configured to elicit discovery of one or more processing activities associated with the asset and/or one or more inventory attributes of the asset. The plurality of questions may each correspond to one or more fields in the asset inventory 1310B, which may, for example, define one or more inventory attributes of the asset.
In particular embodiments, the system is configured to provide an asset assessment 1340B to one or more individuals for completion. As may be understood from FIG. 13 , the system is configured to launch the asset assessment 1340B from the asset inventory 1310B and further configured to create the asset assessment 1340B from the asset template 1330B. The asset assessment 1340B may comprise, for example, one or more questions related to the data asset. The system may, in various embodiments, be configured to map one or more responses provided in the asset assessment 1340B to one or more corresponding fields in the asset inventory 1310B. The system may then be configured to modify the asset inventory 1310B (e.g., and/or a related processing activity inventory 1310A) to include the one or more responses, and store the modified inventory in computer memory. In various embodiments, the system may be configured to approve an asset assessment 1340B (e.g., receive approval of the assessment) prior to feeding the asset inventory attribute values into one or more fields and/or cells of the inventory.
FIG. 13 further includes a detail view 1350 of a relationship between particular data attributes 1320C with an exemplary data inventory 1310C and a questionnaire template 1330C. As may be understood from this detail view 1350, a particular attribute name may map to a particular question title in a template 1330C as well as to a field name in an exemplary data inventory 1310C. In this way, the system may be configured to populate (e.g., automatically populate) a field name for a particular inventory 1310C in response to a user providing a question title as part of a questionnaire template 1330C. Similarly, a particular attribute description may map to a particular question description in a template 1330C as well as to a tooltip on a fieldname in an exemplary data inventory 1310C. In this way, the system may be configured to provide the tooltip for a particular inventory 1310C that includes the question description provided by a user as part of a questionnaire template 1330C.
As may be further understood from the detail view 1350 of FIG. 13 , a particular response type may map to a particular question type in a template 1330C as well as to a field type in an exemplary data inventory 1310C. A particular question type may include, for example, a multiple choice question (e.g., A, B, C, etc.), a freeform response, an integer value, a drop down selection, etc. A particular field type may include, for example, a memo field type, a numeric field type, an integer field type, a logical field type, or any other suitable field type. A particular data attribute may require a response type of, for example: (1) a name of an organization responsible for a data asset (e.g., a free form response); (2) a number of days that data is stored by the data asset (e.g., an integer value); and/or (3) any other suitable response type.
In still other embodiments, the system may be configured to map a one or more attribute values to one or more answer choices in a template 1330C as well as to one or more lists and/or responses in a data inventory 1310C. The system may then be configured to populate a field in the data inventory 1310C with the one or more answer choices provided in a response to a question template 1330C with one or more attribute values.

Exemplary Questionnaire Generation and Completion User Experience

FIGS. 14-25 depict exemplary screen displays that a user may encounter when generating a questionnaire (e.g., one or more questionnaires and/or templates) for populating one or more data elements (e.g., inventory attributes) of a data model for a data asset and/or processing activity. FIG. 14 , for example, depicts an exemplary asset based questionnaire template builder 1400. As may be understood from FIG. 14 , the template builder may enable a user to generate an asset based questionnaire template that includes one or more sections 1420 related to the asset (e.g., asset information, security, disposal, processing activities, etc.). As may be understood in light of this disclosure, the system may be configured to substantially automatically generate an asset based questionnaire template based at least in part on the one or more unpopulated inventory attributes discussed above. The system may, for example, be configured to generate a template that is configured to populate the one or more unpopulated attributes (e.g., by eliciting responses, via a questionnaire to one or more questions that are mapped to the attributes within the data inventory).
In various embodiments, the system is configured to enable a user to modify a default template (e.g., or a system-created template) by, for example, adding additional sections, adding one or more additional questions to a particular section, etc. In various embodiments, the system may provide one or more tools for modifying the template. For example, in the embodiment shown in FIG. 14 , the system may provide a user with a draft and drop question template 1410, from which the user may select a question type (e.g., textbox, multiple choice, etc.).
A template for an asset may include, for example: (1) one or more questions requesting general information about the asset; (2) one or more security-related questions about the asset; (3) one or more questions regarding how the data asset disposes of data that it uses; and/or (4) one or more questions regarding processing activities that involve the data asset. In various embodiments, each of these one or more sections may comprise one or more specific questions that may map to particular portions of a data model (e.g., a data map).
FIG. 15 depicts an exemplary screen display of a processing activity questionnaire template builder 1500. The screen display shown in FIG. 15 is similar to the template builder shown in FIG. 14 with respect to the data asset based template builder. As may be understood from FIG. 15 , the template builder may enable a user to generate a processing activity based questionnaire template that includes one or more sections 1520 related to the processing activity (e.g., business process information, personal data, source, storage, destinations, access and use, etc.). As may be understood in light of this disclosure, the system may be configured to substantially automatically generate a processing activity based questionnaire template based at least in part on the one or more unpopulated inventory attributes related to the processing activity (e.g., as discussed above). The system may, for example, be configured to generate a template that is configured to populate the one or more unpopulated attributes (e.g., by eliciting responses, via a questionnaire to one or more questions that are mapped to the attributes within the data inventory).
In various embodiments, the system is configured to enable a user to modify a default template (e.g., or a system-created template) by, for example, adding additional sections, adding one or more additional questions to a particular section, etc. In various embodiments, the system may provide one or more tools for modifying the template. For example, in the embodiment shown in FIG. 15 , the system may provide a user with a draft and drop question template 1510, from which the user may select a question type (e.g., textbox, multiple choice, asset attributes, data subjects, etc.). The system may be further configured to enable a user to publish a completed template (e.g., for use in a particular assessment). In other embodiments, the system may be configured to substantially automatically publish the template.
In various embodiments, a template for a processing activity may include, for example: (1) one or more questions related to the type of business process that involves a particular data asset; (2) one or more questions regarding what type of personal data is acquired from data subjects for use by a particular data asset; (3) one or more questions related to a source of the acquired personal data; (4) one or more questions related to how and/or where the personal data will be stored and/or for how long; (5) one or more questions related to one or more other data assets that the personal data will be transferred to; and/or (6) one or more questions related to who will have the ability to access and/or use the personal data.
Continuing to FIG. 16 , an exemplary screen display 1600 depicts a listing of assets 1610 for a particular entity. These may, for example, have been identified as part of the data model generation system described above. As may be understood from this figure, a user may select a drop down indicator 1615 to view more information about a particular asset. In the exemplary embodiment shown in FIG. 16 , the system stores the managing organization group for the “New Asset”, but is missing some additional information (e.g., such as a description 1625 of the asset). In order to fill out the missing inventory attributes for the “New Asset”, the system, in particular embodiments, is configured to enable a user to select a Send Assessment indicia 1620 in order to transmit an assessment related to the selected asset to an individual tasked with providing one or more pieces of information related to the asset (e.g., a manager, or other individual with knowledge of the one or more inventory attributes).
In response to the user selecting the Send Assessment indicia 1620, the system may create the assessment based at least in part on a template associated with the asset, and transmit the assessment to a suitable individual for completion (e.g., and/or transmit a request to the individual to complete the assessment).
FIG. 17 depicts an exemplary assessment transmission interface 1700 via which a user can transmit one or more assessments for completion. As shown in this figure, the user may assign a respondent, provide a deadline, indicate a reminder time, and provide one or more comments using an assessment request interface 1710. The user may then select a Send Assessment(s) indicia 1720 in order to transmit the assessment.
FIG. 18 depicts an exemplary assessment 1800 which a user may encounter in response to receiving a request to complete the assessment as described above with respect to FIGS. 16 and 17 . As shown in FIG. 18 , the assessment 1800 may include one or more questions that map to the one or more unpopulated attributes for the asset shown in FIG. 16 . For example, the one or more questions may include a question related to a description of the asset, which may include a free form text box 1820 for providing a description of the asset. FIG. 19 depicts an exemplary screen display 1900 with the text box 1920 completed, where the description includes a value of “Value_1”. As shown in FIGS. 18 and 19 , the user may have renamed “New Asset” (e.g., which may have included a default or placeholder name) shown in FIGS. 16 and 17 to “7th Asset.”
Continuing to FIG. 20 , the exemplary screen display 2000 depicts the listing of assets 2010 from FIG. 16 with some additional attributes populated. For example, the Description 2025 (e.g., “Value_1”) provided in FIG. 19 has been added to the inventory. As may be understood in light of this disclosure, in response to a user providing the description via the assessment shown in FIGS. 18 and 19 , the system may be configured to map the provided description to the attribute value associated with the description of the asset in the data inventory. The system may have then modified the data inventory for the asset to include the description attribute. In various embodiments, the system is configured to store the modified data inventory as part of a data model (e.g., in computer memory).
FIGS. 21-24 depict exemplary screen displays showing exemplary questions that make up part of a processing activity questionnaire (e.g., assessment). FIG. 21 depicts an exemplary interface 2100 for responding to a first question 2110 and a second question 2120. As shown in FIG. 21 , the first question 2110 relates to whether the processing activity is a new or existing processing activity. The first question 2110 shown in FIG. 21 is a multiple choice question. The second question 2120 relates to whether the organization is conducting the activity on behalf of another organization. As shown in this figure, the second question 2120 includes both a multiple choice portion and a free-form response portion.
As discussed above, in various embodiments, the system may be configured to modify a questionnaire in response to (e.g., based on) one or more responses provided by a user completing the questionnaire. In particular embodiments, the system is configured to modify the questionnaire substantially on-the-fly (e.g., as the user provides each particular answer). FIG. 22 depicts an interface 2200 that includes a second question 2220 that differs from the second question 2120 shown in FIG. 21 . As may be understood in light of this disclosure, in response to the user providing a response to the first question 2110 in FIG. 21 that indicates that the processing activity is a new processing activity, the system may substantially automatically modify the second question 2120 from FIG. 21 to the second question 2220 from FIG. 22 (e.g., such that the second question 2220 includes one or more follow up questions or requests for additional information based on the response to the first question 2110 in FIG. 21 ).
As shown in FIG. 22 , the second question 2220 requests a description of the activity that is being pursued. In various embodiments (e.g., such as if the user had selected that the processing activity was an existing one), the system may not modify the questionnaire to include the second question 2220 from FIG. 22 , because the system may already store information related to a description of the processing activity at issue. In various embodiments, any suitable question described herein may include a tooltip 2225 on a field name (e.g., which may provide one or more additional pieces of information to guide a user's response to the questionnaire and/or assessment).
FIGS. 23 and 24 depict additional exemplary assessment questions. The questions shown in these figures relate to, for example, particular data elements processed by various aspects of a processing activity.
FIG. 25 depicts a dashboard 2500 that includes an accounting of one or more assessments that have been completed, are in progress, or require completion by a particular organization. The dashboard 2500 shown in this figure is configured to provide information relate to the status of one or more outstanding assessments. As may be understood in light of this disclosure, because of the volume of assessment requests, it may be necessary to utilize one or more third party organizations to facilitate a timely completion of one or more assessment requests. In various embodiments, the dashboard may indicate that, based on a fact that a number of assessments are still in progress or incomplete, that a particular data model for an entity, data asset, processing activity, etc. remains incomplete. In such embodiments, an incomplete nature of a data model may raise one or more flags or indicate a risk that an entity may not be in compliance with one or more legal or industry requirements related to the collection, storage, and/or processing of personal data.

Intelligent Identity Scanning Module

Turning to FIG. 26 , in particular embodiments, the Intelligent Identity Scanning Module 2600 is configured to scan one or more data sources to identify personal data stored on one or more network devices for a particular organization, analyze the identified personal data, and classify the personal data (e.g., in a data model) based at least in part on a confidence score derived using one or more machine learning techniques. The confidence score may be and/or comprise, for example, an indication of the probability that the personal data is actually associated with a particular data subject (e.g., that there is at least an 80% confidence level that a particular phone number is associated with a particular individual.)
When executing the Intelligent Identity Scanning Module 2600, the system begins, at Step 2610, by connecting to one or more databases or other data structures, and scanning the one or more databases to generate a catalog of one or more individuals and one or more pieces of personal information associated with the one or more individuals. The system may, for example, be configured to connect to one or more databases associated with a particular organization (e.g., one or more databases that may serve as a storage location for any personal or other data collected, processed, etc. by the particular organization, for example, as part of a suitable processing activity. As may be understood in light of this disclosure, a particular organization may use a plurality of one or more databases (e.g., the One or More Databases 140 shown in FIG. 1 ), a plurality of servers (e.g., the One or More Third Party Servers 160 shown in FIG. 1 ), or any other suitable data storage location in order to store personal data and other data collected as part of any suitable privacy campaign, privacy impact assessment, processing activity, etc.
In particular embodiments, the system is configured to scan the one or more databases by searching for particular data fields comprising one or more pieces of information that may include personal data. The system may, for example, be configured to scan and identify one of more pieces of personal data such as: (1) name; (2) address; (3) telephone number; (4) e-mail address; (5) social security number; (6) information associated with one or more credit accounts (e.g., credit card numbers); (7) banking information; (8) location data; (9) internet search history; (10) non-credit account data; and/or (11) any other suitable personal information discussed herein. In particular embodiments, the system is configured to scan for a particular type of personal data (e.g., or one or more particular types of personal data).
The system may, in various embodiments, be further configured to generate a catalog of one or more individuals that also includes one or more pieces of personal information (e.g., personal data) identified for the individuals during the scan. The system may, for example, in response to discovering one or more pieces of personal data in a particular storage location, identify one or more associations between the discovered pieces of personal data. For example, a particular database may store a plurality of individuals' names in association with their respective telephone numbers. One or more other databases may include any other suitable information.
The system may, for example, generate the catalog to include any information associated with the one or more individuals identified in the scan. The system may, for example, maintain the catalog in any suitable format (e.g., a data table, etc.).
Continuing to Step 2620, the system is configured to scan one or more structured and/or unstructured data repositories based at least in part on the generated catalog to identify one or more attributes of data associated with the one or more individuals. The system may, for example, be configured to utilize information discovered during the initial scan at Step 2610 to identify the one or more attributes of data associated with the one or more individuals.
For example, the catalog generated at Step 2610 may include a name, address, and phone number for a particular individual. The system may be configured, at Step 2620, to scan the one or more structured and/or unstructured data repositories to identify one or more attributes that are associated with one or more of the particular individual's name, address and/or phone number. For example, a particular data repository may store banking information (e.g., a bank account number and routing number for the bank) in association with the particular individual's address. In various embodiments, the system may be configured to identify the banking information as an attribute of data associated with the particular individual. In this way, the system may be configured to identify particular data attributes (e.g., one or more pieces of personal data) stored for a particular individual by identifying the particular data attributes using information other than the individual's name.
Returning to Step 2630, the system is configured to analyze and correlate the one or more attributes and metadata for the scanned one or more structured and/or unstructured data repositories. In particular embodiments, the system is configured to correlate the one or more attributes with metadata for the associated data repositories from which the system identified the one or more attributes. In this way, the system may be configured to store data regarding particular data repositories that store particular data attributes.
In particular embodiments, the system may be configured to cross-reference the data repositories that are discovered to store one or more attributes of personal data associated with the one or more individuals with a database of known data assets. In particular embodiments, the system is configured to analyze the data repositories to determine whether each data repository is part of an existing data model of data assets that collect, store, and/or process personal data. In response to determining that a particular data repository is not associated with an existing data model, the system may be configured to identify the data repository as a new data asset (e.g., via asset discovery), and take one or more actions (e.g., such as any suitable actions described herein) to generate and populate a data model of the newly discovered data asset. This may include, for example: (1) generating a data inventory for the new data asset; (2) populating the data inventory with any known attributes associated with the new data asset; (3) identifying one or more unpopulated (e.g., unknown) attributes of the data asset; and (4) taking any suitable action described herein to populate the unpopulated data attributes.
In particular embodiments, the system my, for example: (1) identify a source of the personal data stored in the data repository that led to the new asset discovery; (2) identify one or more relationships between the newly discovered asset and one or more known assets; and/or (3) etc.
Continuing to Step 2640, the system is configured to use one or more machine learning techniques to categorize one or more data elements from the generated catalog, analyze a flow of the data among the one or more data repositories, and/or classify the one or more data elements based on a confidence score as discussed below.
Continuing to Step 2650, the system, in various embodiments, is configured to receive input from a user confirming or denying a categorization of the one or more data elements, and, in response, modify the confidence score. In various embodiments, the system is configured to iteratively repeat Steps 2640 and 2650. In this way, the system is configured to modify the confidence score in response to a user confirming or denying the accuracy of a categorization of the one or more data elements. For example, in particular embodiments, the system is configured to prompt a user (e.g., a system administrator, privacy officer, etc.) to confirm that a particular data element is, in fact, associated with a particular individual from the catalog. The system may, in various embodiments, be configured to prompt a user to confirm that a data element or attribute discovered during one or more of the scans above were properly categorized at Step 2640.
In particular embodiments, the system is configured to modify the confidence score based at least in part on receiving one or more confirmations that one or more particular data elements or attributes discovered in a particular location during a scan are associated with particular individuals from the catalog. As may be understood in light of this disclosure, the system may be configured to increase the confidence score in response to receiving confirmation that particular types of data elements or attributes discovered in a particular storage location are typically confirmed as being associated with particular individuals based on one or more attributes for which the system was scanning.

Exemplary Intelligent Identity Scanning Technical Platforms

FIG. 27 depicts an exemplary technical platform via which the system may perform one or more of the steps described above with respect to the Intelligent Identity Scanning Module 2600. As shown in the embodiment in this figure, an Intelligent Identity Scanning System 2600 comprises an Intelligent Identity Scanning Server 130, such as the Intelligent Identity Scanning Server 130 described above with respect to FIG. 1 . The Intelligent Identity Scanning Server 130 may, for example, comprise a processing engine (e.g., one or more computer processors). In some embodiments, the Intelligent Identity Scanning Server 130 may include any suitable cloud hosted processing engine (e.g., one or more cloud-based computer servers). In particular embodiments, the Intelligent Identity Scanning Server 130 is hosted in a Microsoft Azure cloud.
In particular embodiments, the Intelligent Identity Scanning Server 130 is configured to sit outside one or more firewalls (e.g., such as the firewall 195 shown in FIG. 26 ). In such embodiments, the Intelligent Identity Scanning Server 130 is configured to access One or More Remote Computing Devices 150 through the Firewall 195 (e.g., one or more firewalls) via One or More Networks 115 (e.g., such as any of the One or More Networks 115 described above with respect to FIG. 1 ).
In particular embodiments, the One or More Remote Computing Devices 150 include one or more computing devices that make up at least a portion of one or more computer networks associated with a particular organization. In particular embodiments, the one or more computer networks associated with the particular organization comprise one or more suitable servers, one or more suitable databases, one or more privileged networks, and/or any other suitable device and/or network segment that may store and/or provide for the storage of personal data. In the embodiment shown in FIG. 27 , the one or more computer networks associated with the particular organization may comprise One or More Third Party Servers 160, One or More Databases 140, etc. In particular embodiments, the One or More Remote Computing Devices 150 are configured to access one or more segments of the one or more computer networks associated with the particular organization. In some embodiments, the one or more computer networks associated with the particular organization comprise One or More Privileged Networks 165. In still other embodiments, the one or more computer networks comprise one or more network segments connected via one or more suitable routers, one or more suitable network hubs, one or more suitable network switches, etc.
As shown in FIG. 27 , various components that make up one or more parts of the one or more computer networks associated with the particular organization may store personal data (e.g., such as personal data stored on the One or More Third Party Servers 160, the One or More Databases 140, etc.). In various embodiments, the system is configured to perform one or more steps related to the Intelligent Identity Scanning Server 2600 in order to identify the personal data for the purpose of generating the catalog of individuals described above (e.g., and/or identify one or more data assets within the organization's network that store personal data)
As further shown in FIG. 27 , in various embodiments, the One or More Remote Computing Devices 150 may store a software application (e.g., the Intelligent Identity Scanning Module). In such embodiments, the system may be configured to provide the software application for installation on the One or More Remote Computing Devices 150. In particular embodiments, the software application may comprise one or more virtual machines. In particular embodiments, the one or more virtual machines may be configured to perform one or more of the steps described above with respect to the Intelligent Identity Scanning Module 2600 (e.g., perform the one or more steps locally on the One or More Remote Computing Devices 150).
In various embodiments, the one or more virtual machines may have the following specifications: (1) any suitable number of cores (e.g., 4, 6, 8, etc.); (2) any suitable amount of memory (e.g., 4 GB, 8 GB, 16 GB etc.); (3) any suitable operating system (e.g., CentOS 7.2); and/or (4) any other suitable specification. In particular embodiments, the one or more virtual machines may, for example, be used for one or more suitable purposes related to the Intelligent Identity Scanning System 2700. These one or more suitable purposes may include, for example, running any of the one or more modules described herein, storing hashed and/or non-hashed information (e.g., personal data, personally identifiable data, catalog of individuals, etc.), storing and running one or more searching and/or scanning engines (e.g., Elasticsearch), etc.
In various embodiments, the Intelligent Identity Scanning System 2700 may be configured to distribute one or more processes that make up part of the Intelligent Identity Scanning Process (e.g., described above with respect to the Intelligent Identity Scanning Module 1800). The one or more software applications installed on the One or more Remote Computing Devices 150 may, for example, be configured to provide access to the one or more computer networks associated with the particular organization to the Intelligent Identity Scanning Server 130. The system may then be configured to receive, from the One or more Remote Computing Devices 150 at the Intelligent Identity Scanning Server 130, via the Firewall 195 and One or More Networks 115, scanned data for analysis.
In particular embodiments, the Intelligent Identity Scanning System 2700 is configured to reduce an impact on a performance of the One or More Remote Computing Devices 150, One or More Third Party Servers 160 and other components that make up one or more segments of the one or more computer networks associated with the particular organization. For example, in particular embodiments, the Intelligent Identity Scanning System 2700 may be configured to utilize one or more suitable bandwidth throttling techniques. In other embodiments, the Intelligent Identity Scanning System 2700 is configured to limit scanning (e.g., any of the one or more scanning steps described above with respect to the Intelligent Identity Scanning Module 2600) and other processing steps (e.g., one or more steps that utilize one or more processing resources) to non-peak times (e.g., during the evening, overnight, on weekends and/or holidays, etc.). In other embodiments, the system is configured to limit performance of such processing steps to backup applications and data storage locations. The system may, for example, use one or more sampling techniques to decrease a number of records required to scan during the personal data discovery process.
FIG. 28 depicts an exemplary asset access methodology that the system may utilize in order to access one or more network devices that may store personal data (e.g., or other personally identifiable information). As may be understood from this figure, the system may be configured to access the one or more network devices using a locally deployed software application (e.g., such as the software application described immediately above). In various embodiments, the software application is configured to route identity scanning traffic through one or more gateways, configure one or more ports to accept one or more identity scanning connections, etc.
As may be understood from this figure, the system may be configured to utilize one or more credential management techniques to access one or more privileged network portions. The system may, in response to identifying particular assets or personally identifiable information via a scan, be configured to retrieve schema details such as, for example, an asset ID, Schema ID, connection string, credential reference URL, etc. In this way, the system may be configured to identify and store a location of any discovered assets or personal data during a scan.

Data Subject Access Request Fulfillment Module

Turning to FIG. 29 , in particular embodiments, a Data Subject Access Request Fulfillment Module 2900 is configured to receive a data subject access request, process the request, and fulfill the request based at least in part on one or more request parameters. In various embodiments, an organization, corporation, etc. may be required to provide information requested by an individual for whom the organization stores personal data within a certain time period (e.g., 30 days). As a particular example, an organization may be required to provide an individual with a listing of, for example: (1) any personal data that the organization is processing for an individual, (2) an explanation of the categories of data being processed and the purpose of such processing; and/or (3) categories of third parties to whom the data may be disclosed.
Various privacy and security policies (e.g., such as the European Union's General Data Protection Regulation, and other such policies) may provide data subjects (e.g., individuals, 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: (1) a right to obtain confirmation of whether a particular organization is processing their personal data; (2) a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected); (3) a right to obtain information about one or more categories of data being processed (e.g., what type of personal data is being collected, stored, etc.); (4) a right to obtain information about one or more categories of recipients with whom their personal data may be shared (e.g., both internally within the organization or externally); (5) a right to obtain information about a time period for which their personal data will be stored (e.g., or one or more criteria used to determine that time period); (6) a right to obtain a copy of any personal data being processed (e.g., a right to receive a copy of their personal data in a commonly used, machine-readable format); (7) a right to request erasure (e.g., the right to be forgotten), rectification (e.g., correction or deletion of inaccurate data), or restriction of processing of their personal data; and (8) any other suitable rights related to the collection, storage, and/or processing of their personal data (e.g., which may be provided by law, policy, industry or organizational practice, etc.).
As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store personal data in a plurality of different locations which may include one or more known and/or unknown locations. As such, complying with particular privacy and security policies related to personal data (e.g., such as responding to one or more requests by data subjects related to their personal data) may be particularly difficult (e.g., in terms of cost, time, etc.). In particular embodiments, a data subject access request fulfillment system may utilize one or more data model generation and population techniques (e.g., such as any suitable technique described herein) to create a centralized data map with which the system can identify personal data stored, collected, or processed for a particular data subject, a reason for the processing, and any other information related to the processing.
Turning to FIG. 29 , when executing the Data Subject Access Request Fulfillment Module 2900, the system begins, at Step 2910, by receiving a data subject access request. In various embodiments, the system receives the request via a suitable web form. In certain embodiments, the request comprises a particular request to perform one or more actions with any personal data stored by a particular organization regarding the requestor. For example, in some embodiments, the request may include a request to view one or more pieces of personal data stored by the system regarding the requestor. In other embodiments, the request may include a request to delete one or more pieces of personal data stored by the system regarding the requestor. In still other embodiments, the request may include a request to update one or more pieces of personal data stored by the system regarding the requestor. In still other embodiments, the request may include a request based on any suitable right afforded to a data subject, such as those discussed above.
Continuing to Step 2920, the system is configured to process the request by identifying and retrieving one or more pieces of personal data associated with the requestor that are being processed by the system. For example, in various embodiments, the system is configured to identify any personal data stored in any database, server, or other data repository associated with a particular organization. In various embodiments, the system is configured to use one or more data models, such as those described above, to identify this personal data and suitable related information (e.g., where the personal data is stored, who has access to the personal data, etc.). In various embodiments, the system is configured to use intelligent identity scanning (e.g., as described above) to identify the requestor's personal data and related information that is to be used to fulfill the request.
In still other embodiments, the system is configured to use one or more machine learning techniques to identify such personal data. For example, the system may identify particular stored personal data based on, for example, a country in which a website that the data subject request was submitted is based, or any other suitable information.
In particular embodiments, the system is configured to scan and/or search one or more existing data models (e.g., one or more current data models) in response to receiving the request in order to identify the one or more pieces of personal data associated with the requestor. The system may, for example, identify, based on one or more data inventories (e.g., one or more inventory attributes) a plurality of storage locations that store personal data associated with the requestor. In other embodiments, the system may be configured to generate a data model or perform one or more scanning techniques in response to receiving the request (e.g., in order to automatically fulfill the request).
Returning to Step 2930, the system is configured to take one or more actions based at least in part on the request. In some embodiments, the system is configured to take one or more actions for which the request was submitted (e.g., display the personal data, delete the personal data, correct the personal data, etc.). In particular embodiments, the system is configured to take the one or more actions substantially automatically. In particular embodiments, in response a data subject submitting a request to delete their personal data from an organization's systems, 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 computing systems), automatically facilitate the deletion of the data subject's personal data from the various systems (e.g., by automatically assigning a plurality of tasks to delete data across multiple business systems to effectively delete the data subject's personal data from the systems). 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.

Data Subject Access Request User Experience

FIGS. 30-31 depict exemplary screen displays that a user may view when submitting a data subject access request. As shown in FIG. 30 , a website 3000 associated with a particular organization may include a user-selectable indicia 3005 for submitting a privacy-related request. A user desiring to make such a request may select the indicia 3005 in order to initiate the data subject access request process.
FIG. 31 depicts an exemplary data subject access request form in both an unfilled and filled out state. As shown in this figure, the system may prompt a user 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 info, opting out, deleting data, updating data, etc.); (3) first name; (4) last name; (5) email address; (6) telephone number; (7) home address; and/or (8) one or more details associated with the request.
As discussed in more detail above, a data subject may submit a subject access request, for example, to request a listing of any personal information that a particular organization is currently storing regarding the data subject, to request that the personal data be deleted, to opt out of allowing the organization to process the personal data, etc.

Alternative Embodiment

In particular embodiments, a data modeling or other system described herein may include one or more features in addition to those described. Various such alternative embodiments are described below.
Processing Activity and Data Asset Assessment Risk Flagging
In particular embodiments, the questionnaire template generation system and assessment system described herein may incorporate one or more risk flagging systems. FIGS. 32-35 depict exemplary user interfaces that include risk flagging of particular questions within a processing activity assessment. As may be understood from these figures, a user may select a flag risk indicia to provide input related to a description of risks and mitigation of a risk posed by one or more inventory attributes associated with the question. As shown in these figures, the system may be configured to substantially automatically assign a risk to a particular response to a question in a questionnaire. In various embodiments, the assigned risk is determined based at least in part on the template from which the assessment was generated.
In particular embodiments, the system may utilize the risk level assigned to particular questionnaire responses as part of a risk analysis of a particular processing activity or data asset. Various techniques for assessing the risk of various privacy campaigns are described in U.S. patent application Ser. No. 15/256,419, filed Sep. 2, 2016, entitled “Data processing systems and methods for operationalizing privacy compliance and assessing the risk of various respective privacy campaigns,” which is hereby incorporated herein in its entirety.

Centralized Repository of Personally Identifiable Information (PII) Overview

A centralized data repository system, in various embodiments, is configured to provide a central data-storage repository (e.g., one or more servers, databases, etc.) for the centralized storage of personally identifiable information (PII) and/or personal data for one or more particular data subjects. In particular embodiments, the centralized data repository may enable the system to populate one or more data models (e.g., using one or more suitable techniques described above) substantially on-the-fly (e.g., as the system collects, processes, stores, etc. personal data regarding a particular data subject). In this way, in particular embodiments, the system is configured to maintain a substantially up-to-date data model for a plurality of data subjects (e.g., each particular data subject for whom the system collects, processes, stores, etc. personal data). The system may then be configured to substantially automatically respond to one or more data access requests by a data subject (e.g., individual, entity, organization, etc.), for example, using the substantially up-to-date data model. In particular embodiments, the system may be configured to respond to the one or more data access requests using any suitable technique described herein.
As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in a plurality of different locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store personal data in a plurality of different locations which may include one or more known and/or unknown locations. As such, complying with particular privacy and security policies related to personal data (e.g., such as responding to one or more requests by data subjects related to their personal data) may be particularly difficult (e.g., in terms of cost, time, etc.). Accordingly, utilizing and maintaining a centralized data repository for PII may enable the system to more quickly and accurately respond to data subject access requests and other requests related to collected, stored, and processed personal data. In particular embodiments, the centralized data repository may include one or more third party data repositories (e.g., one or more third party data repositories maintained on behalf of a particular entity that collects, stores, and/or processes personal data).
In various embodiments, a third party data repository system is configured to facilitate the receipt and centralized storage of personal data for each of a plurality of respective data subjects. In particular embodiments, the system may be configured to: (1) receive personal data associated with a particular data subject (e.g., a copy of the data, a link to a location of where the data is stored, etc.); and (2) store the personal data in a suitable data format (e.g., a data model, a reference table, etc.) for later retrieval. In other embodiments, the system may be configured to receive an indication that personal data has been collected regarding a particular data subject (e.g., collected by a first party system, a software application utilized by a particular entity, etc.).
In particular embodiments, the third party data repository system is configured to: (1) receive an indication that a first party system (e.g., entity) has collected and/or processed a piece of personal data for a data subject; (2) determine a location in which the first party system has stored the piece of personal data; (3) optionally digitally store (e.g., in computer memory) a copy of the piece of personal data and associate, in memory, the piece of personal data with the data subject; and (4) optionally digitally store an indication of the storage location utilized by the first party system for the piece of personal data. In particular embodiments, the system is configured to provide a centralized database, for each particular data subject (e.g., each particular data subject about whom a first party system collects or has collected personally identifiable information), of any personal data processed and/or collected by a particular entity.
In particular embodiments, a third party data repository system is configured to interface with a consent receipt management system (e.g., such as the consent receipt management system described below). In particular embodiments, the system may, for example: (1) receive an indication of a consent receipt having an associated unique subject identifier and one or more receipt definitions (e.g., such as any suitable definition described herein); (2) identify, based at least in part on the one or more receipt definitions, one or more pieces of repository data associated with the consent receipt (e.g., one or more data elements or pieces of personal data for which the consent receipt provides consent to process; a storage location of the one or more data elements for which the consent receipt provides consent to process; etc.); (3) digitally store the unique subject identifier in one or more suitable data stores; and (4) digitally associate the unique subject identifier with the one or more pieces of repository data. In particular embodiments, the system is configured to store the personal data provided as part of the consent receipt in association with the unique subject identifier.
In particular embodiments, the system is configured to, for each stored unique subject identifier: (1) receive an indication that new personal data has been provided by or collected from a data subject associated with the unique subject identifier (e.g., provided to an entity or organization that collects and/or processes personal data); and (2) in response to receiving the indication, storing the new personal data (e.g., or storing an indication of a storage location of the new personal data by the entity) in association with the unique subject identifier. In this way, as an entity collects additional data for a particular unique data subject (e.g., having a unique subject identifier, hash, etc.), the third party data repository system is configured to maintain a centralized database of data collected, stored, and or processed for each unique data subject (e.g., indexed by unique subject identifier). The system may then, in response to receiving a data subject access request from a particular data subject, fulfill the request substantially automatically (e.g., by providing a copy of the personal data, deleting the personal data, indicating to the entity what personal data needs to be deleted from their system and where it is located, etc.). The system may, for example, automatically fulfill the request by: (1) identifying the unique subject identifier associated with the unique data subject making the request; and (2) retrieving any information associated with the unique data subject based on the unique subject identifier.

Exemplary Centralized Data Repository System Architecture

FIG. 36 is a block diagram of a centralized data repository system 3600 according to a particular embodiment. In various embodiments, the centralized data repository system 3600 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 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. In various other embodiments, the centralized data repository system 3600 is a stand-alone system that is configured to interface with one or more first party data management or other systems for the purpose of maintaining a centralized data repository of personal data collected, stored, and/or processed by each of the one or more first party data systems.
As may be understood from FIG. 36 , the centralized data repository system 3600 includes one or more computer networks 115, One or More Centralized Data Repository Servers 3610, a Consent Receipt Management Server 3620, One or More First Party System Servers 3630, One or More Databases 140 or other data structures, and one or more remote data subject computing devices 3650 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.). Although in the embodiment shown in FIG. 36 , the One or More Centralized Data Repository Servers 3610, Consent Receipt Management Server 3620, One or More First Party System Servers 3630, One or More Databases 140 or other data structures, and one or more remote data subject computing devices 3650 are shown as separate servers, it should be understood that in other embodiments, one or more of these servers and/or computing devices may comprise a single server, a plurality of servers, one or more cloud-based servers, or any other suitable configuration.
In particular embodiments, the One or More Centralized Data Repository Servers 3610 may be configured to interface with the One or More First Party System Servers 3630 to receive any of the indications or personal data (e.g., for storage) described herein. The One or More Centralized Data Repository Servers 3610 and One or More First Party System Servers 3630 may, for example, interface via a suitable application programming interface, direct connection, etc. In a particular embodiment, the One or More Centralized Data Repository Servers 3610 comprise the Consent Receipt Management Server 3620.
In a particular example, a data subject may provide one or more pieces of personal data via the One or More Remote Data Subject Computing Devices 3650 to the One or More First Party System Servers 3630. The data subject may, for example, complete a webform on a website hosted on the One or More First Party System Servers 3630. The system may then, in response to receiving the one or more pieces of personal data at the One or More First Party System Servers 3630, transmit an indication to the One or More Centralized Data Repository Servers 3610 that the One or More First Party System Servers 3630 have collected, stored, and/or processed the one or more pieces of personal data. In response to receiving the indication, the One or More Centralized Data Repository Servers 3610 may then store the one or more pieces of personal data (e.g., a copy of the data, an indication of the storage location of the personal data in the One or More First Party System Servers 3630, etc.) in a centralized data storage location (e.g., in One or More Databases 140, on the One or More Centralized Data Repository Servers 3610, etc.).

Centralized Data Repository Module

Various functionality of the centralized data repository system 3600 may be implemented via a Centralized Data Repository Module 3700. The system, when executing certain steps of the Centralized Data Repository Module, may be configured to generate, a central repository of personal data on behalf of an entity, and populate the central repository with personal data as the entity collects, stores and/or processes the personal data. In particular embodiments, the system is configured to index the personal data within the central repository by data subject.
FIG. 37 depicts a Centralized Data Repository Module 3700 according to a particular embodiment. The system, when executing the Centralized Data Repository Module 3700, begins, at Step 3710, by receiving a request to generate a central repository of personal data on behalf of an entity. In particular embodiments, the system is a third-party system that receives a request from the entity to generate and maintain a central repository (e.g., third party repository) of personal data that the entity collects, stores, and or processes.
In particular embodiments, the system, in response to receiving the request, is configured to generate the central repository by: (1) designating at least a portion of one or more data stores for the storage of the personal data, information about the data subjects about whom the personal data is collected, etc.; (2) initiating a connection between the central repository and one or more data systems operated by the entity (e.g., one or more first party systems); (3) etc.
Continuing to Step 3720, the system is configured to generate, for each data subject about whom the entity collects, receives, and/or processes personal data, a unique identifier. The system may, for example: (1) receive an indication that a first party system has collected, stored, and/or processed a piece of personal data; (2) identify a data subject associated with the piece of personal data; (3) determine whether the central repository system is currently storing data associated with the data subject; and (4) in response to determining that the central repository system is not currently storing data associated with the data subject (e.g., because the data subject is a new data subject), generating the unique identifier. In various embodiments, the system is configured to assign a unique identifier for each data subject about whom the first party system has previously collected, stored, and/or processed personal data.
In particular embodiments, the unique identifier may include any unique identifier such as, for example: (1) any of the one or more pieces of personal data collected, stored, and/or processed by the system (e.g., name, first name, last name, full name, address, phone number, e-mail address, etc.); (2) a unique string or hash comprising any suitable number of numerals, letters, or combination thereof; and/or (3) any other identifier that is sufficiently unique to distinguish between a first and second data subject for the purpose of subsequent data retrieval.
In particular embodiments, the system is configured to assign a permanent identifier to each particular data subject. In other embodiments, the system is configured to assign one or more temporary unique identifiers to the same data subject.
In particular embodiments, the unique identifier may be based at least in part on the unique receipt key and/or unique subject identifier discussed below with respect to the consent receipt management system. As may be understood in light of this disclosure, when receiving consent form a data subject to process, collect, and at least store one or more particular types of personal data associated with the data subject, the system is configured to generate a unique ID to memorialize the consent and provide authorization for the system to collect the subject's data. In any embodiment described herein, the system may be configured to utilize any unique ID generated for the purposes of tracking data subject consent as a unique identifier in the context of the central repository system described herein.
In particular embodiments, the system is configured to continue to Step 3730, and store the unique identifier in computer memory. In particular embodiments, the system is configured to store the unique identifier in an encrypted manner. In various embodiments, the system is configured to store the unique identifier in any suitable location (e.g., the one or more databases 140 described above).
In particular embodiments, the system is configured to store the unique identifier as a particular file structure such as, for example, a particular folder structure in which the system is configured to store one or more pieces of personal data (e.g., or pointers to one or more pieces of personal data) associated with the unique identifier (e.g., the data subject associated with the unique identifier). In other embodiments, the system is configured to store the unique identifier in any other suitable manner (e.g., in a suitable data table, etc.).
Returning to Step 3740, the system is configured to receive an indication that one or more computer systems have received, collected or processed one or more pieces of personal data associated with a data subject. In particular embodiments, the one or more computer systems include any suitable computer system associated with a particular entity. In other embodiments, the one or more computer systems comprise one or more software applications, data stores, databases, etc. that collect, process, and/or store data (e.g., personally identifiable data) on behalf of the entity (e.g., organization). In particular embodiments, the system is configured to receive the indication through integration with the one or more computer systems. In a particular example, the system may provide a software application for installation on a system device that is configured to transmit the indication in response to the system receiving, collecting, and/or processing one or more pieces of personal data.
In particular embodiments, the system may receive the indication in response to: (1) a first party system, data store, software application, etc. receiving, collecting, storing, and or processing a piece of data that includes personally identifying information; (2) a user registering for an account with a particular entity (e.g., an online account, employee account, social media account, e-mail account, etc.); (3) a company storing information about one or more data subjects (e.g., employee information, customer information, potential customer information, etc.; and/or (4) any other suitable indication that a first entity or any computer system or software on the first entity's behalf has collected, stored, and/or processed a piece of data that includes or may include personally identifiable information.
As a particular example, the system may receive the indication in response to a user submitting a webform via a website operated by the first entity. The webform may include, for example, one or more fields that include the user's e-mail address, billing address, shipping address, and payment information for the purposes of collected payment data to complete a checkout process on an e-commerce website. In this example, because the information submitted via the webform contains personal data (e.g., personally identifiable data) the system, in response to receiving an indication that the user has submitted the at least partially completed webform, may be configured to receive the indication described above with respect to Step 3740.
In various embodiments, a first party privacy management system or other system (e.g., privacy management system, marketing system, employee records database management system, etc.) may be configured to transmit an indication to the central repository system in response to collecting, receiving, or processing one or more pieces of personal data personal data.
In some embodiments, the indication may include, for example: (1) an indication of the type of personal data collected; (2) a purpose for which the personal data was collected; (3) a storage location of the personal data by the first party system; and/or (4) any other suitable information related to the one or more pieces of personal data or the handling of the personal data by the first party system. In particular embodiments, the system is configured to receive the indication via an application programming interface, a software application stored locally on a computing device within a network that makes up the first party system, or in any other suitable manner.
Continuing to Step 3750, the central repository system is configured to store, in computer memory, an indication of the personal data in association with the respective unique identifier. In various embodiments, the central repository system comprises a component of a first party system for the centralized storage of personal data collected by one or more various distributed computing systems (e.g., and software applications) operated by a particular entity for the purpose of collecting, storing, and/or processing personal data. In other embodiments, the central repository system is a third-party data repository system that is separate from the one or more first party systems described above. In particular embodiments, for example, a third-party data repository system may be configured to maintain a central repository of personal data for a plurality of different entities.
In particular embodiments, the central repository system is configured to store a copy of the personal data (e.g., store a digital copy of the personal data in computer memory associated with the central repository system). In still other embodiments, the central repository system is configured to store an indication of a storage location of the personal data within the first party system. For example, the system may be configured to store an indication of a physical location of a particular storage location (e.g., a physical location of a particular computer server or other data store) and an indication of a location of the personal data in memory on that particular storage location (e.g., a particular path or filename of the personal data, a particular location in a spreadsheet, CSV file, or other suitable document, etc.).
In various embodiments, the system may be configured to confirm receipt of valid consent to collect, store, and/or process personal data from the data subject prior to storing the indication of the personal data in association with the respective unique identifier. In such embodiments, the system may be configured to integrate with (e.g., interface with) a consent receipt management system (e.g., such as the consent receipt management system described more fully below). In such embodiments, the system may be configured to: (1) receive the indication that the first party system has collected, stored, and/or processed a piece of personal data; (2) identify, based at least in part on the piece of personal data, a data subject associated with the piece of personal data; (3) determine, based at least in part on one or more consent receipts received from the data subject(e.g., one or more valid receipt keys associated with the data subject), and one or more pieces of information associated with the piece of personal data, whether the data subject has provided valid consent to collect, store, and/or process the piece of personal data; (4) in response to determining that the data subject has provided valid consent, storing the piece of personal data in any manner described herein; and (5) in response to determining that the data subject has not provided valid consent, deleting the piece of personal data (e.g., not store the piece of personal data).
In particular embodiments, in response to determining that the data subject has not provided valid consent, the system may be further configured to: (1) automatically determine where the data subject's personal data is stored (e.g., by the first party system); and (2) in response to determining the location of the data (which may be on multiple computing systems), automatically facilitate the deletion of the data subject's personal data from the various systems (e.g., by automatically assigning a plurality of tasks to delete data across multiple business systems to effectively delete the data subject's personal data from the systems). 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.
Next, at optional step 3760, the system is configured to take one or more actions based at least in part on the data stored in association with the unique identifier. In particular embodiments, the one or more actions may include, for example, responding to a data subject access request initiated by a data subject (e.g., or other individual on the data subject's behalf) associated with the unique identifier. In various embodiments, the system is configured to identify the unique identifier associated with the data subject making the data subject access request based on information submitted as part of the request.

Consent Receipt Management Systems

In particular embodiments, any entity (e.g., organization, company, etc.) that collects, stores, processes, etc. personal data may require one or more of: (1) consent from a data subject from whom the personal data is collected and/or processed; and/or (2) a lawful basis for the collection and/or processing of the personal data. In various embodiments, the entity may be required to, for example: (1) demonstrate that a data subject has freely given specific, informed, and unambiguous indication of the data subject's agreement to the processing of his or her personal data (e.g., in the form of a statement or clear affirmative action); (2) demonstrate that the entity received consent from a data subject in a manner clearly distinguishable from other matters (e.g., in an intelligible and easily accessible form, using clear and plain language, etc.); (3) enable a data subject to withdraw consent as easily as the data subject can give consent; (4) separate a data subject's consent from performance under any contract unless such processing is necessary for performance under the contract; etc.
In various embodiments, a consent receipt management system may be implemented in the context of any suitable privacy management system that is configured to ensure compliance with one or more legal or industry standards related to the collection and/or storage of private information (e.g., such as personal data). Various privacy and security policies (e.g., such as the European Union's General Data Protection Regulation, and other such policies) may provide data subjects (e.g., individuals, 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: (1) a right to erasure of the data subject's personal data (e.g., in cases where no legal basis applies to the processing and/or collection of the personal data; (2) a right to withdraw consent to the processing and/or collection of their personal data; (3) a right to receive the personal data concerning the data subject, which he or she has provided to an entity (e.g., organization), in a structured, commonly used and machine-readable format; and/or (4) any other right which may be afforded to the data subject under any applicable legal and/or industry policy.
In particular embodiments, the consent receipt management system is configured to: (1) enable an entity to demonstrate that valid consent has been obtained for each particular data subject for whom the entity collects and/or processes personal data; and (2) enable one or more data subjects to exercise one or more rights described herein.
The system may, for example, be configured to track data on behalf of an entity that collects and/or processes persona data related to: (1) who consented to the processing or collection of personal data (e.g., the data subject themselves or a person legally entitled to consent on their behalf such as a parent, guardian, etc.); (2) when the consent was given (e.g., a date and time); (3) what information was provided to the consenter at the time of consent (e.g., a privacy policy, what personal data would be collected following the provision of the consent, for what purpose that personal data would be collected, etc.); (4) how consent was received (e.g., one or more copies of a data capture form, webform, etc. via which consent was provided by the consenter); (5) when consent was withdrawn (e.g., a date and time of consent withdrawal if the consenter withdraws consent); and/or (6) any other suitable data related to receipt or withdrawal of consent.
In further embodiments, the system may be configured to provide data subjects with a centralized interface that is configured to: (1) provide information regarding each of one or more valid consents that the data subject has provided to one or more entities related to the collection and/or processing of their personal data; (2) provide one or more periodic reminders regarding the data subject's right to withdraw previously given consent (e.g., every 6 months in the case of communications data and metadata, etc.); (3) provide a withdrawal mechanism for the withdrawal of one or more previously provided valid consents (e.g., in a format that is substantially similar to a format in which the valid consent was given by the data subject); (4) refresh consent when appropriate (e.g., the system may be configured to elicit updated consent in cases where particular previously validly consented to processing is used for a new purpose, a particular amount of time has elapsed since consent was given, etc.).
In particular embodiments, the system is configured to manage one or more consent receipts between a data subject and an entity. In various embodiments, a consent receipt may include a record (e.g., a data record stored in memory and associated with the data subject) of consent, for example, as a transactional agreement where the data subject is already identified or identifiable as part of the data processing that results from the provided consent. In any embodiment described herein, the system may be configured to generate a consent receipt in response to a data subject providing valid consent. In some embodiments, the system is configured to determine whether one or more conditions for valid consent have been met prior to generating the consent receipt.

Exemplary Consent Receipt Data Flow

FIG. 38 depicts an exemplary data flow that a consent receipt management system may utilize in the recordation and management of one or more consent receipts. In particular embodiments, a third party consent receipt management system may be configured to manage one or more consent receipts for a particular entity. As may be understood from this figure, a data subject may access an interaction interface (e.g., via the web) for interacting with a particular entity (e.g., one or more entity systems). The interaction interface (e.g., user interface) may include, for example, a suitable website, web form, user interface etc. The interaction interface may be provided by the entity. Using the interaction interface, a data subject may initiate a transaction with the entity that requires the data subject to provide valid consent (e.g., because the transaction includes the processing of personal data by the entity). The transaction may include, for example: (1) accessing the entity's website; (2) signing up for a user account with the entity; (3) signing up for a mailing list with the entity; (4) a free trial sign up; (5) product registration; and/or (6) any other suitable transaction that may result in collection and/or processing personal data, by the entity, about the data subject.
As may be understood from this disclosure, any particular transaction may record and/or require one or more valid consents from the data subject. For example, the system may require a particular data subject to provide consent for each particular type of personal data that will be collected as part of the transaction. The system may, in various embodiments, be configured to prompt the data subject to provide valid consent, for example, by: (1) displaying, via the interaction interface, one or more pieces of information regarding the consent (e.g., what personal data will be collected, how it will be used, etc.); and (2) prompt the data subject to provide the consent.
In response to the data subject (e.g., or the entity) initiating the transaction, the system may be configured to: (1) generate a unique receipt key (e.g., unique receipt ID); (2) associate the unique receipt key with the data subject (e.g., a unique subject identifier), the entity, and the transaction; and (3) electronically store (e.g., in computer memory) the unique receipt key. The system may further store a unique user ID (e.g., unique subject identifier) associated with the data subject (e.g., a hashed user ID, a unique user ID provided by the data subject, unique ID based on a piece of personal data such as an e-mail address, etc.).
In a particular embodiment, the unique consent receipt key is generated by a third party consent receipt management system. The system may then be configured to associate the unique consent receipt key with the interaction interface, and further configured to associate the unique consent receipt key with a unique transaction ID generated as a result of a data subject transaction initiated via the interaction interface.
In particular embodiments, the unique consent receipt key may be associated with one or more receipt definitions, which may include, for example: (1) the unique transaction ID; (2) an identity of one or more controllers and/or representatives of the entity that is engaging in the transaction with the data subject (e.g., and contact information for the one or more controllers); (3) one or more links to a privacy policy associated with the transaction at the time that consent was given; (4) a listing of one or more data types for which consent to process was provided (e.g., email, MAC address, name, phone number, browsing history, etc.); (5) one or more methods used to collect data for which consent to process was provided (e.g., using one or more cookies, receiving the personal data from the data subject directly, etc.); (6) a description of a service (e.g., a service provided as part of the transaction such as a free trial, user account, etc.); (7) one or more purposes of the processing (e.g., for marketing purposes, to facilitate contact with the data subject, etc.); (8) a jurisdiction (e.g., the European Union, United States, etc.); (9) a legal basis for the collection of personal data (e.g., consent); (10) a type of consent provided by the data subject (e.g. unambiguous, explicit, etc.); (11) one or more categories or identities of other entities to whom the personal data may be transferred; (12) one or more bases of a transfer to a third party entity (e.g., adequacy, binding corporate rules, etc.); (13) a retention period for the personal data (e.g., how long the personal data will be stored); (14) a withdrawal mechanism (e.g., a link to a withdrawal mechanism); (15) a timestamp (e.g., date and time); (16) a unique identifier for the receipt; and/or (17) any other suitable information. FIG. 39 depicts an exemplary consent definition summary for a particular transaction (e.g., free trial signup).
In response to receiving valid consent from the data subject, the system is configured to transmit the unique transaction ID and the unique consent receipt key back to the third party consent receipt management system for processing and/or storage. In other embodiments, the system is configured to transmit the transaction ID to a data store associated with one or more entity systems (e.g., for a particular entity on behalf of whom the third party consent receipt management system is obtaining and managing validly received consent). In further embodiments, the system is configured to transmit the unique transaction ID, the unique consent receipt key, and any other suitable information related to the validly given consent to the centralized data repository system described above for use in determining whether to store particular data and/or for assigning a unique identifier to a particular data subject for centralized data repository management purposes.
The system may be further configured to transmit a consent receipt to the data subject which may include, for example: (1) the unique transaction ID; (2) the unique consent receipt key; and/or (3) any other suitable data related to the validly provided consent. In some embodiments, the system is configured to transmit a consent receipt in any suitable format (e.g., JSON, HTML, e-mail, text, cookie, etc.). In particular embodiments, the receipt transmitted to the data subject may include a link to a subject rights portal via which the data subject may, for example: (1) view one or more provided valid consents; (2) withdraw consent; (3) etc.

Exemplary Data Subject Consent Receipt User Experience

FIGS. 40 and 41 depict exemplary screen displays that a data subject may encounter when providing consent to the processing of personal data. As shown in FIG. 40 , a data subject (e.g., John Doe) may provide particular personal data (e.g., first and last name, email, company, job title, phone number, etc.) when signing up for a free trial with a particular entity via a trial signup interface 4000. As may be understood in light of this disclosure, the free trial may constitute a transaction between the data subject (e.g., user) and a particular entity providing the free trial. In various embodiments, the data subject (e.g., user) may encounter the interface shown in FIG. 40 in response to accessing a website associated with the particular entity for the free trial (e.g., a sign up page).
In particular embodiments, the interface 4000 is configured to enable the user (e.g., data subject) to provide the information required to sign up for the free trial. As shown in FIG. 40 , the interface further includes a listing of particular things that the data subject is consenting to (e.g., the processing of first name, last name, work email, company, job title, and phone number) as well as one or more purposes for the processing of such data (e.g., marketing information). The interface further includes a link to a Privacy Policy that governs the use of the information.
In various embodiments, in response to the user (e.g., data subject) submitting the webform shown in FIG. 40 , the system is configured to generate a consent receipt that memorializes the user's provision of the consent (e.g., by virtue of the user submitting the form). FIG. 41 depicts an exemplary consent receipt 4100 in the form of a message transmitted to the data subject (e.g., via e-mail). As shown in this figure, the consent receipt includes, for example: (1) a receipt number (e.g., a hash, key, or other unique identifier); (2) what information was processed as a result of the user's consent (e.g., first and last name, email, company, job title, phone number, etc.); (3) one or more purposes of the processing (e.g., marketing information); (4) information regarding withdrawal of consent; (5) a link to withdraw consent; and (6) a timestamp at which the system received the consent (e.g., a time at which the user submitted the form in FIG. 40 ). In other embodiments, the consent receipt transmitted to the user may include any other suitable information.
FIG. 42 depicts an exemplary log of consent receipts 4200 for a particular transaction (e.g., the free trial signup described above). As shown in this figure, the system is configured to maintain a database of consent receipts that includes, for example, a timestamp of each receipt, a unique key associated with each receipt, a customer ID associated with each receipt (e.g., the customer's e-mail address), etc. In particular embodiments, the centralized data repository system described above may be configured to cross-reference the database of consent receipts (e.g., or maintain the database) in response to receiving the indication that a first party system has received, stored, and/or processed personal data (e.g., via the free trial signup interface) in order to confirm that the data subject has provided valid consent prior to storing the indication of the personal data.

Exemplary Transaction Creation User Experience

FIGS. 43-54 depict exemplary user interfaces via which a user (e.g., a controller or other individual associated with a particular entity) may create a new transaction for which the system is configured to generate a new interaction interface (e.g., interface via which the system is configured to elicit and receive consent for the collection and/or processing of personal data from a data subject under the new transaction.
As shown in FIG. 43 , the system is configured to display a dashboard of existing transactions 4300 that are associated with a particular entity. In the example shown in this figure, the dashboard includes, for example: (1) a name of each transaction; (2) a status of each transaction; (2) one or more data categories collected as part of each transaction; (3) a unique subject ID used as part of the transaction (e.g., email, device ID, etc.); (4) a creation date of each transaction; (5) a date of first consent receipt under each transaction; and (6) a total number of receipts received for each transaction. The dashboard further includes a Create New Transaction button, which a user may select in order to create a new transaction.
As may be understood in light of this disclosure, in various embodiments, the centralized data repository system described above may limit storage of personal data on behalf of a particular entity to specific personal data for which the particular entity has received consent from particular data subjects. Based on the exemplary dashboard of existing transactions shown in FIG. 43 , for example, the system may be configured to not store any personal data collected, and/or processed other than in response to an indication that the data was collected through the free trial signup or product registration transaction.
FIG. 44 depicts an interface 4400 for creating a new transaction, which a user may access, for example, by selecting the Create New Transaction button shown in FIG. 43 . As may be understood from this figure, when creating a new transaction, the user may enter, via one or more text entry forms, a name of the transaction, a description of the transaction, a group associated with the transaction, and/or any other suitable information related to the new transaction.
Continuing to FIG. 45 , the system may be configured to prompt the user to select whether the new transaction is based on an existing processing activity. An existing processing activity may include, for example, any other suitable transaction or any other activity that involves the collection and/or processing of personal data. In response to the user selecting that the new transaction is not related to an existing processing activity (e.g., as shown in FIG. 45 ), the system may be configured to prompt the user, via one or more additional interfaces, to provide information regarding the new transaction.
FIGS. 47-54 depict exemplary user interfaces via which the user may provide additional information regarding the new transaction. In various embodiments, the system may be configured to prompt the user to provide the information via free-form text entry, via one or more drop down menus, by selecting one or more predefined selections, or in any suitable manner. In some embodiments, the system is configured to prompt the user to provide one or more standardized pieces of information regarding the new transaction. In other embodiments, the system is configured to enable a particular entity (e.g., organization, company, etc.) to customize one or more questions or prompts that the system displays to a user creating a new transaction.
As shown in FIG. 46 , the system may, for example, prompt the user, via the user interface, to: (1) describe a process or service that the consent under the transaction relates to; (2) provide a public URL where consent is or will be collected; (3) provide information regarding how consent is being collected (e.g., via a website, application, device, paper form, etc.); (4) provide information regarding one or more data elements that will be processed based on the consent provided by the data subject (e.g., what particular personal data will be collected); and (5) provide information regarding what data elements are processed by one or more background checks (e.g., credit check and/or criminal history).
Continuing to FIG. 47 , the system may be configured to prompt the user to provide data related to, for example: (1) one or more elements that will be used to uniquely identify a data subject; (2) a purpose for seeking consent; (3) what type of consent is sought (e.g., unambiguous, explicit, not sure, etc.); (4) who is the data controller in charge of the processing of the personal data (e.g., the legal entity responsible); (5) a contact address (e.g., for the data controller; (6) etc.
As shown in FIG. 48 , the system may be further configured to prompt the user to provide data regarding, for example: (1) who the contact person is for the transaction (e.g., a job title, name, etc. of the contact person); (2) a contact email (e.g., an email address that a data subject can contact to get more information about the transaction, consent, etc.); (3) a contact telephone number (e.g., a telephone number that a data subject can contact to get more information about the transaction, consent, etc.); (4) an applicable jurisdiction for the processing (e.g., European Union, United States, Other, etc.), which may include one or more jurisdictions; (5) a URL of a privacy policy associated with the transaction; (6) etc.
Next, as shown in FIG. 49 , the system may be further configured to prompt the user to provide data regarding: (1) whether the personal data will be shared with one or more third parties; (2) a name of the one or more third parties; (3) whether the processing of the personal data will involve a transfer of the personal data outside of the original jurisdiction; (4) a listing of one or more destination countries, regions, or other jurisdictions that will be involved in any international transfer; (5) a process for a data subject to withdraw consent; (6) a URL for the withdrawal mechanism; (7) etc. FIG. 50 depicts a user interface that includes additional data prompts for the user to respond to regarding the new transaction. As shown in FIG. 50 , the system may be further configured to prompt the user to provide data regarding, for example: (1) what the retention period is for the personal data (e.g., how long the personal data will be stored in identifiable form, a period before anonymization of the personal data, etc.); and/or (2) a life span of the consent (e.g., a period of time during which the consent is assumed to be valid).
FIG. 51 shows an exemplary user interface for selecting a processing activity in response to the user indicating that the new transaction is based on an existing processing activity. The user may, for example, use a drop down menu to select a suitable existing processing activity. In particular embodiments, the system is configured to populate the drop down menu with one or more processing activities from a data model associated with the processing activity. The system may then be configured to substantially automatically populate one or more responses to the questions described above based at least in part on the data model (e.g., automatically include particular data elements collected as part of the processing activity, etc.).
In particular embodiments, the system is further configured to enable a controller (e.g., or other user on behalf of the entity) to search for one or more consent receipts received for a particular data subject (e.g., via a unique subject identifier). FIG. 52 depicts a search for a unique subject identifier that includes an e-mail address. As shown in this figure, the unique subject identifier (e.g., john.doe@gmail.com) has one associated consent receipt having a receipt number, a receipt date and time, and a withdrawal date. FIG. 53 depicts an additional exemplary search results page indicating one or more results for consent receipts associated with the unique subject identifier of john.doe@gmail.com. As shown in this figure, the system may be configured to display a process name (e.g., transaction name), receipt number, consent date, status, withdrawal date, and other suitable information for one or more consent receipts associated with the searched for unique subject identifier.
As may be understood in light of this disclosure, in response to a user creating a new transaction, the system may be configured to generate a web form, web page, piece of computer code, etc. for the collection of consent by a data subject as part of the new transaction. FIG. 54 depicts an exemplary dashboard of consent receipt management implementation code which the system may automatically generate for the implementation of a consent receipt management system for a particular transaction. As shown in this figure, the system displays particular computer code (e.g., in one or more different programming language) that the system has generated. A user may place the generated code on a webpage or other location that the user desires to collect consent.

Repository of Application Privacy Analysis Data

An application privacy analysis system, in various embodiments, is configured to provide a data-storage repository (e.g., one or more servers, databases, etc.) for the storage of application privacy analysis data for one or more particular software applications (e.g., one or more mobile device software applications). In particular embodiments, the application privacy analysis data repository may enable the system to populate one or more data models (e.g., using one or more suitable techniques described above) substantially on-the-fly (e.g., as the system generates, collects, processes, stores, etc. application privacy analysis data regarding a particular application). In this way, in particular embodiments, the system is configured to maintain a substantially up-to-date data model for a plurality of applications (e.g., each particular application for which the system generates, collects, processes, stores, etc. application privacy analysis data). The system may then be configured to substantially automatically respond to one or more data access requests by one or more systems and devices, for example, using the substantially up-to-date data model. In particular embodiments, the system may be configured to respond to the one or more data access requests using any suitable technique described herein.
As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. for which data regarding the collection and storage of personal data or personal information by applications operating on data subject devices or consumer devices may be of use. Application developers may not readily or reliably provide personal data or personal information access and/or collection capability information about their applications. In some embodiments, an application privacy analysis system may analyze applications to determine the personal data and/or personal information collection capabilities of such applications. An application privacy analysis system may also analyze software applications to determine how each application accesses, requests, access to, or otherwise collects any information that may be personal and/or private to a data subject or consumer. For example, an application privacy analysis system may analyze an application to determine the device component access permissions that the application requires or requests, such as permissions to access device hardware (e.g., camera, microphone, receiver, transmitter, etc.) and/or permissions to access device data (contacts, calendar, location, photos, etc.). An application privacy analysis system may also, or instead, analyze an application to determine the device storage, if any, that the application may require and/or request access to (e.g., shared data, application database, key data, device data, etc.). The results of such analysis may be stored in a data repository. Utilizing and maintaining a data repository for application privacy analysis data may enable the system to quickly and accurately respond to requests related to mobile application privacy analysis data. In particular embodiments, the application privacy analysis repository may include one or more third party data repositories (e.g., one or more third party data repositories maintained on behalf of a particular entity that generates, collects, stores, and/or processes application privacy analysis data).
In various embodiments, an application privacy analysis system is configured to facilitate the analysis of applications (e.g., mobile device applications), the generation of application privacy analysis data, and the storage of mobile application privacy analysis data for each of a plurality of applications. In particular embodiments, the system may be configured to: (1) receive or otherwise acquire an application; (2) analyze the application to determine its privacy-related attributes; and (3) store application privacy analysis data in a suitable data format (e.g., a data model, a reference table, etc.) for later retrieval. In particular embodiments, privacy-related attributes may include device component access and/or storage permissions that an application may require or request. Privacy-related attributes may also include recipients of personal data, personal information, and/or other data collected by a software application. Privacy-related attributes may also include specific personal information, types of personal information, and/or any indicators thereof.
In particular embodiments, the system may be configured to statically analyze an application by, for example: (1) loading the application (e.g., acquiring the application software and storing it into a computer memory); (2) determining specific identifying information for the application; (3) determining whether information about the application's privacy-related attributes is available in a database; (4) if information about the application's privacy-related attributes is available in the database, using that information to determine application privacy analysis data for that application; and (5) digitally storing the application privacy analysis data in one or more suitable data stores. In particular embodiments, the system is configured to store the application privacy analysis data associated with a particular application in association with a unique application identifier. The system may store specific identifying information for an application and associate such information with the unique application identifier. The system may include the application's name, publisher, version number, serial code, any other identifying data, or any combination thereof as identifying information for the application. The system may perform searches based on such identifying information, including performing searches using hashing. The system may set and/or transmit a flag or other indicator indicating that the application should be dynamically analyzed. The system may determine to set and/or transmit such a flag based on a failure to locate the application in a database of application privacy analysis data or for any other reason.
In particular embodiments, the system may be configured to dynamically analyze an application by, for example: (1) loading the application (e.g., acquiring the application software and storing it into a computer memory); (2) executing the application and providing, as input to the application, test, or “dummy” data to initiate communications between the application and any other devices or systems; (3) inspecting communications data (e.g., network traffic) exchanged between the application and any other devices or systems; (4) determining the privacy-related attributes and/or characteristics of the inspected communications data to generate application privacy analysis data; and (5) digitally storing the application privacy analysis data in one or more suitable data stores. In particular embodiments, the system is configured to store the application privacy analysis data associated with a particular application in association with a unique application identifier. The system may store specific privacy-related attributes and/or characteristics determined based on dynamic analysis of a particular application and associate such information with the associated unique application identifier. The system may include, as such specific privacy-related attributes and/or characteristics of a dynamically analyzed application, one or more geographic locations (city, county, state, country, zip code, etc.), identities, IP addresses, MAC addresses, and/or other network addresses of other systems and devices with which the application is in communication. Specific privacy-related attributes and/or characteristics determined based on inspected communications may also include one or more types of personal data being sent to other systems and devices with which the application is in communication, as well as any information received from such other systems and devices. Specific privacy-related attributes and/or characteristics determined based on inspected communications may also include one or more types of data elements and/or one or more specific data elements exchanged with other systems and devices with which the application is in communication

Exemplary Application Privacy Analysis System Architecture

FIG. 55 is a block diagram of an Application Privacy Analysis System 5500 according to a particular embodiment. In various embodiments, the Application Privacy Analysis System 5500 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 organization and be configured to aid in compliance with one or more laws, regulations, or policies related to the collection, transmission, and storage of personal data or personal information. In various other embodiments, the Application Privacy Analysis System 5500 is a stand-alone system that is configured to analyze software applications, such as software applications that are executed on a laptop or desktop computer or on a portable computing device such as a smartphone. Analyzed applications may be applications created by one or more third party application developers, may be provided by one or more application provider servers or other systems, and may be installed on one or more remote devices. The Application Privacy Analysis System 5500 may generate privacy-related information about the capabilities of such applications and may maintain a centralized database of privacy-related application capability information and privacy-related attributes and/or characteristics for such applications.
As may be understood from FIG. 55 , the Application Privacy Analysis System 5500 includes One or More Computer Networks 115 (for example, as described herein in regard to FIG. 1 ), One or More Application Privacy Analysis Data Repository Servers 5510, an Application Privacy Scanning Server 5520, One or More Third Party System Servers 5530, One or More Databases 140 (for example, as described herein in regard to FIG. 1 ) or other data structures, and One or More Remote Data Subject Computing Devices 5550 (e.g., a smartphone, desktop computer, laptop computer, tablet computer, etc. Although in the embodiment shown in FIG. 55 , the One or More Application Privacy Data Repository Servers 5510, Application Privacy Scanning Server 5520, One or More Third Party System Servers 5530, One or More Databases 140 or other data structures, and One or More Remote Data Subject Computing Devices 5550 are shown as separate entities, it should be understood that in other embodiments, one or more of these servers, computing devices, and/or entities may comprise a single server, a plurality of servers, one or more cloud-based servers, or any other suitable configuration.
In particular embodiments, the One or More Application Privacy Analysis Data Repository Servers 5510 may be configured to store information generated by the Application Privacy Scanning Server 5520, for example storing such information at One or More Databases 140. The Application Privacy Scanning Server 5520 may acquire an application from the One or More Third Party System Servers 5530 and may store, process, execute, and/or analyze such an application as described herein to generate privacy-related capability information for the application. The One or More Application Privacy Analysis Data Repository Servers 5510 and the One or More Third Party System Servers 5530 may, for example, interface via a suitable application programming interface (API), direct connection, etc. The Application Privacy Scanning Server 5520 may, alternatively, acquire an application from the One or More Remote Data Subject Computing Devices 5550 and may store, process, execute, and/or analyze such an application as described herein to generate privacy-related capability information for the application. The One or More Application Privacy Analysis Data Repository Servers 5510 and the One or More Remote Data Subject Computing Devices 5550 may, for example, interface via a suitable application programming interface, direct connection, etc. The Application Privacy Scanning Server 5520 may store generated privacy-related capability information for an application for later retrieval, for example, at the One or More Application Privacy Data Repository Servers 5510. The One or More Application Privacy Analysis Data Repository Servers 5510 and the Application Privacy Scanning Server 5520 may, for example, interface via a suitable application programming interface, direct connection, etc. In a particular embodiment, the Application Privacy Scanning Server 5520 may incorporate the One or More Application Privacy Data Repository Servers 5510.
In a particular example, the One or More Remote Data Subject Computing Devices 5550 may provide an application, or an indication of an application, configured on the One or More Remote Data Subject Computing Devices 5550, to the Application Privacy Scanning Server 5520. Alternatively, the Application Privacy Scanning Server 5520 may acquire information regarding an application via other means, such as directly from the One or More Third Party System Servers 5530 that may provide the application, and acquire the application using such information. The system may, upon retrieval or receipt of an application at the Application Privacy Scanning Server 5520, analyze the application to generate privacy-related capability information (e.g., specific privacy-related attributes and/or characteristics) for the application and transmit data representing the privacy-related capability information for the application to the One or More Application Privacy Data Repository Servers 5510. The One or More Application Privacy Analysis Data Repository Servers 5510 may process such data and/or may store such data in a centralized data storage location (e.g., at the One or More Databases 140, the One or More Application Privacy Data Repository Servers 5510, etc.).

Exemplary Application Privacy Analysis System

FIG. 56 is a block diagram of an exemplary Application Privacy Analysis System 5600 according to a particular embodiment. Note that the functions, modules, and components of the Application Privacy Analysis System 5600 may be implemented in conjunction with, encompassing, or as part of any other disclosed systems and devices, such as the Application Privacy Analysis System 5500. The Application Privacy Analysis System 5600 may be 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 organization and be configured to aid in compliance with one or more laws, regulations, and/or policies related to the collection, transmission, and storage of personal data and/or personal information. In various other embodiments, the Application Privacy Analysis System 5600 may be a stand-alone system that is configured to analyze applications created by one or more third party application developer and/or provider servers or other systems and installed on one or more remote devices, generate privacy-related information about the capabilities of such applications (e.g., determine privacy-related attributes and/or characteristics of such applications), and maintain a centralized database of privacy-related application capability information.
The Application Privacy Analysis System 5600 may have an App Intake Module 5610 that may load or otherwise prepare a software application (e.g., a mobile device application or other software application) for analysis and/or execution. The Application Privacy Analysis System 5600 may acquire an application from a third-party system that hosts, generates, or otherwise provides the application. The Application Privacy Analysis System 5600 may use identifying information about an application that it obtained from a data subject computing device or a consumer computing device to acquire the application from a third-party system that hosts, generates, or otherwise provides the application. In an alternative embodiment, the Application Privacy Analysis System 5600 may acquire an application from a data subject computing device or a consumer computing device itself.
The Application Privacy Analysis System 5600 may include a Decompiler Module 5620 that may deconstruct an acquired application for analysis. The Decompiler Module 5620 can reduce the application to source code, assembly language, machine code, and/or some other interpretation of the functions of the application, or an approximation thereof. The Application Privacy Analysis System 5600 may have a Static Analysis Module 5630 that may use the output of the Decompiler Module 5620 to perform analysis of the application based on the application code or the approximation of the application code. The Static Analysis Module 5630 scans the application code for various privacy-related attributes and/or characteristics. For example, the Static Analysis Module 5630 may scan the application code to determine whether the application collects, requests, or otherwise attempts to access personal data and/or personal information.
The Static Analysis Module 5630 may also, or instead, scan the application code to determine whether and how the code may use permissions to gain access to one or more device components (e.g., access to a camera, microphone, contacts, calendar, photographs, location, etc.) and device storage (e.g., encrypted storage, unencrypted storage, an application database, key/chain and/or other authentication information (e.g., private key information, public key information, blockchain information, etc.), any storage that may be configured with personal data and/or personal information, storage preferences, etc.). The Static Analysis Module 5630 may also scan the application code to determine whether and how the code may share application-generated data or data subject computing device originated data (e.g., personal information) with other remote and or local entities (e.g., other applications, other systems, web services, etc.). Where any data is shared, the Static Analysis Module 5630 also attempts to determine where such data is being sent. For example, the Static Analysis Module 5630 may determine a geographical destination location, such as a city, county, state, country, zip code, etc. Alternatively, or in the process of determining a geographical destination, the Static Analysis Module 5630 may determine a destination network address, such as an IP addresses, a MAC address, other network address, network identifier, etc. Upon determining a destination network address for data shared by the application, the system may use that network address to determine a geographical location, for example, by using network look-up techniques that associate network addresses with geographical locations.
In various embodiments, the Static Analysis Module 5630 may scan the application code to determine any application programming interface (API) calls that are made by the code. The system may analyze such API calls to determine the mobile application's access to, and use of, various privacy-related attributes and/or characteristics. For example, the Static Analysis Module 5630 may analyze the API calls to determine whether the application collects, requests, or otherwise attempts to access personal data and/or personal information, the permissions the application requests and/or has been granted, the data that the application has access to on the mobile device, the components or hardware which the application has access, etc.
In various embodiments, the Application Privacy Analysis System 5600 may use a determined geographical destination of shared data to determine potentially applicable privacy laws and regulations. For example, the Application Privacy Analysis System 5600 may determine that data is being sent to Europe and may then determine that the GDPR is applicable to this data transfer. In another example, the Application Privacy Analysis System 5600 may determine that data is being sent to California and may then determine that the California Consumer Privacy Act (CCPA) is applicable to this data transfer. The Application Privacy Analysis System 5600 may also, or instead, use a location of the mobile device executing the application to determine applicable laws and regulations. The system, based on a location of the mobile device executing the application and/or a destination of data being transmitted by the application, may take corresponding actions and generated records related to privacy law and regulation compliance as described herein.
In an embodiment, the Application Privacy Analysis System 5600 may have a Dynamic Analysis Module 5640 that may perform analysis of the application as the application executes. The Dynamic Analysis Module 5640 inspects the communications data and metadata (e.g., network traffic) transmitted and received by the application for privacy-related attributes and/or characteristics. For example, the Dynamic Analysis Module 5640 may inspect communications data and metadata originating from the application and/or directed to the application to determine whether this data includes any personal data or personal information. The Dynamic Analysis Module 5640 may also inspect the communications data and metadata to determine whether such data indicates how device storage is accessed and protected (e.g., encrypted storage, unencrypted storage, an application database, key/chain and/or other authentication information (e.g., private key information, public key information, blockchain information, etc.), storage preferences, etc.). The Dynamic Analysis Module 5640 may also inspect the communications data and metadata to determine whether and how the application is sharing application-generated data or data subject computing device originated data with other remote and or local entities (e.g., other applications, other systems, web services, etc.). The Dynamic Analysis Module 5640 may also determine where any shared data is being sent (e.g., a destination geographical location, such as a city, county, state, country, zip code, etc., and/or a network destination, such as an IP addresses, a MAC addresses, other network address, network identifier, etc.). The Dynamic Analysis Module 5640 may also determine whether and how any data elements are being used based on the communications data. To perform this dynamic analysis, the Dynamic Analysis Module 5640 may feed data (e.g., “dummy” data) to the application as it executes the application and analyzes the output of the application using any of various means, such as network and device diagnostic tools, traffic sniffers, traffic analysis tools, etc.
In an embodiment, the Application Privacy Analysis System 5600 may have, or may access, one or more Third-Party Software Development Kit (SDK) Databases 5650 that contain information about known development tools that may have been used to develop the application under analysis. Such Third-Party SDK Databases 5650 may also, or instead, contain information about the application itself. The Application Privacy Analysis System 5600 may determine a source for the SDK, such as a platform, creator, or provider of the SDK (e.g., FACEBOOK, GOOGLE, etc.) Upon determining or obtaining identifying information about the application under analysis, the Application Privacy Analysis System 5600 may use such information to query the Third-Party SDK Databases 5650 for privacy-related information about the application. The Application Privacy Analysis System 5600 may perform such one or more queries during static analysis, dynamic analysis, or both. For example, either or both of the Static Analysis Module 5630 and the Dynamic Analysis Module 5640 may query the Third-Party SDK Databases 5650 for privacy-related information about the application under analysis. In a particular embodiment, the Static Analysis Module 5630 may query the Third-Party SDK Databases 5650 for privacy-related information about the application under analysis and, based upon the results of such one or more queries, the Static Analysis Module 5630 may set a flag or provide some other indication that the Dynamic Analysis Module 5640 should analyze the application.
In an embodiment, the Application Privacy Analysis System 5600 may have, or may access, a Privacy Analysis Database 5660 in which it may store the results of the analysis of the application. The Application Privacy Analysis System 5600 may store all, or any subset of, results of the analyses performed by either or both of the Static Analysis Module 5630 and the Dynamic Analysis Module 5640, any related data, and any representations and indications of such results and data at the Privacy Analysis Database 5660. In a particular embodiment, the Application Privacy Analysis System 5600 generates one or more scores associated with the risk, privacy characteristic, and/or reputation of an application that it has analyzed. In another embodiment, the Application Privacy Analysis System 5600 generates one or more recommendations associated with the risk, privacy characteristic, and/or reputation of an application that it has analyzed. Such scores and recommendations may also be stored at the Privacy Analysis Database 5660.
The system may present a score for an application and may present rankings of multiple scores and respective applications, for example, using a graphical user interface, to allow a user to view the relative privacy assessments of several applications on one interface. The system may highlight or color code such rankings to indicate application privacy capabilities and risk. For example, an application that obtains a high-risk score (e.g., collects and transmits personal data, attempts to modify storage) may be highlighted in bright red and/or listed above lower risk applications, while an application that has a low risk score (e.g., does not access personal data, does not request permission to modify storage) may be highlighted in green and/or listed below higher risk applications.

Exemplary Static Privacy Analysis System

A more detailed static privacy analysis system example will now be described. FIG. 57 is a block diagram of a Static Privacy Analysis System 5700 according to a particular embodiment. Note that the functions, modules, and components of the Static Privacy Analysis System 5700 may be implemented in conjunction with, encompassing, or as part of any other disclosed systems and devices, such as the Application Privacy Analysis System 5500 and the Application Privacy Analysis System 5600. In various embodiments, the Static Privacy Analysis System 5700 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 organization and be configured to aid in compliance with one or more legal or industry regulations related to the collection, transmission, and storage of personal data. In various other embodiments, the Static Privacy Analysis System 5700 is a stand-alone system that is configured to analyze applications created by one or more third party application developer and/or provider servers or other systems and installed on one or more remote devices, generate privacy-related information about the capabilities of such applications, and maintain a centralized database of privacy-related application capability information.
The Static Privacy Analysis System 5700 may analyze an Application 5710, which may be, in an example, a decompiled Application 5710. The decompiled Application 5710 may include application source code, associated assembly language, associated machine code, or any other interpretation of the functions, inputs, and outputs of the application 5710, or any approximation thereof. The Static Privacy Analysis System 5700 may also analyze a Third-Party SDK 5715 used to generate Application 5710. The Static Privacy Analysis System 5700 may determine one or more Third-Party SDKs 5715 used to generate Application 5710 by using identifying information for Application 5710 to query Third-Party SDK Databases 5720, for example, as described herein in regard to other embodiments.
The Static Privacy Analysis System 5700 scans the application 5710 and Third-Party SDK 5715 for various privacy-related functions, attributes, and characteristics. For example, the Static Privacy Analysis System 5700 may determine, based on the decompiled Application 5710, whether the application 5710 references any personal data or personal information. The Static Privacy Analysis System 5700 also determines how application 5710 and Third-Party SDK 5715 interact with an Operating System (OS) 5730. In a particular embodiment, OS 5730 may be any operating system that may be used on a computing device, such as any computing device of any Data Subject 5701. For example, OS 5730 may be an OS of a smartphone, desktop computer, laptop computer, tablet computer, etc.
The Static Privacy Analysis System 5700 scans the application 5710 and Third-Party SDK 5715 for to determine whether and how the application 5710 and Third-Party SDK 5715 may use or access Device Component Privacy Permissions 5732 (e.g., permissions for access to a camera, microphone, photographs, location, calendar, contacts, etc.) and Device Storage 5734 (e.g., shared storage, an application database, key/chain and/or other authentication information (e.g., private key information, public key information, blockchain information, etc.), advertising identifiers and related settings, encrypted storage, unencrypted storage, storage preferences, etc.). The Static Analysis Module 5700 may also scan the application 5710 and Third-Party SDK 5715 to determine whether and how the application may call, or be configured as, an “open into” application that executes within another application (e.g., allowing the application to operate under the permissions of another application). The Static Analysis Module 5700 may also analyze API calls made by the application 5710 and/or Third-Party SDKs 5715 to determine any access to, and use of, various privacy-related attributes and/or characteristics.
In various embodiments, the Static Analysis Module 5700 may also analyze API calls made by the application 5710 and/or Third-Party SDKs 5715, the permissions requested and/or granted to the application 5710 and/or Third-Party SDKs 5715, and any other portions of the application 5710 and/or Third-Party SDKs 5715 to determine whether and to where any data may be transmitted by the application 5710. The system may use this geographical information to determine the applicable laws and regulation and take corresponding actions as described herein.
In a particular embodiment, the Static Privacy Analysis System 5700 may determine, based on the results of the analysis of the application 5710 and Third-Party SDK 5715, that the application requires additional analysis, for example, dynamic privacy analysis. In such an embodiment, the Static Privacy Analysis System 5700 may set a flag or provide some other indication to a privacy analysis system or module that dynamic privacy analysis is needed for the application.
In an embodiment, the Static Privacy Analysis System 5700 may have, or may access, a Privacy Analysis Database 5760 in which it may store the results of the static analysis of the application. The Static Privacy Analysis System 5700 may store all, or any subset of, results of its analysis, data elements used by Application 5710, any related data, and any representations and indications of such results and data at the Privacy Analysis Database 5760. In a particular embodiment, the Static Privacy Analysis System 5700 generates one or more scores associated with the risk, privacy characteristic, and/or reputation of an application that it has analyzed. In another embodiment, the Static Privacy Analysis System 5700 generates one or more recommendations associated with the risk, privacy characteristic, and/or reputation of an application that it has analyzed. Such scores and recommendations may also be stored at the Privacy Analysis Database 5760.
The system may present a score or recommendation for an application based on the analysis performed by the Static Privacy Analysis System 5700, and may present rankings of multiple scores/recommendations and respective applications, for example, using a graphical user interface, to allow a user to view the relative privacy assessments of several applications on one interface. The system may highlight or color code such rankings to indicate application privacy capabilities and risk. For example, an application that obtains a high risk score (e.g., collects and transmits personal data, attempts to modify storage) may be highlighted in bright red and/or listed above lower risk applications, while an application that has a low risk score (e.g., does not access personal data, does not request permission to modify storage) may be highlighted in green and/or listed below higher risk applications.

Exemplary Dynamic Privacy Analysis System

A more detailed dynamic privacy analysis system example will now be described. FIG. 58 is a block diagram of a Dynamic Privacy Analysis System 5800 according to a particular embodiment. Note that the functions, modules, and components of the Dynamic Privacy Analysis System 5800 may be implemented in conjunction with, encompassing, or as part of any other disclosed systems and devices, such as the Application Privacy Analysis System 5500 and the Application Privacy Analysis System 5600. In various embodiments, the Dynamic Privacy Analysis System 5800 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 organization and be configured to aid in compliance with one or more laws, regulations, and/or policies related to the collection, transmission, and storage of personal data. In various other embodiments, the Dynamic Privacy Analysis System 5800 is a stand-alone system that is configured to analyze applications created by one or more third party application developer and/or provider servers or other systems and installed on one or more remote devices, generate privacy-related information about the capabilities of such applications, and maintain a centralized database of privacy-related application capability information.
In an embodiment, the Dynamic Privacy Analysis System 5800 may analyze an Application 5810 by executing the application and providing Test Data 5830 (e.g., “dummy data”) as input 5831 to Application 5810. Test Data 5830 may simulate data associated with a data subject, such as Data Subject 5801. Test Data may include any personal data or personal information (e.g., first name and last name, first initial and last name, credit card number, bank account number, other financial account number, social security number, phone number, address, etc.) Application 5810 may be executed using a Network Proxy 5820 and output from the Application 5810 may be inspected using a Traffic Inspection Module 5840. Traffic Inspection Module 5840 may be any network or device diagnostic tool, such as a traffic sniffer, a traffic analysis tool, etc.
The Dynamic Privacy Analysis System 5800 inspects the communications data and metadata (e.g., network traffic) generated as output 5811 by the application 5810 and communications data and metadata 5871 received by, or directed to, the application 5810 for privacy-related data and attributes. For example, the Dynamic Privacy Analysis System 5800 may inspect output 5811 and communications data and metadata 5871 to determine whether this data includes any personal data or personal information. The Dynamic Privacy Analysis System 5800 may further inspect output 5811 and communications data and metadata 5871 to determine whether this data indicates whether and how device component permissions are set on a data subject computing device (e.g., permissions for access to a camera, microphone, contacts, calendar, photographs, location, etc.). The Dynamic Privacy Analysis System 5800 may also inspect the communications data and metadata to determine whether such data indicates how device storage is accessed and protected (e.g., encrypted storage, unencrypted storage, an application database, key/chain and/or other authentication information, storage preferences, etc.).
In a particular embodiment, the Dynamic Privacy Analysis System 5800 may inspect output 5811 and/or communications data and/or metadata 5871, for example being exchanged via Internet 5870, to determine whether and how the application is sharing application-generated data or data subject computing device originated data (e.g., personal data) with other remote and/or local entities (e.g., other applications, other systems, web services, etc.). For example, the Dynamic Privacy Analysis System 5800 may determine whether traffic from the Application 5810 is being sent to and/or received from Third-Party Web Service 5880 and/or being sent to and/or received from Application Web Service 5890. Either or both of the Third-Party Web Service 5880 and the Application Web Service 5890 may be associated with Application 5810. The Dynamic Privacy Analysis System 5800 may also determine where any shared data is being exchanged with the Application 5810 (e.g., a destination geographical location, such as a city, county, state, country, zip code, etc., and/or a network destination, such as an IP addresses, a MAC addresses, other network address, network identifier, etc.). The Dynamic Privacy Analysis System 5800 may also determine whether and how any data elements are being used based on the communications data.
In various embodiments, upon determining a geographical or jurisdictional destination for output 5811 and/or communications data and metadata 5871, the Dynamic Privacy Analysis System 5800 may use this geographical information to determine the applicable laws and regulation and take corresponding actions as described herein.
In a particular embodiment, the Dynamic Privacy Analysis System 5800 scans the application 5810 to determine information that the Dynamic Privacy Analysis System 5800 can use to query a Third-Party SDK Database 5860 to identify any one or more Third-Party SDKs that may have been used to generate the Application 5810. The Dynamic Privacy Analysis System 5800 can then use such SDK-related information to determine how to more effectively analyze communications data and metadata exchanged by the Application 5810. The Dynamic Privacy Analysis System 5800 may also analyze the communications data and metadata exchanged by the Application 5810 to determine whether and how the Application 5810 may call, or be configured as, an “open into” application that executes within another application (e.g., allowing the application to operate under the permissions of another application).
In an embodiment, the Dynamic Privacy Analysis System 5800 may have, or may access, a Privacy Analysis Database 5850 in which it may store the results of the static analysis of the application. The Dynamic Privacy Analysis System 5800 may store all, or any subset of, results of its analysis, data elements used by Application 5810, any related data, and any representations and indications of such results and data in the Privacy Analysis Database 5850. In a particular embodiment, Dynamic Privacy Analysis System 5800 generates one or more scores associated with the risk, privacy characteristic, and/or reputation of an application that it has analyzed. In another embodiment, the Dynamic Privacy Analysis System 5800 generates one or more recommendations associated with the risk, privacy characteristic, and/or reputation of an application that it has analyzed. Such scores and recommendations may also be stored at the Privacy Analysis Database 5850.
The system may present a score or recommendation for an application based on the analysis performed by the Dynamic Privacy Analysis System 5800, and may present rankings of multiple scores/recommendations and respective applications, for example, using a graphical user interface, to allow a user to view the relative privacy assessments of several applications on one interface. The system may highlight or color code such rankings to indicate application privacy capabilities and risk. For example, an application that obtains a high risk score (e.g., collects and transmits personal data, attempts to modify storage) may be highlighted in bright red and/or listed above lower risk applications, while an application that has a low risk score (e.g., does not access personal data, does not request permission to modify storage) may be highlighted in green and/or listed below higher risk applications.

Privacy Analysis Module

FIG. 59 depicts a Privacy Analysis Module 5900 according to a particular embodiment.
Various functionality of the Application Privacy Analysis System 5500, the Application Privacy Analysis System 5600, the Static Privacy Analysis System 5700, and the Dynamic Privacy Analysis System 5800 may be implemented via a Privacy Analysis Module 5900. The system, when executing certain steps of the Privacy Analysis Module 5900, may be configured to analyze applications created by one or more third party application developer and/or provider servers or other systems and installed on one or more remote devices, generate privacy-related information about the capabilities of such applications, and generate and maintain a centralized database of privacy-related application capability information. In particular embodiments, the system may be configured to index the privacy-related application capability information within the central repository by application function, application developer, application owner, or any other criteria.
A privacy analysis system, when executing the Privacy Analysis Module 5900, begins, at Step 5910, by receiving or acquiring an application (e.g., a mobile device application) for analysis. The Privacy Analysis Module 5900 may request an application from an application developer or provider, or from a data subject computing device, and may receive the application via any means. In particular embodiments, the Privacy Analysis Module 5900 may receive an instruction or request to perform privacy analysis on an application and may responsively acquire or request the application from a third-party application developer or provider system. The Privacy Analysis Module 5900, or any system operating such a module, can use identifying information about an application that it obtained from a data subject computing device or a consumer computing device to acquire the application from the third-party system that hosts, generates, or otherwise provides the application. In an alternative embodiment, the Privacy Analysis Module 5900 may acquire an application from a data subject computing device or a consumer computing device itself
At Step 5920, the Privacy Analysis Module 5900 may have, or may access, one or more Third-Party SDK Databases that contain information about known development tools that may have been used to develop the application under analysis. Such Third-Party SDK Databases may also, or instead, contain information about the application itself. Upon determining or obtaining identifying information about the application under analysis, for example, at Step 5910, the Privacy Analysis Module 5900 may use such information to query the Third-Party SDK Databases for privacy-related information about the application. The Privacy Analysis Module 5900 may perform such one or more queries prior to, during, or after performing the steps of Static Privacy Analysis 5930, Dynamic Privacy Analysis 5940, or both. For example, before, during, or after performing either or both of Static Privacy Analysis 5930 and Dynamic Privacy Analysis 5940, the Privacy Analysis Module 5900 may query the Third-Party SDK Databases for privacy-related information about the application under analysis. Information obtained at Step 5920 may be used to facilitate either or both of Static Privacy Analysis 5930 and Dynamic Privacy Analysis 5940.
In an embodiment, the Privacy Analysis Module 5900 may perform Static Privacy Analysis 5930, by, at Step 5931, decompiling the application under analysis. The Privacy Analysis Module 5900 may deconstruct the application for analysis by reducing the application to source code, assembly language, machine code, or some other interpretation of the functions of the application, or an approximation thereof. At Step 5932, the Privacy Analysis Module 5900 performs static analysis of the application based on the decompiled application code or the approximation of the decompiled application code. Such static analysis may include the Privacy Analysis Module 5900 scanning the application code for various privacy-related functions and attributes. For example, the Privacy Analysis Module 5900 may scan the application code to determine whether and how the code may reference, access, collect, transmit, receive, and/or manipulate any personal data or personal information. The Privacy Analysis Module 5900 may also scan the application code to determine whether and how the code may use permissions to access device components (e.g., access to a camera, microphone, contacts, calendar, photographs, location, etc.) and device storage (e.g., encrypted storage, unencrypted storage, an application database, key/chain and/or other authentication information, storage preferences, etc.). The Privacy Analysis Module 5900 may also scan the application code to determine whether any API calls are made and how those call interact with the executing device and its associated storage, components, permissions, and any data located therein.
The Privacy Analysis Module 5900 may also scan the application code to determine whether and how the code may share application-generated data or data subject computing device originated data with other remote and or local entities (e.g., other applications, other systems, web services, etc.). Where the Privacy Analysis Module 5900 determines that data is shared, the Privacy Analysis Module 5900 attempts to determine where such data is being sent (e.g., a destination geographical location, such as a city, county, state, country, zip code, etc., and/or a network destination, such as an IP addresses, a MAC addresses, other network address, network identifier, etc.) The Privacy Analysis Module 5900 may use destination geographical information to determine the applicable laws and regulation and take corresponding actions as described herein.
In a particular embodiment, the Privacy Analysis Module 5900 may set a flag or provide some other indication that a dynamic analysis should be performed for the application, for example, based upon the results of the analysis of Step 5932 and/or based on results of queries made to Third-Party SDK Databases for privacy-related information about the application under analysis.
In an embodiment, the Privacy Analysis Module 5900 may perform Dynamic Privacy Analysis 5940, by, at Step 5941, executing the application and providing it test data (e.g., “dummy” input traffic”). The Privacy Analysis Module 5900, at Step 5942, inspects the communications data and metadata (e.g., network traffic) transmitted and received by the application for privacy-related data and attributes (e.g., personal information). For example, the Privacy Analysis Module 5900 may inspect the communications data and metadata to determine whether such data includes any personal data or personal information. The Privacy Analysis Module 5900 may also inspect the communications data and metadata to determine whether this data indicates whether and how device component access permissions are set on a data subject computing device (e.g., permissions for access to a camera, microphone, contacts, calendar, photographs, location, etc.). The Privacy Analysis Module 5900 may also inspect the communications data and metadata to determine whether such data indicates how device storage is accessed and protected (e.g., encrypted storage, unencrypted storage, an application database, key/chain and/or other authentication information, storage preferences, etc.). The Privacy Analysis Module 5900 may also inspect the communications data and metadata to determine whether and how the application is sharing application-generated data or data subject computing device originated data with other remote and or local entities (e.g., other applications, other systems, web services, etc.). The Privacy Analysis Module 5900 may also determine where any shared data is being sent (e.g., a destination geographical location, such as a city, county, state, country, zip code, etc., and/or a network destination, such as an IP addresses, a MAC addresses, other network address, network identifier, etc.). The Privacy Analysis Module 5900 may also determine whether and how any data elements are being used based on the communications data. In performing this dynamic analysis, the Privacy Analysis Module 5900 analyze the output of the application using any of various means, such as network and device diagnostic tools, traffic sniffers, traffic analysis tools, etc.
The Privacy Analysis Module 5900, at Step 5950, may generate privacy analysis data based on one or both of Static Privacy Analysis 5930 and Dynamic Privacy Analysis 5940. In a particular embodiment, the Privacy Analysis Module 5900 may generate one or more scores associated with the risk, privacy characteristic, and/or reputation of an application that it has analyzed. In another embodiment, the Privacy Analysis Module 5900 may generate one or more recommendations associated with the risk, privacy characteristic, and/or reputation of an application that it has analyzed.
At Step 5960, the Privacy Analysis Module 5900 may store the results of its analysis of the application and any associated data, such as scores and recommendations based on the analysis. The Privacy Analysis Module 5900 may store all, or any subset of, the results of the Static Privacy Analysis 5930 and Dynamic Privacy Analysis 5940, any related data, and any representations and indications of such results and data at a privacy analysis database. Such a privacy analysis database may be any database or other storage device or system, whether local, remote, first-party, third-party, etc.
Further at Step 5960, the system may present a score or recommendation for an application based on the analysis performed by the Privacy Analysis Module 5900, and may present rankings of multiple scores/recommendations and respective applications, for example, using a graphical user interface, to allow a user to view the relative privacy assessments of several applications on one interface. The system may highlight or color code such rankings to indicate application privacy capabilities and risk. For example, an application that obtains a high-risk score (e.g., collects and transmits personal data, attempts to modify storage) may be highlighted in bright red and/or listed above lower risk applications, while an application that has a low-risk score (e.g., does not access personal data, does not request permission to modify storage) may be highlighted in green and/or listed below higher risk applications. SDK Discovery and Assessment System
To ensure compliance with privacy regulations and/or standards, an entity may take one or more steps to determine the privacy and/or security impact of data and/or software installed on computing devices that the entity may control and/or interact with. For example, an entity may interact with and/or engage in the use of various types of tracking tools (e.g., cookies). Tracking tools may make collect and/or process privacy-related data (e.g., personal data, PII, etc.). Tracking tools may also, or instead, perform functions that have privacy implications, such as tracking a user's activities, location, etc. In various embodiments, the disclosed systems may analyze and assess (e.g., score, categorize, etc.) data and/or applications installed on a mobile device based on various privacy-related criteria and/or security-related criteria. In particular embodiments, the system may identify one or more particular software development kits (SDKs) used to develop a mobile application and apply the disclosed privacy and/or security assessment techniques to the identified one or more SDKs.
In various embodiments, the system may identify one or more software development kits (SDKs) configured on a mobile device and/or used to generate an application configured on the mobile device. Using natural language processing (NLP) artificial intelligence techniques, the system may generate a tokenized name for the SDK that includes tokens representing the vendor of the SDK and various functions performed by applications generated using the SDK. The system may determine scores for one or more such tokens and determine a privacy category or score for the SDK based on the token scores. The security and privacy impact of the particular identified SDK may be assessed based, at least in part, on one or more privacy and security impact determinations (e.g., scores, categorization, etc.) associated with the SDK and/or the SDK vendor.
In various embodiments, the system is configured to generate, access, and/or maintain a database of SDK and vendor information (e.g., an SDK and vendor information database or a third-party SDK database) that may include, but is not limited to: (1) SDK identifying information (e.g., package name); (2) vendor information for one or more SDKs; (3) privacy and/or security information (e.g., assessments, categorizations, scores, etc.) for one or more SDKs; (4) privacy and/or security information (e.g., assessments, categorizations, scores, etc.) for one or more functions of one or more SDKs; and (5) privacy and/or security information (e.g., assessments, categorizations, scores, etc.) for one or more vendors. Once a particular SDK is identified, the system may use this database to generate a privacy and/or security assessment of the identified SDK.
In various embodiments, the system is configured to identify one or more SDKs configured on a mobile device (e.g., Android-based mobile device, iPhone, etc.) by scanning one or more folders (e.g., all folders) on the mobile device for information that may be used to identify an SDK that may be configured on the mobile device. In scanning the mobile device, the system may identify one or more software packages (e.g., one or more software files, one or more collections of software files, individual software files, etc.) configured on the mobile device. In particular embodiments, the system may determine a name associated with one or more packages configured on the mobile device. The system may use regular expression (RegEx) searching techniques to search one or more databases (e.g., an SDK and vendor information database or a third-party SDK database) to cross-reference the names (or any portion of a name) of each such identified package with one or more known SDK packages. If the system determines that the name of an identified package corresponds to one or more known SDK packages, the system may determine that that particular identified package is a valid SDK package. If the system is unable to cross-reference the name of an identified package to one or more known SDK packages, the system may determine that that particular identified package is not a valid SDK package. The system may record this determination in an SDK and vendor information database for future reference.
The system may “tokenize” the name of a particular identified package, for example using NLP. In various embodiments, SDK package names may have a structure such as the following exemplary structure:

- <common_term>.<vendor_name>.<functionality>. <functionality> . . .
  where: (1) “common term” may be a term such as “com,” “io,” “net,” etc.; (2) “vendor name” may identify a vendor with terms such as “FACEBOOK,” “GOOGLE,” “ADOBE,” etc.; and (3) “functionality” may identify particular functionality with terms such as “auth,” “ads,” “internal,” “core,” etc. Each package name may have multiple functionality terms (e.g., <common_term>.<vendor_name>.<functionality>.<functionality>) to allow the indication of multiple functionalities associated with a particular SDK package.

The system may use a model to calculate a score for each of the SDK categories with which the particular identified package may be associated using the tokenized name of the package. In various embodiments, the system may remove or ignore the <common term> portion of the tokenized name in performing the scoring and/or categorization determinations described herein. In particular embodiments, the SDK categories may include categories such as advertisements, analytics, location, utilities, development tools, targeting, functional, etc. The system may identify a respective category for each identified <functionality> term based, at least in part, on a listing of one or more <functionality> terms and a corresponding SDK category for each term in the listing of <functionality> terms. In particular embodiments, such a functionality term categorization table may be stored in a database (e.g., an SDK and vendor information database or a third-party SDK database) and may have been generated for use by the system and/or by a third party as described herein.
In various embodiments, the system may assign a particular identified package to a particular (e.g., privacy) category that is associated with the highest scoring <functionality> term among the <functionality> terms in its tokenized package name. For example, if a particular identified package has functionality terms corresponding to the categories X, Y, and Z having respective SDK category scores of 10, 20 and 30 (e.g., category X has a score of 10, category Y has a score of 20, and category Z has a score of 30), the system will assign the category of Z to the identified package because Z's associated SDK category score is the highest of those associated with the identified package's functionality tokens. The system may also, or instead, assign or otherwise use the determined category score as a privacy risk score and/or a privacy assessment score for the package (e.g., assign a score of 30 to the package) and/or in calculating a privacy risk score and/or a privacy assessment score for the package.
In particular embodiments, the system may also apply weighting factors in the scoring process by adding a weight to key tokens or terms from each category. The system may then assign a particular identified package to a particular (e.g., privacy) category based on the score for the highest scoring weighted category associated with the particular identified package. For example, if a particular identified package has functionality terms corresponding to the categories P, Q, and R, with respective SDK category scores of 10, 20 and 30, but Q is weighted by 30 and the other categories are not, (e.g., category P has a weighted score of 10, category Q has a weighted score of 50, and category R has a weighted score of 30), the system will assign the category of Q to the identified package because Q's weighted SDK category score is the highest of those associated with the identified package's functionality tokens. The system may also, or instead, assign or otherwise use the determined weighted category score as a privacy risk score and/or a privacy assessment score for the package (e.g., assign a score of 50 to the package) and/or in calculating a privacy risk score and/or a privacy assessment score for the package.
In an illustrative example, the system may identify an SDK package with the name “io.segment.analytics.internal.” The system may then determine this SDK package name include the <functionality> terms “analytics” and “internal.” Based on these identified <functionality> terms and, in particular embodiments, reference to a functionality term categorization table, the system may determine that “analytics” is associated with the Targeting SDK category and “internal” is associated with the Functional SDK category. The system may then further determine (e.g., using a functionality term categorization table) that, within the Targeting SDK category, the term “analytics” is a key (e.g., weighted) token, while within the Functional SDK category, the term “internal” is not a key (e.g., not weighted) token. Therefore, based on this determination, the system may assign the category Targeting and/or the score associated with the Targeting SDK category to this SDK package because the term “analytics” is a key token within the Targeting SDK category (and not assign the classification and/or score associated with the Functional SDK category because the term “internal” is not a key token within the Functional SDK category).
In various embodiments, the system may determine that a category score for a particular identified package is inconclusive. For example, the system may be unable to determine a category associated with a particular identified package because none of the functionality tokens in the tokenized package name have assigned scores (e.g., in a functionality term categorization table or listing). The system may represent an inconclusive score as a null value or other value that the system is configured to recognize as an inconclusive score (e.g., “0,” “−1”). In this case, the system may use the <vendor name> from the tokenized package name to identify a vendor associated with the particular identified package. For example, the system may query a vendor database (e.g., an SDK and vendor information database) using the vendor name token to identify a particular vendor associated with the vendor name token. The system may then determine a category and/or generate a vendor score for the particular identified package based on that vendor information by, in particular embodiments, querying a vendor term categorization table that may be stored on an SDK and vendor information database using the vendor name token. In particular embodiments, the system may access a vendor term categorization table to determine a category for a vendor and/or a vendor score based on a vendor's name and/or other information. A vendor term categorization table may be stored in a database (e.g., an SDK and vendor information database or a third-party SDK database) and may have been generated for use by the system and/or by a third party as described herein.
In various embodiments, the system may determine a category score for a particular SDK as well as a vendor score based on vendor information. The system may then use the vendor score to determine, at least in part, an overall score for the particular identified package. In particular embodiments, the system may determine an overall score for the particular identified package based on a combination of a vendor score and a category score using a formula or algorithm and, in some examples, other available information. In other particular embodiments, the system may determine an overall score for the particular identified package based on only one of a vendor score or a category score. The system may then assign this score as a privacy risk score and/or privacy assessment score to the SDK and/or may use this score to determine a (e.g., privacy) category for the SDK. The system may also, or instead, use this overall score to determine a (e.g., privacy) category for the SDK.
A more detailed SDK discovery and assessment system example will now be described. FIG. 60 depicts an exemplary system 6000 for discovering and assessing one or more SDKs configured on a mobile device. In various embodiments, the SDK discovery and assessment server 6020 may be configured to communicate (e.g., wirelessly and/or using a wired connection) with the mobile device 6050. In particular embodiments, the mobile device 6050 may be an Android-based mobile device, while in other embodiments the mobile device 6050 may be any other type of mobile device using any other operating system software (e.g., iPhone).
The SDK discovery and assessment server 6020 may scan the mobile device 6050 to identify one or more files that may be SDK packages. For example, the SDK discovery and assessment server 6020 may scan each folder configured to store files on the mobile device 6050 to identify the names of each file stored in each such folder. The system may use any means of scanning and/or searching the files on the mobile device 6050, including accessing the mobile device 6050 using an API to perform a filename search or using operating system features configured on the mobile device 6050 to locate and identify files configured on mobile device 6050. In various embodiments, the SDK discovery and assessment server 6020 may undertake SDK package scanning and analysis in response to one or more instructions received from the one or more applications privacy analysis servers 6010, which may be performing one or more privacy analysis functions (e.g., as described herein) related to the mobile device 6050 and/or software configured thereon. In various embodiments, a privacy analysis system (e.g., the privacy analysis system 5600) may integrate one or more of the SDK package scanning and analysis functions disclosed herein. For example, SDK package scanning and analysis functions may be performed as part of, or in coordination with, any of the static analysis functions and/or dynamic analysis functions described above.
The SDK discovery and assessment server 6020 may identify one or more software packages (e.g., one or more software files, one or more collections of software files, individual software files, etc.) configured on the mobile device 6050. In particular embodiments, the system may determine a name associated with one or more packages configured on the mobile device 6050 by evaluating the file structure within which each such package may be stored. For example, as illustrated in FIG. 60 , the system may identify a “com” package located in folders 6051 that is associated with “vendor1” and has the functions “function1,” “function2,” and “function3.” The SDK discovery and assessment server 6020 may search (e.g., using RegEx and/or other searching techniques) the SDK and vendor information database 6040 and/or the third-party SDK database 6030 to cross-reference the identified package names (or any portion of the name) with one or more known SDK packages. If the SDK discovery and assessment server 6020 determines that the name of the identified package corresponds to one or more known SDK packages, the system may determine that that particular identified package is a valid SDK package. If the SDK discovery and assessment server 6020 is unable to cross-reference the name of the identified package to one or more known SDK packages, the system may determine that that particular identified package is not a valid SDK package. The system may record this determination in the SDK and vendor information database 6040 and/or provide the information to the one or more applications privacy analysis servers 6010 for future reference.
The SDK discovery and assessment server 6020 may tokenize the name of the identified package using NLP. In this particular example, the identified package name may be tokenized as “com.vendor1.function1.function2.function3,” where “com” represents a common system term associated with the package and/or its file system location, “vendor1” is an identifier of the vendor associated with the package, and each of “function1,” “function2,” and “function3” identify particular functionality of the package.
The SDK discovery and assessment server 6020 may categorize the identified package based on its associated functions by querying a functionality term categorization table to determine a category associated with one or more of the functionality terms in the package's tokenized name. In performing this categorization, the SDK discovery and assessment server 6020 may ignore or remove the common term in the tokenized package name. In various embodiments, the system may use a table (e.g., a functionality term categorization table) to identify the category associated with each functionality term. Such a table may be generated and/or stored at a system such as the SDK and vendor information database 6040 and/or the third-party SDK database 6030. Table 1 shown below is an illustrative example of a functionality term categorization table.

TABLE 1

Functionality term	Category	Score	Weight	Key term?

function1	Targeting		10	20	Yes
function2	Functional	20	0	No
function3	Location		15	5	Yes

The SDK discovery and assessment server 6020 may associate the categories associated with each functional term of the tokenize package name with the package. In the current example, the SDK discovery and assessment server 6020 may determine that the “com.vendor1.function1.function2.function3” package is associated with the “Targeting,” “Functional,” and “Location” categories based on the associations of its functional terms with those categories indicated in a functionality term categorization table. The system may then determine which of the categories associated with the package has a highest associated score. In the current example, the SDK discovery and assessment server 6020 may determine that the “Functional” category associated with the functional term “function2” has the highest score among the categories associated with package. Therefore, the SDK discovery and assessment server 6020 may assign the “Functional” category and/or the score corresponding to the “Functional” category (e.g., 20) to the “com.vendor1.function1.function2.function3” package.
In various embodiments, the system may also, or instead, use one or more weighting factors in the scoring process to determine a score for an identified package. In the current example, the SDK discovery and assessment server 6020 may determine that the “Functional” category associated with the functional term “function2” has the highest score among the categories associated with package but has a weighting of 0, thus giving that category a weighted score of 20. The system may also determine that the “Targeting” category associated with the functional term “functionl” has a score of 10 with a weighting of 20, thus giving that category a weighted score of 30. Therefore, because it has the highest weighted score of the associated categories, the SDK discovery and assessment server 6020 may assign the “Targeting” category and/or the weighted score corresponding to the “Targeting” category (e.g., 30) to the “com.vendor1.function1.function2.function3” package.
In various embodiments, the system may also, or instead, determine whether a functionality term within a tokenized package name is a key term in calculating a score for the package. In the current example, the SDK discovery and assessment server 6020 may determine that the “Targeting” category associated with the functional term “functionl” and the “Location” category associated with the functional term “function3” are key terms (e.g., as indicated in a functionality term categorization table or listing, such as Table 1). The system may make this determination based on an explicit indicator that a particular categories is a key category (e.g., an indicator that a category is associated with a functionality term that is a key term, as shown in Table 1) or based on implicit information, such as determining that a particular term has non-zero (or positive) weighting factor (also as shown in Table 1). In this particular example, because it has the highest weighted score among the applicable key categories, the SDK discovery and assessment server 6020 may assign the “Targeting” category, the score corresponding to the “Targeting” category, and/or the weighted score corresponding to the “Targeting” category (e.g., 30) to the “com.vendor1.function1.function2.function3” package.
In various embodiments, the SDK discovery and assessment server 6020 may determine that a category score for a particular identified package is inconclusive or may otherwise be unable to determine a category or score for a package. For example, the SDK discovery and assessment server 6020 may determine that there is no particular category associated with the identified package (e.g., none of its functionality terms are associated with a known category) or that there is no score available or determinable for the categories associated with the package (e.g., there are no scores available or determinable for any of its functionality terms). In the current example, if unable to determine a category score for the “com.vendor1.function1.function2.function3” package, the SDK discovery and assessment server 6020 may use the vendor name “vendorl” from the tokenized package name to identify a vendor and/or vendor category associated with the package. In particular embodiments, the SDK discovery and assessment server 6020 may determine the vendor score and/or category by querying a vendor database to access a vendor term categorization table (e.g., by querying the SDK and vendor information database 6040 and/or the third-party SDK database 6030 to access a table such as Table 2) to identify a vendor score and/or category associated with a particular vendor using the vendor name token. The SDK discovery and assessment server 6020 may then determine a score and/or category for the identified package by assigning the vendor score and/or category associated with “vendor1” to the identified package. In particular embodiments, the system may assign the determined category and/or score for “vendor1” as the privacy category and/or score, respectively, for the “com.vendor1.function1.function2.function3” package. A vendor term categorization table may be generated and/or stored in a database (e.g., the SDK and vendor information database 6040 and/or the third-party SDK database 6030) and may have been generated for use by the system and/or by a third party as described herein.
In various embodiments, a particular vendor may be associated with multiple categories, each of which may have a score and/or a weighting as described above in regard to a functionality term categorization table. In such embodiments, the system may determine a vendor categorization and/or vendor score for a particular SDK package by selecting the vendor category and/or score associated with the highest vendor score and/or highest weighted vendor score from among the scores/weighted scores associated with the vendor represented in the vendor token of the particular SDK packages' tokenized name.

TABLE 2

Vendor term	Category	Score	Weight

vendor1

Targeting

10	20
vendor1	Functional	20	0
vendor1	Location	25	5

In various embodiments, the SDK discovery and assessment server 6020 may determine a category score for the “com.vendor1.function1.function2.function3” package as well as a vendor score. The SDK discovery and assessment server 6020 may then use a combination of the vendor score and the category score to determine an overall score for the SDK and/or a (e.g., privacy) category for the SDK. For example, the SDK discovery and assessment server 6020 may determine a weighted category score of 30 and a vendor score of 10 for the package, and then determine an overall score of 40. In particular embodiments, the system may use a formula, algorithm, and/or other available information to determine a privacy risk score and/or a privacy assessment score for a package. In other particular embodiments, the system may determine an overall privacy risk or privacy impact score for a particular package based on only one of a vendor score or a category score by assigning the vendor score or the category score as the privacy risk or privacy impact score for the particular package.

Mobile SDK Package Assessment Module

FIG. 61 depicts a Mobile SDK Package Assessment Module 6100 according to various embodiments. In executing the Mobile SDK Assessment Module 6100, the system begins at Step 6110 by identifying a package on a mobile device (e.g., an Android-based mobile device, an iPhone, etc.). The system may identify the package by scanning one or more folders, and/or one or more files contained therein, configured on the mobile device for information (e.g., package name, file name, folder name, etc.) that may be used to identify a package.
The system may use RegEx searching techniques to search one or more databases to cross-reference the name of the identified package with one or more known SDK packages. Each of these one or more databases may be a database of SDK and vendor information that may include SDK identifying information (e.g., package name) and respective vendor information for particular SDK packages. Such databases may also store category and/or vendor scoring information as described herein. If the system determines that the name of the identified package correspond to one or more known SDK packages, the system may determine that that particular identified package is a valid SDK package. If the system is unable to cross-reference the name of the identified package to one or more known SDK packages, the system may determine that that particular identified package is not a valid SDK package.
At Step 6120, the system may tokenize the name of the identified package, for example using NLP, in order to use portions of the name for further assessment. As noted above, the tokenized SDK package name of an identified package may take the form of “<common term>.<vendor name>.<functionalityX>.<functionalityY> .<functionalityZ>.”
Using the <functionality> portion(s) of the package name, at Step 6130 the system may determine one or more categories associated with the identified package. For example, the system may identify a respective category for each identified <functionality> term of the package name based, at least in part, on a listing of one or more <functionality> terms and a corresponding category for each term in the listing of <functionality> terms (e.g., as described above). This listing of functionality terms and corresponding categories may be stored in a table or other data structure in a database of SDK-related information.
At Step 6140, the system may determine a category score for each category associated with the identified package (e.g., as determined as Step 6130), for example as described above using a table or other data structure in a database of SDK-related information. In particular embodiments, the system may apply a weighting factor at Step 6140 to one or more of the category scores, for example, in response to determining that a particular category score is associated with key category or a key <functionality> term in the package name as described above or otherwise determining an applicable weighting factor for the category.
At Step 6150, the system may determine the highest category score from among the scores of the one or more categories associated with the identified package. Where one or more of the category scores is weighted, the system may use the one or more weighted scores to select the highest category score. The system may assign the category associated with the determined highest category score to the identified package. The system may also, or instead, assign the determined highest category score to the identified package.
If the system determines that the category score cannot be determined at Step 6150 (e.g., there is no particular category associated with the particular identified package that has an associated score) or if the category score determined at Step 6150 is otherwise inconclusive, the system may determine and use a vendor score to determine a privacy category, privacy risk score, and/or a privacy assessment score for the package. Alternatively, or in addition, the system may determine that a vendor score is to be used in conjunction with a category score to determine a privacy category, privacy risk score, and/or a privacy assessment score for the package. At Step 6160, the system may use the <vendor name> from the tokenized package name to identify a vendor associated with the package, for example, by querying a vendor and/or SDK database to determine a vendor associated with the package. At Step 6170, the system may then determine a vendor category and/or score associated with the vendor that may be used in assessing the identified package by querying a vendor and/or SDK database using the determined vendor to access a vendor term categorization table and identify a vendor score and/or category that corresponds to the vendor. For example, the system may assign the category and/or score associated with the vendor to the SDK package.
At Step 6180, the system may determine an overall score (e.g., a privacy risk score and/or a privacy assessment score) for the identified package that reflects the package assessment performed by the system. In particular embodiments, this overall score is based on a category score (e.g., as determined at Step 6150). For example, the system may assign the category score as the overall score. In other particular embodiments, this overall score is based on a vendor score (e.g., as determined at Step 6170). For example, the system may assign the vendor score as the overall score. In still other particular embodiments, this overall score is determined based on a combination of one or more category scores (e.g., as determined at Step 6150), one or more vendor scores (e.g., as determined at Step 6170) and/or other information. For example, the system may use an algorithm or formula to calculate an overall score using one or more category scores and one or more vendor scores. The system may also use other information, a formula, algorithm, and/or various weighting factors to determine the overall score. This overall score may be assigned to an SDK as a privacy risk score and/or privacy assessment score and/or may be used to determine a (e.g., privacy) category for the SDK.

CONCLUSION

Although embodiments above are described in reference to various privacy assessment 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 embodiment or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments. 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.
Many modifications and other embodiments will come to mind to one skilled in the art to which this disclosure pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the teachings set forth herein are 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.

Claims

What is claimed is:

1. A method comprising:

scanning, by computing hardware, at least one of a folder on a mobile device or a file stored on the mobile device to determine identifying information for a third-party development tool;

generating, by the computing hardware, a functionality token for the third-party development tool by:

querying, based on the identifying information for the third-party development tool, a database that stores a plurality of third-party identities in correlation with a plurality of respective identifying information of third-party development tools,

determining, based on a result of querying the database, a third-party identity corresponding to the third-party development tool, and

generating the functionality token based on the third-party identity;

determining, by the computing hardware, a functionality category for the functionality token;

assigning, by the computing hardware, a third-party development tool category to the third-party development tool based on the functionality category; and

linking, by the computing hardware, the third-party development tool category to the third-party development tool.

2. The method of claim 1, wherein:

the method further comprises generating, by the computing hardware, a tokenized name for the third-party development tool using natural language processing on at least one of a filename for the file stored on the mobile device or content in the file stored on the mobile device; and

the identifying information for the third-party development tool comprises the tokenized name.

3. The method of claim 2, further comprising:

determining, by the computing hardware, based on the identifying information, a source of the third-party development tool; and

assigning, by the computing hardware, the third-party development tool category based on the source.

4. The method of claim 3, wherein:

the tokenized name comprises a source token; and

the method comprises determining the source of the third-party development tool based on the source token.

5. The method of claim 1, wherein scanning the at least one of the folder on the mobile device or the file stored on the mobile device comprises performing a filename search on the mobile device to determine the identifying information for the third-party development tool.

6. The method of claim 1, wherein:

the functionality token comprises a first functionality token representing a first functionality type of the third-party development tool and a second functionality token representing a second functionality type of the third-party development tool; and

assigning, by the computing hardware, the third-party development tool category to the third-party development tool based on the functionality category comprises assigning the third-party development tool category based on a relative relevance weighting of the first functionality token and the second functionality token.

7. The method of claim 1, wherein the third-party development tool is a software development kit used to generate an application, the application being configured to operate on the mobile device.

8. A system comprising:

a non-transitory computer-readable medium storing instructions; and

a processing device communicatively coupled to the non-transitory computer-readable medium, wherein, the processing device is configured to execute the instructions and thereby perform operations comprising:

scanning at least one of a folder on a mobile device or a file stored on the mobile device to determine identifying information for a third-party development tool;

generating a source token for the third-party development tool by:

generating the source token based on the third-party identity;

identifying a third-party computing system from the source token;

assigning a third-party development tool category to the third-party development tool based on the third-party computing system; and

linking the third-party development tool category to the third-party development tool.

9. The system of claim 8, wherein:

the operations further comprise generating a tokenized name for the third-party development tool using natural language processing on at least one of a filename for the file stored on the mobile device or content in the file stored on the mobile device; and

10. The system of claim 9, wherein:

the tokenized name comprises a first function token; and

the operations further comprise assigning the third-party development tool category based on the first functionality token.

11. The system of claim 10, wherein:

the tokenized name comprises a second function token; and

the operations further comprise assigning the third-party development tool category based on the first functionality token and the second functionality token.

12. The system of claim 8 wherein scanning the at least one of a folder on the mobile device or the file stored on the mobile device comprises determining the identifying information for the third-party development tool based on at least one of a package name, a file name, or a folder name.

13. The system of claim 9, wherein the third-party development tool is a software development kit used to generate an application.

14. The system of claim 8, wherein the third-party development tool category includes at least one of a targeting category, a functional category, or a location category.

15. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by processing hardware, configure the processing hardware to perform operations comprising:

generating a tokenized name for the third-party development tool based on the identifying information, the tokenized name comprising a functionality token representing a function of the third-party development tool;

assigning a third-party development tool category to the third-party development tool based on the functionality token; and

linking the assigned third-party development tool category to the third-party development tool.

16. The non-transitory computer-readable medium of claim 15, wherein:

generating the tokenized name for the third-party development tool comprises using natural language processing on at least one of a filename for the file stored on the mobile device or content in the file stored on the mobile device; and

17. The non-transitory computer-readable medium of claim 15, wherein scanning the at least one of the folder on the mobile device or the file stored on the mobile device comprises performing a filename search on the mobile device to determine the identifying information for the third-party development tool.

18. The non-transitory computer-readable medium of claim 15, wherein:

the functionality token is a first functionality token;

the tokenized name comprises a second functionality token; and

the operations further comprise assigning the third-party development tool category based on the first functionality token but not on the second functionality token.

19. The non-transitory computer-readable medium of claim 15, wherein:

assigning the third-party development tool category to the third-party development tool based on the functionality category comprises assigning the third-party development tool category based on a relative relevance weighting of the first functionality token and the second functionality token.

20. The non-transitory computer-readable medium of claim 15, wherein the third-party development tool is a software development kit used to generate an application, the application being configured to operate on the mobile device.