System to manage privacy preferences

A system comprising:

• a processing unit;
• and
• a storage device comprising instructions, which when executed by the processing unit, cause the processing unit to perform operations comprising:;
• maintaining, using a first event stream with entries published by a contact master component, a plurality of privacy preference data entries derived from two or more customer relationship management (CRM) systems, wherein the entries in the first event stream have timestamps identifying when a client provided respective privacy preference data to a respective CRM system;
• maintaining, using a second event stream with entries published by a consent engine subscribed to the first event stream, a plurality of solicitation preference data, each solicitation preference data in the plurality of solicitation preference data including a timestamp, and each solicitation preference data determined by the consent engine by applying a set of rules to filter a respective privacy preference data from the plurality of privacy preference data published by the contact master component in the first event stream, wherein the consent engine receives each privacy preference data from the first event stream at least once responsive to the contact master component writing each privacy preference data to the first event stream;
• responsive to receiving privacy preference data from the first event stream, the consent engine applying the set of rules to the received privacy preference data to determine solicitation preference data and publishing the solicitation preference data to the second event stream;
• receiving, from a first CRM system of the two or more CRM systems, a request for a current solicitation preference of a client;
• accessing one or more entries in the second event stream associated with the client;
• determining the current solicitation preference of the client from the entries in the second event stream associated with the client based on determining a most recent timestamp of the entries in the second event stream;
• and
• providing, to the first CRM system, the current solicitation preference associated with the client.

A non-transitory computer-readable medium comprising instructions, which when executed by a processing unit, configure the processing unit to perform operations comprising:

• maintaining, using a first event stream with entries published by a contact master component, a plurality of privacy preference data entries derived from two or more customer relationship management (CRM) systems, wherein the entries in the first event stream have timestamps identifying when a client provided respective privacy preference data to a respective CRM system;
• maintaining, using a second event stream with entries published by a consent engine subscribed to the first event stream, a plurality of solicitation preference data, each solicitation preference data in the plurality of solicitation preference data including a timestamp, and each solicitation preference data determined by the consent engine by applying a set of rules to filter a respective privacy preference data from the plurality of privacy preference data published by the contact master component in the first event stream, wherein the consent engine receives each privacy preference data from the first event stream at least once responsive to the contact master component writing each privacy preference data to the first event stream;
• responsive to receiving privacy preference data from the first event stream, the consent engine applying the set of rules to the received privacy preference data to determine solicitation preference data and publishing the solicitation preference data to the second event stream;
• receiving, from a first CRM system of the two or more CRM systems, a request for a current solicitation preference of a client;
• accessing one or more entries in the second event stream associated with the client;
• determining the current solicitation preference of the client from the entries in the second event stream associated with the client based on determining a most recent timestamp of the entries in the second event stream;
• and
• providing, to the first CRM system, the current solicitation preference associated with the client.