Abstract: A consent management system (CMS) manages a number of individual consent data records of data subjects. The CMS stores predefined consent templates to be instantiated when an individual consent data record is created. The CMS represents a centralized system for management of individual consent data records that are created, stored, and maintained in relation to provided consent by data subjects for purposes of operations related to stored personal data records by associated application systems. The CMS may run on an on-premise, cloud, or personal device computing platform.

Abstract: A consent management system (CMS) manages a number of individual consent data records of data subjects. The CMS stores predefined consent templates to be instantiated when an individual consent data record is created. The CMS represents a centralized system for management of individual consent data records that are created, stored, and maintained in relation to provided consent by data subjects for purposes of operations related to stored personal data records by associated application systems. The CMS may run on an on-premise, cloud, or personal device computing platform.

Abstract: A system and method for managing application(s)' access to personal data of an enterprise business partner is presented. The method includes selecting business partners having personal data records stored in a database connected to an enterprise computing system, for each particular business partner identifying each application that accesses the business partner's personal data records, inquiring from each identified application if it has reached an end-of-purpose period for the personal data records. If an end-of-purpose period has been reached receiving a start-of-retention-time from the application, storing the start-of-retention-time indication in a data record associated with the particular business partner, and blocking access by the particular application to the personal data records of the particular business partner.

Abstract: A system and method for managing application(s)' access to personal data of an enterprise business partner is presented. The method includes selecting business partners having personal data records stored in a database connected to an enterprise computing system, for each particular business partner identifying each application that accesses the business partner's personal data records, inquiring from each identified application if it has reached an end-of-purpose period for the personal data records. If an end-of-purpose period has been reached receiving a start-of-retention-time from the application, storing the start-of-retention-time indication in a data record associated with the particular business partner, and blocking access by the particular application to the personal data records of the particular business partner.

Abstract: Proliferation of duplicative master data in a master data server is prevented. Data is received from a first client computer system at a master data server that includes a data store for master data used by the first client computer system and a second client computer system. Preliminary tests are run to determine whether the data received from the first client computer system are duplicative of master data in the data store. The received data are in the data store as master data and distributed to the second client computer system if the preliminary tests do not determine that the received data are duplicative of master data in the data store. Additional tests are run after distribution of the received data to the second client computer system to determine whether the data received from the first client computer system are duplicative of master data in the data store.

Abstract: Proliferation of duplicative master data in a master data server is prevented. Data is received from a first client computer system at a master data server that includes a data store for master data used by the first client computer system and a second client computer system. Preliminary tests are run to determine whether the data received from the first client computer system are duplicative of master data in the data store. The received data are in the data store as master data and distributed to the second client computer system if the preliminary tests do not determine that the received data are duplicative of master data in the data store. Additional tests are run after distribution of the received data to the second client computer system to determine whether the data received from the first client computer system are duplicative of master data in the data store.