Deleting users in Splio CDP

Overview

Splio allows you to delete all data for specific users which is a must at least for GDPR compliance.

The main use cases for this are:

• Deleting specific users, for example when you receive a request for the right to be forgotten.
• Deleting a selection of users, for example, inactive users that you need to delete as part of your data retention policy.

Deletions are processed weekly by Splio on the basis of delivered files containing lists of user identifiers to delete.

Key things to know about the deletion process:

• Deletion will happen both in Splio CDP and any linked Splio database (Marketing Automation, Loyalty, Mobile Wallets)
• If you operate Splio CDP with Identity Resolution, deletions are processed with propagation at the master and deduplicated profile (meaning all source profiles related to a master profile to delete will end up being deleted).
• Besides deleting users in Splio, you should make sure to delete them also in your source information systems, so that they will never be exported again to Splio (Splio will not block their data from being ingested again). In order to help you achieve that, as a result of deletion being processed, Splio can deliver deletion report files that can eventually in turn be processed by source information systems.

📘

This feature is activated and configured on demand. If you are willing to do so, get in touch with your contact at Splio.

Delivering user deletion files

Deletion files are to be delivered on the same SFTP account you are using for any other file asset. If you do not have one, you should ask your contact at Splio.

Specification for the deletion files:

• Needs to be named users_to_delete_{source}_YYYYMMDDHHMMSS.csv (the {source} token is necessary to let Splio know the origin of the files in case of a multi-source setup).
• Contains a single user_id column consisting of the users' identifier to delete
  • In the context of a multi-source setup with identity resolution, the users' identifiers can either be unique and deduplicated, or source ones. This is to be decided at setup time.
  • In the context of a mono-source setup without identity resolution, the users' identifiers are naturally the source system ones.

Deletion data scope

All data related to the listed users will be deleted from Splio CDP Database: user profile, purchase history, campaigns and reactions history, etc.

An exception to that, Splio will keep a deletion audit trace of every user identifier processed, allowing Splio if necessary to justify when a given user identifier has been deleted.

However at that moment, deletion will remain partial in linked Splio databases (Marketing Automation, Loyalty, Mobile Wallets), see other platforms documentations for further details.

Deletion report files

Optionally, as a result of processing deletion requests, Splio can issue deletion report files.

Deletion report files will be delivered on the same SFTP account where you are delivering daily update files.

Specification for the deletion report files:

• Named users_deletion_report_{source}_YYYYMMDDHHMMSS.csv
• Contains a single user_id column consisting of the deleted users' identifiers