Delete Entities by GDPR
Learn about General Data Protection Regulation (GDPR) compliance, including deleting consumer profiles and configuration.
GDPR Compliance Requirements in Reltio Platform
- All profile entity or entities.
- All historical data.
- All losing entity or entities. For more information, see Merging Two Entities.
- All records from the Activity Log except records about creating and deleting. The Activity Log must contain these two entries, and all other entries must be deleted:
- Date when the profile was created.
- Date when the profile was deleted.
Right to be Forgotten
With the Reltio Platform, you can flag entities, also known as Consumer Profiles, for deletion upon request from the consumer. This is a three-step process:
- Collect the consumer’s request in a rights management application and publish it to the Reltio Platform.
- The corresponding entities in Reltio are updated with the DeleteEntity flag.
- The Delete Entity job is executed through the Entity Delete API -
To Delete Entities by GDPR:
- Contact your Reltio Support or the Customer Service Manager to have GDPR support enabled.
- Add an attribute with the name DeleteEntity. The attribute must be at the top level of attributes and be of type Boolean.
- Add the true value to the DeleteEntity attribute in entities which are marked for deletion. Note:
- If there are multiple values in the attribute, a defined OV strategy is used.
- If the OV strategy resolves both values (true and false) as winners, the entity is not deleted.
- Schedule the Delete Entities by GDPR task for execution. Note: Stop and Pause are not supported.
Schedules a Delete Entities by GDPR task for a single tenant. Tenant admin role is required.
|tenantId||Yes||ID of the tenant to delete entities.|
If false, all data connected to deleting entities from Activity Log (except the records about entity creation and deleting) will not be deleted.
Default value is true.
If true, all historic data of the entities marked for GDPR deletion is processed. For each historic entity its history (and activity log if the purgeActivityLog parameter is set to true) is purged of all crosswalks and associated data of the entity marked for GDPR deletion.
Note: If you turn on this parameter (set it to true), it can slow down the GDPR delete task since it must enumerate and possibly modify the entire history and activity log of every historic entity of the entity marked for GDPR deletion.
Default value is false.