removing customer from database

Hi everyone,

 

We’ve had a customer request that he be completely removed from the database, and it’s been so long since I’ve had one of those requests that I thought I’d poll the forum and see how you all handle it.  I was thinking of something along the lines of merging it into an anonymous account, possibly even changing the identifying info on the ‘bad’ record to anonymous first.  I don’t like the idea of outright deletion, which could be nearly impossible if there are any transactions on the record.  Any suggestions, comments or best practices to share?...

 

Cheers,

Kathleen

Parents
  • We don't do this, and Tessitura makes it difficult, which it (arguably) should. Setting them to Inactive is enough to keep them from being contacted.

  • When we have been asked to do this, we have used the approach that Kevin described. From reading the customer requests, it was always about a desire for us to no longer have their personal details (name, address, phone, email), and merging with an anon record, then deleting the names and contact details meets that desire. 

    We have a policy of expunging CC details after the transaction, so we are not concerned about the ticket history and sale data living on in the anon record, which may not be the same for other orgs?

    It might be worth investigating a script that expunges CC details for a specific constituent?

    I would be hesitant to only mark them as inactive because of the few ways that inactive constituents can still pop up in various reports or legacy lists. Something else to keep in mind would be to check with the marketing team that they always pull in fresh lists/extractions into their e-marketing tool when sending an EDM.

Reply
  • When we have been asked to do this, we have used the approach that Kevin described. From reading the customer requests, it was always about a desire for us to no longer have their personal details (name, address, phone, email), and merging with an anon record, then deleting the names and contact details meets that desire. 

    We have a policy of expunging CC details after the transaction, so we are not concerned about the ticket history and sale data living on in the anon record, which may not be the same for other orgs?

    It might be worth investigating a script that expunges CC details for a specific constituent?

    I would be hesitant to only mark them as inactive because of the few ways that inactive constituents can still pop up in various reports or legacy lists. Something else to keep in mind would be to check with the marketing team that they always pull in fresh lists/extractions into their e-marketing tool when sending an EDM.

Children
  • I suppose it is worth mentioning that we interpret "removing from database" very different to "removing from mailing list" in which case we would impose contact restrictions and, perhaps, inactivation if the patron was leaving the country, for example.  

    There have been amendments to the Australian Privacy Act requiring stricter compliance so we would need to do more than inactivate the record if the request specified *removal from database*.