Patent Publication Number: US-11663359-B2

Title: Data processing systems for identifying whether cookies contain personally identifying information

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 16/623,157, filed Dec. 16, 2019, which is a national phase entry of PCT/US2018/037504, filed Jun. 14, 2018, now expired, which is a continuation of U.S. patent application Ser. No. 15/858,802, filed Dec. 29, 2017, now U.S. Pat. No. 10,013,577, issued Jul. 3, 2018, and is also a continuation of U.S. patent application Ser. No. 15/626,052, filed Jun. 16, 2017, now U.S. Pat. No. 9,858,439, issued Jan. 2, 2018. The disclosures of all of the above patent applications are hereby incorporated herein by reference in their entirety. 
    
    
     BACKGROUND 
     Changes in legal and industry regulations related to the creation, collection, and storage of cookies for web site visitors have affected what sort of information can be included in cookies. Depending on a type and purpose of a particular cookie, the particular cookie may be required to avoid utilizing personally identifiable information. Accordingly, there is a need for improved systems and methods to ensure that website cookies follow relevant industry and legal requirements. 
     SUMMARY 
     A computer-implemented data processing method for identifying personal data in a particular web beacon, In any embodiment described herein, comprises: (A) scanning, by one or more processors, using a plurality of unique user profiles, a single website for one or more web beacons; (B) scanning, by one or more processors, a plurality of websites using a first particular one of the plurality of unique user profiles that persists across the plurality of websites for the one or more web beacons; (C) identifying, by one or more processors, the particular web beacon from the one or more web beacons; (D) determining, by one or more processors, a host of the particular web beacon; (E) determining, by one or more processors, a purpose of the particular web bacon; (F) determining, by one or more processors, based at least in part on the host of the particular cookie and the purpose of the particular cookie, whether a particular individual is likely to be identified by the particular web beacon; (G) in response to determining that a particular individual is likely to be identified by the particular cookie, generating, by one or more processors, a report regarding a likelihood that the particular individual might be identified by the particular web beacon; and (H) displaying, by one or more processors, the report to an individual associated with the single website. 
     A computer-implemented data-processing method of determining whether a particular HTML, canvas element of one or more canvas elements may include personally identifiable data, In any embodiment described herein, comprises: (A) creating, by one or more processors, a plurality of unique user profiles; (B) storing, by one or more processors, the plurality of unique user profiles in computer memory; (C) using, by one or more processors, each of the plurality of unique user profiles to scan a plurality of websites for one or more canvas read attempts; (D) gathering, by one or more processors, for each of the plurality of web sites, canvas element data for each of the plurality of unique user profiles, the canvas element data comprising the one or more canvas elements making the one or more canvas read attempts; (E) determining, by one or more processors, for each of the one or more canvas elements, a respective canvas element host; (F) determining, by one or more processors, based on the respective canvas element host, whether a particular canvas element of the one or more canvas elements may include personally identifiable data; and (G) in response to determining that the particular canvas element of the one or more canvas elements may include the personally identifiable data, transmitting a notification to an individual associated with at least one of the plurality of websites comprising the canvas element data associated with the particular canvas element. 
     A computer-implemented data-processing method of identifying one or more cookies of a plurality of cookies that may contain personal data, In any embodiment described herein, comprises: (1) creating, by one or more processors, a first unique user profile; (2) storing, by one or more processors, the first unique user profile in memory; (3) using, by one or more processors, the first unique user profile to access one or more first webpages of a first website; (4) collecting, by one or more processors, for each of the one or more first webpages, first cookie data for the first unique user profile, the first cookie data being associated with a first plurality of cookies; (5) using, by one or more processors, the first unique user profile to access one or more second webpages of a second website; (6) collecting, by one or more processors, for each of the one or more second webpages, second cookie data for the first unique user profile, the second cookie data being associated with a second plurality of cookies; (7) determining, by one or more processors, based on the first cookie data and the second cookie data, whether the first plurality of cookies contain one or more cookies that may contain personal data; (8) in response to determining that the first plurality of cookies contain one or more cookies that may contain personal data, generating, by one or more processors, a report including the first plurality of cookies; and (8) displaying, by one or more processors, the report to a site-owner of the first website. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Various embodiments of a system and method for determining whether particular cookies include personal data or may potentially be used to identify a particular individual are described below. In the course of this description, reference will be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein: 
         FIG.  1    depicts a cookie data collection and analysis system according to particular embodiments. 
         FIG.  2    is a schematic diagram of a computer (such as the cookie data collection and analysis server  110 , or one or more remote computing devices  130 ) that is suitable for use in any embodiment described herein of the cookie data collection and analysis system shown in  FIG.  1   . 
         FIG.  3    is a flowchart showing an example of a processes performed by the Cookie Data Collection and Analysis Module according to particular embodiments. 
         FIGS.  4 - 5    depict exemplary screen displays and graphical user interfaces (GUIs) according to various embodiments of the system, which may display information associated with the system or enable access to or interaction with the system by one or more users. 
     
    
    
     DETAILED DESCRIPTION 
     Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings. It should be understood that the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. 
     Overview 
     In any embodiment described herein, a personal data identification system is configured to determine whether one or more particular cookies can be uniquely attributable to a particular device, a particular user of the particular device, or a particular individual. In such embodiments, a cookie from which a particular individual may be directly identified or potentially identified may fall under the sort of personal data that a particular organization may be required, under one or more legal or industry requirements, to handle in a particular manner. 
     In any embodiment described herein, the personal data identification system is configured to determine whether one or more particular cookies may be used to directly identify a particular user or individual based on, for example: (1) a host of the one or more particular cookie; (2) a name of the one or more particular cookies; and/or (3) a value for the one or more particular cookies. In any embodiment described herein, the system is configured to use the host value to determine whether a particular cookie is a first-party cookie or a third-party cookie. As may be understood by one skilled in the art, a cookie may be more likely to identify a user if, for example: (1) the purpose of the cookie is to single out the individual or create a profile (e.g., in the case of a tracking cookie); (2) the cookie is a third-party cookie, and may involve unknown or unclear data practices; (3) the cookie is associated with a third-party host that has a policy that may allow selling and/or sharing of data; and/or (4) whether the cookie persists for a reasonable period of time, which may, for example, increase an amount of longitudinal data that can be compiled for a user associated with the cookie. 
     In any embodiment described herein, the personal data identification system may be implemented in the context of any suitable privacy compliance system that is configured to ensure compliance with one or more legal or industry standards related to the collection and storage of private information. In any embodiment described herein, a particular organization or sub-group may initiate a privacy campaign as part of its business activities. In such embodiments, the privacy campaign may include any undertaking by a particular organization (e.g., such as a project or other activity) that includes the collection, entry, and/or storage (e.g., in memory) of any privacy information or personal data associated with one or more individuals. In other embodiments, a privacy campaign may include any project undertaken by an organization that includes the use of personal data, or to any other activity which could have an impact on the privacy of one or more individuals. 
     In any embodiment described herein, the 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/or (11) any other suitable personal information discussed herein. In any embodiment described herein, such personal data may include one or more cookies (e.g., where the individual is directly identifiable or may be identifiable based at least in part on information stored as part of the one or more cookies). 
     In any embodiment described herein, the system may, for example, be configured to: (1) generate one or more virtual profiles; (2) use the one or more virtual profiles to access a plurality of websites; (3) collect cookie data for the plurality of websites for the one or more virtual profiles; and (4) analyze the cookie data to determine whether a particular website of the plurality of websites utilizes one or more cookies that may potentially include personal data. The system may then generate a report of the analysis, and display the report to an administrator or other individual associated with the particular website. 
     Exemplary Technical Platforms 
     As will be appreciated by one skilled in the relevant field, the present invention may be, for example, embodied as a computer system, a method, or a computer program product. Accordingly, various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, particular embodiments may take the form of a computer program product stored on a computer-readable storage medium having computer-readable instructions (e.g., software) embodied in the storage medium. Various embodiments may take the form of web-implemented computer software. Any suitable computer-readable storage medium may be utilized including, for example, hard disks, compact disks, DVDs, optical storage devices, and/or magnetic storage devices. 
     Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatuses (e.g., systems), and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by a computer executing computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus to create means for implementing the functions specified in the flowchart block or blocks. 
     These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner such that the instructions stored in the computer-readable memory produce an article of manufacture that is configured for implementing the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. 
     Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of mechanisms for performing the specified functions, combinations of steps for performing the specified functions, and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and other hardware executing appropriate computer instructions. 
     Example System Architecture 
       FIG.  1    is a block diagram of a Cookie Data Collection and Analysis System  100  according to a particular embodiment. In any embodiment described herein, the Cookie Data Collection and Analysis System  100  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 any embodiment described herein, the Cookie Data Collection and Analysis System  100  is configured to scan and analyze one or more of the particular organization&#39;s websites (e.g., one or more webpages) to identify one or more cookies which may contain personal data or may potentially be used to identify a particular individual or device. 
     As may be understood from  FIG.  1   , the Cookie Data Collection and Analysis System  100  includes one or more computer networks  115 , a Cookie Data Collection and Analysis Server  110 , a Privacy Compliance Server  120 , 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 any embodiment described herein, the one or more computer networks  115  facilitate communication between the Cookie Data Collection and Analysis Server  110 , Privacy Compliance Server  120 , one or more remote computing devices  130  (e.g., a desktop computer, laptop computer, tablet computer, etc.), and one or more databases  140 . 
     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 Cookie Data Collection and Analysis Server  110  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. 
       FIG.  2    illustrates a diagrammatic representation of a computer  200  that can be used within the Cookie Data Collection and Analysis System  100 , for example, as a client computer (e.g., one or more remote computing devices  130  shown in  FIG.  1   ), or as a server computer (e.g., Cookie Data Collection and Analysis System  110  shown in  FIG.  1   ). In any embodiment described herein, the computer  200  may be suitable for use as a computer within the context of the Cookie Data Collection and Analysis System  100  that is configured to monitor a user&#39;s system inputs to ascertain whether any of those inputs are abnormal. 
     In any embodiment described herein, the computer  200  may be connected (e.g., networked) to other computers in a LAN, an intranet, an extranet, and/or the Internet. As noted above, the computer  200  may operate in the capacity of a server or a client computer in a client-server network environment, or as a peer computer in a peer-to-peer (or distributed) network environment. The Computer  200  may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any other computer capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that computer. Further, while only a single computer is illustrated, the term “computer” shall also be taken to include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. 
     An exemplary computer  200  includes a processing device  202 , a main memory  204  (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), static memory  206  (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device  218 , which communicate with each other via a bus  232 . 
     The processing device  202  represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device  202  may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device  202  may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device  202  may be configured to execute processing logic  226  for performing various operations and steps discussed herein. 
     The computer  120  may further include a network interface device  208 . The computer  200  also may include a video display unit  210  (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device  212  (e.g., a keyboard), a cursor control device  214  (e.g., a mouse), and a signal generation device  216  (e.g., a speaker). 
     The data storage device  218  may include a non-transitory computer-accessible storage medium  230  (also known as a non-transitory computer-readable storage medium or a non-transitory computer-readable medium) on which is stored one or more sets of instructions (e.g., software instructions  222 ) embodying any one or more of the methodologies or functions described herein. The software instructions  222  may also reside, completely or at least partially, within main memory  204  and/or within processing device  202  during execution thereof by computer  200 —main memory  204  and processing device  202  also constituting computer-accessible storage media. The software instructions  222  may further be transmitted or received over a network  115  via network interface device  208 . 
     While the computer-accessible storage medium  230  is shown in an exemplary embodiment to be a single medium, the term “computer-accessible storage medium” should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-accessible storage medium” should also be understood to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the computer and that cause the computer to perform any one or more of the methodologies of the present invention. The term “computer-accessible storage medium” should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc. 
     Exemplary System Platform 
     Various embodiments of a cookie data collection and analysis system  100  may be implemented in the context of any suitable system (e.g., a privacy compliance system). For example, the cookie data collection and analysis system may be implemented to analyze a particular company or other organization&#39;s website (e.g., or websites) to determine whether the web site (e.g., or web sites) utilize(s) one or more cookies which may include personal data or may potentially be used to identify a particular individual. In any embodiment described herein, the system may implement the module in order to at least partially ensure compliance with one or more regulations (e.g., legal requirements) related to the collection and/or storage of personal data. Various aspects of the system&#39;s functionality may be executed by certain system modules, including a Cookie Data Collection and Analysis Module  300 . 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 Cookie Data Collection and Analysis Module  300  described herein may perform the steps described below in an order other than in which they are presented. In still other embodiments, the Cookie Data Collection and Analysis Module  300  may omit certain steps described below. In various other embodiments, the Cookie Data Collection and Analysis Module  300  may perform steps in addition to those described. 
     Cookie Data Collection and Analysis Module 
     In any embodiment described herein, a Cookie Data Collection and Analysis Module  300  is configured to: (1) collect cookie data for one or more websites; and (2) determine, based at least in part on the cookie data, whether one or more cookies utilized by a particular one of the one or more websites include personal data and/or may potentially be used to identify a particular individual. 
     Turning to  FIG.  3   , In any embodiment described herein, when executing the Cookie Data Collection and Analysis Module  300 , the system begins, at Step  310 , by creating one or more virtual profiles and storing the one or more virtual profiles in memory. In any embodiment described herein, the system is configured to generate a plurality of unique virtual profiles such that one or more websites may recognize each of the unique virtual profiles is the same individual over time. In any embodiment described herein, the system is configured to generate the unique virtual profiles such that one or more websites may recognize each unique virtual profile both within a particular website and across different websites. 
     In any embodiment described herein, the system is configured to create the one or more virtual profiles by assigning one or more attributes (e.g., unique attributes) to each of the one or more unique virtual profiles. In any embodiment described herein, the one or more attributes may include, for example: (1) one or more browser settings (e.g., browser type, one or more security settings, etc.); (2) one or more connection settings (e.g., connection type, connection speed, IP address, etc.); (3) one or more operating system settings (e.g., Windows, Linux, etc.); (4) one or more device settings (e.g., mobile, desktop, specific type, etc.); (5) name; (6) username; (7) gender; (8) age (e.g., age range); and/or (9) any other suitable attribute that may at least partially define a user profile. In any embodiment described herein, two or more of the unique virtual profiles may share one or more attributes. As a particular example, a first unique virtual profile may comprise the following attributes: (1) browser: Google Chrome; (2) operating system: iOS version 10.1; (3) device: iPhone 6s; (4) username: sample1; etc. 
     In any embodiment described herein, the system is configured to store the one or more unique virtual profiles in memory. The system may, for example, store the one or more unique virtual profiles in the One or More Databases  140  described above. In any embodiment described herein, the system is configured to store the one or more unique virtual profiles in memory for later retrieval by the system. In any embodiment described herein, the system is configured to utilize the one or more unique virtual profiles over time to access one or more websites. The system may, for example, utilize a virtual machine to emulate each of the one or more unique virtual profiles and systematically access the one or more websites using each of the one or more unique virtual profiles using the virtual machine. As may be understood in light of this disclosure, this may, for example, enable the system to determine whether particular persistent cookies utilized by particular websites may be used to identify a particular individual. The re-utilization of the one or more unique virtual profiles at various points in time is described more fully below. 
     Continuing to Step  320 , the system, in any embodiment described herein, is configured to use the one or more unique virtual profiles (e.g., each of the one or more unique virtual profiles) to access one or more web pages of one or more websites). In any embodiment described herein, the system is configured to simulate access by a plurality of unique users to each of the one or more web pages in order to collect cookie data for each of the one or more web pages. In any embodiment described herein, the system is configured to do this by using the one or more unique virtual profiles to access each webpage of a particular website. In other embodiments, the system is configured to do this by using the one or more unique virtual profiles to access a subset of the webpages that make up a particular website. 
     In any embodiment described herein, the one or more webpages may include, for example: (1) one or more webpages from one or more related websites (e.g., one or more websites owned or operated by a particular organization, company, or individual); (2) one or more webpages from one or more unrelated websites; (3) one or more webpages that make up a portion of webpages of a particular website; (4) one or more webpages that make up every webpage of a particular website; (5) one or more webpages from a plurality of websites; and/or (6) any other suitable combination of webpages and/or websites. 
     Returning to Step  330 , the system collects, for each of the one or more unique virtual profiles, cookie data from each of the one or more webpages. In any embodiment described herein, the system is configured to collect the cookie data for each unique virtual profile while the system is using the respective unique virtual profile to access the one or more webpages. The system may, for example: (1) access a first webpage of the one or more webpages using a first unique virtual profile; (2) collect cookie data from the first webpage for the first unique virtual profile; and (3) repeat steps 1 and 2 for each of the one or more webpages using each of the one or more unique virtual profiles. In any embodiment described herein, the system is configured to substantially simultaneously collect the cookie data for each of the one or more unique virtual profiles. In still other embodiments, the system is configured to collect the cookie data in any suitable order or timeframe. 
     In any embodiment described herein, the cookie data may include, for example, data for one or more cookies. In any embodiment described herein, the cookie data may include, for example: (1) a type of each of the one or more cookies; (2) a purpose of each of the one or more cookies; (3) a host of each of the one or more cookies; (4) a name of each of the one or more cookies; (5) a value of each of the one or more cookies; and/or (6) any other suitable data related to each of the one or more cookies. 
     Continuing to Step  340 , the system is configured to analyze the cookie data to determine whether one or more cookies of a plurality of cookies may contain personal data or may potentially be used to identify a particular individual. In any embodiment described herein, the system may analyze the cookie data to determine a persistence of a particular cookie. In any embodiment described herein, the system may determine an expiration time of a particular cookie. In any embodiment described herein, the system may be configured to determine that one or more cookies may contain personal data in response to determining that an amount of time prior to the expiration time is above a particular threshold amount of time (e.g., thirty seconds, one minute, one hour, one day, two days, one week, two weeks, one month, or any other suitable amount of time). In any embodiment described herein, the threshold amount of time may vary based at least in part on whether the cookie is a first-party or a third-party cookie. 
     In any embodiment described herein, the system is configured to determine whether the one or more cookies are unique to a particular virtual profile. In response to determining that the one or more cookies are unique, the system may determine that the one or more cookies may potentially be used to identify a particular individual. 
     In any embodiment described herein, the system is configured to analyze the one or more cookies to determine whether the one or more cookies are first-party cookies or third-party cookies. In any embodiment described herein, the system is configured to determine that a third-party cookie may potentially be used to identify a particular individual. In such embodiments, a third-party cookie may include a cookie generated by a third-party, which may, for example, engage in unknown and or unclear data practices. For example, computer code associated with the third-party cookie may collect information via the cookie for a particular user that is beyond a scope of data intended to that a particular website intended to collect when the website utilized the third-party cookie. 
     In any embodiment described herein, analyzing the cookie data may include comparing data associated with a first cookie to data associated with a second cookie. In any embodiment described herein, the first and second cookie may include a first cookie associated with a first virtual profile and a second cookie associated with a second virtual profile. In any embodiment described herein, the system is configured to determine whether the first or second cookie persists across a plurality of webpages across, for example: (1) a particular website; (2) a particular domain; (3) a plurality of web sites; and/or (4) a plurality of domains. In any embodiment described herein, the system may determine that a particular cookie that persists across a plurality of websites or domains may include personally identifiable data. 
     Returning to Step  350 , the system, in response to determining that the one or more cookies may contain personal data or potentially be used to identify the particular individual, generates a report regarding the one or more cookies. In any embodiment described herein, the report may include an identification of the one or more cookies. In other embodiments, the report may flag one or more cookies identified as potentially including personal data. In still other embodiments, the system may be configured to automatically cease collection of data associated with the one or more cookies (e.g., until one or more users review the generated report). 
     Next, at Step  360 , the system displays the report to one or more individuals associated with a particular one of the one or more websites. In any embodiment described herein, the system is configured to display the report on a suitable computer device, such as any of the one or more remote computing devices  130  shown in  FIG.  1   . In any embodiment described herein, the one or more individuals may include any suitable individual, such as, for example: (1) a site owner of a particular webpage (e.g., of a particular website) of the one or more webpages; (2) a privacy officer associated with an organization that runs a particular webpage of the one or more webpages; and/or (3) any other suitable individual associated with any of the one or more individuals for which the cookie data analysis described above was performed. In any embodiment described herein, the report may enable the one or more individuals to make one or more changes to (e.g., modify) one or more cookies from the one or more webpages. The modifications may include, for example, one or more changes to modify data collected and stored along with one or more particular cookies to ensure that such storage does not involve personal data in a way that may conflict with one or more legal or industry requirements. 
     Exemplary User Experience 
       FIGS.  4 - 5    depict exemplary screen displays that a user may encounter related to the system described herein.  FIG.  4    depicts a screen display  400  that a user may experience when accessing a particular website. As may be understood from this figure, a particular website may prompt a user to authorize the collection of data related to their experience on the website using cookies. In any embodiment described herein, the system described herein may determine that cookies collected following authorization from a user are more likely to include personal data and/or may be likely to identify the individual user. In still other embodiments, the system may be configured to not flag such cookies (e.g., in a generated report), as the user has provided explicit authorization to collect such personal data (e.g., via one or more cookies). In still other embodiments, the system may be configured to flag cookies that are prohibited by law. 
       FIG.  5    depicts an exemplary screen display of a webpage  500  that illustrates exemplary cookies that may persist across a plurality of websites. As shown in this figure, a user has the option to share content from the webpage on Facebook via a Facebook Share button  505 . As may be understood from this figure, the webpage is not part of Facebook&#39;s domain and is an entirely separate website. In this example, however, because the user is separately logged into Facebook (e.g., on the same web browser), Facebook can track the user at the present webpage using a cookie. The computer code utilized by the present website to enable users to share the website via Facebook would likely be determined by the system to potentially contain personally identifiable information (e.g., through the user&#39;s Facebook profile). If, for example, the same user visited a plurality of websites with an embedded Facebook Share Button  505 , characteristics for cookies set for the user may become stable for that user. In this example, the likelihood that the user may be identified is relatively high (e.g., because the stability of the profile that may be identified may begin to look like a behavioral profile for that user). The system may, for a different user accessing the websites, create a similarly stable profile for the second user that differs from that of the first user. In this way, cookies that persist across a plurality of websites may be more likely to become uniquely identifiable for particular users. Such cookies may be flagged by the system as potentially problematic for potentially containing personal data or personally identifiable information. 
       FIG.  5    further includes a third-party advertisement  510 , which may, for example, utilize a third-party cookie. As discussed above, third-party cookies may be more likely to include personal data or potentially personally identifiable data. Advertisements such as these may, for example, be encoded by a third-party provider, which may direct advertisements based on information such as a user&#39;s browsing history, etc. Accordingly, the system may be configured to determine that a third-party cookie may contain personal information (e.g., and flag it as such in a report for the webpage  500 ). 
     Alternative Embodiments 
     Various embodiments of a system for identifying and determining whether a particular cookie may contain personally identifiable data may include one or more features in addition to those described herein. Various alternative embodiments of such a system are described below. 
     Real Time Check 
     In any embodiment described herein, the system is configured to scan a portion of the webpages on a particular website (e.g., rather than the entire website at once). In any embodiment described herein, this may, for example, avoid denial of access by the website (e.g., in response to being identified as an automated access). In such embodiments, the system is configured to scan a first portion of webpages of a particular website (e.g., using one or more virtual profiles) at a first time, and a second portion of webpages at a second time. 
     Website Scanning in Response to Determination of a Change in Privacy Policy 
     In any embodiment described herein, one or more websites may update a privacy policy for the website (e.g., to comply with one or more legal or policy changes). In any embodiment described herein, a change in a privacy policy may modify a relationship between a website and its users. In such embodiments, the system may be configured to: (1) determine that a particular website has changed its privacy policy; and (2) perform a new scan of the website (e.g., using one or more virtual profiles) in response to determining the change. The system may, for example, scan a website&#39;s privacy policy at a first time and a second time to determine whether a change has occurred. In any embodiment described herein, the change in policy may modify a manner in which the system analyzes cookie data to determine whether it may include personal data or potentially personally identifiable data. 
     Webform Scanning Across a Plurality of Webpages 
     In any embodiment described herein, a particular webpage or collection of webpages (e.g., website) may use one or more webforms to collect personal data associated with a user of the webpage. 
     In any embodiment described herein, any system described herein may be configured to use one or more website scanning tools to, for example: (1) identify a webform (e.g., on a website associated with a particular entity or organization); (2) robotically complete the webform; (3) and analyze the completed webform to determine whether the webform collects personally identifiable information. 
     In any embodiment described herein, the system may, for example: (1) robotically fill out the webform (e.g., using one or more virtual profiles); (2) analyze one or more pieces of computer code associated with the webform (e.g., JavaScript, HTML, etc.); and (3) map one or more business processes that utilize the data collected via the webform based at least in part on the analyzed one or more pieces of computer code. In any embodiment described herein, a particular entity that utilizes a webform to collect personal data for use in a particular processing activity (e.g., business process) may analyze one or more pieces of computer code associated with the webform to determine: (1) one or more systems associated with the entity to which data entered the webform is routed (e.g., one or more data assets that serve as a destination asset to data entered via the webform); (2) a purpose for the collection of the data entered via the webform (e.g., a processing activity that utilizes the destination asset discussed above; (3) a type of data collected via the webform; and/or (4) any other suitable information related to the collection of data via the webform. 
     In any embodiment described herein, a system may be configured to transmit a webform completion confirmation e-mail to a user that completes the webform. In any embodiment described herein, the system may be configured to analyze the e-mail or other message to identify one or more business processes that utilize the data collected by the webform (e.g., by scraping one or more contents of the e-mail or other message). The system may then determine a purpose of the data collection and/or an associated processing activity based at least in part on the analysis. 
     Canvas Fingerprinting 
     In any embodiment described herein, one or more websites may use one or more canvas fingerprinting techniques to identify and track visitors using one or more HTML5 canvas elements. In any embodiment described herein, the one or more websites use the one or more HTML5 canvas elements by: (1) causing a website visitor&#39;s browser “draw” a hidden line of text or 3D graphic that is converted into a digital token; (2) storing the digital token in computer memory. A system may then use the digital token to generate a profile of a user&#39;s browsing activity, which may, for example, allow advertisers to target advertising to the user&#39;s inferred demographics and preferences. 
     As may be understood in light of this disclosure, the creation of such a profile may involve potentially identifiable information. In any embodiment described herein, the profile (e.g., fingerprint) may be based at least in part on browser, operating system, and installed graphics hardware. Although this combination may not necessarily comprise personal data, such information could be combined with other data (e.g., browsing history, IP address, MAC address, etc.) to be sufficiently unique to identify a particular individual. As such, in any embodiment described herein, the system may scan one or more webpages for HTML5 canvas elements to identify potential webpages that may utilize such techniques to generate profiles for visitors (e.g., which may potentially contain personally identifiable information). 
     In any embodiment described herein, a system may be configured to scan a plurality of webpages using a plurality of unique virtual profiles (e.g., using a plurality of virtual machines or other virtual profile techniques) for canvas read attempts. The system may then be configured to use information regarding canvas read attempts across a particular website (e.g., in combination with other data) to determine whether a particular website or webpage may track and store personally identifiable information. In any embodiment described herein, each unique virtual profile may be defined by a particular IP address, MAC address, graphics hardware, operating system, browser, etc. 
     Web Beacon Identification and Scanning 
     In any embodiment described herein, one or more websites, email systems, etc. may utilize one or more web beacons (e.g., web bugs) to check that a user (e.g., a particular user) has accessed a piece of content. In any embodiment described herein, the one or more websites may utilize the one or more web beacons for one or more email tracking purposes, page tagging, and/or web analytics. Web beacons may, for example, be utilized to track who is reading a webpage or email, when, and from which computer. A web beacon may also, for example, be used to determine whether a particular email has been read, forwarded to another individual, etc. In any embodiment described herein, a web beacon may be used to determine whether a web page has been copied to another website. In any embodiment described herein, a web beacon may comprise one or more images (e.g., clear images such as gif or png images). 
     In any embodiment described herein, a web beacon may be used by one or more third parties to monitor activity of one or more customers at a particular website. For example, for a company that owns a network of websites, the company may use web beacons to count and recognize users travelling around different servers on the network. The system may, in any embodiment described herein, utilize web beacons in place of or in addition to cookies. 
     In any embodiment described herein, a web beacon comprises a small (e.g., typically pixel transparent) GIF or PNG image (e.g., or an image of the same color as a background) that is embedded into an HTML or other page. In any embodiment described herein, the page is usually a page on the web or within the content of an email. When a user opens a page with a browser or email reader, the image and other information is downloaded. In any embodiment described herein, when using a web beacon to track a user, a system may be configured to: (1) receive a request from the browser or email reader at a server that stores the image or information; and (2) identify a source of the request based at least in part on the request (e.g., and IP address or MAC address from which the request was received). 
     In any embodiment described herein, a third party may provide one or more elements that are utilized as web beacons (e.g., one or more advertisements, banners, buttons, etc.) on a particular website. The third party may then, for example, gather information about visitors to various websites as the third party pulls HTML content from the main site (e.g., when the third party site receives a request to download the element used as the beacon). A company or organization that provides one or more buttons or images that are used on many different sites may be able to at least partially track browsing habits of a significant number of web users (e.g., such as social media site users). As discussed above, browsing habits in combination with other information such as IP address, MAC address, etc. may potentially contain personally identifiable information. Accordingly, in addition to cookies as described above, a system such as the system described herein may scan one or more web sites for one or more images that call to a third party host. In any embodiment described herein, the system may be configured to determine that a particular web page element is a web beacon that may track potentially identifiable information in response to identifying the particular web page element on at least a particular number of webpages that make up a particular web site. 
     CONCLUSION 
     Although embodiments above are described in reference to various privacy compliance monitoring systems, it should be understood that various aspects of the system described above may be applicable to other privacy-related systems, or to other types of systems, in general. 
     While this specification contains many specific embodiment details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination. 
     Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. 
     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 monitoring user inputs related to 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.