If your organization has requirements to anonymize guest data from events, Admins can use the Guest Data Privacy function to permanently de-identify guest data while retaining event metrics.

This function will anonymize everything tied to a guest, which includes PII (personal identifiable information) like name, email and all custom fields. The remaining details will be guest status, guest RSVP totals for an RSVP event, order ID, and order totals for a ticketed event.

The anonymization happens at the Event level, but additional anonymization is at the Contact level. The Contact level anonymization happens when a Contact is not in any non-anonymized Event.

	This feature is available to Basic, Pro, and Enterprise plans
	Roles available: Admin, Admin (Basic)
	This feature is in Limited Availability

For Basic and Professional plans:

To anonymize guest data: 

1. Click Settings.
   This is where you will see a list of events that are eligible for anonymization. By default, this is any event that has not been modified or RSVP’d to within the last 90 days.
   
   
   
2. Click the Anonymize Guest Data. This action is not reversible.

For Enterprise plans:

To anonymize guest data: 

1. Click Settings.
This is where you will see a list of events eligible for anonymization. By default, this is any event that has not been modified or RSVP’d to within the last 90 days.

2. Configure any additional settings.
Choose different event inactivity periods — including 30, 60, 90 and 120 days, and determine if you would like to exclude specific events from the anonymization list.

3. Click the Anonymize Guest Data. This action is not reversible.

Data Anonymization FAQs

This article answers the most commonly asked questions about Splash's Data Anonymization function.

How does the anonymization happen?

The following is a scenario to explain how data is anonymized in Splash. 

1. Guest "Bob" RSVPs to Event "A".
2. Days later "Bob" RSVPs to Event "B".
3. Event "A" is eligible to be anonymized and the Splash customer confirms to anonymize it (only Event "A"). Then:
   • "Bob" guest data in Event "A" will be anonymized. Basically "Bob" guest data in Event "A" is removed.
   • "Bob" contact level information WILL NOT be anonymized as "Bob" is still a guest on Event "B”.
4. Event "B" is now eligible to be anonymized and the Splash customer confirms to anonymize it. Then:
   • "Bob" guest data in Event "B" will be anonymized. 
   • "Bob" contact level information WILL be anonymized as "Bob" is not a guest on any non-anonymized Event.

What happens to anonymized events? Are there any restrictions to be aware of?

Event Page

• • Guests will not be able to view or register on the event post-anonymization, as the event page will auto-unpublish post-anonymization.

Event-Level Guest List

• • Hosts will be blocked from adding new guests to the guest list post-anonymization.
  • Hosts will be blocked from editing guest data on the guest list post-anonymization.
  • Hosts will not be able to import Guest lists from anonymized events.

Email Sender

• • Hosts will be blocked from sending new emails or editing existing emails on the email sender post-anonymization.
  • Hosts will be blocked from adding recipients or adding quick lists on emails post-anonymization.

Event-Level Integrations

• • Hosts will be prevented from adding new integrations post-anonymization.
  • Existing integrations will be disabled post-anonymization, meaning hosts will not be able to edit them on an anonymized event.

What if I accidentally anonymize an event? Can I get that data back?

• Anonymizing data is irreversible and the original data cannot be recovered by Splash. 

What do anonymized contacts look like in the Contacts Manager?

• Anonymized contacts will not appear in the Contacts Manager. Their record is only available in the Splash guest list but is anonymized.

How can I anonymize a single contact?

• Splash supports the action of anonymizing contact data using incoming webhooks. You can read more about setting this up in this article.