Hi,
I'm curious to hear what other organizations are doing when an individual wants to be removed from the database.
We received a request from a patron who does not want to be contacted by us or to keep any information about him in our system. We started by offering to unsubscribe him from our all of our contact lists, but that did not satisfy him. I am also hesitant to simply inactivate his account as it would still appear in a search. I have a feeling he would call back and have a representative search the database to test us.
I would especially love to hear from people dealing with GDPR.
Thanks,
Richard
Hi Richard,
New in Version 14.1 is a Purge Constituents functionality which addresses GDPR concerns directly. We haven't used it yet ourselves, but it seems to remove all personal data with the exception of the primary postal code, and you get to keep the sales data. Here's the info: https://www.tessituranetwork.com/Help_System_v141/Content/GDPR/Schedule%20Purge.htm
Lauren
We're still on v12.5.1 - our process is to update the constituent record to remove all data such as Credit Cards, e-addresses, etc. We have a generic constituent record called "Anonymous Constituent" into which the constituent is then merged.
Martin
Thanks Lauren and Martin for the suggestions. I'll look into both and discuss with our team.