Abstract: The present disclosure involves systems, software, and computer implemented methods for data privacy. One example method includes performing a processing action for a data subject for a purpose using a set of data categories that are associated with the purpose. The purpose has a retention period and is a parent purpose in a purpose hierarchy with at least one dependent purpose as a child purpose of the purpose. Dependent purpose retention periods and dependent purpose data categories are determined for each dependent purposes as respective subsets of the set of data categories. In response to an end of purpose for the purpose, data of the set of data categories is blocked. Data in the set of data categories that are not dependent purpose data categories is retained according to the retention period and data of each dependent purpose data category is retained according to a corresponding dependent retention period.

Abstract: The present disclosure involves systems, software, and computer implemented methods for data privacy protocols. One example method includes receiving information defining a purpose for processing personal data of a data category stored in an object. A first mapping is received of a processing action to the purpose. Input data to be obtained for the processing action is identified. A determination is made as to whether the input data is of the data category that has been mapped to the purpose. The processing action is executed using the input data as purpose-based processing of the input data, in response to determining that the input data can be used during execution of the processing action for the purpose. Processing of the input data by the processing action is prevented, in response to determining that the input data cannot be used during execution of the processing action for the purpose.

Abstract: The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes receiving, from a requesting application in a landscape that includes a set of multiple applications, a data subject information request for a data subject. A set of target applications is determined from the set of multiple applications. The data subject information request is provided to each target application in the set of target applications. A data subject information response is received from each of the target applications. Each data subject information response includes application data for the data subject that was retrieved by a respective target application in response to the data subject information request. The received data subject information responses are aggregated to generate an aggregated data subject information response.

Abstract: The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes sending a block command for an object to each application in a multiple-application landscape that includes a master data distribution application. A blocking status is received from each application that indicates whether the application successfully blocked the object in response to the block command. An overall blocking status is determined based on the received blocking statuses. In response to determining that at least one application failed to block the object, an unblock command is sent to each application. An unblocking status is received from each application and an overall unblocking status is determined. In response to determining that at least one application failed to unblock the object, a redistribution request is sent to the master data distribution application to redistribute the object to applications that failed to unblock the object.

Abstract: The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes determining to initiate an integrated end of purpose protocol for an object. An end-of-purpose query is provided to multiple applications that requests each application to determine whether the application is able to block the object. End-of-purpose statuses are received, in response to the end-of-purpose query, that each indicate whether a respective application is able to block the object. The end-of-purpose statuses are evaluated to determine whether an aligned end of purpose has been reached for the object. In response to determining that the aligned end of purpose has been reached for the object, a block command is provided to each application that instructs the application to locally block the object in the application.

Abstract: Systems and processes for managing access to personal data based on a purpose for storing the personal data are provided. In a method for managing personal data access, personal data for a data subject corresponding to a first data category is received, and an operation is executed in a purpose agent to associate one or more purposes to the personal data, where the one or more purposes are assigned to the first data category and include at least a first purpose. The personal data may be stored in a data storage system, and the stored personal data may be designated as being associated with the one or more purposes. Access to the personal data may be controlled based on the one or more purposes.

Abstract: The present disclosure involves systems, software, and computer implemented methods for aligned purpose disassociation in a multi-system landscape. One example method includes receiving, from multiple systems, a can-disassociate status for a purpose for an object instance. The status from a respective system can be an affirmative status that indicates that the system can disassociate the purpose from the instance or a negative status that indicates that the system cannot disassociate the purpose from the instance. The received statuses are evaluated to determine a central disassociate purpose decision for the purpose for the instance. The central disassociate purpose decision can be to disassociate the purpose from the instance when no system has the negative status and to not disassociate the purpose from the instance when at least one system has the negative status. The central disassociate purpose decision is provided to at least some of the multiple systems.

Abstract: Computer-readable media, methods, and systems are disclosed for providing purpose-based processing of data. A purpose agent assigns one or more purposes to a set of data such that access to the set of data may be restricted to a select few specifically authorized entities based on an assigned purpose. A retention period for storing the data is determined based on the assigned purpose. When the retention period expires the data is deleted from a data store.

Abstract: The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes sending a block command for an object to each application in a multiple-application landscape that includes a master data distribution application. A blocking status is received from each application that indicates whether the application successfully blocked the object in response to the block command. An overall blocking status is determined based on the received blocking statuses. In response to determining that at least one application failed to block the object, an unblock command is sent to each application. An unblocking status is received from each application and an overall unblocking status is determined. In response to determining that at least one application failed to unblock the object, a redistribution request is sent to the master data distribution application to redistribute the object to applications that failed to unblock the object.

Abstract: The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes determining to initiate an integrated end of purpose protocol for an object. An end-of-purpose query is provided to multiple applications that requests each application to determine whether the application is able to block the object. End-of-purpose statuses are received, in response to the end-of-purpose query, that each indicate whether a respective application is able to block the object. The end-of-purpose statuses are evaluated to determine whether an aligned end of purpose has been reached for the object. In response to determining that the aligned end of purpose has been reached for the object, a block command is provided to each application that instructs the application to locally block the object in the application.

Abstract: The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes receiving, from a requesting application in a landscape that includes a set of multiple applications, a data subject information request for a data subject. A set of target applications is determined from the set of multiple applications. The data subject information request is provided to each target application in the set of target applications. A data subject information response is received from each of the target applications. Each data subject information response includes application data for the data subject that was retrieved by a respective target application in response to the data subject information request. The received data subject information responses are aggregated to generate an aggregated data subject information response.

Abstract: The present disclosure involves systems, software, and computer implemented methods for aligned purpose disassociation in a multi-system landscape. One example method includes receiving, from multiple systems, a can-disassociate status for a purpose for an object instance. The status from a respective system can be an affirmative status that indicates that the system can disassociate the purpose from the instance or a negative status that indicates that the system cannot disassociate the purpose from the instance. The received statuses are evaluated to determine a central disassociate purpose decision for the purpose for the instance. The central disassociate purpose decision can be to disassociate the purpose from the instance when no system has the negative status and to not disassociate the purpose from the instance when at least one system has the negative status. The central disassociate purpose decision is provided to at least some of the multiple systems.

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 data information framework collects related data sharing characteristics (e.g., personal information, others) revealed by associated purpose information, and reports on that data. The location of the data is not restricted, and can be collected from various locations (e.g. different databases on different computer systems). An engine implements data creation defining links between different stored data structures (e.g., tables) using specific fields. A plurality of tables may be grouped into a smaller number of table clusters to facilitate constructing the data model. The model may be evaluated, enhanced, and/or corrected (e.g., by a user). The model may include fields reflecting the purpose information for the stored data, said fields accessible by the engine during data handling processes. The data model may include descriptions providing data storage location. Purpose information may be mapped to table fields.

Abstract: Various embodiments of systems and methods to determine data retention rules for data entities are described herein. In one aspect, the data entities are obtained. Usage statuses of the data entities are determined. One or more purpose of data corresponding to the one or more data entities is received. Further, legal entities corresponding to the one or more data entities are identified based on line organization attributes and the usage statuses. Process object attributes associated with the one or more data entities are identified based on the legal entities. Retention rules for the one or more data entities are determined based on the one or more purpose of data, the legal entities and the process object attributes.

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: Embodiments described herein relate to an improved technique for blocking access to data records associated with an entity in a network comprising a plurality of systems. The operations include accessing and analyzing determination criteria associated with the entity to determine in which systems the data should be blocked. An end-of-purpose determination can be performed in one or more of the systems based on whether the current system is a master system, a dependent system of the master system, or a standalone system of the plurality of systems. Access to the entity data records can then be blocked from the appropriate systems when an end of purpose for the data has been reached for any processes running on the system.

Abstract: A data information framework collects related data sharing characteristics (e.g., personal information, others) revealed by associated purpose information, and reports on that data. The location of the data is not restricted, and can be collected from various locations (e.g. different databases on different computer systems). An engine implements data creation defining links between different stored data structures (e.g., tables) using specific fields. A plurality of tables may be grouped into a smaller number of table clusters to facilitate constructing the data model. The model may be evaluated, enhanced, and/or corrected (e.g., by a user). The model may include fields reflecting the purpose information for the stored data, said fields accessible by the engine during data handling processes. The data model may include descriptions providing data storage location. Purpose information may be mapped to table fields.

Abstract: Embodiments described herein relate to an improved technique for blocking access to data records associated with an entity in a network comprising a plurality of systems. The operations include accessing and analyzing determination criteria associated with the entity to determine in which systems the data should be blocked. An end-of-purpose determination can be performed in one or more of the systems based on whether the current system is a master system, a dependent system of the master system, or a standalone system of the plurality of systems. Access to the entity data records can then be blocked from the appropriate systems when an end of purpose for the data has been reached for any processes running on the system.

Abstract: Various embodiments of systems and methods to determine data retention rules for data entities are described herein. In one aspect, the data entities are obtained. Usage statuses of the data entities are determined. One or more purpose of data corresponding to the one or more data entities is received. Further, legal entities corresponding to the one or more data entities are identified based on line organization attributes and the usage statuses. Process object attributes associated with the one or more data entities are identified based on the legal entities. Retention rules for the one or more data entities are determined based on the one or more purpose of data, the legal entities and the process object attributes.