Hello community,
I was wondering if any community peers using GDPR functionality would like to connect and share their experience. We have a situation that we have tried to explain below but it will be great to discuss this over a call.
To be CCPA compliant, we are trying to opt Reltio GDPR functionality but facing roadblocks.
Problem Statement:
We have multiple customer records merged in a single profile, and when we receive a CCPA request, we just mask that specific customer record and not the whole profile. So the situation is that a profile has masked as well as unmasked customer record.
Since the profile history is maintained (which is a problem) we have decided to use Reltio GDPR functionality to delete the masked record. Before deleting the profile and its history, we have to unmerge certain contributor providers whose PII information can be extracted from the profile as they shouldn't be wiped out of Reltio Entity.
Once we unmerge, Customer Entity id of the profile retains the history and post running the GDPR task with default parameters to delete the history. it contains history. So, to be compliant we don't want any history or linkage with any profile which is de-identified.
Our need: When we unmerge a contributor from the profile and run GDPR task with default parameters. Profile gets deleted but unmerged contributor contains history of the deleted profile.
Note:
-> We do not want to delete the whole profile with GDPR as the profile contains information which is not supposed to be deleted with it.
-> We cannot use hard delete functionality as profile history will not be deleted.