Multi-administrator opt-out system and method

The system addresses opt-out challenges in multi-administrator environments by creating a master opt-out list with metadata and pseudonymizing data, ensuring compliance and enhancing campaign effectiveness while protecting privacy and reducing costs.

JP7579340B2Active Publication Date: 2024-11-07LIVERAMP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2022533376
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-12-05
Filing Date
2020-11-19
Publication Date
2024-11-07
Estimated Expiration
2040-11-19

AI Technical Summary

Technical Problem

Existing data processing systems struggle to handle opt-out requests from data subjects in multi-administrator environments, leading to non-compliance with privacy laws and reduced effectiveness of joint campaigns due to incompatible data formats and identifiers.

Method used

A system and method that uses data resolution processing to create a master opt-out list by attaching metadata to data from multiple data controllers, ensuring opt-out requests are respected across all controllers while allowing joint campaigns, and pseudonymizing data to protect privacy.

Benefits of technology

Ensures compliance with privacy laws and enhances campaign effectiveness by respecting data subject preferences, protecting privacy, and reducing computational costs through parallel processing of combined datasets.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579340000001
    Figure 0007579340000001
  • Figure 0007579340000002
    Figure 0007579340000002
Patent Text Reader

Abstract

A system and method for handling workflows for multiple data controllers fully respects data subject opt-outs, but still leverages the synergy of combined data from multiple controllers to increase the effectiveness of message sending. A data service provider performs a data resolution process on the data from each data controller. The results of the resolution process are used to create an opt-out list that can track various types of data in various formats, all of which can be used in joint campaigns. Metadata is added to the data so that the originating data controller is tracked throughout the process. The data is then combined, resulting in a master opt-out list. If a data subject has opted out for any of the controllers, the opt-out applies to the joint campaign.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This application claims priority to U.S. Provisional Patent Application No. 62 / 943,897, filed December 5, 2019, which is incorporated herein by reference in its entirety.

[0002] The field of the invention is opt-out control in multi-administrator environments using data processing systems that contain personally identifiable information (PII). [Background technology]

[0003] Many businesses hold data about consumers in order to create targeted messages to customers and potential customers. These businesses include retailers that hold data about their own customers as well as third-party data providers that may hold data about many consumers in a given geographic area. Businesses that hold data about consumers are subject to a growing number of data privacy laws, regulations, and rules in various jurisdictions, including, for example, the European Union's General Data Protection Regulation (GDPR). All of these laws, regulations, and rules are collectively referred to herein as "privacy laws." Businesses that hold such data processing systems need to ensure that their technology enables them to comply with applicable privacy laws.

[0004] One of the requirements of privacy laws in many jurisdictions is the technical capability to restrict the processing of personal data at the request of a person who is a data subject. This is commonly referred to as enabling the person to "opt out" of or to the use of this data. Under the GDPR, companies with consumer data are considered "data controllers", each of which is a natural or legal person, public authority, agency or other body that, alone or jointly with others, determines the purposes and means of the processing of personal data. The term "joint controllers" is used to describe situations in which two or more controllers jointly determine the purposes and means of processing. A "data processor" is a natural or legal person, public authority, agency or other body that processes personal data on behalf of a controller. An example of a data processor is a data services provider (DSP) that receives consumer data from a retailer and processes it on the retailer's behalf as part of a campaign to deliver targeted messages. A "data subject" is an identified or identifiable natural person, such as a consumer.

[0005] The GDPR includes a "right to restriction", meaning that a data subject can request the restriction of the processing of data concerning that data subject. When a controller receives a restriction request, the controller may not forward the data to a data processor for processing and the controller must not process the data itself. This right to restriction is generally considered here as a form of "opting out". The controller needs to be able to process opt-out requests within its data processing systems and therefore needs to implement and maintain hardware and software technologies for this purpose. A common measure is to maintain an opt-out list. In practice, a data subject can contact the controller, provide contact information such as an email address, and instruct the controller to stop sending messages targeted at the data subject. The controller then adds the data subject's email address to the controller's opt-out list. This opt-out list is forwarded to data processors working with the controller, so that the data processor can similarly avoid any targeted messages that would otherwise reach this data subject. After that, when the data processor processes the controller's data, messages sent to this data subject's e-mail address will be suppressed, i.e. they will not be sent.

[0006] While the opt-out lists just described work in a single-administrator environment, problems arise when multiple administrators want to engage in a joint campaign to send targeted messages. For example, one might assume that an airline, a car rental company, and a hotel chain want to engage in a joint campaign. The three companies may want to offer a discount to consumers who use all three of the companies' services when booking a trip. Each company may want to provide its own customer data to make the campaign effective, and may want to use a data service provider (DSP) to process the data and generate information for online messaging. Because the companies may have different, but complementary, information about the same consumer, combining the data of the three companies could better formulate a targeted message offer that would be of interest to that consumer.

[0007] In the joint campaign scenario just described, the airline, car rental company, and hotel chain are each the data controller, and the DSP is the data processor. Each will have their own opt-out list associated with their customers. However, the data from each of the three data controllers will often be in a different format. For example, the airline may have a frequent flyer program that is keyed by name, address, and internal customer number. The car rental company may use name and email address data. The hotel may use name and phone number data. When processing data for this multi-controller workflow, the DSP will want to use the combined properties of the three data sets to better target messages presented to a given data subject. However, the DSP must also take into account opt-out requests made by the consumer to each of the three data controllers. A data subject may have opted out to one or two of the three data controllers, but not all three. If a DSP chooses only one opt-out list to work with, it will not respect the opt-out requests of any consumers who have opted out to one of the other data controllers. As a result, campaigns will not comply with the opt-out requests of data subjects and may not comply with applicable privacy laws depending on the jurisdiction. DSPs also cannot simply aggregate opt-out lists because data is maintained in different formats and different identifiers are used to distinguish between each of the company's customers. DSPs can process data separately for each data controller and use each data controller's opt-out list when processing the controllers' data separately, but in this case the synergy of combining complementary data from multiple controllers will be lost and campaigns will therefore be less effective.

[0008] It will be appreciated that this same technical problem described above is raised when any two or more data controllers wish to engage in a joint campaign. Another instance where this problem arises is when one company uses data collected by another company, whereby both the data seller and the data buyer assume the role of data controller. In yet another instance, multiple companies share the responsibility of collecting and maintaining a mixed data set, where all providers would be considered data controllers. Prior art systems for handling opt-outs do not allow for compliance with privacy laws such as the GDPR in any of these situations. Therefore, improved data processing systems and methods are desired that technically facilitate full compliance with opt-out requirements while still allowing joint campaigns and other joint uses of data involving multiple data controllers.

[0009] The references mentioned in this Background section are not admitted to be prior art with respect to this invention. Summary of the Invention [Means for solving the problem]

[0010] The present invention relates to a system and method for processing a multi-data controller workflow, whereby the data subject's opt-out is fully respected, but the synergy of the combined data can still be achieved to improve the effectiveness of the campaign. The DSP performs a data resolution process on the data from each data controller. The results of the resolution process can be used to create an opt-out list that can track different types of data in different formats, all of which can be used for the joint campaign. As the data is pulled from multiple controllers and processed together in the multi-controller workflow, metadata is added to the data so that the originating data controller is tracked throughout the processing by the DSP. The data is then finally combined, resulting in a master opt-out list. If a data subject has opted out for any of the controllers in a multi-data controller workflow, the opt-out is applied to the joint campaign, even though one of the controllers' data may not strictly be the subject of the data subject's opt-out request. The present invention thereby realizes the data subject's intent by applying the opt-out directive to the data collected by each controller. However, because the combined opt-out only applies to multi-data controller workflows, each individual data controller workflow will still have a record of the data subject and may not receive an opt-out request from the data subject.

[0011] In various implementations of the invention, this approach offers many advantages: The DSP can isolate data from multiple data curators from each other, thereby preserving the confidentiality of all curators from the other curators; Companies participating in a collaboration do not need to disclose any of the company's customer data to another company; This not only helps protect the privacy of data subjects, but also allows the curators to comply with privacy laws and their own set privacy policies; This therefore encourages the curators to engage in campaigns for multiple curators with the assurance that the curator's data is protected, which improves campaign results and presents the curator's customers with offers that are more likely to be attractive to them.

[0012] Another advantage of the approach according to certain implementations of the present invention is that by applying identity resolution to the opt-out process, it is more likely that the actual wishes of the data subject will be respected. For example, assume that a data subject has multiple email addresses known to the DSP, but in an opt-out request provides only one of these email addresses to one of the data controllers involved in the joint campaign. The resolution process allows the DSP to apply the opt-out to all of these email addresses, and not just the email address provided to the data controller when the data subject made the opt-out request. Thus, although the system and method may exceed the strict requirements of applicable privacy laws, it comes closer to respecting the actual intentions of the data subject, thereby reducing the risk of a data subject being upset by receiving a message during a joint campaign if the data subject believed that the data subject's opt-out request should have blocked that message. This is similarly beneficial for data controllers involved in joint campaigns, as they do not risk losing customers due to their upset at being the subject of a joint campaign if they expected not to receive such messaging.

[0013] Another advantage of certain implementations of the present invention is that when a data controller transmits data to a DSP, the ingestion process replaces all identifiable personal information with pseudonymous identifiers. For example, if the input data contained "John Doe, j.doe@mail.com," this may be replaced with "f572d396fae9206628714fb2ce00f72e94f2258f." While the DSP can protect the data with security measures, this type of pseudonymization provides an additional layer of defense against data breaches. Even if the data is compromised by a malicious actor, such an actor would not be able to reassociate any pseudonymous identifiers with the original name and email address. This protects the actual identifiable information (such as name, address, etc.) and protects the association of other data (such as purchase history, products viewed, etc.) with any particular individual.

[0014] Another advantage of certain implementations of the present invention is that just as data controllers are isolated from each other during multi-controller processing, the DSP also isolates the data controller from the online message delivery platform. When a person interacts with a website, the website may use a login or other identity to establish an online "session." For example, if someone logs into their Facebook account, Facebook knows the identity associated with the activity of that session. When reporting message activity from a website, the DSP can anonymize the records to isolate activity (such as clicking on a banner message) from a specific individual. The data controller can receive aggregate reports to measure the effectiveness of the data controller's targeted messaging, but the data controller cannot associate specific website activity with a specific data subject. This feature again helps to further protect the privacy of individual consumers.

[0015] These and other features, objects and advantages of the present invention will be better understood from a consideration of the following detailed description of the preferred embodiment in conjunction with the drawings described below. [Brief description of the drawings]

[0016] [Figure 1] 1 is a data flow diagram illustrating a method according to an implementation of the present invention. [Diagram 2] FIG. 2 is a diagram of a hardware and software computer processing system architecture for implementing the method of FIG. 1 according to an implementation of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] Before describing the present invention in further detail, it is to be understood that the present invention is not limited to the specific embodiments described in any paragraph herein, and that the terminology used in describing a particular embodiment is for the purpose of describing that particular embodiment only, and is not intended to be limiting, since the scope of the present invention is limited only by the claims.

[0018] A method according to an implementation of the present invention may be described with reference to the data flow diagram of FIG. 1. A data administrator maintains records of data subjects as administrator data subject records 10. Typically, data subjects are customers (or potential customers). The number of such records is very large, and some companies may maintain records for millions of customers. The records include customer details such as contact information, purchase history, buying preferences, demographic information, etc. The company (the data administrator) is interested in retaining existing customers and gaining the trust and targeting effectiveness of new customers. Thus, the company collects information that it believes will help in this effort. To make the data effective for online targeted messaging, the customer records need to be converted into a format that can be used by the programmatic messaging platform or platforms 32 to the destination.

[0019] The data controller maintains a controller opt-out record 12, separate from the data subject record 10. This controller opt-out record 12 is maintained in compliance with applicable privacy laws and with the data controller's own established privacy policy, as explained above. When a data subject contacts the controller and instructs the controller to restrict processing in some way, the controller adds the subject's request to the opt-out record. The controller periodically transmits this controller opt-out record 12 to the data processor, thereby conveying the subject's request to other entities that may have access to the subject's data to handle campaigns. In Figure 1, the controller opt-out record 12 refers to the opt-out record sent by one or more data controllers to the data processor.

[0020] When a Data Service Provider (DSP) receives the controller's data subject records 10 from a data controller, it first pseudonymizes the records in a pseudonymization step 16. This means that any personally identifying information is replaced with a pseudonymous identifier. Additionally, the records are extended with metadata to add an identifier or tag corresponding to the data controller that supplied the record. This step results in a new data set: data subject record + metadata records 24. For example, a record sent by the car rental company Drive-Rite containing "John Doe, j.doe@mail.com" might have the name and email replaced with "f572d396fae9206628714fb2ce00f72e94f2258f" and a metadata tag added to note Drive-Rite as the data controller.

[0021] The pseudonymous identifier is obtained through the matching process step 22. The matching process step 22 eliminates minor differences in identifying information. Thus, if one administrator has "John Doe" and another administrator has "John Q. Doe" and both have the same email address, the matching process 22 is likely to return the same pseudonymous identifier for both records. This standardization ensures that the same pseudonymous identifier is consistently generated for the same consumer. In one example, the pseudonymous identifier may be generated by applying a hashing algorithm. Any slight difference in the string input to the hashing algorithm will result in different pseudonymous identifiers, and standardization in the matching process step 22 ensures that similar consumers have similar pseudonymous identifiers regardless of the data administrator that supplies the data. In this way, complementary data from various data administrators in a multi-administrator environment can be used together to improve campaign results.

[0022] After the replacement of personally identifiable data with a pseudonymous identifier is performed, there is no permanent description of the correspondence between the original identifying data (John Doe, j.doe@mail.com) and the pseudonymous data ("f572d396fae9206628714fb2ce00f72e94f2258f"). Thus, this conversion prevents re-identification in both directions. Entities in the online world, such as the programmatic messaging platform 32 to the destination, cannot associate the pseudonymous identifier with a known person. Similarly, the original data controller cannot connect a known person to an online activity. Thus, the two-way pseudonymization in certain implementations of the present invention protects the data subject's information from unethical data use.

[0023] DSPs rely on data controllers to forward opt-out data in the form of controller opt-out records 12 in addition to the controller's data subject records 10. That is, a typical controller's data subject (customer) records 10 contain identifying information and properties (purchase history, preferences, survey results, etc.). In contrast, controller opt-out records 12 contain only identifying information and instruct the DSP to place a given data subject (or subjects) on a controller-specific suppression list. When the DSP processes data from the controller, it suppresses all records relating to any subjects in the suppression list, as described more fully below.

[0024] It will be appreciated that records of the same data subject must be reconciled through a matching process step 22, not only to match pseudonymous identifiers, but also to make the complementary data useful together. Controllers can use different identifying information (such as name, email, phone, address, etc.) that may differ in content and spelling, but the effectiveness of a joint campaign depends on resolving the differences. The matching process step 22 creates an understanding of the common data subject identity. After the pseudonymization process, all original identifying information has been resolved, common identifying information has been determined, and matching records have been assigned the same pseudonymous identifier. As explained more fully below, the matching identifiers can be found in step 26 for source identifiers, or in step 28 for destination identifiers, mapping identifiers to destinations. Each data set remains entirely separate; i.e., the data sets themselves are not merged. However, pseudonymous identifiers have been selected from a common framework, allowing correlation of subject records across data sets from multiple data controllers. The shared framework of pseudonymous identifiers allows the opt-out process to use a data subject's opt-out request that is first sent to any data controller and then forwarded to a data processor to aggregate the data set. Any data subject's opt-out request to any controller in a workflow applies to all records in the workflow.

[0025] To initiate a multi-administrator workflow, multiple companies submit data records to the DSP and mutually authorize the DSP to combine and distribute the multiple companies' data to the programmatic messaging platform. To protect privacy, data is not shared between the admins. Each admin retains sole ownership of the original admin data subject records10 submitted by that admin. Note that in some cases, depending on the type of multi-administrator arrangement, one or more admins may not actually provide data to the workflow. For clarity, Figure 1 shows only one set of incoming admin data, but the key point here is that multiple admins are involved in the workflow.

[0026] The information from the multiple managers is combined to build a combined data set, step 20. Each manager benefits from the information provided by the other managers without exchanging data. For example, if one manager knows that a customer likes to travel in April and another manager knows that the same customer stays at a resort hotel, the combined information may be used to offer special prices on a tropical spring break. Traditionally, each manager would only have access to the data that each manager has collected. Any use of online targeted messaging would operate according to boundaries that separate one manager's information from another manager's information.

[0027] When processing the controller opt-out record 12, the DSP cannot rely on the controller opt-out record 12 containing all known identifying information about the data subject. For example, a typical controller data subject record 10 from a controller may contain name, email, phone, and customer number. That same controller may send an controller opt-out record 12 that contains only a customer number. The DSP performs a match processing step 22 on the controller data subject record 10 as well as the controller opt-out record 12, associating the customer number with the data subject's name, email, and phone number using the previous complete data subject record. Each of these attributes is added to a suppression list maintained for the given data controller. When the DSP processes subsequent data records to apply opt-out suppressions in the opt-out service 14, this match processing step 22 allows the DSP to recognize data subject records that may only have a phone number without having to specifically include an opt-out record identifier in every record. The opt-out suppression process of the Opt-Out Service14 therefore more fully represents the data subject's intent without requiring full coordination between the data controller and the data processor.

[0028] The DSP workflow applies opt-out suppression in step 26 after forming the joint dataset in step 20 of building the combined dataset. The data processor has to take into account the opt-out directive from the data subject (even if the directive was received indirectly through the data controller). This means filtering out all records belonging to data subjects requesting an opt-out, which are identified in the controller’s opt-out record 12. If processing data from only one data controller, this check is easy: if a person opts out with controller C, the controller forwards the request to the DSP and updates the opt-out suppression list held for controller C. If the DSP processes data on behalf of controller C, the DSP applies its specific suppression list and filters out any records of data subjects in the list.

[0029] Applying opt-outs to multiple controllers involves subtleties to consider data subject rights. The combined dataset may contain records for a given data subject, some of which are subject to an explicit opt-out and others not. For example, John Doe may have opted out with Fly-Rite airlines but not with Stay-Rite hotels. (Perhaps Doe travels a lot by car, often books rooms with Stay-Rite, and appreciates the discount coupons he receives by email.) In a workflow with just one controller, Stay-Rite could use Doe's data. But with multiple controllers, the situation changes. The combined dataset contains records from all controllers involved in the workflow. Each data subject's record is the union of all such records from every controller in the workflow. The DSP addresses data subject rights by applying the union of all controllers to every record. So if a data subject opts out with any data controller, that opt-out applies to the entire dataset. If the workflow suppresses a record for opt-out processing, it extracts the data subject from each record and contacts the opt-out service 14, requesting the status of all data controllers from the joint campaign request 18. Record identifiers are included both as inputs and outputs. It is therefore possible that destination identifiers, known only in the step of mapping identifiers to destinations 28, may be subject to an opt-out directive. If an opt-out request exists for any controller, the DSP's workflow excludes the record.

[0030] The remaining records are then created for transmission to the destination programmatic messaging platform 32 in a data delivery step 30. This includes a conversion to another pseudonymous identifier. The pseudonymous identifier stored in the data subject record + metadata record 24 is kept internal to the DSP. The ethical handling of the data subject's data ensures the two-way privacy mentioned above, i.e. the data controller cannot associate the data subject's record with a specific online activity and the online programmatic messaging platform cannot associate the online activity with a specific data subject's record. Therefore, the internal pseudonymous identifier is converted and replaced with a new identifier created specifically for the destination programmatic messaging platform 32.

[0031] From the method outlined above, it can be seen that the DSP uses constituent datasets provided by individual data curators and dynamically synthesizes joint datasets as needed. Each curator handles its own dataset without the involvement of other curators. Data subjects are uniquely identified and the semantics of the data in each dataset are specific to each curator. No prior agreement or technical arrangement between the curators is required to initiate a multi-curator workflow. Instead, the curator contacts the DSP, describes the individual datasets to be used, specifies what data to be synthesized, and specifies which targeted messaging platforms should receive the delivery.

[0032] The DSP dynamically synthesizes the joint controller relationships when creating the combined dataset. Regardless of the data controllers associated with each component dataset, i.e., the data controllers of the individual records and subject properties, a set of joint controllers is created to cover the entirety of the processing workflow. The set of joint controllers is used for compliance with all data regulations, including opt-out processing. The set of joint controllers is used for record suppression that typically applies to a single data controller. All controllers are applied to enforce the data subject's intent to exercise their opt-out right for all records. In a typical joint controller arrangement from the prior art, all controllers would agree on the data format and content. Data subject (customer) records would be shared and all controllers would have physical and semantic access to the information. Specifically, data subject identification would be unidirectional and would affect all records in the dataset. The invention includes techniques that allow complete separation between the component datasets without any sharing of data between the joint controllers, as described in the implementations described herein. The invention thus automates compliance with applicable privacy laws and the privacy policies of various data controllers and processors.

[0033] Importantly, without a system for enforcing data subject rights across aggregated datasets, the multi-controller workflow described above would not be permissible under many privacy laws. These laws specifically require data controllers to enforce data subject opt-out requests. By construction, the aggregated dataset would be subject to opt-out directives from all data controllers. Without a mechanism for enforcing subject rights across aggregated datasets, the aggregated dataset would violate privacy laws that exist in many jurisdictions.

[0034] A hardware and software system for implementing the just-described method according to an embodiment of the present invention may be described with reference to FIG. 2. The system may be implemented as a virtual "computing engine" (shown as a hexagon in FIG. 2) in a cloud-based computing environment. Similarly, each storage system (shown as a cylinder in FIG. 2) may be implemented as a virtual component of the cloud-based computing environment. Each such component may be physically implemented as one or more subcomponents and may be considered to be implemented on thousands of processors within a particular cloud-based computing environment or across multiple such environments. Similarly, a firewall switch (shown as a rectangle in FIG. 2) may include one or many public and private network switches and routers.

[0035] The data manager system 50 communicates with the public cloud-based platform 52 through a firewall 54. Although only two data manager systems 50 are shown in FIG. 2, it is understood that the present invention in various implementations can be used with any number of data manager systems 50. This architecture allows for storage of the manager data subject record 10 and the manager opt-out record 12 (also shown in FIG. 1) for use by the DSP in the public cloud-based platform 52. The public cloud-based platform 52 can communicate with the data processor cloud-based platform 56 through a firewall 54. The processor data subject record 11 and the processor opt-out record 13 are stored locally in the data processor cloud-based platform 56 for processing performed by the DSP. Similarly, the created data storage 60 can be used to store the end results of the system, including the data to be distributed in the data distribution step 30 of FIG. 1. Three different calculation engines can be used to perform the processing steps shown in FIG. 1: an ingestion calculation engine 62, a workflow calculation engine 64, and a distribution calculation engine 66. Results from the distribution computing engine 66 are sent through the firewall 54 of the data processor's cloud-based platform 56 to one or more destination platforms 32. This is just one example, but it should be understood that in alternative implementations of the invention, the processing steps may be split across more or fewer logical or physical computing engines, as necessary given the particular cloud or non-cloud computing environment.

[0036] In these implementations, the present invention reduces the computational costs associated with performing the necessary operations in addition to technically enabling joint campaigns while preserving automatic compliance with privacy laws. As described above, a campaign with three data managers can be simulated by running three separate workflows. Each workflow processes only one data set and applies the necessary operations of the data managers. These individual workflows incur overhead such as scheduling, resource allocation, execution, and monitoring. If the computational cost of a single workflow is 1×W, the cost of the three workflows would be approximately 3×W. However, the joint campaign described herein significantly changes this computational cost structure. All three data sets can be processed in parallel in a single workflow. Furthermore, the operations to enforce data regulations can be performed once for the combined set of managers, with effectively no additional cost for the single manager. Again, if the workflow for a single data set costs 1×W, the cost of a joint campaign with three data sets in these implementations of the present invention is approximately 1×(W+3i), where “i” represents the incremental cost. As a practical matter, it will turn out that 1×(W+3i) is much less than 3×W. For example, assume that the cost of the basic workflow is W=100 and the incremental cost of the collaborative campaign is i=5. That is, executing the collaborative workflow increases the amount of computation per dataset in the workflow by 5%. In this case, it will turn out that the cost of the three individual workflows is 3×W=300, while the cost of the collaborative campaign is only 1×(W+3i)=115. Thus, the present invention in these implementations simultaneously improves functionality to enable compliance with applicable privacy laws and reduces total computational costs. These computational cost savings increase as the number of administrators participating in the collaborative campaign increases, resulting in even greater efficiency in campaigns with a larger number of administrators contributing data.

[0037] The present invention may be implemented by any combination of hardware and software in the implementations described herein and in various alternative implementations. For example, in one embodiment, the system and method may be implemented by a computer system or collection of computer systems, each of which includes one or more processors that execute program instructions stored in a computer-readable storage medium coupled to the processors. The program instructions may perform the functions described herein. The various systems and displays shown in the figures and described herein represent example implementations. The order of any method may be changed and various elements may be added, modified, or omitted.

[0038] The computer processing system or computer processing device described herein may be implemented as a hardware portion of a cloud-based computer processing system or a non-cloud-based computer processing system as forming part of various implementations of the present invention. The computer system may be any of a variety of types of devices, including but not limited to a general purpose server, a personal computer system, a desktop computer, a laptop or notebook computer, a mainframe computer system, a handheld computer, a workstation, a network computer, a consumer device, an application server, a storage device, a telephone, a mobile phone, or generally any type of computer processing node, computing node, computing device, and / or computer processing device. The computer processing system includes one or more processors (any of which may include multiple processing cores, which may be single or multi-threaded) coupled to a system memory via an input / output (I / O) interface. The computer system may further include a network interface coupled to the I / O interface.

[0039] In various embodiments, the computer system may be a single processor system including one processor, or a multiprocessor system including multiple processors. The processor may be any suitable processor capable of executing computer processing instructions. The processor may be, for example, a general purpose or embedded processor implementing any of a variety of instruction set architectures in various embodiments. In a multiprocessor system, each of the processors may typically, but not necessarily, implement the same instruction set. The computer system also includes one or more network communication devices (e.g., network interfaces) for communicating with other systems and / or components over a communications network, such as a local area network, a wide area network, or the Internet. For example, a client application running on the computer processing device may use the network interface to communicate with a server application running on a single server or a cluster of servers implementing one or more of the components of the system described herein in a cloud computing environment, or in a non-cloud computing environment, such as implemented in various secondary systems. In another example, an instance of a server application running on a computer system may use a network interface to communicate with other instances of the application, which may be implemented on other computer systems.

[0040] A computing device also includes one or more persistent storage devices and / or one or more I / O devices. In various embodiments, the persistent storage devices may correspond to disk drives, tape drives, solid state memory, other mass storage devices, or any other persistent storage devices. A computing system (or a distributed application or operating system running on a computing system) may store instructions and / or data in a persistent storage device as desired, and may retrieve the stored instructions and / or data as needed. A computing system may, for example, in some embodiments, implement one or more nodes of a control plane or control system, and the persistent storage device may include solid state drives attached to the server nodes. Multiple computing systems may share the same persistent storage device, or may share a pool of persistent storage devices, where the devices in the pool represent the same or different storage technologies.

[0041] A computer system includes one or more system memories that can store code / instructions and data accessible to the processor. System memory can include multiple levels of memory and memory caches in the system, designed to swap information in memory based on access speed, for example. Interleaving and swapping can be extended to persistent storage in virtual memory implementations. Technologies used to implement memory can include, by way of example, static random-access memory (RAM), dynamic RAM, read-only memory (ROM), non-volatile memory, or flash type memory. As with persistent storage, multiple computer systems may share the same system memory, or may share a pool of system memory. The system memory or multiple system memories can store program instructions executable by the processor to perform the routines described herein. In various embodiments, the program instructions can be coded in binary, assembly language, any interpreted language such as Java, compiled languages ​​such as C / C++, or any combination thereof, with the specific languages ​​shown herein being merely exemplary. In some embodiments, the program instructions may implement multiple separate client, server nodes, and / or other components.

[0042] In some implementations, the program instructions may include executable instructions for implementing an operating system (not shown), which may be any of a variety of operating systems, such as UNIX, LINUX, Solaris, MacOS, or Microsoft Windows. Any or all of the program instructions may be provided as a computer program product or software, which may include a non-transitory computer-readable storage medium having stored thereon instructions that may be used to program a computer system (or other electronic device) to perform a process according to various implementations. A non-transitory computer-readable storage medium may include any mechanism for storing information in a machine-readable (e.g., computer) form (e.g., software, processing application). Generally speaking, a non-transitory computer-accessible medium may include a computer-readable storage medium or memory medium, such as a magnetic or optical medium, e.g., a disk or DVD / CD-ROM coupled to a computer system via an I / O interface. A non-transitory computer-readable storage medium may also include any volatile or non-volatile medium, such as RAM or ROM, that may be included in some embodiments of a computer system as system memory or another type of memory. In other implementations, the program instructions may be communicated using optical, acoustic, or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.) transmitted over a communication medium, such as a network and / or wired or wireless link, as may be implemented via a network interface. The network interface may be used to interface with other devices, which may include other computer systems or any type of external electronic device.Generally, system memory, persistent storage, and / or remote storage on other devices accessible over a network may store data blocks, replicas of data blocks, metadata related to the data blocks and / or the state of the data blocks, database configuration information, and / or any other information usable in performing the routines described herein.

[0043] In certain implementations, the I / O interface may coordinate I / O traffic between the processor, system memory, and any peripheral devices in the system, including through a network interface or other peripheral interface. In some embodiments, the I / O interface may perform any necessary protocol conversion, timing conversion, or other data conversion to convert data signals from one component (e.g., system memory) into a form suitable for use by another component (e.g., processor). In some embodiments, the I / O interface may include support for devices attached through various types of peripheral buses, such as, for example, variations on the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard. Also, in some embodiments, some or all of the functionality of the I / O interface, such as the interface to the system memory, may be incorporated directly within the processor.

[0044] The network interface may enable data exchange between the computer system and other devices attached to the network, such as, for example, other computer systems (which may implement server nodes, primary nodes, read-only nodes of one or more storage systems, and / or clients of the database system described herein). In addition, the I / O interface may enable communication between the computer system and various I / O devices and / or remote storage devices. The input / output devices may, in some embodiments, include one or more display terminals, keyboards, keypads, touchpads, scanning devices, voice or light recognition devices, or any other device suitable for inputting or retrieving data from one or more computer systems. The input / output devices may be directly connected to a particular computer system, or may generally be connected to multiple computer systems in a cloud computing environment, grid computing environment, or other system including multiple computer systems. The multiple input / output devices may be in communication with the computer system, or may be distributed among various nodes of a distributed system including the computer system. The user interfaces described herein may be visible to a user using various types of display screens, which may include CRT displays, LCD displays, LED displays, and other display technologies. In some implementations, input may be received via a display using touch screen technology, and in other implementations, input may be received via a keyboard, mouse, touchpad, or other input technology, or any combination of these technologies.

[0045] In some embodiments, similar input / output devices may be separate from the computer system and may interact with one or more nodes of a distributed system including the computer system through a wired or wireless connection, such as via a network interface. The network interface may typically support one or more wireless network protocols (e.g., Wi-Fi / IEEE 802.11, or another wireless network standard). The network interface may support communication over any suitable wired or wireless general-purpose data network, such as, for example, other types of Ethernet networks. Additionally, the network interface may support communication over a telecommunications / telephony network, such as an analog voice network or a digital fiber communications network, communication over a storage area network, such as a Fibre Channel SAN, or communication over any other suitable type of network and / or protocol.

[0046] Any of the embodiments of the distributed system described herein, or any of the components of the embodiments, may be implemented as one or more network-based services in a cloud computing environment. For example, read / write nodes and / or read-only nodes in a database tier of a database system may provide database services and / or other types of data storage services using a distributed storage system, as described herein, as network-based services to clients. In some embodiments, the network-based services may be implemented by software and / or hardware systems designed to support interoperable machine-to-machine interaction over a network. A web service may have an interface described in a machine-processable format, such as Web Services Description Language (WSDL). Other systems may interact with the network-based service in a manner defined by the description of the network-based service's interface. For example, the network-based service may specify various operations that other systems may invoke and may specify a particular application programming interface (API) to which other systems may be expected to conform when requesting the various operations.

[0047] In various embodiments, a network-based service may be requested or invoked by using a message that includes parameters and / or data associated with the network-based service request. Such a message may be formatted according to a particular markup language, such as Extensible Markup Language (XML), and / or may be encapsulated using a protocol, such as Simple Object Access Protocol (SOAP). To perform a network-based service request, a network-based service client may assemble a message that includes the request and communicate the message to an addressable endpoint (e.g., a Uniform Resource Locator (URL)) corresponding to the web service using an Internet-based application layer transport protocol, such as Hypertext Transfer Protocol (HTTP). In some embodiments, a network-based service may be implemented using Representational State Transfer (REST) ​​techniques rather than message-based techniques. For example, a network-based service implemented according to REST techniques may be invoked by parameters included in HTTP methods, such as PUT, GET, or DELETE.

[0048] Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Although any methods and materials similar or equivalent to those described herein can also be used in the practice or testing of the present invention, a limited number of exemplary methods and materials are described herein. It will be apparent to those skilled in the art that many more modifications are possible without departing from the inventive concepts herein.

[0049] All terms used herein should be interpreted as broadly as possible without being inconsistent with the context. When groupings are used herein, it is intended that all individual elements of the group, and all possible combinations and subcombinations of the group, are included individually. When ranges are described herein, it is intended that the ranges include all subranges and individual points within the ranges. All references cited herein are incorporated herein by reference unless inconsistent with the disclosure of this specification.

Claims

1. 1. A system for handling multiple administrator opt-outs, comprising: at least one memory for storing a sequence of instructions; at least one processor configured to execute the sequences of instructions; the sequences of instructions, when executed, cause the at least one processor to: performing a match process on a first set of data subject records from a first custodian to identify data subjects associated with each of the data subject records in the first set of data subject records; performing a match process on a second set of data subject records from a second custodian to identify the data subjects associated with each of the data subject records in the second set of data subject records; augmenting the first set of data subject records with metadata, the metadata including a first administrator identifier uniquely associated with the first administrator, to generate a first set of data subject and metadata records; augmenting the second set of data subject records with metadata, the metadata including a second administrator identifier uniquely associated with the second administrator, to generate a second set of data subject and metadata records; constructing a dataset combining the first set of data subject and metadata records and the second set of data subject and metadata records; and applying an opt-out service to the combined data set using a first set of opt-out records including a first list of data subjects who are opted out and a first type of associated personally identifiable information and a second set of opt-out records including a second list of data subjects who are opted out and a second type of associated personally identifiable information to suppress records in the combined data set that match any of the first set of opt-out records and the second set of opt-out records. A system that executes the above.

2. 2. The system of claim 1 , wherein the sequences of instructions, when executed, further cause the at least one processor to perform pseudonymization on a first set of records for the data subject prior to performing a matching process on the first set of records for the data subject, and to perform pseudonymization on a second set of records for the data subject prior to performing a matching process on the second set of records for the data subject.

3. 2. The system of claim 1, wherein the sequences of instructions, when executed, further cause the at least one processor to replace any personally identifiable information in the first set of data subject records and the second set of data subject records with a pseudonymous identifier.

4. 4. The system of claim 3, wherein the sequences of instructions, when executed, further cause the at least one processor to eliminate minor differences in personally identifiable information between the first set of data subject records and the second set of data subject records such that pseudonymous identifiers for a particular data subject in the first set of data subject records and the second set of data subject records match.

5. The system of claim 4 , wherein the first type of personally identifiable information and the second type of personally identifiable information are distinct.

6. 6. The system of claim 5, wherein the sequences of instructions, when executed, further cause the at least one processor to perform a merge operation on the first set of opt-out records to expand the first set of opt-out records with a pseudonym identifier, and to perform a merge operation on the second set of opt-out records to expand the second set of opt-out records with a pseudonym identifier.

7. 7. The system of claim 6, wherein the instruction sequences, when executed, further cause the at least one processor to convert a pseudonym identifier in the first set of data subject and metadata records to a first destination identifier and replace the first destination identifier with a pseudonym identifier, and convert a pseudonym identifier in the second set of data subject and metadata records to a second destination identifier and replace the second destination identifier with a pseudonym identifier.

8. 1. A computerized method for handling multi-administrator opt-outs, comprising: performing a match process on the plurality of sets of data subject records to identify a data subject associated with each data subject record in the plurality of sets of data subject records; augmenting each of the data subject records in the plurality of sets of data subject records with metadata including an administrator identifier uniquely associated with an administrator among a plurality of administrators to generate a plurality of sets of data subject and metadata records; constructing a combined data set by combining data subject and metadata records from said multiple sets of data subject and metadata records; applying an opt-out service to the combined data set using a plurality of sets of opt-out records, each set including a list of data subjects who are opted out and associated personally identifiable opt-out information, to suppress records in the combined data set that match any of the records in the plurality of sets of opt-out records; A method comprising:

9. 9. The method of claim 8, further comprising pseudonymizing records of the data subjects within the plurality of sets of records of the data subjects prior to performing a merging process on the records of the data subjects within the plurality of sets of records of the data subjects.

10. 10. The method of claim 9, wherein each of the data subject records in the plurality of sets of data subject records includes data subject personally identifiable information, the method further comprising replacing the data subject personally identifiable information in each of the data subject records in the plurality of sets of data subject records with a pseudonymous identifier.

11. 11. The method of claim 10, wherein the step of replacing the data subject personally identifiable information for each of the data subject's records in a plurality of sets of records for the data subject with a pseudonymous identifier comprises generating the pseudonymous identifier from the data subject's record in the plurality of sets of records for the data subject using a hashing technique.

12. 11. The method of claim 10, further comprising performing a matching process to standardize the data subject personally identifiable information across the multiple sets of records for the data subject, such that a pseudonymous identifier for each particular data subject record that is matched across the multiple sets of records for the data subject is identical.

13. 13. The method of claim 12, further comprising: performing a merge process on the multiple sets of opt-out records to augment each of the opt-out records in the multiple sets of opt-out records with supplemental data subject personally identifiable information.

14. 14. The method of claim 13, further comprising: converting pseudonymous identifiers in the multiple sets of records of the data subject to destination identifiers; and forwarding the multiple sets of records of the data subject to at least one programmatic messaging platform.

15. 1. A computerized, multi-administrator opt-out processing system, comprising: At least one processor; A non-transitory computer readable storage medium; a pseudonymization routine stored on the non-transitory computer readable storage medium and implemented as code executable on the at least one processor, the pseudonymization routine being configured to augment a plurality of sets of data records, each of the sets of data records originating from a different administrator, with metadata including an identifier keyed to one of the administrators from which the plurality of sets of data records originated; a matching routine stored on the non-transitory computer readable storage medium and implemented as code executable on the at least one processor, the matching routine configured to resolve identity information of a data subject for each of a plurality of records within a plurality of sets of data of the records; a combined dataset construction routine stored on the non-transitory computer readable storage medium and implemented as code executable on the at least one processor, the combined dataset construction routine configured to construct a combined dataset by combining a plurality of sets of records of data without removing any metadata of the datasets within the plurality of sets of records of data; an opt-out service routine stored on the non-transitory computer-readable storage medium and implemented as code executable on the at least one processor, the opt-out service routine configured to read a plurality of opt-out records, each corresponding to a record of data in the combined data set, and to suppress each corresponding record of data in the combined data set; A system comprising:

16. 16. The system of claim 15, wherein the pseudonymization routine is further configured to convert personally identifiable information of each record in the plurality of sets of records of the data into an internal pseudonymous identifier.

17. 17. The system of claim 16, wherein the matching processing routine is further configured to resolve a data subject from an opt-out record in a plurality of sets of opt-out records and augment each of the opt-out records in the plurality of sets of opt-out records with supplemental data regarding a corresponding data subject.

18. 20. The system of claim 17, further comprising an identifier-to-destination mapping routine stored on the non-transitory computer-readable storage medium and implemented as code executable on the at least one processor, the identifier-to-destination mapping routine configured to convert the hidden identifiers to destination identifiers within the combined data set.

19. 20. The system of claim 18, wherein the pseudonymization routine is further configured to convert personally identifiable information of each record in the plurality of sets of records of the data into the internal pseudonymous identifier by applying a hashing routine.

Citation Information

Patent Citations

  • Determination method, determination device and determination program

    JP2017010521A

  • Anonymized Global Opt-Out

    US20210019445A1