|
iaeon
|
April 11, 2018 at 12:18 pm
What is the best way of purging old attendee and events data from the EE3 database?
For attendees the criteria would be something like ‘last registration > 1080 days’
I ask as GDPR compliance requires that data is not held unnecessarily.
|
|
Josh
|
April 12, 2018 at 9:24 am
Hi there,
While EE3 does not have the feature you describe, you can go into the attendee list for any older event, then check the checkbox at the top of the table. This will select all attendees, then you click the Delete button. This will delete all attendees for the event from the database.
|
|
iaeon
|
April 14, 2018 at 3:04 pm
Thanks Josh.
For 100% clarity on attendees in EE3: Is it correct that attendee entries are unique on each event?
In other words if I delete John Smith from an old event and he has also booked for one or more newer events he will only be deleted from the old event I have selected and NOT from any subsequent events?
|
|
Ian Just
|
April 14, 2018 at 3:08 pm
I never thought I would be jealous of people with EE3 rather than EE4, but this just makes it worse that you can’t (currently) do this in EE4…
|
|
iaeon
|
April 14, 2018 at 3:29 pm
BTW the reason this is an issue is to do with EU GDPR compliance. Getting rid of old data on people one should not hold on to…
|
|
Tony
|
April 16, 2018 at 3:53 am
Hi there,
For attendees the criteria would be something like ‘last registration > 1080 days’
Can I ask where you are getting that value from?
As far as I am aware, the GDPR states that data should be:
‘kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed’
So I’m just curious as to where you are getting 1080 days from?
I ask as GDPR compliance requires that data is not held unnecessarily.
Whilst I understand that GDPR does state exactly that, so does the Data Protection Act 1995:
‘Personal data processed for any purpose or purposes shall not be kept for longer than is necessary for that purpose or those purposes.’
As you are in the UK this isn’t something new, GDPR is effectively an update to the DPA act (not really, but it can be considered as such).
The main issue with GDPR is you likely don’t have explicit consent for all of those past registrations to be added to your mailing lists or any other marketing you may be using.
For 100% clarity on attendees in EE3: Is it correct that attendee entries are unique on each event?
In other words if I delete John Smith from an old event and he has also booked for one or more newer events he will only be deleted from the old event I have selected and NOT from any subsequent events?
That’s correct, each attendee is a unique entry within the database in EE3.
I never thought I would be jealous of people with EE3 rather than EE4, but this just makes it worse that you can’t (currently) do this in EE4…
You can remove previous registrations within EE4, it’s just not as easy/quick as it was with EE3.
For EE4 you need to remove any payments liked to the transaction for the registrations you want to delete first. From Event Espresso -> Registrations click the TXN date for the specific registration, remove the payments by clicking the trash icon next to the payments and then remove the registration.
We have some open tickets to make this easier within EE4.
|
