Reltio Connect

Hello everyone, 
Our CCPA process is to de-identify these records at the source systems level by changing the names and addresses and those updates names are sent to Reltio as an update. The problem with this approach is that we can still see the real names in the history activity log. We are considering deleting these individual crosswalk IDs which will take care of this situation. 
I was wondering if the community members have suggestions for handling CCPA records. Is there any other way to take care of this apart from deleting? Can we just delete the history without deleting a crosswalk? 

Regards
Haresh

Hi Haresh,

I would have 2 questions on this:

1. What is the intended processing purpose of storing deidentified data in Reltio? Is it being fed to downstream systems? For example, are they being added to suppression lists for "do not sell" or are being opted out of all email/push/SMS communications?
2. Is the activity history log being exported or sent downstream? If not, what is the specific concern raised by your data privacy team?

Regards,
Walt

Hi @Walt Feldman,
Those are great questions. Here are the answers I received.
1. Purpose of de-id was more for downstream reporting and historical  analytics i.e. how many requests we are getting etc. They are not used for any specific purpose. 
2.  The activity history log is not being used downstream but the concern is that the data would still exist in history/activity log. 


Haresh​

If the consumer data is used “internally, in a lawful manner that is compatible with the context in which the consumer provided the information”, this consumer data is except from CCPA erasures. Provided you are not sending this data downstream into your MarTech estate or doing any sharing/selling of this data with any 3rd, parties, you are just using the data "internally".

Thanks Walt, I agree. I don't think we have to worry about the history in Reltio.