US 9,898,769 B2Grant

Data processing systems and methods for operationalizing privacy compliance via integrated mobile applications

Issue Date:2018-02-20

•20 Claims

•22 Drawing Sheets

Abstract

Data processing systems and methods for receiving data regarding a plurality of data privacy campaigns and for using that data to modify stored data associated with the data privacy campaign. In various embodiments, the system may be adapted to: (1) display one or more visual summaries of one or more data flow diagrams that visually depicts key features of the data flow, such as whether data is confidential and/or encrypted; (2) automatically assess and display a relative risk associated with each campaign; and (3) automatically set, monitor, and facilitate the timely completion of an audit schedule for each campaign. In some embodiments, the system is configured to provide a mobile application via which a user may view information related to the privacy campaign, modify that data, etc.

Metadata

Assignee

OneTrust, LLC

Inventor

Kabir A. Barday

Application Information

Application Number:US 15/619,451

Filing Date:2017-06-10

Priority Date:2016-04-01

Art Unit:3629

Classifications

IPC:

G06Q10/10G06Q40/08G06F21/31G06Q30/06G06Q10/06G06Q50/26

Field of Search:

G06Q 30/0609G06Q 50/265

Patent Drawings (22 sheets)

Description

Cross Reference to Related Applications

[0001] This application is a continuation-in-part of U.S. patent application Ser. No. 15/256,419, filed Sep. 2, 2016, which is a continuation of U.S. patent application Ser. No. 15/169,643, filed May 31, 2016, which claims priority to U.S. Provisional Patent Application Ser. No. 62/317,457, filed Apr. 1, 2016, and this application also claims priority to U.S. Provisional Patent Application Ser. No. 62/360,123, filed Jul. 8, 2016; U.S. Provisional Patent Application Ser. No. 62/353,802, filed Jun. 23, 2016; and U.S. Provisional Patent Application Ser. No. 62/348,695, filed Jun. 10, 2016, the disclosures of which are hereby incorporated by reference in their entirety.

Background

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

[0003] 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. Accordingly, there is a need for improved systems and methods to manage personal data in a manner that complies with such policies.

Summary

[0004] A computer-implemented data processing method according to various embodiments comprises: (1) providing a software application for installation on a mobile computing device; (2) displaying on a graphical user interface, via the software application, a prompt to modify an electronic record for a privacy campaign, wherein the privacy campaign utilizes personal data collected from at least one or more persons or one or more entities; (3) receiving, from a user of the mobile computing device, first information associated with the privacy campaign; (4) modifying the electronic record for the privacy campaign based at least in part on the first information; and (5) displaying, on the graphical user interface, second information associated with the privacy campaign. In various embodiments, the first information comprises one or more of: (1) one or more responses to one or more screening questions; (2) one or more pieces of information related to a particular privacy incident associating with the privacy campaign; (3) one or more response to one or more training quizzes.

[0005] A computer-implemented data processing method for electronically receiving the input of campaign data related to a privacy campaign, in some embodiments comprises: (1) providing a software application for installation on a mobile computing device; (2) displaying on a graphical user interface, via the software application, a prompt to create an electronic record for a privacy campaign, wherein the privacy campaign utilizes personal data collected from at least one or more persons or one or more entities; (3) receiving a command to create an electronic record for the privacy campaign; (4) creating an electronic record for the privacy campaign and digitally storing the record; (5) presenting, on one or more graphical user interfaces, a plurality of prompts for the input of campaign data related to the privacy campaign; (6) electronically receiving campaign data input by one or more users via the graphical user interface; (7) processing the campaign data by electronically associating the campaign data with the record for the privacy campaign; (8) receiving, via the software application, one or more inputs related to the privacy campaign; and (9) modifying the electronic record for the privacy campaign based at least in part on the one or more inputs. In various embodiments, the campaign data identifies each of: (1) a description of the campaign; (2) one or more types of personal data related to the campaign; (3) a subject from which the personal data was collected; (4) the storage of the personal data; and (5) access to the personal data;

Brief Description of the Drawings

[0006] Various embodiments of a privacy campaign data modification 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:

[0007] FIG. 1 is diagram illustrating an exemplary network environment in which the present system and methods for operationalizing privacy compliance may operate.

[0008] FIG. 2 is a schematic diagram of a computer (such as the server 120, or user device 140, 150, 160, 170, 180, 190) that is suitable for use in various embodiments;

[0009] FIG. 3 is a diagram illustrating an example of the elements (e.g., subjects, owner, etc.) that may be involved in privacy compliance.

[0010] FIG. 4 is a flow chart showing an example of a process performed by the Main Privacy Compliance Module.

[0011] FIG. 5 is a flow chart showing an example of a process performed by the Risk Assessment Module.

[0012] FIG. 6 is a flow chart showing an example of a process performed by the Privacy Audit Module.

[0013] FIG. 7 is a flow chart showing an example of a process performed by the Data Flow Diagram Module.

[0014] FIG. 8 is an example of a graphical user interface (GUI) showing a dialog that allows for entry of description information related to a privacy campaign.

[0015] FIG. 9 is an example of a notification, generated by the system, informing a business representative (e.g., owner) that they have been assigned to a particular privacy campaign.

[0016] FIG. 10 is an example of a GUI showing a dialog that allows entry of the type of personal data that is being collected for a campaign.

[0017] FIG. 11 is an example of a GUI that shows a dialog that allows collection of campaign data regarding the subject from whom the personal data was collected.

[0018] FIG. 12 is an example of a GUI that shows a dialog for inputting information regarding where the personal data related to a campaign is stored.

[0019] FIG. 13 is an example of a GUI that shows information regarding the access of the personal data related to a campaign.

[0020] FIG. 14 is an example of an instant messaging session overlaid on top of a GUI, wherein the GUI contains prompts for the entry or selection of campaign data.

[0021] FIG. 15 is an example of a GUI showing an inventory page.

[0022] FIG. 16 is an example of a GUI showing campaign data, including a data flow diagram.

[0023] FIG. 17 is an example of a GUI showing a page that allows editing of campaign data.

[0024] FIG. 18 depicts a privacy campaign data modification system according to particular embodiments.

[0025] FIG. 19 is a flowchart showing an example of a process performed by the Mobile Privacy Compliance Module according to particular embodiments.

[0026] FIGS. 20-21 depict an exemplary screen display and graphical user interface (GUI) 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.

Detailed Description

[0027] 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.

[0028] Overview

[0029] In various embodiments, a mobile privacy compliance system is configured to enable a user using a mobile computing device to, for example: (1) submit one or more answers to one or more screening questions related to a particular privacy campaign; (2) document one or more privacy incidents related to a particular privacy campaign; (3) complete one or more training exercise related to a particular privacy campaign; (4) complete one or more questionnaires related to privacy compliance knowledge; and/or (5) undertake any other activity related to the initiation of a new privacy campaign, the submission of information related to an existing privacy campaign, and/or the measurement of a risk of a particular privacy campaign or privacy maturity of a particular entity. In particular, the system is configured to provide a software application or other user interface for installation on a mobile computing device (e.g., smartphone) through which the user may submit information related to the privacy campaign.

[0030] In various embodiments, a 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 privacy information or personal data associated with one or more individuals. This personal data may include, for example, for an individual: (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) account data; and (11) any other suitable personal information discussed herein.

[0031] As generally discussed above, a particular organization may be required to implement operational policies and processes to comply with one or more legal requirements in handling such personal data. A particular organization may further take steps to comply with one or more industry best practices. In particular embodiments, these operational policies and processes may include, for example: (1) storing personal data in a suitable location; (2) limiting access to the personal data to only suitable individuals or entities within the origination or external to the organization; (3) limiting a length of time for which the data will be stored; and (4) any other suitable policy to ensure compliance with any legal or industry guidelines. In particular embodiments, the legal or industry guidelines may vary based at least in part on, for example: (1) the type of data being stored; (2) an amount of data; (3) whether the data is encrypted; (4) etc.

[0032] For example, a particular organization's privacy compliance system may store information related to a plurality of privacy campaigns that the particular organization has undertaken. Each particular privacy campaign may include the receipt or entry and subsequent storage of personal data associated with one or more individuals as part of the privacy campaign. An exemplary privacy campaign, may, for example, include the collection and storage of the organization's employees' names, contact information, banking information, and social security numbers for use by the organization's accounting department for payroll purposes.

[0033] In relation to a particular organization's privacy compliance activities, the organization may utilize a privacy compliance system to ensure compliance with one or more legal or industry requirements related to the collection and/or storage of personal data. The mobile privacy compliance system may be configured to collect information via a mobile application which may, for example, be utilized by a privacy compliance system to, for example: (1) measure a risk level of a particular privacy campaign; (2) adjust an audit schedule of a particular privacy campaign; (3) measure a privacy maturity of a particular subgroup of the organization; and/or (4) take any other suitable action with respect to the collected information.

[0034] Exemplary Technical Platforms

[0035] As will be appreciated by one skilled in the relevant field, a system for operationalizing privacy compliance and assessing risk of privacy campaigns 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, mobile, wearable computer-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.

[0036] 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 step of the block diagrams and flowchart illustrations, and combinations of steps in the block diagrams and flowchart illustrations, respectively, may 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 step or steps

[0037] These computer program instructions may also be stored in a computer-readable memory that may 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 step or steps. 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 step or steps.

[0038] Accordingly, steps 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 step of the block diagrams and flowchart illustrations, and combinations of steps in the block diagrams and flowchart illustrations, may 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.

[0039] Example System Architecture

[0040] FIG. 1 is a block diagram of a System 100 according to a particular embodiment. As may be understood from this figure, the System 100 includes one or more computer networks 110, a Server 120, a Storage Device 130 (which may contain one or more databases of information), one or more remote client computing devices such as a tablet computer 140, a desktop or laptop computer 150, or a handheld computing device 160, such as a cellular phone, browser and Internet capable set-top boxes 170 connected with a TV 180, or even smart TVs 180 having browser and Internet capability. The client computing devices attached to the network may also include copiers/printers 190 having hard drives (a security risk since copies/prints may be stored on these hard drives). The Server 120, client computing devices, and Storage Device 130 may be physically located in a central location, such as the headquarters of the organization, for example, or in separate facilities. The devices may be owned or maintained by employees, contractors, or other third parties (e.g., a cloud service provider). In particular embodiments, the one or more computer networks 115 facilitate communication between the Server 120, one or more client computing devices 140, 150, 160, 170, 180, 190, and Storage Device 130.

[0041] 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 switched telephone network (PSTN), or any other type of network. The communication link between the Server 120, one or more client computing devices 140, 150, 160, 170, 180, 190, and Storage Device 130 may be, for example, implemented via a Local Area Network (LAN) or via the Internet.

[0042] Example Computer Architecture Used within the System

[0043] FIG. 2 illustrates a diagrammatic representation of the architecture of a computer 200 that may be used within the System 100, for example, as a client computer (e.g., one of computing devices 140, 150, 160, 170, 180, 190, shown in FIG. 1), or as a server computer (e.g., Server 120 shown in FIG. 1). In exemplary embodiments, the computer 200 may be suitable for use as a computer within the context of the System 100 that is configured to operationalize privacy compliance and assess risk of privacy campaigns. 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.

[0044] 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.), a 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.

[0045] 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.

[0046] The computer 200 may further include a network interface device 208. The computer 200 also may include a video display unit 210 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 212 (e.g., a keyboard), a cursor control device 214 (e.g., a mouse), and a signal generation device 216 (e.g., a speaker). The data storage device 218 may include a non-transitory computer-readable 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 222 (e.g., software, software modules) embodying any one or more of the methodologies or functions described herein. The software 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 222 may further be transmitted or received over a network 220 via network interface device 208.

[0047] While the computer-readable storage medium 230 is shown in an exemplary embodiment to be a single medium, the terms “computer-readable storage medium” and “machine-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-readable 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 present invention. The term “computer-readable storage medium” should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc.

[0048] Exemplary System Platform

[0049] According to various embodiments, the processes and logic flows described in this specification may be performed by a system (e.g., System 100) that includes, but is not limited to, one or more programmable processors (e.g., processor 202) executing one or more computer program modules to perform functions by operating on input data and generating output, thereby tying the process to a particular machine (e.g., a machine programmed to perform the processes described herein). This includes processors located in one or more of client computers (e.g., client computers 140, 150, 160, 170, 180, 190 of FIG. 1). These devices connected to network 110 may access and execute one or more Internet browser-based program modules that are “served up” through the network 110 by one or more servers (e.g., server 120 of FIG. 1), and the data associated with the program may be stored on a one or more storage devices, which may reside within a server or computing device (e.g., Main Memory 204, Static Memory 206), be attached as a peripheral storage device to the one or more servers or computing devices, or attached to the network (e.g., Storage 130).

[0050] The System 100 facilitates the acquisition, storage, maintenance, use, and retention of campaign data associated with a plurality of privacy campaigns within an organization. In doing so, various aspects of the System 100 initiates and creates a plurality of individual data privacy campaign records that are associated with a variety of privacy-related attributes and assessment related meta-data for each campaign. These data elements may include: the subjects of the sensitive information, the respective person or entity responsible for each campaign (e.g., the campaign's “owner”), the location where the personal data will be stored, the entity or entities that will access the data, the parameters according to which the personal data will be used and retained, the Risk Level associated with a particular campaign (as well as assessments from which the Risk Level is calculated), an audit schedule, and other attributes and meta-data. The System 100 may also be adapted to facilitate the setup and auditing of each privacy campaign. These modules may include, for example, a Main Privacy Compliance Module, a Risk Assessment Module, a Privacy Audit Module, a Data Flow Diagram Module, and a Communications Module (examples of which are described below). It is to be understood that these are examples of modules of various embodiments, but the functionalities performed by each module as described may be performed by more (or less) modules. Further, the functionalities described as being performed by one module may be performed by one or more other modules.

[0051] A. Example Elements Related to Privacy Campaigns

[0052] FIG. 3 provides a high-level visual overview of example “subjects” for particular data privacy campaigns, exemplary campaign “owners,” various elements related to the storage and access of personal data, and elements related to the use and retention of the personal data. Each of these elements may, in various embodiments, be accounted for by the System 100 as it facilitates the implementation of an organization's privacy compliance policy.

[0053] As may be understood from FIG. 3, sensitive information may be collected by an organization from one or more subjects 300. Subjects may include customers whose information has been obtained by the organization. For example, if the organization is selling goods to a customer, the organization may have been provided with a customer's credit card or banking information (e.g., account number, bank routing number), social security number, or other sensitive information.

[0054] An organization may also possess personal data originating from one or more of its business partners. Examples of business partners are vendors that may be data controllers or data processors (which have different legal obligations under EU data protection laws). Vendors may supply a component or raw material to the organization, or an outside contractor responsible for the marketing or legal work of the organization. The personal data acquired from the partner may be that of the partners, or even that of other entities collected by the partners. For example, a marketing agency may collect personal data on behalf of the organization, and transfer that information to the organization. Moreover, the organization may share personal data with one of its partners. For example, the organization may provide a marketing agency with the personal data of its customers so that it may conduct further research.

[0055] Other subjects 300 include the organization's own employees. Organizations with employees often collect personal data from their employees, including address and social security information, usually for payroll purposes, or even prior to employment, for conducting credit checks. The subjects 300 may also include minors. It is noted that various corporate privacy policies or privacy laws may require that organizations take additional steps to protect the sensitive privacy of minors.

[0056] Still referring to FIG. 3, within an organization, a particular individual (or groups of individuals) may be designated to be an “owner” of a particular campaign to obtain and manage personal data. These owners 310 may have any suitable role within the organization. In various embodiments, an owner of a particular campaign will have primary responsibility for the campaign, and will serve as a resident expert regarding the personal data obtained through the campaign, and the way that the data is obtained, stored, and accessed. As shown in FIG. 3, an owner may be a member of any suitable department, including the organization's marketing, HR, R&D, or IT department. As will be described below, in exemplary embodiments, the owner can always be changed, and owners can sub-assign other owners (and other collaborators) to individual sections of campaign data input and operations.

[0057] Referring still to FIG. 3, the system may be configured to account for the use and retention 315 of personal data obtained in each particular campaign. The use and retention of personal data may include how the data is analyzed and used within the organization's operations, whether the data is backed up, and which parties within the organization are supporting the campaign.

[0058] The system may also be configured to help manage the storage and access 320 of personal data. As shown in FIG. 3, a variety of different parties may access the data, and the data may be stored in any of a variety of different locations, including on-site, or in “the cloud”, i.e., on remote servers that are accessed via the Internet or other suitable network.

[0059] B. Main Compliance Module

[0060] FIG. 4 illustrates an exemplary process for operationalizing privacy compliance. Main Privacy Compliance Module 400, which may be executed by one or more computing devices of System 100, may perform this process. In exemplary embodiments, a server (e.g., server 140) in conjunction with a client computing device having a browser, execute the Main Privacy Compliance Module (e.g., computing devices 140, 150, 160, 170, 180, 190) through a network (network 110). In various exemplary embodiments, the Main Privacy Compliance Module 400 may call upon other modules to perform certain functions. In exemplary embodiments, the software may also be organized as a single module to perform various computer executable routines.

[0061] I. Adding a Campaign

[0062] The process 400 may begin at step 405, wherein the Main Privacy Compliance Module 400 of the System 100 receives a command to add a privacy campaign. In exemplary embodiments, the user selects an on-screen button (e.g., the Add Data Flow button 1555 of FIG. 15) that the Main Privacy Compliance Module 400 displays on a landing page, which may be displayed in a graphical user interface (GUI), such as a window, dialog box, or the like. The landing page may be, for example, the inventory page 1500 below. The inventory page 1500 may display a list of one or more privacy campaigns that have already been input into the System 100. As mentioned above, a privacy campaign may represent, for example, a business operation that the organization is engaged in, or some business record, that may require the use of personal data, which may include the personal data of a customer or some other entity. Examples of campaigns might include, for example, Internet Usage History, Customer Payment Information, Call History Log, Cellular Roaming Records, etc. For the campaign “Internet Usage History,” a marketing department may need customers' on-line browsing patterns to run analytics. This might entail retrieving and storing customers' IP addresses, MAC address, URL history, subscriber ID, and other information that may be considered personal data (and even sensitive personal data). As will be described herein, the System 100, through the use of one or more modules, including the Main Privacy Campaign Module 400, creates a record for each campaign. Data elements of campaign data may be associated with each campaign record that represents attributes such as: the type of personal data associated with the campaign; the subjects having access to the personal data; the person or persons within the company that take ownership (e.g., business owner) for ensuring privacy compliance for the personal data associated with each campaign; the location of the personal data; the entities having access to the data; the various computer systems and software applications that use the personal data; and the Risk Level (see below) associated with the campaign.

[0063] II. Entry of Privacy Campaign Related Information, Including Owner

[0064] At step 410, in response to the receipt of the user's command to add a privacy campaign record, the Main Privacy Compliance Module 400 initiates a routine to create an electronic record for a privacy campaign, and a routine for the entry data inputs of information related to the privacy campaign. The Main Privacy Compliance Module 400 may generate one or more graphical user interfaces (e.g., windows, dialog pages, etc.), which may be presented one GUI at a time. Each GUI may show prompts, editable entry fields, check boxes, radial selectors, etc., where a user may enter or select privacy campaign data. In exemplary embodiments, the Main Privacy Compliance Module 400 displays on the graphical user interface a prompt to create an electronic record for the privacy campaign. A user may choose to add a campaign, in which case the Main Privacy Compliance Module 400 receives a command to create the electronic record for the privacy campaign, and in response to the command, creates a record for the campaign and digitally stores the record for the campaign. The record for the campaign may be stored in, for example, storage 130, or a storage device associated with the Main Privacy Compliance Module (e.g., a hard drive residing on Server 110, or a peripheral hard drive attached to Server 110).

[0065] The user may be a person who works in the Chief Privacy Officer's organization (e.g., a privacy office rep, or privacy officer). The privacy officer may be the user that creates the campaign record, and enters initial portions of campaign data (e.g., “high level” data related to the campaign), for example, a name for the privacy campaign, a description of the campaign, and a business group responsible for administering the privacy operations related to that campaign (for example, though the GUI shown in FIG. 6). The Main Privacy Compliance Module 400 may also prompt the user to enter a person or entity responsible for each campaign (e.g., the campaign's “owner”). The owner may be tasked with the responsibility for ensuring or attempting to ensure that the privacy policies or privacy laws associated with personal data related to a particular privacy campaign are being complied with. In exemplary embodiments, the default owner of the campaign may be the person who initiated the creation of the privacy campaign. That owner may be a person who works in the Chief Privacy Officer's organization (e.g., a privacy office rep, or privacy officer). The initial owner of the campaign may designate someone else to be the owner of the campaign. The designee may be, for example, a representative of some business unit within the organization (a business rep). Additionally, more than one owner may be assigned. For example, the user may assign a primary business rep, and may also assign a privacy office rep as owners of the campaign.

[0066] In many instances, some or most of the required information related to the privacy campaign record might not be within the knowledge of the default owner (i.e., the privacy office rep). The Main Data Compliance Module 400 can be operable to allow the creator of the campaign record (e.g., a privacy officer rep) to designate one or more other collaborators to provide at least one of the data inputs for the campaign data. Different collaborators, which may include the one or more owners, may be assigned to different questions, or to specific questions within the context of the privacy campaign. Additionally, different collaborators may be designated to respond to pats of questions. Thus, portions of campaign data may be assigned to different individuals.

[0067] Still referring to FIG. 4, if at step 415 the Main Privacy Compliance Module 400 has received an input from a user to designate a new owner for the privacy campaign that was created, then at step 420, the Main Privacy Compliance Module 400 may notify that individual via a suitable notification that the privacy campaign has been assigned to him or her. Prior to notification, the Main Privacy Compliance Module 400 may display a field that allows the creator of the campaign to add a personalized message to the newly assigned owner of the campaign to be included with that notification. In exemplary embodiments, the notification may be in the form of an email message. The email may include the personalized message from the assignor, a standard message that the campaign has been assigned to him/her, the deadline for completing the campaign entry, and instructions to log in to the system to complete the privacy campaign entry (along with a hyperlink that takes the user to a GUI providing access to the Main Privacy Compliance Module 400. Also included may be an option to reply to the email if an assigned owner has any questions, or a button that when clicked on, opens up a chat window (i.e., instant messenger window) to allow the newly assigned owner and the assignor a GUI in which they are able to communicate in real-time. An example of such a notification appears in FIG. 16 below. In addition to owners, collaborators that are assigned to input portions of campaign data may also be notified through similar processes. In exemplary embodiments, The Main Privacy Compliance Module 400 may, for example through a Communications Module, be operable to send collaborators emails regarding their assignment of one or more portions of inputs to campaign data. Or through the Communications Module, selecting the commentators button brings up one or more collaborators that are on-line (with the off-line users still able to see the messages when they are back on-line. Alerts indicate that one or more emails or instant messages await a collaborator.

[0068] At step 425, regardless of whether the owner is the user (i.e., the creator of the campaign), “someone else” assigned by the user, or other collaborators that may be designated with the task of providing one or more items of campaign data, the Main Privacy Campaign Module 400 may be operable to electronically receive campaign data inputs from one or more users related to the personal data related to a privacy campaign through a series of displayed computer-generated graphical user interfaces displaying a plurality of prompts for the data inputs. In exemplary embodiments, through a step-by-step process, the Main Privacy Campaign Module may receive from one or more users' data inputs that include campaign data like: (1) a description of the campaign; (2) one or more types of personal data to be collected and stored as part of the campaign; (3) individuals from which the personal data is to be collected; (4) the storage location of the personal data, and (5) information regarding who will have access to the personal data. These inputs may be obtained, for example, through the graphical user interfaces shown in FIGS. 8 through 13, wherein the Main Compliance Module 400 presents on sequentially appearing GUIs the prompts for the entry of each of the enumerated campaign data above. The Main Compliance Module 400 may process the campaign data by electronically associating the campaign data with the record for the campaign and digitally storing the campaign data with the record for the campaign. The campaign data may be digitally stored as data elements in a database residing in a memory location in the server 120, a peripheral storage device attached to the server, or one or more storage devices connected to the network (e.g., storage 130). If campaign data inputs have been assigned to one or more collaborators, but those collaborators have not input the data yet, the Main Compliance Module 400 may, for example through the Communications Module, sent an electronic message (such as an email) alerting the collaborators and owners that they have not yet supplied their designated portion of campaign data.

[0069] III. Privacy Campaign Information Display

[0070] At step 430, Main Privacy Compliance Module 400 may, in exemplary embodiments, call upon a Risk Assessment Module 430 that may determine and assign a Risk Level for the privacy campaign, based wholly or in part on the information that the owner(s) have input. The Risk Assessment Module 430 will be discussed in more detail below.

[0071] At step 432, Main Privacy Compliance Module 400 may in exemplary embodiments, call upon a Privacy Audit Module 432 that may determine an audit schedule for each privacy campaign, based, for example, wholly or in part on the campaign data that the owner(s) have input, the Risk Level assigned to a campaign, and/or any other suitable factors. The Privacy Audit Module 432 may also be operable to display the status of an audit for each privacy campaign. The Privacy Audit Module 432 will be discussed in more detail below.

[0072] At step 435, the Main Privacy Compliance Module 400 may generate and display a GUI showing an inventory page (e.g., inventory page 1500) that includes information associated with each campaign. That information may include information input by a user (e.g., one or more owners), or information calculated by the Main Privacy Compliance Module 400 or other modules. Such information may include for example, the name of the campaign, the status of the campaign, the source of the campaign, the storage location of the personal data related to the campaign, etc. The inventory page 1500 may also display an indicator representing the Risk Level (as mentioned, determined for each campaign by the Risk Assessment Module 430), and audit information related to the campaign that was determined by the Privacy Audit Module (see below). The inventory page 1500 may be the landing page displayed to users that access the system. Based on the login information received from the user, the Main Privacy Compliance Module may determine which campaigns and campaign data the user is authorized to view, and display only the information that the user is authorized to view. Also from the inventory page 1500, a user may add a campaign (discussed above in step 405), view more information for a campaign, or edit information related to a campaign (see, e.g., FIGS. 15, 16, 17).

[0073] If other commands from the inventory page are received (e.g., add a campaign, view more information, edit information related to the campaign), then step 440, 445, and/or 450 may be executed.

[0074] At step 440, if a command to view more information has been received or detected, then at step 445, the Main Privacy Compliance Module 400 may present more information about the campaign, for example, on a suitable campaign information page 1500. At this step, the Main Privacy Compliance Module 400 may invoke a Data Flow Diagram Module (described in more detail below). The Data Flow Diagram Module may generate a flow diagram that shows, for example, visual indicators indicating whether data is confidential and/or encrypted (see, e.g., FIG. 1600 below).

[0075] At step 450, if the system has received a request to edit a campaign, then, at step 455, the system may display a dialog page that allows a user to edit information regarding the campaign (e.g., edit campaign dialog 1700).

[0076] At step 460, if the system has received a request to add a campaign, the process may proceed back to step 405.

[0077] C. Risk Assessment Module

[0078] FIG. 5 illustrates an exemplary process for determining a Risk Level and Overall Risk Assessment for a particular privacy campaign performed by Risk Assessment Module 430.

[0079] I. Determining Risk Level

[0080] In exemplary embodiments, the Risk Assessment Module 430 may be operable to calculate a Risk Level for a campaign based on the campaign data related to the personal data associated with the campaign. The Risk Assessment Module may associate the Risk Level with the record for the campaign and digitally store the Risk Level with the record for the campaign.

[0081] The Risk Assessment Module 430 may calculate this Risk Level based on any of various factors associated with the campaign. The Risk Assessment Module 430 may determine a plurality of weighting factors based upon, for example: (1) the nature of the sensitive information collected as part of the campaign (e.g., campaigns in which medical information, financial information or non-public personal identifying information is collected may be indicated to be of higher risk than those in which only public information is collected, and thus may be assigned a higher numerical weighting factor); (2) the location in which the information is stored (e.g., campaigns in which data is stored in the cloud may be deemed higher risk than campaigns in which the information is stored locally); (3) the number of individuals who have access to the information (e.g., campaigns that permit relatively large numbers of individuals to access the personal data may be deemed more risky than those that allow only small numbers of individuals to access the data); (4) the length of time that the data will be stored within the system (e.g., campaigns that plan to store and use the personal data over a long period of time may be deemed more risky than those that may only hold and use the personal data for a short period of time); (5) the individuals whose sensitive information will be stored (e.g., campaigns that involve storing and using information of minors may be deemed of greater risk than campaigns that involve storing and using the information of adults); (6) the country of residence of the individuals whose sensitive information will be stored (e.g., campaigns that involve collecting data from individuals that live in countries that have relatively strict privacy laws may be deemed more risky than those that involve collecting data from individuals that live in countries that have relative lax privacy laws). It should be understood that any other suitable factors may be used to assess the Risk Level of a particular campaign, including any new inputs that may need to be added to the risk calculation.

[0082] In particular embodiments, one or more of the individual factors may be weighted (e.g., numerically weighted) according to the deemed relative importance of the factor relative to other factors (i.e., Relative Risk Rating).

[0083] These weightings may be customized from organization to organization, and/or according to different applicable laws. In particular embodiments, the nature of the sensitive information will be weighted higher than the storage location of the data, or the length of time that the data will be stored.

[0084] In various embodiments, the system uses a numerical formula to calculate the Risk Level of a particular campaign. This formula may be, for example: Risk Level for campaign=(Weighting Factor of Factor 1)*(Relative Risk Rating of Factor 1)+(Weighting Factor of Factor 2)*(Relative Risk Rating of Factor 2)+ . . . (Weighting Factor of Factor N)*(Relative Risk Rating of Factor N). As a simple example, the Risk Level for a campaign that only collects publicly available information for adults and that stores the information locally for a short period of several weeks might be determined as Risk Level=(Weighting Factor of Nature of Sensitive Information)*(Relative Risk Rating of Particular Sensitive Information to be Collected)+(Weighting Factor of Individuals from which Information is to be Collected)*(Relative Risk Rating of Individuals from which Information is to be Collected)+(Weighting Factor of Duration of Data Retention)*(Relative Risk Rating of Duration of Data Retention)+(Weighting Factor of Individuals from which Data is to be Collected)*(Relative Risk Rating of Individuals from which Data is to be Collected). In this example, the Weighting Factors may range, for example from 1-5, and the various Relative Risk Ratings of a factor may range from 1-10. However, the system may use any other suitable ranges.

[0085] In particular embodiments, the Risk Assessment Module 430 may have default settings for assigning Overall Risk Assessments to respective campaigns based on the numerical Risk Level value determined for the campaign, for example, as described above. The organization may also modify these settings in the Risk Assessment Module 430 by assigning its own Overall Risk Assessments based on the numerical Risk Level. For example, the Risk Assessment Module 430 may, based on default or user assigned settings, designate: (1) campaigns with a Risk Level of 1-7 as “low risk” campaigns, (2) campaigns with a Risk Level of 8-15 as “medium risk” campaigns; (3) campaigns with a Risk Level of over 16 as “high risk” campaigns. As show below, in an example inventory page 1500, the Overall Risk Assessment for each campaign can be indicated by up/down arrow indicators, and further, the arrows may have different shading (or color, or portions shaded) based upon this Overall Risk Assessment. The selected colors may be conducive for viewing by those who suffer from color blindness.

[0086] Thus, the Risk Assessment Module 430 may be configured to automatically calculate the numerical Risk Level for each campaign within the system, and then use the numerical Risk Level to assign an appropriate Overall Risk Assessment to the respective campaign. For example, a campaign with a Risk Level of 5 may be labeled with an Overall Risk Assessment as “Low Risk”. The system may associate both the Risk Level and the Overall Risk Assessment with the campaign and digitally store them as part of the campaign record.

[0087] II. Exemplary Process for Assessing Risk

[0088] Accordingly, as shown in FIG. 5, in exemplary embodiments, the Risk Assessment

[0089] Module 430 electronically retrieves from a database (e.g., storage device 130) the campaign data associated with the record for the privacy campaign. It may retrieve this information serially, or in parallel. At step 505, the Risk Assessment Module 430 retrieves information regarding (1) the nature of the sensitive information collected as part of the campaign. At step 510, the Risk Assessment Module 430 retrieves information regarding the (2) the location in which the information related to the privacy campaign is stored. At step 515, the Risk Assessment Module 430 retrieves information regarding (3) the number of individuals who have access to the information. At step 520, the Risk Assessment Module retrieves information regarding (4) the length of time that the data associated with a campaign will be stored within the System 100. At step 525, the Risk Assessment Module retrieves information regarding (5) the individuals whose sensitive information will be stored. At step 530, the Risk Assessment Module retrieves information regarding (6) the country of residence of the individuals whose sensitive information will be stored.

[0090] At step 535, the Risk Assessment Module takes into account any user customizations to the weighting factors related to each of the retrieved factors from steps 505, 510, 515, 520, 525, and 530. At steps 540 and 545, the Risk Assessment Module applies either default settings to the weighting factors (which may be based on privacy laws), or customizations to the weighting factors. At step 550, the Risk Assessment Module determines a plurality of weighting factors for the campaign. For example, for the factor related to the nature of the sensitive information collected as part of the campaign, a weighting factor of 1-5 may be assigned based on whether non-public personal identifying information is collected.

[0091] At step 555, the Risk Assessment Module takes into account any user customizations to the Relative Risk assigned to each factor, and at step 560 and 565, will either apply default values (which can be based on privacy laws) or the customized values for the Relative Risk. At step 570, the Risk Assessment Module assigns a relative risk rating for each of the plurality of weighting factors. For example, the relative risk rating for the location of the information of the campaign may be assigned a numerical number (e.g., from 1-10) that is lower than the numerical number assigned to the Relative Risk Rating for the length of time that the sensitive information for that campaign is retained.

[0092] At step 575, the Risk Assessment Module 430 calculates the relative risk assigned to the campaign based upon the plurality of Weighting Factors and the Relative Risk Rating for each of the plurality of factors. As an example, the Risk Assessment Module 430 may make this calculation using the formula of Risk Level=(Weighting Factor of Factor 1)*(Relative Risk Rating of Factor 1)+(Weighting Factor of Factor 2)*(Relative Risk Rating of Factor 2)+ . . . (Weighting Factor of Factor N)*(Relative Risk Rating of Factor N).

[0093] At step 580, based upon the numerical value derived from step 575, the Risk Assessment

[0094] Module 430 may determine an Overall Risk Assessment for the campaign. The Overall Risk Assessment determination may be made for the privacy campaign may be assigned based on the following criteria, which may be either a default or customized setting: (1) campaigns with a Risk Level of 1-7 as “low risk” campaigns, (2) campaigns with a Risk Level of 8-15 as “medium risk” campaigns; (3) campaigns with a Risk Level of over 16 as “high risk” campaigns. The Overall Risk Assessment is then associated and stored with the campaign record.

[0095] D. Privacy Audit Module

[0096] The System 100 may determine an audit schedule for each campaign, and indicate, in a particular graphical user interface (e.g., inventory page 1500), whether a privacy audit is coming due (or is past due) for each particular campaign and, if so, when the audit is/was due. The System 100 may also be operable to provide an audit status for each campaign, and alert personnel of upcoming or past due privacy audits. To further the retention of evidence of compliance, the System 100 may also receive and store evidence of compliance. A Privacy Audit Module 432, may facilitate these functions.

[0097] I. Determining a Privacy Audit Schedule and Monitoring Compliance

[0098] In exemplary embodiments, the Privacy Audit Module 432 is adapted to automatically schedule audits and manage compliance with the audit schedule. In particular embodiments, the system may allow a user to manually specify an audit schedule for each respective campaign. The Privacy Audit Module 432 may also automatically determine, and save to memory, an appropriate audit schedule for each respective campaign, which in some circumstances, may be editable by the user.

[0099] The Privacy Audit Module 432 may automatically determine the audit schedule based on the determined Risk Level of the campaign. For example, all campaigns with a Risk Level less than 10 may have a first audit schedule and all campaigns with a Risk Level of 10 or more may have a second audit schedule. The Privacy Audit Module may also be operable determine the audit schedule based on the Overall Risk Assessment for the campaign (e.g., “low risk” campaigns may have a first predetermined audit schedule, “medium risk” campaigns may have a second predetermined audit schedule, “high risk” campaigns may have a third predetermined audit schedule, etc.).

[0100] In particular embodiments, the Privacy Audit Module 432 may automatically facilitate and monitor compliance with the determined audit schedules for each respective campaign. For example, the system may automatically generate one or more reminder emails to the respective owners of campaigns as the due date approaches. The system may also be adapted to allow owners of campaigns, or other users, to submit evidence of completion of an audit (e.g., by for example, submitting screen shots that demonstrate that the specified parameters of each campaign are being followed). In particular embodiments, the system is configured for, in response to receiving sufficient electronic information documenting completion of an audit, resetting the audit schedule (e.g., scheduling the next audit for the campaign according to a determined audit schedule, as determined above).

[0101] II. Exemplary Privacy Audit Process

[0102] FIG. 6 illustrates an exemplary process performed by a Privacy Audit Module 432 for assigning a privacy audit schedule and facilitating and managing compliance for a particular privacy campaign. At step 605, the Privacy Audit Module 432 retrieves the Risk Level associated with the privacy campaign. In exemplary embodiments, the Risk Level may be a numerical number, as determined above by the Risk Assessment Module 430. If the organization chooses, the Privacy Audit Module 432 may use the Overall Risk Assessment to determine which audit schedule for the campaign to assign.

[0103] At step 610, based on the Risk Level of the campaign (or the Overall Risk Assessment), or based on any other suitable factor, the Privacy Audit Module 432 can assign an audit schedule for the campaign. The audit schedule may be, for example, a timeframe (i.e., a certain amount of time, such as number of days) until the next privacy audit on the campaign to be performed by the one or more owners of the campaign. The audit schedule may be a default schedule. For example, the Privacy Audit Module can automatically apply an audit schedule of 120 days for any campaign having Risk Level of 10 and above. These default schedules may be modifiable. For example, the default audit schedule for campaigns having a Risk Level of 10 and above can be changed from 120 days to 150 days, such that any campaign having a Risk Level of 10 and above is assigned the customized default audit schedule (i.e., 150 days). Depending on privacy laws, default policies, authority overrides, or the permission level of the user attempting to modify this default, the default might not be modifiable.

[0104] At step 615, after the audit schedule for a particular campaign has already been assigned, the Privacy Audit Module 432 determines if a user input to modify the audit schedule has been received. If a user input to modify the audit schedule has been received, then at step 620, the Privacy Audit Module 432 determines whether the audit schedule for the campaign is editable (i.e., can be modified). Depending on privacy laws, default policies, authority overrides, or the permission level of the user attempting to modify the audit schedule, the campaign's audit schedule might not be modifiable.

[0105] At step 625, if the audit schedule is modifiable, then the Privacy Audit Module will allow the edit and modify the audit schedule for the campaign. If at step 620 the Privacy Audit Module determines that the audit schedule is not modifiable, in some exemplary embodiments, the user may still request permission to modify the audit schedule. For example, the Privacy Audit Module 432 can at step 630 provide an indication that the audit schedule is not editable, but also provide an indication to the user that the user may contact through the system one or more persons having the authority to grant or deny permission to modify the audit schedule for the campaign (i.e., administrators) to gain permission to edit the field. The Privacy Audit Module 432 may display an on-screen button that, when selected by the user, sends a notification (e.g., an email) to an administrator. The user can thus make a request to modify the audit schedule for the campaign in this manner.

[0106] At step 635, the Privacy Audit Module may determine whether permission has been granted by an administrator to allow a modification to the audit schedule. It may make this determination based on whether it has received input from an administrator to allow modification of the audit schedule for the campaign. If the administrator has granted permission, the Privacy Audit Module 432 at step 635 may allow the edit of the audit schedule. If at step 640, a denial of permission is received from the administrator, or if a certain amount of time has passed (which may be customized or based on a default setting), the Privacy Audit Module 432 retains the audit schedule for the campaign by not allowing any modifications to the schedule, and the process may proceed to step 645. The Privacy Audit Module may also send a reminder to the administrator that a request to modify the audit schedule for a campaign is pending.

[0107] At step 645, the Privacy Audit Module 432 determines whether a threshold amount of time (e.g., number of days) until the audit has been reached. This threshold may be a default value, or a customized value. If the threshold amount of time until an audit has been reached, the Privacy Audit Module 432 may at step 650 generate an electronic alert. The alert can be a message displayed to the collaborator the next time the collaborator logs into the system, or the alert can be an electronic message sent to one or more collaborators, including the campaign owners. The alert can be, for example, an email, an instant message, a text message, or one or more of these communication modalities. For example, the message may state, “This is a notification that a privacy audit for Campaign Internet Browsing History is scheduled to occur in 90 days.” More than one threshold may be assigned, so that the owner of the campaign receives more than one alert as the scheduled privacy audit deadline approaches. If the threshold number of days has not been reached, the Privacy Audit Module 432 will continue to evaluate whether the threshold has been reached (i.e., back to step 645).

[0108] In exemplary embodiments, after notifying the owner of the campaign of an impending privacy audit, the Privacy Audit Module may determine at step 655 whether it has received any indication or confirmation that the privacy audit has been completed. In example embodiments, the Privacy Audit Module allows for evidence of completion to be submitted, and if sufficient, the Privacy Audit Module 432 at step 660 resets the counter for the audit schedule for the campaign. For example, a privacy audit may be confirmed upon completion of required electronic forms in which one or more collaborators verify that their respective portions of the audit process have been completed. Additionally, users can submit photos, screen shots, or other documentation that show that the organization is complying with that user's assigned portion of the privacy campaign. For example, a database administrator may take a screen shot showing that all personal data from the privacy campaign is being stored in the proper database and submit that to the system to document compliance with the terms of the campaign.

[0109] If at step 655, no indication of completion of the audit has been received, the Privacy

[0110] Audit Module 432 can determine at step 665 whether an audit for a campaign is overdue (i.e., expired). If it is not overdue, the Privacy Audit Module 432 will continue to wait for evidence of completion (e.g., step 655). If the audit is overdue, the Privacy Audit Module 432 at step 670 generates an electronic alert (e.g., an email, instant message, or text message) to the campaign owner(s) or other administrators indicating that the privacy audit is overdue, so that the organization can take responsive or remedial measures.

[0111] In exemplary embodiments, the Privacy Audit Module 432 may also receive an indication that a privacy audit has begun (not shown), so that the status of the audit when displayed on inventory page 1500 shows the status of the audit as pending. While the audit process is pending, the Privacy Audit Module 432 may be operable to generate reminders to be sent to the campaign owner(s), for example, to remind the owner of the deadline for completing the audit.

[0112] E. Data Flow Diagram Module

[0113] The system 110 may be operable to generate a data flow diagram based on the campaign data entered and stored, for example in the manner described above.

[0114] I. Display of Security Indicators and Other Information

[0115] In various embodiments, a Data Flow Diagram Module is operable to generate a flow diagram for display containing visual representations (e.g., shapes) representative of one or more parts of campaign data associated with a privacy campaign, and the flow of that information from a source (e.g., customer), to a destination (e.g., an internet usage database), to which entities and computer systems have access (e.g., customer support, billing systems). Data Flow Diagram Module may also generate one or more security indicators for display. The indicators may include, for example, an “eye” icon to indicate that the data is confidential, a “lock” icon to indicate that the data, and/or a particular flow of data, is encrypted, or an “unlocked lock” icon to indicate that the data, and/or a particular flow of data, is not encrypted. In the example shown in FIG. 16, the dotted arrow lines generally depict respective flows of data and the locked or unlocked lock symbols indicate whether those data flows are encrypted or unencrypted. The color of dotted lines representing data flows may also be colored differently based on whether the data flow is encrypted or non-encrypted, with colors conducive for viewing by those who suffer from color blindness.

[0116] II. Exemplary Process Performed by Data Flow Diagram Module

[0117] FIG. 7 shows an example process performed by the Data Flow Diagram Module 700. At step 705, the Data Flow Diagram retrieves campaign data related to a privacy campaign record. The campaign data may indicate, for example, that the sensitive information related to the privacy campaign contains confidential information, such as the social security numbers of a customer.

[0118] At step 710, the Data Flow Diagram Module 700 is operable to display on-screen objects (e.g., shapes) representative of the Source, Destination, and Access, which indicate that information below the heading relates to the source of the personal data, the storage destination of the personal data, and access related to the personal data. In addition to campaign data regarding Source, Destination, and Access, the Data Flow Diagram Module 700 may also account for user defined attributes related to personal data, which may also be displayed as on-screen objects. The shape may be, for example, a rectangular box (see, e.g., FIG. 16). At step 715, the Data Flow Diagram Module 700 may display a hyperlink label within the on-screen object (e.g., as shown in FIG. 16, the word “Customer” may be a hyperlink displayed within the rectangular box) indicative of the source of the personal data, the storage destination of the personal data, and access related to the personal data, under each of the respective headings. When a user hovers over the hyperlinked word, the Data Flow Diagram is operable to display additional campaign data relating to the campaign data associated with the hyperlinked word. The additional information may also be displayed in a pop up, or a new page. For example, FIG. 16 shows that if a user hovers over the words “Customer,” the Data Flow Diagram Module 700 displays what customer information is associated with the campaign (e.g., the Subscriber ID, the IP and Mac Addresses associated with the Customer, and the customer's browsing and usage history). The Data Flow Diagram Module 700 may also generate for display information relating to whether the source of the data includes minors, and whether consent was given by the source to use the sensitive information, as well as the manner of the consent (for example, through an End User License Agreement (EULA)).

[0119] At step 720, the Data Flow Diagram Module 700 may display one or more parameters related to backup and retention of personal data related to the campaign, including in association with the storage destination of the personal data. As an example, Data Flow Diagram 1615 of FIG. 16 displays that the information in the Internet Usage database is backed up, and the retention related to that data is Unknown.

[0120] At 725, the Data Flow Diagram Module 700 determines, based on the campaign data associated with the campaign, whether the personal data related to each of the hyperlink labels is confidential. At Step 730, if the personal data related to each hyperlink label is confidential, the Data Flow Diagram Module 700 generates visual indicator indicating confidentiality of that data (e.g., an “eye” icon, as show in Data Flow Diagram 1615). If there is no confidential information for that box, then at step 735, no indicators are displayed. While this is an example of the generation of indicators for this particular hyperlink, in exemplary embodiments, any user defined campaign data may visual indicators that may be generated for it.

[0121] At step 740, the Data Flow Diagram Module 700 determined whether any of the data associated with the source, stored in a storage destination, being used by an entity or application, or flowing to one or more entities or systems (i.e., data flow) associated with the campaign is designated as encrypted. If the data is encrypted, then at step 745 the Data Flow Diagram Module 700 may generate an indicator that the personal data is encrypted (e.g., a “lock” icon). If the data is non-encrypted, then at step 750, the Data Flow Diagram Module 700 displays an indicator to indicate that the data or particular flow of data is not encrypted. (e.g., an “unlocked lock” icon). An example of a data flow diagram is depicted in FIG. 9. Additionally, the data flow diagram lines may be colored differently to indicate whether the data flow is encrypted or unencrypted, wherein the colors can still be distinguished by a color-blind person.

[0122] F. Communications Module

[0123] In exemplary embodiments, a Communications Module of the System 100 may facilitate the communications between various owners and personnel related to a privacy campaign. The Communications Module may retain contact information (e.g., emails or instant messaging contact information) input by campaign owners and other collaborators. The Communications Module can be operable to take a generated notification or alert (e.g., alert in step 670 generated by Privacy Audit Module 432) and instantiate an email containing the relevant information. As mentioned above, the Main Privacy Compliance Module 400 may, for example through a communications module, be operable to send collaborators emails regarding their assignment of one or more portions of inputs to campaign data. Or through the communications module, selecting the commentators button brings up one or more collaborators that are on-line

[0124] In exemplary embodiments, the Communications Module can also, in response to a user request (e.g., depressing the “comment” button show in FIG. 9, FIG. 10, FIG. 11, FIG. 12, FIG. 13, FIG. 16), instantiate an instant messaging session and overlay the instant messaging session over one or more portions of a GUI, including a GUI in which a user is presented with prompts to enter or select information. An example of this instant messaging overlay feature orchestrated by the Communications Module is shown in FIG. 17. While a real-time message session may be generated, off-line users may still able to see the messages when they are back on-line.

[0125] The Communications Module may facilitate the generation of alerts that indicate that one or more emails or instant messages await a collaborator.

[0126] If campaign data inputs have been assigned to one or more collaborators, but those collaborators have not input the data yet, the Communications Module, may facilitate the sending of an electronic message (such as an email) alerting the collaborators and owners that they have not yet supplied their designated portion of campaign data. Exemplary User Experience

[0127] In the exemplary embodiments of the system for operationalizing privacy compliance, adding a campaign (i.e., data flow) comprises gathering information that includes several phases: (1) a description of the campaign; (2) the personal data to be collected as part of the campaign; (3) who the personal data relates to; (4) where the personal data be stored; and (5) who will have access to the indicated personal data.

[0128] A. FIG. 8: Campaign Record Creation and Collaborator Assignment

[0129] FIG. 8 illustrates an example of the first phase of information gathering to add a campaign. In FIG. 8, a description entry dialog 800 may have several fillable/editable fields and drop-down selectors. In this example, the user may fill out the name of the campaign in the Short Summary (name) field 805, and a description of the campaign in the Description field 810. The user may enter or select the name of the business group (or groups) that will be accessing personal data for the campaign in the Business Group field 815. The user may select the primary business representative responsible for the campaign (i.e., the campaign's owner), and designate him/herself, or designate someone else to be that owner by entering that selection through the Someone Else field 820. Similarly, the user may designate him/herself as the privacy office representative owner for the campaign, or select someone else from the second Someone Else field 825. At any point, a user assigned as the owner may also assign others the task of selecting or answering any question related to the campaign. The user may also enter one or more tag words associated with the campaign in the Tags field 830. After entry, the tag words may be used to search for campaigns, or used to filter for campaigns (for example, under Filters 845). The user may assign a due date for completing the campaign entry, and turn reminders for the campaign on or off. The user may save and continue, or assign and close.

[0130] In example embodiments, some of the fields may be filled in by a user, with suggest-as-you-type display of possible field entries (e.g., Business Group field 815), and/or may include the ability for the user to select items from a drop-down selector (e.g., drop-down selectors 840a, 840b, 840c). The system may also allow some fields to stay hidden or unmodifiable to certain designated viewers or categories of users. For example, the purpose behind a campaign may be hidden from anyone who is not the chief privacy officer of the company, or the retention schedule may be configured so that it cannot be modified by anyone outside of the organization's' legal department.

[0131] B. FIG. 9: Collaborator Assignment Notification and Description Entry

[0132] Moving to FIG. 9, in example embodiments, if another business representative (owner), or another privacy office representative has been assigned to the campaign (e.g., John Doe in FIG. 8), the system may send a notification (e.g., an electronic notification) to the assigned individual, letting them know that the campaign has been assigned to him/her. FIG. 9 shows an example notification 900 sent to John Doe that is in the form of an email message. The email informs him that the campaign “Internet Usage Tracking” has been assigned to him, and provides other relevant information, including the deadline for completing the campaign entry and instructions to log in to the system to complete the campaign (data flow) entry (which may be done, for example, using a suitable “wizard” program). The user that assigned John ownership of the campaign may also include additional comments 905 to be included with the notification 900. Also included may be an option to reply to the email if an assigned owner has any questions.

[0133] In this example, if John selects the hyperlink Privacy Portal 910, he is able to access the system, which displays a landing page 915. The landing page 915 displays a Getting Started section 920 to familiarize new owners with the system, and also display an “About This Data Flow” section 930 showing overview information for the campaign.

[0134] C. FIG. 10: What Personal Data is Collected

[0135] Moving to FIG. 10, after the first phase of campaign addition (i.e., description entry phase), the system may present the user (who may be a subsequently assigned business representative or privacy officer) with a dialog 1000 from which the user may enter in the type of personal data being collected.

[0136] In addition, questions are described generally as transitional questions, but the questions may also include one or more smart questions in which the system is configured to: (1) pose an initial question to a user and, (2) in response to the user's answer satisfying certain criteria, presenting the user with one or more follow-up questions. For example, in FIG. 10, if the user responds with a choice to add personal data, the user may be additionally presented follow-up prompts, for example, the select personal data window overlaying screen 800 that includes commonly used selections may include, for example, particular elements of an individual's contact information (e.g., name, address, email address), Financial/Billing Information (e.g., credit card number, billing address, bank account number), Online Identifiers (e.g., IP Address, device type, MAC Address), Personal Details (Birthdate, Credit Score, Location), or Telecommunication Data (e.g., Call History, SMS History, Roaming Status). The System 100 is also operable to pre-select or automatically populate choices—for example, with commonly-used selections 1005, some of the boxes may already be checked. The user may also use a search/add tool 1010 to search for other selections that are not commonly used and add another selection. Based on the selections made, the user may be presented with more options and fields. For example, if the user selected “Subscriber ID” as personal data associated with the campaign, the user may be prompted to add a collection purpose under the heading Collection Purpose 1015, and the user may be prompted to provide the business reason why a Subscriber ID is being collected under the “Describe Business Need” heading 1020.

[0137] D. FIG. 11: Who Personal Data is Collected From

[0138] As displayed in the example of FIG. 11, the third phase of adding a campaign may relate to entering and selecting information regarding who the personal data is gathered from. As noted above, the personal data may be gathered from, for example, one or more Subjects 100. In the exemplary “Collected From” dialog 1100, a user may be presented with several selections in the “Who Is It Collected From” section 1105. These selections may include whether the personal data was to be collected from an employee, customer, or other entity. Any entities that are not stored in the system may be added. The selections may also include, for example, whether the data was collected from a current or prospective subject (e.g., a prospective employee may have filled out an employment application with his/her social security number on it). Additionally, the selections may include how consent was given, for example through an end user license agreement (EULA), on-line Opt-in prompt, Implied consent, or an indication that the user is not sure. Additional selections may include whether the personal data was collected from a minor, and where the subject is located.

[0139] E. FIG. 12: Where is the Personal Data Stored

[0140] FIG. 12 shows an example “Storage Entry” dialog screen 1200, which is a graphical user interface that a user may use to indicate where particular sensitive information is to be stored within the system. From this section, a user may specify, in this case for the Internet Usage History campaign, the primary destination of the personal data 1220 and how long the personal data is to be kept 1230. The personal data may be housed by the organization (in this example, an entity called “Acme”) or a third party. The user may specify an application associated with the personal data's storage (in this example, ISP Analytics), and may also specify the location of computing systems (e.g., servers) that will be storing the personal data (e.g., a Toronto data center). Other selections indicate whether the data will be encrypted and/or backed up.

[0141] The system also allows the user to select whether the destination settings are applicable to all the personal data of the campaign, or just select data (and if so, which data). In FIG. 12, the user may also select and input options related to the retention of the personal data collected for the campaign (e.g., How Long Is It Kept 1230). The retention options may indicate, for example, that the campaign's personal data should be deleted after a per-determined period of time has passed (e.g., on a particular date), or that the campaign's personal data should be deleted in accordance with the occurrence of one or more specified events (e.g., in response to the occurrence of a particular event, or after a specified period of time passes after the occurrence of a particular event), and the user may also select whether backups should be accounted for in any retention schedule. For example, the user may specify that any backups of the personal data should be deleted (or, alternatively, retained) when the primary copy of the personal data is deleted.

[0142] F. FIG. 13: Who and What Systems Have Access to Personal Data

[0143] FIG. 13 describes an example Access entry dialog screen 1300. As part of the process of adding a campaign or data flow, the user may specify in the “Who Has Access” section 1305 of the dialog screen 1300. In the example shown, the Customer Support, Billing, and Government groups within the organization are able to access the Internet Usage History personal data collected by the organization. Within each of these access groups, the user may select the type of each group, the format in which the personal data was provided, and whether the personal data is encrypted. The access level of each group may also be entered. The user may add additional access groups via the Add Group button 1310.

[0144] G. Facilitating Entry of Campaign Data, Including Chat Shown in FIG. 14

[0145] As mentioned above, to facilitate the entry of data collected through the example GUIs shown in FIGS. 8 through 12, in exemplary embodiments, the system is adapted to allow the owner of a particular campaign (or other user) to assign certain sections of questions, or individual questions, related to the campaign to contributors other than the owner. This may eliminate the need for the owner to contact other users to determine information that they don't know and then enter the information into the system themselves. Rather, in various embodiments, the system facilitates the entry of the requested information directly into the system by the assigned users.

[0146] In exemplary embodiments, after the owner assigns a respective responsible party to each question or section of questions that need to be answered in order to fully populate the data flow, the system may automatically contact each user (e.g., via an appropriate electronic message) to inform the user that they have been assigned to complete the specified questions and/or sections of questions, and provide those users with instructions as to how to log into the system to enter the data. The system may also be adapted to periodically follow up with each user with reminders until the user completes the designated tasks. As discussed elsewhere herein, the system may also be adapted to facilitate real-time text or voice communications between multiple collaborators as they work together to complete the questions necessary to define the data flow. Together, these features may reduce the amount of time and effort needed to complete each data flow.

[0147] To further facilitate collaboration, as shown FIG. 14, in exemplary embodiments, the

[0148] System 100 is operable to overlay an instant messaging session over a GUI in which a user is presented with prompts to enter or select information. In FIG. 14, a communications module is operable to create an instant messaging session window 1405 that overlays the Access entry dialog screen 1400. In exemplary embodiments, the Communications Module, in response to a user request (e.g., depressing the “comment” button show in FIG. 9, FIG. 10, FIG. 11, FIG. 12, FIG. 13, FIG. 16), instantiates an instant messaging session and overlays the instant messaging session over one or more portions of the GUI.

[0149] H: FIG. 15: Campaign Inventory Page

[0150] After new campaigns have been added, for example using the exemplary processes explained in regard to FIGS. 8-13, the users of the system may view their respective campaign or campaigns, depending on whether they have access to the campaign. The chief privacy officer, or another privacy office representative, for example, may be the only user that may view all campaigns. A listing of all of the campaigns within the system may be viewed on, for example, inventory page 1500 (see below). Further details regarding each campaign may be viewed via, for example, campaign information page 1600, which may be accessed by selecting a particular campaign on the inventory page 1500. And any information related to the campaign may be edited or added through, for example, the edit campaign dialog 1700 screen. Certain fields or information may not be editable, depending on the particular user's level of access. A user may also add a new campaign using a suitable user interface, such as the graphical user interface shown in FIG. 15 or FIG. 16.

[0151] In example embodiments, the System 100 (and more particularly, the Main Privacy Compliance Module 400) may use the history of past entries to suggest selections for users during campaign creation and entry of associated data. As an example, in FIG. 10, if most entries that contain the term “Internet” and have John Doe as the business rep assigned to the campaign have the items Subscriber ID, IP Address, and MAC Address selected, then the items that are commonly used may display as pre-selected items the Subscriber ID, IP address, and MAC Address each time a campaign is created having Internet in its description and John Doe as its business rep.

[0152] FIG. 15 describes an example embodiment of an inventory page 1500 that may be generated by the Main Privacy Compliance Module 400. The inventory page 1500 may be represented in a graphical user interface. Each of the graphical user interfaces (e.g., webpages, dialog boxes, etc.) presented in this application may be, in various embodiments, an HTML-based page capable of being displayed on a web browser (e.g., Firefox, Internet Explorer, Google Chrome, Opera, etc.), or any other computer-generated graphical user interface operable to display information, including information having interactive elements (e.g., an iOS, Mac OS, Android, Linux, or Microsoft Windows application). The webpage displaying the inventory page 1500 may include typical features such as a scroll-bar, menu items, as well as buttons for minimizing, maximizing, and closing the webpage. The inventory page 1500 may be accessible to the organization's chief privacy officer, or any other of the organization's personnel having the need, and/or permission, to view personal data.

[0153] Still referring to FIG. 15, inventory page 1500 may display one or more campaigns listed in the column heading Data Flow Summary 1505, as well as other information associated with each campaign, as described herein. Some of the exemplary listed campaigns include Internet Usage History 1510, Customer Payment Information, Call History Log, Cellular Roaming Records, etc. A campaign may represent, for example, a business operation that the organization is engaged in may require the use of personal data, which may include the personal data of a customer. In the campaign Internet Usage History 1510, for example, a marketing department may need customers' on-line browsing patterns to run analytics. Examples of more information that may be associated with the Internet Usage History 1510 campaign will be presented in FIG. 4 and FIG. 5. In example embodiments, clicking on (i.e., selecting) the column heading Data Flow Summary 1505 may result in the campaigns being sorted either alphabetically, or reverse alphabetically.

[0154] The inventory page 1500 may also display the status of each campaign, as indicated in column heading Status 1515. Exemplary statuses may include “Pending Review”, which means the campaign has not been approved yet, “Approved,” meaning the data flow associated with that campaign has been approved, “Audit Needed,” which may indicate that a privacy audit of the personal data associated with the campaign is needed, and “Action Required,” meaning that one or more individuals associated with the campaign must take some kind of action related to the campaign (e.g., completing missing information, responding to an outstanding message, etc.). In certain embodiments, clicking on (i.e., selecting) the column heading Status 1515 may result in the campaigns being sorted by status.

[0155] The inventory page 1500 of FIG. 15 may list the “source” from which the personal data associated with a campaign originated, under the column heading “Source” 1520. The sources may include one or more of the subjects 100 in example FIG. 1. As an example, the campaign “Internet Usage History” 1510 may include a customer's IP address or MAC address. For the example campaign “Employee Reference Checks”, the source may be a particular employee. In example embodiments, clicking on (i.e., selecting) the column heading Source 1520 may result in the campaigns being sorted by source.

[0156] The inventory page 1500 of FIG. 15 may also list the “destination” of the personal data associated with a particular campaign under the column heading Destination 1525. Personal data may be stored in any of a variety of places, for example on one or more storage devices 280 that are maintained by a particular entity at a particular location. Different custodians may maintain one or more of the different storage devices. By way of example, referring to FIG. 15, the personal data associated with the Internet Usage History campaign 1510 may be stored in a repository located at the Toronto data center, and the repository may be controlled by the organization (e.g., Acme corporation) or another entity, such as a vendor of the organization that has been hired by the organization to analyze the customer's internet usage history. Alternatively, storage may be with a department within the organization (e.g., its marketing department). In example embodiments, clicking on (i.e., selecting) the column heading Destination 1525 may result in the campaigns being sorted by destination.

[0157] On the inventory page 1500, the Access heading 1530 may show the number of transfers that the personal data associated with a campaign has undergone. In example embodiments, clicking on (i.e., selecting) the column heading “Access” 1530 may result in the campaigns being sorted by Access.

[0158] The column with the heading Audit 1535 shows the status of any privacy audits associated with the campaign. Privacy audits may be pending, in which an audit has been initiated but yet to be completed. The audit column may also show for the associated campaign how many days have passed since a privacy audit was last conducted for that campaign. (e.g., 140 days, 360 days). If no audit for a campaign is currently required, an “OK” or some other type of indication of compliance (e.g., a “thumbs up” indicia) may be displayed for that campaign's audit status. Campaigns may also be sorted based on their privacy audit status by selecting or clicking on the Audit heading 1535.

[0159] In example inventory page 1500, an indicator under the heading Risk 1540 may also display an indicator as to the Risk Level associated with the personal data for a particular campaign. As described earlier, a risk assessment may be made for each campaign based on one or more factors that may be obtained by the system. The indicator may, for example, be a numerical score (e.g., Risk Level of the campaign), or, as in the example shown in FIG. 15, it may be arrows that indicate the Overall Risk Assessment for the campaign. The arrows may be of different shades, or different colors (e.g., red arrows indicating “high risk” campaigns, yellow arrows indicating “medium risk” campaigns, and green arrows indicating “low risk” campaigns). The direction of the arrows—for example, pointing upward or downward, may also provide a quick indication of Overall Risk Assessment for users viewing the inventory page 1500. Each campaign may be sorted based on the Risk Level associated with the campaign.

[0160] The example inventory page 1500 may comprise a filter tool, indicated by Filters 1545, to display only the campaigns having certain information associated with them. For example, as shown in FIG. 15, under Collection Purpose 1550, checking the boxes “Commercial Relations,” “Provide Products/Services”, “Understand Needs,” “Develop Business & Ops,” and “Legal Requirement” will result the display under the Data Flow Summary 1505 of only the campaigns that meet those selected collection purpose requirements.

[0161] From example inventory page 1500, a user may also add a campaign by selecting (i.e., clicking on) Add Data Flow 1555. Once this selection has been made, the system initiates a routine to guide the user in a phase-by-phase manner through the process of creating a new campaign (further details herein). An example of the multi-phase GUIs in which campaign data associated with the added privacy campaign may be input and associated with the privacy campaign record is described in FIG. 8-13 above.

[0162] From the example inventory page 1500, a user may view the information associated with each campaign in more depth, or edit the information associated with each campaign. To do this, the user may, for example, click on or select the name of the campaign (i.e., click on Internet Usage History 1510). As another example, the user may select a button displayed on screen indicating that the campaign data is editable (e.g., edit button 1560).

[0163] I: FIG. 16: Campaign Information Page and Data Flow Diagram

[0164] FIG. 16 shows an example of information associated with each campaign being displayed in a campaign information page 1600. Campaign information page 1600 may be accessed by selecting (i.e., clicking on), for example, the edit button 1560. In this example, Personal Data Collected section 1605 displays the type of personal data collected from the customer for the campaign Internet Usage History. The type of personal data, which may be stored as data elements associated with the Internet Usage History campaign digital record entry. The type of information may include, for example, the customer's Subscriber ID, which may be assigned by the organization (e.g., a customer identification number, customer account number). The type of information may also include data associated with a customer's premises equipment, such as an IP Address, MAC Address, URL History (i.e., websites visited), and Data Consumption (i.e., the number of megabytes or gigabytes that the user has download).

[0165] Still referring to FIG. 16, the “About this Data Flow” section 1610 displays relevant information concerning the campaign, such as the purpose of the campaign. In this example, a user may see that the Internet Usage History campaign is involved with the tracking of internet usage from customers in order to bill appropriately, manage against quotas, and run analytics. The user may also see that the business group that is using the sensitive information associated with this campaign is the Internet group. A user may further see that the next privacy audit is scheduled for Jun. 10, 2016, and that the last update of the campaign entry was Jan. 2, 2015. The user may also select the “view history” hyperlink to display the history of the campaign.

[0166] FIG. 16 also depicts an example of a Data Flow Diagram 1615 generated by the system, based on information provided for the campaign. The Data Flow Diagram 1615 may provide the user with a large amount of information regarding a particular campaign in a single compact visual. In this example, for the campaign Internet Usage History, the user may see that the source of the personal data is the organization's customers. In example embodiments, as illustrated, hovering the cursor (e.g., using a touchpad, or a mouse) over the term “Customers” may cause the system to display the type of sensitive information obtained from the respective consumers, which may correspond with the information displayed in the “Personal Data Collected” section 1605.

[0167] In various embodiments, the Data Flow Diagram 1615 also displays the destination of the data collected from the User (in this example, an Internet Usage Database), along with associated parameters related to backup and deletion. The Data Flow Diagram 1615 may also display to the user which department(s) and what system(s) have access to the personal data associated with the campaign. In this example, the Customer Support Department has access to the data, and the Billing System may retrieve data from the Internet Usage Database to carry out that system's operations. In the Data Flow Diagram 1615, one or more security indicators may also be displayed. The may include, for example, an “eye” icon to indicate that the data is confidential, a “lock” icon to indicate that the data, and/or a particular flow of data, is encrypted, or an “unlocked lock” icon to indicate that the data, and/or a particular flow of data, is not encrypted. In the example shown in FIG. 16, the dotted arrow lines generally depict respective flows of data and the locked or unlocked lock symbols indicate whether those data flows are encrypted or unencrypted.

[0168] Campaign information page 1600 may also facilitate communications among the various personnel administrating the campaign and the personal data associated with it. Collaborators may be added through the Collaborators button 1625. The system may draw information from, for example, an active directory system, to access the contact information of collaborators.

[0169] If comment 1630 is selected, a real-time communication session (e.g., an instant messaging session) among all (or some) of the collaborators may be instantiated and overlaid on top of the page 1600. This may be helpful, for example, in facilitating population of a particular page of data by multiple users. In example embodiments, the Collaborators 1625 and Comments 1630 button may be included on any graphical user interface described herein, including dialog boxes in which information is entered or selected. Likewise, any instant messaging session may be overlaid on top of a webpage or dialog box. The system may also use the contact information to send one or more users associated with the campaign periodic updates, or reminders. For example, if the deadline to finish entering the campaign data associated with a campaign is upcoming in three days, the business representative of that assigned campaign may be sent a message reminding him or her that the deadline is in three days.

[0170] Like inventory page 1500, campaign information page 1600 also allows for campaigns to be sorted based on risk (e.g., Sort by Risk 1635). Thus, for example, a user is able to look at the information for campaigns with the highest risk assessment.

[0171] J: FIG. 17: Edit Campaign Dialog

[0172] FIG. 17 depicts an example of a dialog box—the edit campaign dialog 1000. The edit campaign dialog 1000 may have editable fields associated with a campaign. In this example, the information associated with the Internet Usage History campaign 310 may be edited via this dialog. This includes the ability for the user to change the name of the campaign, the campaign's description, the business group, the current owner of the campaign, and the particular personal data that is associated with the campaign (e.g., IP address, billing address, credit score, etc.). In example embodiments, the edit campaign dialog 1000 may also allow for the addition of more factors, checkboxes, users, etc.

[0173] The system 100 also includes a Historical Record Keeping Module, wherein every answer, change to answer, as well as assignment/re-assignment of owners and collaborators is logged for historical record keeping.

Integrated Mobile Applications

[0174] Various features of the privacy compliance system discussed above may be implemented via one or more mobile applications. For example, a mobile privacy compliance system may be configured to enable a user using a mobile computing device to, for example: (1) submit one or more answers to one or more screening questions related to a particular privacy campaign; (2) document one or more privacy incidents related to a particular privacy campaign; (3) complete one or more training exercise related to a particular privacy campaign; (4) complete one or more questionnaires related to privacy compliance knowledge; and/or (5) undertake any other activity related to the initiation of a new privacy campaign, the submission of information related to an existing privacy campaign, and/or the measurement of a risk of a particular privacy campaign or privacy maturity of a particular entity. In particular, the system is configured to provide a software application or other user interface for installation on a mobile computing device (e.g., smartphone) through which the user may submit information related to the privacy campaign. One or more embodiments of a mobile privacy compliance system are described below.

Example System Architecture

[0175] FIG. 18 is a block diagram of a Mobile Privacy Compliance System 1800 according to a particular embodiment. In various embodiments, the Mobile Privacy Compliance System 1800 is part of a Privacy Compliance System, or other system, which may, for example, be associated with a particular organization and be configured to ensure compliance with one or more legal or industry regulations related to the collection and storage of personal data. In some embodiments, the Mobile Privacy Compliance System 1800 is configured to facilitate the collection of information for use by the system in any suitable application related to privacy compliance.

[0176] As may be understood from FIG. 18, the Mobile Privacy Compliance System 1800 includes one or more computer networks 115, a Mobile Privacy Compliance Server 1810, a Privacy Compliance Server 1820, one or more remote computing devices 130 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), and One or More Databases 140. In particular embodiments, the one or more computer networks 115 facilitate communication between the Mobile Privacy Compliance Server 1810, Privacy Compliance Server 1820, one or more remote computing devices 130 (e.g., a desktop computer, laptop computer, tablet computer, etc.), and one or more databases 140.

[0177] 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 Mobile Privacy Compliance System 1810 and Database 140 may be, for example, implemented via a Local Area Network (LAN) or via the Internet. In other embodiments, the Database 140 may be stored on any suitable server described herein.

Exemplary Mobile Privacy Compliance System Platform

[0178] Various embodiments of a Mobile Privacy Compliance System 1900 may be implemented in the context of any suitable system (e.g., a privacy compliance system). For example, the Mobile Privacy Compliance System 1900 may be implemented to enable users to submit information related to a particular privacy campaign (e.g., answer screening questions, report a privacy incident, etc.). In particular embodiments, the system may implement one or more steps of the module in order to collect information 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 by, for example: (1) measuring a risk level of a particular privacy campaign; (2) adjusting an audit schedule of a particular privacy campaign; (3) measuring a privacy maturity of a particular subgroup of the organization; and/or (4) taking any other suitable action with respect to the collected information.

[0179] Various aspects of the system's functionality may be executed by certain system modules, including a Mobile Privacy Compliance Module 1900. This module is discussed in greater detail below. Although this module is presented as a series of steps, it should be understood in light of this disclosure that various embodiments of the Mobile Privacy Compliance Module described herein may perform the steps described below in an order other than in which they are presented. In still other embodiments, the Mobile Privacy Compliance Module may omit certain steps described below. In various other embodiments, the Mobile Privacy Compliance Module may perform steps in addition to those described.

Mobile Privacy Compliance Module

[0180] In particular embodiments, a Mobile Privacy Compliance Module 1900 is configured to display and receive input of information related to a particular privacy campaign; and (2) use the inputted information to take one or more actions related to the particular privacy campaign. Turning to FIG. 19, in particular embodiments, when executing the Mobile Privacy Compliance Module 1900, the system begins, at Step 1910, by providing a software application for installation on a mobile computing device (e.g., smartphone, tablet computer, etc.). In various embodiments, the system is configured to provide the software application via a suitable centralized software application repository (e.g., the Apple App Store, Google Play store, etc.). In still other embodiments, the system is configured to provide the software application for download via a suitable website or server.

[0181] In various embodiments, the system is configured to provide the software application for installation on any suitable mobile computing device (e.g., laptop computer, smartphone, tablet, etc.). In various embodiments, the software application is configured to provide one or more user interfaces configured to enable a user to provide one or more pieces of information related to a particular privacy campaign. The software application may, for example, provide one or more user interfaces configured for: (1) enabling a user to input one or more answers to one or more questionnaires related to a particular privacy campaign (e.g., what type of personal data is to be collected, how the data will be handled, who will have access to the data, etc.); (2) displaying training information related to compliance with one or more privacy requirements; (3) enable a user to take one or more images with the mobile computing device (e.g., using one or more imaging devices on the mobile computing device; (4) etc. These one or more user interfaces may include, for example, any suitable user interface described herein (e.g., or a mobile version of such an interface).

[0182] Continuing to Step 1920, the system receives, via the software application on the mobile computing device, first information related to a particular privacy campaign. In various embodiments, the first information may comprise campaign data may be representative of one or more attributes related to the personal data collected as part of the campaign. In other embodiments, the campaign data may include any other information related to the particular privacy campaign with which it is associated. In still other embodiments, the first information may comprise any suitable information described herein with respect to a particular privacy campaign or privacy campaigns.

[0183] The mobile app may also be adapted to provide incremental training to individuals. For example, the system may be adapted to provide incremental training to a user (e.g., in the form of the presentation of short lessons on privacy). Training sessions may be followed by short quizzes that are used to allow the user to assess their understanding of the information and to confirm that they have completed the training. In various embodiments, training session results may be utilized as part of measuring the privacy maturity of an organization by the system.

[0184] Returning to Step 1930, the system is configured to receive, via the software application, an input of second information related to the particular privacy campaign from a user of the mobile computing device. The mobile app may be used, for example, to collect answers to screening questions. The app may also be adapted to allow users to easily input data documenting and/or reporting a privacy incident. For example, the app may be adapted to assist a user in using their mobile device to capture an image of a privacy incident (e.g., a screen shot documenting that data has been stored in an improper location, or that a printout of sensitive information has been left in a public workspace within an organization.). The incident may, for example, be associated with a particular privacy campaign (e.g., because the incident involves personal data collected as part of that campaign. In some embodiments, in response to receiving one or more images of a privacy incident, the system may, for example: (1) perform an updated risk assessment for a particular privacy campaign; (2) flag the particular campaign for review; (3) etc.

[0185] Continuing to Step 1940, the system is configured to take one or more actions related to the particular privacy campaign based at least in part on the second information. In various embodiments, the one or more actions may include, for example: (1) flagging the particular privacy campaign for review; (2) updating one or more pieces of data associated with the particular privacy campaign; (3) calculating an updated risk level for the particular privacy campaign; (4) modifying an audit schedule for the particular privacy campaign; and/or (5) take any other suitable action.

[0186] In some embodiments, the system is configured to calculate an updated risk level for the particular privacy campaign based on the second information. A process for calculating a risk level of a privacy campaign is described above and may use the determination of weighting factors and assignment of relative risk ratings for each of the weighting factors. In particular embodiments in which the system is configured to calculate an updated risk level for a particular privacy campaign, the system may, for example: (1) scan the contents of the second information; (2) identify one or more keywords in the contents of the second information; (3) determine, based at least in part on the one or more keywords identified in the second information, whether to modify a risk level for the particular privacy campaign; and (4) in response to determining to modify the risk level: (A) modifying at least one of the plurality of weighting factors and/or the relative risk rating for at least one of the plurality of weighting factors; and (B) calculating the updated risk level based upon the modified plurality of weighting factors and/or the modified relative risk rating. The system may, for example, determine to modify the risk level for the privacy campaign based at least in part on one or more keywords identified in the first information.

[0187] The system may be further configured to modify an audit schedule for the particular privacy campaign based on the first information (e.g., based on the calculated updated risk level). As may be understood in light of this disclosure and the disclosures incorporated herein, the nature of a particular privacy campaign may dictate a frequency with which the particular privacy campaign should be audited in order to ensure compliance with legal and industry standards related to the collection and storage of personal data as part of the privacy campaign. Particular information that is associated with a particular privacy campaign may contain content that may indicate a reduction in risk of a particular privacy campaign. This may, for example, indicate that the audit frequency for the particular privacy campaign should be reduced (e.g., in order to conserve resources on unnecessary audits).

Exemplary User Experience

[0188] FIG. 20 depicts an exemplary screen display that a user may encounter related to the system described herein. In the exemplary screen display 2000 shown in FIG. 20, the system is embodied as a mobile application for a mobile computing device (e.g., a smartphone 2000). As may be understood from this figure, the mobile application comprises a user interface 2005 for enabling a user to provide information relate to a particular privacy campaign. The system may, for example, use this information to populate an electronic record associated with the campaign. When using the mobile application to provide such information, the user may select a Privacy Campaign Management indicia 2010. This may, for example, enable the user to select a particular privacy campaign, select a type of information to provide, etc.

[0189] The system may, in response to selection, by the user, of the Privacy Campaign Management indicia 2010, provide the user with a listing of a plurality of active privacy campaigns from which to select a particular privacy campaign. The listing may include, for example, one or more formal names for each of the plurality of privacy campaigns, one or more unique identifiers for each of the plurality of privacy campaigns, one or more short names for each of the plurality of privacy campaigns, or any other suitable listing from which the user may identify and select the desired particular privacy campaign. In response to the user selecting a particular privacy campaign, the system may then be configured to submit the provided information in relation to the selected campaign.

[0190] FIG. 21 depicts an exemplary screen display of a mobile application which is configured to enable a user to use a mobile computing device to provide one or more images to the system. For example, the app may be adapted to assist a user in using their mobile device to capture an image of a privacy incident (e.g., a screen shot documenting that data has been stored in an improper location, or that a printout of sensitive information has been left in a public workspace within an organization). The system may then use the one or more images in any suitable manner described herein.

Additional Aspects of System

1. Standardized and customized assessment of vendors' compliance with privacy and/or security policies

[0191] In particular embodiments, the system may be adapted to: (1) facilitate the assessment of one or more vendors' compliance with one or more privacy and/or security policies; and (2) allow organizations (e.g., companies or other organizations) who do business with the vendors to create, view and/or apply customized criteria to information periodically collected by the system to evaluate each vendor's compliance with one or more of the company's specific privacy and/or security policies. In various embodiments, the system may also flag any assessments, projects, campaigns, and/or data flows that the organization has documented and maintained within the system if those data flows are associated with a vendor that has its rating changed so that the rating meets certain criteria (e.g., if the vendor's rating falls below a predetermined threshold).

[0192] In particular embodiments:

- [0193] The system may include an online portal and community that includes a listing of all supported vendors.
- [0194] An appropriate party (e.g., the participating vendor or a member of the on-line community) may use the system to submit an assessment template that is specific to a particular vendor.
  - [0195] If the template is submitted by the vendor itself, the template may be tagged in any appropriate way as “official”
  - [0196] An instance for each organization using the system (i.e., customer) is integrated with this online community/portal so that the various assessment templates can be directly fed into that organization's instance of the system if the organization wishes to use it.
- [0197] Vendors may subscribe to a predetermined standardized assessment format.
  - [0198] Assessment results may also be stored in the central community/portal.
  - [0199] A third party privacy and/or security policy compliance assessor, on a schedule, may (e.g., periodically) complete the assessment of the vendor.
  - [0200] Each organization using the system can subscribe to the results (e.g., once they are available).
  - [0201] Companies can have one or more customized rules set up within the system for interpreting the results of assessments in their own unique way. For example:
    - [0202] Each customer can weight each question within an assessment as desired and set up addition/multiplication logic to determine an aggregated risk score that takes into account the customized weightings given to each question within the assessment.
    - [0203] Based on new assessment results—the system may notify each customer if the vendor's rating falls, improves, or passes a certain threshold.
    - [0204] The system can flag any assessments, projects, campaigns, and/or data flows that the customer has documented and maintained within the system if those data flows are associated with a vendor that has its rating changed.
      2. Privacy policy compliance system that facilitates communications with regulators (including translation aspect)

[0205] In particular embodiments, the system is adapted to interface with the computer systems of regulators (e.g., government regulatory agencies) that are responsible for approving privacy campaigns. This may, for example, allow the regulators to review privacy campaign information directly within particular instances of the system and, in some embodiments, approve the privacy campaigns electronically.

[0206] In various embodiments, the system may implement this concept by:

- [0207] Exporting relevant data regarding the privacy campaign, from an organization's instance of the system (e.g., customized version of the system) in standardized format (e.g., PDF or Word) and sending the extracted data to an appropriate regulator for review (e.g., in electronic or paper format).
  - [0208] Either regular provides the format that the system codes to, or the organization associated with the system provides a format that the regulators are comfortable with.
- [0209] Send secure link to regulator that gives them access to comment and leave feedback
  - [0210] Gives the regulator direct access to the organization's instance of the system with a limited and restricted view of just the projects and associated audit and commenting logs the organization needs reviewed.
  - [0211] Regulator actions are logged historically and the regulator can leave guidance, comments, and questions, etc.
- [0212] Have portal for regulator that securely links to the systems of their constituents.
  Details:
- [0213] When submitted—the PIAs are submitted with requested priority—standard or expedited.
- [0214] DPA specifies how many expedited requests individuals are allowed to receive.
- [0215] Either the customer or DPA can flag a PIA or associated comments/guidance on the PIA with “needs translation” and that can trigger an automated or manual language translation.
- [0216] Regulator could be a DPA “data protection authority” in any EU country, or other country with similar concept like FTC in US, or OPC in Canada.
  3. Systems/Methods for measuring the privacy maturity of a business group within an organization.

[0217] In particular embodiments, the system is adapted for automatically measuring the privacy of a business group, or other group, within a particular organization that is using the system. This may provide an automated way of measuring the privacy maturity, and one or more trends of change in privacy maturity of the organization, or a selected sub-group of the organization.

[0218] In various embodiments, the organization using the system can customize one or more algorithms used by the system to measure the privacy maturity of a business group (e.g., by specifying one or more variables and/or relative weights for each variable in calculating a privacy maturity score for the group). The following are examples of variables that may be used in this process:

- [0219] Issues/Risks found in submitted assessments that are unmitigated or uncaught prior to the assessment being submitted to the privacy office
  - [0220] % of privacy assessments with high issues/total assessments
  - [0221] % with medium
  - [0222] % with low
- [0223] Size and type of personal data used by the group
  - [0224] Total assessments done
  - [0225] Number of projects/campaigns with personal data
  - [0226] Amount of personal data
  - [0227] Volume of data transfers to internal and external parties
- [0228] Training of the people in the group
  - [0229] Number or % of individuals who have watched training, readings, or videos
  - [0230] Number or % of individuals who have completed quizzes or games for privacy training
  - [0231] Number or % of individuals who have attended privacy events either internally or externally
  - [0232] Number or % of individuals who are members of IAPP
  - [0233] Number or % of individuals who have been specifically trained in privacy either internally or externally, formally (IAPP certification) or informally
  - [0234] Usage of an online version of the system, or mobile training or communication portal that customer has implemented
- [0235] Other factors
  4. Automated assessment of compliance (scan app or website to determine behavior/compliance with privacy policies)

[0236] In various embodiments, instead of determining whether an organization complies with the defined parameters of a privacy campaign by, for example, conducting an audit as described above (e.g., by asking users to answer questions regarding the privacy campaign, such as “What is collected” “what cookies are on your website”, etc.), the system may be configured to automatically determine whether the organization is complying with one or more aspects of the privacy policy.

[0237] For example, during the audit process, the system may obtain a copy of a software application (e.g., an “app”) that is collecting and/or using sensitive user information, and then automatically analyze the app to determine whether the operation of the app is complying with the terms of the privacy campaign that govern use of the app.

[0238] Similarly, the system may automatically analyze a website that is collecting and/or using sensitive user information to determine whether the operation of the web site is complying with the terms of the privacy campaign that govern use of the web site.

[0239] In regard to various embodiments of the automatic application-analyzing embodiment referenced above:

- [0240] The typical initial questions asked during an audit may be replaced by a request to “Upload your app here”.
  - [0241] After the app is uploaded to the system, the system detects what privacy permissions and data the app is collecting from users.
  - [0242] This is done by having the system use static or behavioral analysis of the application, or by having the system integrate with a third party system or software (e.g., Veracode), which executes the analysis.
  - [0243] During the analysis of the app, the system may detect, for example, whether the app is using location services to detect the location of the user's mobile device.
  - [0244] In response to determining that the app is collecting one or more specified types of sensitive information (e.g., the location of the user's mobile device), the system may automatically request follow up information from the user by posing one or more questions to the user, such as:
    - [0245] For what business reason is the data being collected?
    - [0246] How is the user's consent given to obtain the data?
    - [0247] Would users be surprised that the data is being collected?
    - [0248] Is the data encrypted at rest and/or in motion?
    - [0249] What would happen if the system did not collect this data? What business impact would it have?
    - [0250] In various embodiments, the system is adapted to allow each organization to define these follow-up questions, but the system asks the questions (e.g., the same questions, or a customized list of questions) for each privacy issue that is found in the app.
  - [0251] In various embodiments, after a particular app is scanned a first time, when the app is scanned, the system may only detect and analyze any changes that have been made to the app since the previous scan of the app.
  - [0252] In various embodiments, the system is adapted to (optionally) automatically monitor (e.g., continuously monitor) one or more online software application marketplaces (such as Microsoft, Google, or Apple's App Store) to determine whether the application has changed. If so, the system may, for example: (1) automatically scan the application as discussed above; and (2) automatically notify one or more designated individuals (e.g., privacy office representatives) that an app was detected that the business failed to perform a privacy assessment on prior to launching the application.

[0253] In regard to various embodiments of the automatic application-analyzing embodiment referenced above:

- [0254] The system prompts the user to enter the URL of the web site to be analyzed, and, optionally, the URL to the privacy policy that applies to the web site.
- [0255] The system then scans the website for cookies, and/or other tracking mechanisms, such as fingerprinting technologies and/or 3rd party SDKs.
  - [0256] The system may then optionally ask the user to complete a series of one or more follow-up questions for each of these items found during the scan of the website.
  - [0257] This may help the applicable privacy office craft a privacy policy to be put on the website to disclose the use of the tracking technologies and SDK's used on the website.
- [0258] The system may then start a continuous monitoring of the website site to detect whether any new cookies, SDKs, or tracking technologies are used. In various embodiments, the system is configured to, for example, generate an alert to an appropriate individual (e.g., a designated privacy officer) to inform them of the change to the website. The privacy officer may use this information, for example, to determine whether to modify the privacy policy for the website or to coordinate discontinuing use of the new tracking technologies and/or SDK's.
- [0259] In various embodiments, the system may also auto-detect whether any changes have been made to the policy or the location of the privacy policy link on the page and, in response to auto-detecting such changes, trigger an audit of the project.
- [0260] It should be understood that the above methods of automatically assessing behavior and/or compliance with one or more privacy policies may be done in any suitable way (e.g., ways other than website scanning and app scanning). For example, the system may alternatively, or in addition, automatically detect, scan and/or monitor any appropriate technical system(s) (e.g., computer system and/or system component or software), cloud services, apps, websites and/or data structures, etc.
  5. System integration with DLP tools.

[0261] DLP tools are traditionally used by information security professionals. Various DLP tools discover where confidential, sensitive, and/or personal information is stored and use various techniques to automatically discover sensitive data within a particular computer system—for example, in emails, on a particular network, in databases, etc. DLP tools can detect the data, what type of data, the amount of data, and whether the data is encrypted. This may be valuable for security professionals, but these tools are typically not useful for privacy professionals because the tools typically cannot detect certain privacy attributes that are required to be known to determine whether an organization is in compliance with particular privacy policies.

[0262] For example, traditional DLP tools cannot typically answer the following questions:

- [0263] Who was the data collected from (data subject)?
- [0264] Where are those subjects located?
- [0265] Are they minors?
- [0266] How was consent to use the data received?
- [0267] What is the use of the data?
- [0268] Is the use consistent with the use specified at the time of consent?
- [0269] What country is the data stored in and/or transferred to?
- [0270] Etc.
- [0271] In various embodiments, the system is adapted to integrate with appropriate DLP and/or data discovery tools (e.g., INFORMATICA) and, in response to data being discovered by those tools, to show each area of data that is discovered as a line-item in a system screen via integration.
- [0272] The system may do this, for example, in a manner that is similar to pending transactions in a checking account that have not yet been reconciled.
- [0273] A designated privacy officer may then select one of those—and either match it up (e.g., reconcile it) with an existing data flow or campaign in the system OR trigger a new assessment to be done on that data to capture the privacy attributes and data flow.
  6. System for generating an organization'S data map by campaign, by system, or by individual data attributes.

[0274] In particular embodiments, the system may be adapted to allow users to specify various criteria, and then to display, to the user, any data maps that satisfy the specified criteria. For example, the system may be adapted to display, in response to an appropriate request: (1) all of a particular customer's data flows that are stored within the system; (2) all of the customer's data flows that are associated with a particular campaign; and/or (3) all of the customer's data flows that involve a particular address.

[0275] Similarly, the system may be adapted to allow privacy officers to document and input the data flows into the system in any of a variety of different ways, including:

- [0276] Document by process
  - [0277] The user initiates an assessment for a certain business project and captures the associated data flows (including the data elements related to the data flows and the systems they are stored in).
- [0278] Document by element
  - [0279] The user initiates an audit of a data element—such as SSN—and tries to identify all data structures associated with the organization that include the SSN. The system may then document this information (e.g., all of the organization's systems and business processes that involve the business processes.)
- [0280] Document by system
  - [0281] The user initiates an audit of a database, and the system records, in memory, the results of the audit.
    7. Privacy policy compliance system that allows users to attach emails to individual campaigns.

[0282] Privacy officers frequently receive emails (or other electronic messages) that are associated with an existing privacy assessment or campaign, or a potential future privacy assessment. For record keeping and auditing purposes, the privacy officer may wish to maintain those emails in a central storage location, and not in email. In various embodiments, the system is adapted to allow users to automatically attach the email to an existing privacy assessment, data flow, and/or privacy campaign. Alternatively or additionally, the system may allow a user to automatically store emails within a data store associated with the system, and to store the emails as “unassigned”, so that they may later be assigned to an existing privacy assessment, data flow, and/or privacy campaign.

- [0283] In various embodiments, the system is adapted to allow a user to store an email using:
  - [0284] a browser plugin-extension that captures webmail;
  - [0285] a Plug-in directly with office 365 or google webmail (or other suitable email application);
  - [0286] a Plug-in with email clients on computers such as Outlook;
  - [0287] via an integrated email alias that the email is forwarded to; or
  - [0288] any other suitable configuration
    8. Various Aspects of Related Mobile Applications

[0289] In particular embodiments, the system may use a mobile app (e.g., that runs on a particular mobile device associated by a user) to collect data from a user. The mobile app may be used, for example, to collect answers to screening questions. The app may also be adapted to allow users to easily input data documenting and/or reporting a privacy incident. For example, the app may be adapted to assist a user in using their mobile device to capture an image of a privacy incident (e.g., a screen shot documenting that data has been stored in an improper location, or that a printout of sensitive information has been left in a public workspace within an organization.)

[0290] The mobile app may also be adapted to provide incremental training to individuals. For example, the system may be adapted to provide incremental training to a user (e.g., in the form of the presentation of short lessons on privacy). Training sessions may be followed by short quizzes that are used to allow the user to assess their understanding of the information and to confirm that they have completed the training.

9. Automatic Generation of Personal Data Inventory for Organization

[0291] In particular embodiments, the system is adapted to generate and display an inventory of the personal data that an organization collects and stores within its systems (or other systems). As discussed above, in various embodiments, the system is adapted to conduct privacy impact assessments for new and existing privacy campaigns. During a privacy impact assessment for a particular privacy campaign, the system may ask one or more users a series of privacy impact assessment questions regarding the particular privacy campaign and then store the answers to these questions in the system's memory, or in memory of another system, such a third-party computer server.

[0292] Such privacy impact assessment questions may include questions regarding: (1) what type of data is to be collected as part of the campaign; (2) who the data is to be collected from; (3) where the data is to be stored; (4) who will have access to the data; (5) how long the data will be kept before being deleted from the system's memory or archived; and/or (6) any other relevant information regarding the campaign.

[0293] The system may store the above information, for example, in any suitable data structure, such as a database. In particular embodiments, the system may be configured to selectively (e.g., upon request by an authorized user) generate and display a personal data inventory for the organization that includes, for example, all of the organization's current active campaigns, all of the organization's current and past campaigns, or any other listing of privacy campaigns that, for example, satisfy criteria specified by a user. The system may be adapted to display and/or export the data inventory in any suitable format (e.g., in a table, a spreadsheet, or any other suitable format).

10. Integrated/Automated Solution for Privacy Risk Assessments

[0294] Continuing with Concept 9, above, in various embodiments, the system may execute multiple integrated steps to generate a personal data inventory for a particular organization. For example, in a particular embodiment, the system first conducts a Privacy Threshold Assessment (PTA) by asking a user a relatively short set of questions (e.g., between 1 and 15 questions) to quickly determine whether the risk associated with the campaign may potentially exceed a predetermined risk threshold (e.g., whether the campaign is a potentially high-risk campaign). The system may do this, for example, by using any of the above techniques to assign a collective risk score to the user's answers to the questions and determining whether the collective risk score exceeds a particular risk threshold value. Alternatively, the system may be configured to determine that the risk associated with the campaign exceeds the risk threshold value if the user answers a particular one or more of the questions in a certain way.

[0295] The system may be configured for, in response to the user's answers to one or more of the questions within the Privacy Threshold Assessment indicating that the campaign exceeds, or may potentially exceed, a pre-determined risk threshold, presenting the user with a longer set of detailed questions regarding the campaign (e.g., a Privacy Impact Assessment). The system may then use the user's answers to this longer list of questions to assess the overall risk of the campaign, for example, as described above.

[0296] In particular embodiments, the system may be configured for, in response to the user's answers to one or more of the questions within the Privacy Threshold Assessment indicating that the campaign does not exceed, or does not potentially exceed, a pre-determined risk threshold, not presenting the user with a longer set of detailed questions regarding the campaign (e.g., a Privacy Impact Assessment). In such a case, the system may simply save an indication to memory that the campaign is a relatively low risk campaign.

[0297] Accordingly, in particular embodiments, the system may be adapted to automatically initiate a Privacy Impact Assessment if the results of a shorter Privacy Threshold Assessment satisfy certain criteria. Additionally, or alternatively, in particular embodiments, the system may be adapted to allow a privacy officer to manually initiate a Privacy Impact Assessment for a particular campaign.

[0298] In particular embodiments, built into the Privacy Threshold Assessment and the Privacy Impact Assessment are the data mapping questions and/or sub-questions of how the personal data obtained through the campaign will be collected, used, stored, accessed, retained, and/or transferred, etc. In particular embodiments: (1) one or more of these questions are asked in the Privacy Threshold Assessment; and (2) one or more of the questions are asked in the Privacy Impact Assessment. In such embodiments, the system may obtain the answers to each of these questions, as captured during the Privacy Threshold Assessment and the Privacy Impact Assessment, and then use the respective answers to generate the end-to-end data flow for the relevant privacy campaign.

[0299] The system may then link all of the data flows across all of the organization's privacy campaigns together in order to show a complete evergreen version of the personal data inventory of the organization. Thus, the system may efficiently generate the personal data inventory of an organization (e.g., through the use of reduced computer processing power) by automatically gathering the data needed to prepare the personal data inventory while conducting Privacy Threshold Assessments and Privacy Impact Assessments.

Automated Approach to Demonstrating Privacy by Design

[0300] Privacy by design is a documented approach to managing privacy risks. One of the primary concepts is evaluating privacy impacts, and making appropriate privacy-protecting changes during the design phase of a project, before the project go-live. Organizations have embraced the concept, but have struggled with how to operationalize and demonstrate that they are doing this.

[0301] In various embodiments, the system is adapted to automate this with the following capabilities: (1) initial assessment; (2) gap analysis/recommendations; and/or (3) final/updated assessment. These capabilities are discussed in greater detail below.

[0302] Initial Assessment

[0303] In various embodiments, when a business team within a particular organization is planning to begin a privacy campaign, the system presents the business team with a set of assessment questions that are designed to help one or more members of the organization's privacy team to understand what the business team's plans are, and to understand whether the privacy campaign may have privacy impact on the organization. The questions may also include a request for the business team to provide the “go-live” date for the privacy campaign. In response to receiving the answers to these questions, the system stores the answers to the system's memory and makes the answers available to the organization's privacy team. The system may also add the “go-live” date to one or more electronic calendars (e.g., the system's electronic docket).

[0304] Gap Analysis/Recommendations

[0305] After the system receives the answers to the questions, one or more members of the privacy team may review the answers to the questions. The privacy team may then enter, into the system, guidance and/or recommendations regarding the privacy campaign. In particular embodiments, the system automatically reminds one or more members of the business team to implement the privacy team's recommendations before the go-live date. The system may also implement one or more audits (e.g., as described above) to make sure that the business team incorporates the privacy team's recommendations before the “go-live” date.

[0306] Final/Updated Assessment

[0307] Once the mitigation steps and recommendations are complete, the system may (e.g., automatically) conduct an updated review to assess the updated privacy impact and privacy risks.

[0308] Reporting and Historical Logging Capabilities

[0309] In particular embodiments, the system includes unique reporting and historical logging capabilities to automate Privacy-by-Design reporting. In various embodiments, the system is adapted to: (1) measure/analyze the initial assessment answers from the business team; (2) measure recommendations for the privacy campaign; (3) measure any changes that were implemented prior to the go-live date; (4) automatically differentiate between: (a) substantive privacy protecting changes, such as the addition of encryption, anonymization, or minimizations; and (b) non-substantive changes, such as spelling correction.

[0310] The system may also be adapted to generate a privacy-by-design report showing that: (1) projects are evaluated prior to go-live; and (2) substantive recommendations are made and implemented prior to go-live. This may be useful in documenting that privacy-by-design is being effectively implemented for a particular privacy campaign.

System for Preventing Individuals from Trying to Game the System

[0311] As discussed above, in particular embodiments, the system is adapted to display a series of threshold questions for particular privacy campaigns and to use conditional logic to assess whether to present additional, follow-up questions to the user. There may be situations in which a user may answer, or attempt to answer, one or more of the threshold questions incorrectly (e.g., dishonestly) in an attempt to avoid needing to answer additional questions. This type of behavior can present serious potential problems for the organization because the behavior may result in privacy risks associated with a particular privacy campaign being hidden due to the incorrect answer or answers.

[0312] To address this issue, in various embodiments, the system: (1) maintains a historical record of every button press (e.g., un-submitted system input) that an individual makes when a question is presented to them; and (2) tracks, and saves to memory, each incidence of the individual changing their answer to a question (e.g., (a) before formally submitting the answer by pressing an “enter” key, or other “submit” key on a user interface, such as a keyboard or graphical user interface on a touch-sensitive display screen; or (b) after initially submitting the answer).

[0313] The system may also be adapted to automatically determine whether a particular question (e.g., threshold question) is a “critical” question that, if answered in a certain way, would cause the conditional logic trigger to present the user with one or more follow-up questions. For example, the system may, in response to receiving the user's full set of answers to the threshold questions, automatically identify any individual question within the series of threshold questions that, if answered in a particular way (e.g., differently than the user answered the question) would have caused the system to display one or more follow up questions. The system may then flag those identified questions, in the system's memory, as “critical” questions.

[0314] Alternatively, the system may be adapted to allow a user (e.g., a privacy officer of an organization) who is drafting a particular threshold question that, when answered in a particular way, will automatically trigger the system to display one or more follow up questions to the user, to indicate that is a “critical” threshold question. The system may then save this “critical” designation of the question to the system's computer memory.

[0315] In various embodiments, the system is configured, for any questions that are deemed “critical” (e.g., either by the system, or manually, as discussed above), to determine whether the user exhibited any abnormal behavior when answering the question. For example, the system may check to see whether the user changed their answer once, or multiple times, before submitting their answer to the question (e.g., by tracking the user's keystrokes while they are answering the threshold question, as described above). As another example, the system may determine whether it took the user longer than a pre-determined threshold amount of time (e.g., 5 minutes, 3 minutes, etc. . . . ) to answer the critical threshold question.

[0316] In particular embodiments, the system may be adapted, in response to determining that the user exhibited abnormal behavior when answering the critical threshold question, to automatically flag the threshold question and the user's answer to that question for later follow up by a designated individual or team (e.g., a member of the organization's privacy team). In particular embodiments, the system may also, or alternatively, be adapted to automatically generate and transmit a message to one or more individuals (e.g., the organization's chief privacy officer) indicating that the threshold question may have been answered incorrectly and that follow-up regarding the question may be advisable. After receiving the message, the individual may, in particular embodiments, follow up with the individual who answered the question, or conduct other additional research, to determine whether the question was answered accurately.

Conclusion

[0317] Although embodiments above are described in reference to various systems and methods for creating and managing data flows related to individual privacy campaigns, 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. For example, the functionality described above for obtaining the answers to various questions (e.g., assigning individual questions or sections of questions to multiple different users, facilitating collaboration between the users as they complete the questions, automatically reminding users to complete their assigned questions, and other aspects of the systems and methods described above) may be used within the context of Privacy Impact Assessments (e.g., in having users answer certain questions to determine whether a certain project complies with an organization's privacy policies).

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

[0319] 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.

[0320] Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. While examples discussed above cover the use of various embodiments in the context of operationalizing privacy compliance and assessing risk of privacy campaigns, various embodiments may be used in any other suitable context. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for the purposes of limitation.

Claims

Certificate of Correction present

The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.

What is claimed is:

1. A computer-implemented data processing method for electronically receiving the input of campaign data related to a privacy campaign and electronically calculating a risk level for the privacy campaign based on the data inputs comprising:

providing a software application for installation on a mobile computing device;

displaying on a graphical user interface, via the software application, a prompt to create an electronic record for a privacy campaign, wherein the privacy campaign utilizes personal data collected from at least one or more persons or one or more entities;

receiving a command to create an electronic record for the privacy campaign;

creating an electronic record for the privacy campaign and digitally storing the record;

presenting, on one or more graphical user interfaces, a plurality of prompts for the input of campaign data related to the privacy campaign;

electronically receiving campaign data input by one or more users via the graphical user interface, wherein the campaign data identifies each of:

a description of the campaign;

one or more types of personal data related to the campaign;

a subject from which the personal data was collected;

the storage of the personal data; and

access to the personal data;

processing the campaign data by electronically associating the campaign data with the record for the privacy campaign;

receiving, via the software application, one or more inputs related to the privacy campaign, the one or more inputs comprising an image of a privacy incident captured using the mobile computing device;

automatically scanning the image of the privacy incident;

analyzing the scanned image to identify the privacy campaign associated with the privacy incident;

modifying the electronic record for the privacy campaign based at least in part on the one or more inputs:,

analyzing the image to identify one or more contents in the image;

determining, based at least in part on the one or more contents, whether to modify a risk level for the privacy campaign; and

in response to determining to modify the risk level, calculating an updated risk level for the privacy campaign by:

identifying a plurality of risk factors for the privacy campaign, wherein each of the plurality of risk factors has an associated weighting factor and the plurality of risk factors includes:

a type of the personal data collected as part of the privacy campaign; and

storage information for the personal data collected as part of the privacy campaign;

electronically modifying the associated weighting factor for at least one of the plurality factors;

after modifying the associated weighting factor for at least one of the plurality of risk factors, electronically calculating the updated risk level of the privacy campaign based upon, for each respective one of the plurality of risk factors, the weighting factor for the risk factor; and

digitally storing the updated risk level associated with the record for the campaign.

2. The computer-implemented data processing method of claim 1, wherein the method further comprises:

electronically calculating the updated risk level for the campaign based upon one or more factors selected from the group consisting of:

a nature of the personal data associated with the campaign;

a physical storage location of the personal data associated with the campaign;

a length of time that the personal data associated with the campaign will be retained in storage; and

a type of individual from which the personal data associated with the campaign originated; and

digitally storing the updated risk level associated with the record for the campaign.

3. The computer-implemented data processing method of claim 1, wherein the one or more inputs comprise one or more images of one or more privacy incidents.

4. The computer-implemented data processing method of claim 3, wherein:

the one or more images comprise one or more pieces of the personal data; and

the method further comprises analyzing the one or more images to identify the one or more pieces of personal data.

5. The computer-implemented data processing method of claim 4, wherein modifying the electronic record for the privacy campaign based at least in part on the one or more inputs comprises adjusting the risk level associated with the privacy campaign based on the one or more pieces of personal data.

6. The computer-implemented data processing method of claim 4, wherein modifying the electronic record for the privacy campaign based at least in part on the one or more inputs comprises modifying an audit schedule of the privacy campaign based on the one or more pieces of personal data.

7. The computer-implemented data processing method of claim 4, wherein the one or more images are one or more images selected from the group consisting of:

one or more images captured with an imaging device associated with the mobile computing device; and

one or more screenshots from a display screen associated with the mobile computing device.

8. The computer-implemented data processing method of claim 1, wherein:

the method further comprises measuring a privacy maturity of a particular organization;

the one or more inputs related to the privacy campaign comprise one or more responses to one or more training questionnaires; and

measuring the privacy maturity of the particular organization comprises modifying the measured privacy maturity based at least on part on the one or more responses.

9. The computer-implemented data processing method of claim 8, further comprising:

modifying a risk level associated with the privacy campaign based at least in part on the measured privacy maturity.

10. A computer-implemented data processing method comprising:

providing a software application for installation on a mobile computing device;

displaying on a graphical user interface, via the software application, a prompt to modify an electronic record for a privacy campaign, wherein the privacy campaign utilizes personal data collected from at least one or more persons or one or more entities;

receiving, from a user of the mobile computing device, first information associated with the privacy campaign;

modifying the electronic record for the privacy campaign based at least in part on the first information;

receiving, via the software application, an input of second information related to the privacy campaign, wherein the second information comprises an image of a particular privacy incident,

scanning one or more contents of the second information;

identifying one or more keywords in the one or more contents of the second information;

determining, based at least in apart on the one or more keywords identified in the second information, whether to modify a risk level for the particular privacy campaign; and

in response to determining to modify the risk level;

modifying at least one weighting factor of a plurality of weighting factors used to calculate the risk level, wherein each of the plurality of weighting factors is associated with a respective piece of the first information; and

calculating an updated risk level for the privacy campaign based at least in part on the modified at least one weighting factor, the plurality of weighting factors, and each perspective piece of the first information; and

displaying, on the graphical user interface, the second information associated with the privacy campaign, wherein:

the second information comprises information selected from a group consisting of:

one or more responses to one or more screening questions;

one or more pieces of information related to the particular privacy incident associated with the privacy campaign;

one or more response to one or more training quizzes.

11. The computer-implemented data processing method of claim 10, wherein:

the first information comprises the one or more pieces of information related to the particular privacy incident; and

the method further comprises:

analyzing the one or more pieces of information related to the particular privacy incident; and

modifying an audit schedule for the privacy campaign based at least in part on the analysis.

12. The computer-implemented data processing method of claim 11, wherein the one or more pieces of information related to the particular privacy incident comprise at least one unique identifier associated with the campaign.

13. The computer-implemented data processing method of claim 12, wherein the electronic record digitally stores campaign data related to a privacy campaign, and the campaign data identifies each of:

a description of the privacy campaign;

one or more types of personal data related to the privacy campaign;

a subject from which the personal data was collected;

a storage location of the personal data; and

one or more access permissions related to the personal data.

14. The computer-implemented data processing method of claim 13, wherein modifying the electronic record for the privacy campaign based at least in part on the first information comprises populating the campaign data in the electronic record based at least in part on the first information.

15. The computer-implemented data processing method of claim 14, further comprising calculating risk level for the privacy campaign based on the campaign data, wherein calculating the risk level for the campaign comprises:

electronically retrieving the campaign data associated with the electronic record for the campaign;

electronically determining a plurality of weighting factors for the campaign, wherein the plurality of weighting factors are based upon a plurality of factors including:

a nature of the personal data associated with the campaign;

a physical storage location of the personal data associated with the campaign;

a length of time that the personal data associated with the campaign will be retained in storage; and

a type of individual from which the personal data associated with the campaign originated;

electronically assigning a relative risk rating for each of the plurality of factors; and

electronically calculating a risk level for the campaign based upon the plurality of weighting factors and the relative risk rating for each of the plurality of factors; and

digitally storing the risk level associated with the record for the campaign.

16. The computer-implemented data processing method of claim 14, wherein modifying the electronic record for the privacy campaign based at least in part on the first information comprises:

calculating the risk level for the campaign based on the first information; and

modifying the risk level based at least in part on the first information.

17. The computer-implemented data processing method of claim 16, further comprising electronically determining an audit schedule for the campaign based at least in part on the risk level.

18. The computer-implemented data processing method of claim 10, wherein the first information associated with the privacy campaign comprises one or more images captured using one or more imaging devices of the mobile computing device.

19. The computer-implemented data processing method of claim 10, wherein the method further comprises analyzing the one or more images to identify the first information.

20. The computer-implemented data processing method of claim 19, wherein the method further comprises analyzing the one or more images to identify the privacy campaign.

Patent Citations (109)

Patent	Date	Inventor	Cited By
US5276735(A)	1994-01-01	Boebert et al.	Applicant
US6816944(B2)	2004-11-01	Peng	Applicant
US6925443(B1)	2005-08-01	Baggett, Jr. et al.	Applicant
US7234065(B2)	2007-06-01	Breslin et al.	Applicant
US7251624(B1)	2007-07-01	Lee et al.	Applicant
US7260830(B2)	2007-08-01	Sugimoto	Applicant
US7287280(B2)	2007-10-01	Young	Applicant
US7478157(B2)	2009-01-01	Bohrer et al.	Applicant
US7603356(B2)	2009-10-01	Schran et al.	Applicant
US7729940(B2)	2010-06-01	Harvey et al.	Applicant
US7788632(B2)	2010-08-01	Kuester et al.	Applicant
US7801758(B2)	2010-09-01	Gracie et al.	Applicant
US7853468(B2)	2010-12-01	Callahan et al.	Applicant
US7877812(B2)	2011-01-01	Koved et al.	Applicant
US7885841(B2)	2011-02-01	King	Applicant
US7966663(B2)	2011-06-01	Strickland et al.	Applicant
US7991559(B2)	2011-08-01	Dzekunov et al.	Applicant
US8019881(B2)	2011-09-01	Sandhu et al.	Applicant
US8146074(B2)	2012-03-01	Ito et al.	Applicant
US8156158(B2)	2012-04-01	Rolls et al.	Applicant
US8176334(B2)	2012-05-01	Vainstein	Applicant
US8504481(B2)	2013-08-01	Motahari et al.	Applicant
US8578036(B1)	2013-11-01	Holfelder et al.	Applicant
US8583694(B2)	2013-11-01	Siegel et al.	Applicant
US8601591(B2)	2013-12-01	Krishnamurthy et al.	Applicant
US8612420(B2)	2013-12-01	Sun et al.	Applicant
US8612993(B2)	2013-12-01	Grant et al.	Applicant
US8683502(B2)	2014-03-01	Shkedi et al.	Applicant
US8712813(B2)	2014-04-01	King	Applicant
US8805707(B2)	2014-08-01	Schumann, Jr. et al.	Applicant
US8805925(B2)	2014-08-01	Price et al.	Applicant
US8812342(B2)	2014-08-01	Barcelo et al.	Applicant
US8819253(B2)	2014-08-01	Simeloff et al.	Applicant
US8826446(B1)	2014-09-01	Liu et al.	Applicant
US8914299(B2)	2014-12-01	Pesci-Anderson et al.	Applicant
US8943076(B2)	2015-01-01	Stewart et al.	Applicant
US9092796(B2)	2015-07-01	Eversoll et al.	Applicant
US9094434(B2)	2015-07-01	Williams et al.	Applicant
US9152820(B1)	2015-10-01	Pauley, Jr. et al.	Applicant
US9158655(B2)	2015-10-01	Wadhwani et al.	Applicant
US9172706(B2)	2015-10-01	Krishnamurthy et al.	Applicant
US9202085(B2)	2015-12-01	Mawdsley et al.	Applicant
US9215252(B2)	2015-12-01	Smith et al.	Applicant
US9288118(B1)	2016-03-01	Pattan	Applicant
US9338188(B1)	2016-05-01	Ahn	Applicant
US9348802(B2)	2016-05-01	Massand	Applicant
US9384357(B2)	2016-07-01	Patil et al.	Applicant
US9401900(B2)	2016-07-01	Levasseur et al.	Applicant
US9424021(B2)	2016-08-01	Zamir	Applicant
US9477660(B2)	2016-10-01	Scott et al.	Applicant
US9507960(B2)	2016-11-01	Bell et al.	Applicant
US9521166(B2)	2016-12-01	Wilson	Applicant
US9602529(B2)	2017-03-01	Jones et al.	Applicant
US9646095(B1)	2017-05-01	Gottlieb et al.	Applicant
US9652314(B2)	2017-05-01	Mahiddini	Applicant
US9654541(B1)	2017-05-01	Kapczynski et al.	Applicant
US9691090(B1)	2017-06-01	Barday	Applicant
US9721108(B2)	2017-08-01	Krishnamurthy et al.	Applicant
US2002/0161594(A1)	2002-10-01	Bryan et al.	Applicant
US2003/0041250(A1)	2003-02-01	Proudler	Applicant
US2006/0075122(A1)	2006-04-01	Lindskog et al.	Applicant
US2007/0027715(A1)	2007-02-01	Gropper et al.	Applicant
US2007/0157311(A1)	2007-07-01	Meier et al.	Applicant
US2007/0266420(A1)	2007-11-01	Hawkins et al.	Applicant
US2007/0283171(A1)	2007-12-01	Breslin et al.	Applicant
US2008/0028435(A1)	2008-01-01	Strickland et al.	Applicant
US2009/0204452(A1)	2009-08-01	Iskandar et al.	Applicant
US2010/0121773(A1)	2010-05-01	Currier et al.	Applicant
US2010/0333012(A1)	2010-12-01	Adachi et al.	Applicant
US2011/0010202(A1)	2011-01-01	Neale	Applicant
US2012/0102543(A1)	2012-04-01	Kohli et al.	Applicant
US2012/0116923(A1)	2012-05-01	Irving et al.	Applicant
US2012/0259752(A1)	2012-10-01	Agee	Applicant
US2013/0218829(A1)	2013-08-01	Martinez	Applicant
US2013/0311224(A1)	2013-11-01	Heroux et al.	Applicant
US2013/0332362(A1)	2013-12-01	Ciurea	Applicant
US2013/0340086(A1)	2013-12-01	Blom	Applicant
US2014/0006616(A1)	2014-01-01	Aad et al.	Applicant
US2014/0012833(A1)	2014-01-01	Humprecht	Applicant
US2014/0032265(A1)	2014-01-01	Paprocki	Applicant
US2014/0040134(A1)	2014-02-01	Ciurea	Applicant
US2014/0047551(A1)	2014-02-01	Nagasundaram et al.	Applicant
US2014/0089039(A1)	2014-03-01	McClellan	Applicant
US2014/0208418(A1)	2014-07-01	Libin	Applicant
US2014/0278663(A1)	2014-09-01	Samuel et al.	Applicant
US2014/0283027(A1)	2014-09-01	Orona et al.	Applicant
US2014/0337466(A1)	2014-11-01	Li et al.	Applicant
US2015/0066577(A1)	2015-03-01	Christiansen et al.	Applicant
US2015/0106948(A1)	2015-04-01	Holman et al.	Applicant
US2015/0106949(A1)	2015-04-01	Holman et al.	Applicant
US2015/0169318(A1)	2015-06-01	Nash	Applicant
US2015/0229664(A1)	2015-08-01	Hawthorn et al.	Applicant
US2015/0242778(A1)	2015-08-01	Wilcox et al.	Applicant
US2015/0269384(A1)	2015-09-01	Holman et al.	Applicant
US2015/0356362(A1)	2015-12-01	Demos	Applicant
US2016/0048700(A1)	2016-02-01	Stransky-Heilkron	Applicant
US2016/0099963(A1)	2016-04-01	Mahaffey et al.	Applicant
US2016/0162269(A1)	2016-06-01	Pogorelik et al.	Applicant
US2016/0234319(A1)	2016-08-01	Griffin	Applicant
US2016/0321748(A1)	2016-11-01	Mahatma et al.	Applicant
US2016/0364736(A1)	2016-12-01	Maugans, III	Applicant
US2017/0142158(A1)	2017-05-01	Laoutaris et al.	Applicant
US2017/0161520(A1)	2017-06-01	Lockhart, III et al.	Applicant
US2017/0177324(A1)	2017-06-01	Frank et al.	Applicant
US2017/0193624(A1)	2017-07-01	Tsai	Applicant
US2017/0206707(A1)	2017-07-01	Guay et al.	Applicant
US2017/0270318(A1)	2017-09-01	Ritchie	Examiner
US2017/0330197(A1)	2017-11-01	DiMaggio	Examiner
WO2015116905	2015-08-01		Applicant

Non-Patent Literature (71)

Office Action, dated Dec. 15, 2016, from corresponding U.S. Appl. No. 15/256,419.Applicant
Restriction Requirement, dated Jan. 18, 2017, from corresponding U.S. Appl. No. 15/256,430.Applicant
Restriction Requirement, dated Nov. 21, 2016, from corresponding U.S. Appl. No. 15/254,901.Applicant
TRUSTe Announces General Availability of Assessment Manager for Enterprises to Streamline Data Privacy Management with Automation, PRNewswire, Mar. 4, 2015.Applicant
www.truste.com (1), 200150207, Internet Archive Wayback Machine, www.archive.org, Feb. 7, 2015.Applicant
Notice of Allowance, dated Apr. 12, 2017, from corresponding U.S. Appl. No. 15/256,419.Applicant
Notice of Allowance, dated May 5, 2017, from corresponding U.S. Appl. No. 15/254,901.Applicant
International Search Report, dated Jun. 6, 2017, from corresponding International Application No. PCT/US2017/025605.Applicant
International Search Report, dated Jun. 6, 2017, from corresponding International Application No. PCT/US2017/025611.Applicant
Written Opinion of the International Searching Authority, dated Jun. 6, 2017, from corresponding International Application No. PCT/US2017/025611.Applicant
Written Opinion of the International Searching Authority, dated Jun. 6, 2017, from corresponding International Application No. PCT/US2017/025605.Applicant
International Search Report, dated Jun. 21, 2017, from corresponding International Application No. PCT/US2017/025600.Applicant
Written Opinion of the International Searching Authority, dated Jun. 21, 2017, from corresponding International Application No. PCT/US2017/025600.Applicant
Ghiglieri, Marco et al.; Personal DLP for Facebook, 2014 IEEE International Conference on Pervasive Computing and Communication Workshops (Percom Workshops); IEEE; Mar. 24, 2014; pp. 629-634.Applicant
International Search Report, dated Aug. 15, 2017, from corresponding International Application No. PCT/US2017/036919.Applicant
International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036889.Applicant
International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036890.Applicant
International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036893.Applicant
International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036901.Applicant
International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036913.Applicant
International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036920.Applicant
Invitation to Pay Additional Search Fees, dated Aug. 10, 2017, from corresponding International Application No. PCT/US2017/036912.Applicant
Invitation to Pay Additional Search Fees, dated Aug. 10, 2017, from corresponding International Application No. PCT/US2017/036917.Applicant
Korba, Larry et al.; “Private Data Discovery for Privacy Compliance in Collaborative Environments”; Cooperative Design, Visualization, and Engineering; Springer Berlin Heidelberg; Sep. 21, 2008; pp. 142-150.Applicant
Office Action, dated Jul. 21, 2017, from corresponding U.S. Appl. No. 15/256,430.Applicant
Restriction Requirement, dated Jul. 28, 2017, from corresponding U.S. Appl. No. 15/169,658.Applicant
Symantec, Symantex Data Loss Prevention—Discover, monitor, and protect confidential data; 2008; Symantec Corporation; http://www.mssuk.com/images/Symantec%2014552315—IRC—BR—DLP—03.09—sngl.pdf.Applicant
Written Opinion of the International Searching Authority, dated Aug. 15, 2017, from corresponding International Application No. PCT/US2017/036919.Applicant
Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036889.Applicant
Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036890.Applicant
Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036893.Applicant
Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036901.Applicant
Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036913.Applicant
Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036920.Applicant
Notice of Allowance, dated Aug. 18, 2017, from corresponding U.S. Appl. No. 15/619,455.Applicant
Office Action, dated Aug. 23, 2017, from corresponding U.S. Appl. No. 15/626,052.Applicant
International Search Report, dated Aug. 21, 2017, from corresponding International Application No. PCT/US2017/036914.Applicant
Invitation to Pay Additional Search Fees, dated Aug. 24, 2017, from corresponding International Application No. PCT/US2017/036888.Applicant
Office Action, dated Aug. 24, 2017, from corresponding U.S. Appl. No. 15/169,643.Applicant
Office Action, dated Aug. 29, 2017, from corresponding U.S. Appl. No. 15/619,237.Applicant
Office Action, dated Aug. 30, 2017, from corresponding U.S. Appl. No. 15/619,212.Applicant
Office Action, dated Aug. 30, 2017, from corresponding U.S. Appl. No. 15/619,382.Applicant
Written Opinion of the International Searching Authority, dated Aug. 21, 2017, from corresponding International Application No. PCT/US2017/036914.Applicant
Office Action, dated Sep. 1, 2017, from corresponding U.S. Appl. No. 15/619,459.Applicant
International Search Report, dated Aug. 29, 2017, from corresponding International Application No. PCT/US2017/036898.Applicant
International Search Report, dated Sep. 1, 2017, from corresponding International Application No. PCT/US2017/036896.Applicant
Office Action, dated Sep. 11, 2017, from corresponding U.S. Appl. No. 15/619,375.Applicant
Office Action, dated Sep. 11, 2017, from corresponding U.S. Appl. No. 15/619,478.Applicant
Office Action, dated Sep. 19, 2017, from corresponding U.S. Appl. No. 15/671,073.Applicant
Office Action, dated Sep. 5, 2017, from corresponding U.S. Appl. No. 15/619,469.Applicant
Office Action, dated Sep. 6, 2017, from corresponding U.S. Appl. No. 15/619,479.Applicant
Office Action, dated Sep. 7, 2017, from corresponding U.S. Appl. No. 15/633,703.Applicant
Office Action, dated Sep. 8, 2017, from corresponding U.S. Appl. No. 15/619,251.Applicant
Written Opinion of the International Searching Authority, dated Aug. 29, 2017, from corresponding International Application No. PCT/US2017/036898.Applicant
Written Opinion of the International Searching Authority, dated Sep. 1, 2017, from corresponding International Application No. PCT/US2017/036896.Applicant
Office Action, dated Sep. 22, 2017, from corresponding U.S. Appl. No. 15/619,278.Applicant
Notice of Allowance, dated Sep. 27, 2017, from corresponding U.S. Appl. No. 15/626,052.Applicant
International Search Report, dated Oct. 3, 2017, from corresponding International Application No. PCT/US2017/036912.Applicant
Written Opinion of the International Searching Authority, dated Oct. 3, 2017, from corresponding International Application No. PCT/US2017/036912.Applicant
International Search Report, dated Oct. 12, 2017, from corresponding International Application No. PCT/US2017/036888.Applicant
Written Opinion of the International Searching Authority, dated Oct. 12, 2017, from corresponding International Application No. PCT/US2017/036888.Applicant
International Search Report, dated Oct. 20, 2017, from corresponding International Application No. PCT/US2017/036917.Applicant
Written Opinion of the International Searching Authority, dated Oct. 20, 2017, from corresponding International Application No. PCT/US2017/036917.Applicant
Office Action, dated Nov. 1, 2017, from corresponding U.S. Appl. No. 15/169,658.Applicant
Notice of Allowance, dated Nov. 7, 2017, from corresponding U.S. Appl. No. 15/671,073.Applicant
Final Office Action, dated Nov. 29, 2017, from corresponding U.S. Appl. No. 15/619,237.Applicant
Notice of Allowance, dated Dec. 5, 2017, from corresponding U.S. Appl. No. 15/633,703.Applicant
Notice of Allowance, dated Dec. 6, 2017, from corresponding U.S. Appl. No. 15/619,459.Applicant
Notice of Allowance, dated Dec. 12, 2017, from corresponding U.S. Appl. No. 15/169,643.Applicant
Notice of Allowance, dated Dec. 12, 2017, from corresponding U.S. Appl. No. 15/619,212.Applicant
Notice of Allowance, dated Dec. 12, 2017, from corresponding U.S. Appl. No. 15/619,382.Applicant

Abstract