Interact - GDPR – General Technical Aspect of The Right of Erasure

As part of the General Data Protection Regulation (GDPR) Interact provides a utility which allows Interact users to generate ‘delete’ statements for the customer’s record that need to be erased from the Interact system. These delete statements are specific to the system tables only. The utility takes customer records to be erased as inputs in the form of csv files and generates the delete statements as the output. Listed below are the Interact system tables where customer information can reside, for which delete statements are generated:

Design Time: UACI_XSessResponse

Run Time:
  • UACI_CHOfferAttrib
  • UACI_CHStaging
  • UACI_RHStaging
  • UACI_EventPatternState
  • UACI_UserEventActivity
  • UACI_Treatment
  • UACI_APIRequestInfo
  • UACI_APIRequestAttr
  • UACI_OffersSegmentsAPILog
  • UACI_OffersSegmentsIDLog
  • UACI_Consent
Production DB:
  • UACI_ScoreOverride
  • UACI_BlackList

If Interact List Process box is used in the flowchart, then the UACI_ScoreOverride and UACI_BlackList tablenames must be replaced with the user-defined tablenames mentioned in the process box and the same table names must be specified in the file.

  1. Interact downtime is recommended while executing SQL scripts that are created by the Interact GDPR utility as these scripts contain delete statements.
  2. The Interact GDPR utility will not delete the Profile data to be erased from the User database. This needs to be done manually and is the sole responsibility of the Interact user.
  3. The Interact GDPR utility will only provide ‘delete’ statements. The Interact user should get the statements reviewed by their respective DBA prior to execution.
  4. The Interact GDPR utility ‘delete’ statements do not contain commit statements. The user must either auto-commit as required or commit manually.
  5. Creating indexes on all the additional history tables is recommended. This will make the delete operation faster.
  6. The Interact GDPR utility only deletes customer records to be erased from the tables mentioned above. The customer records from Interact temporary tables, output flat files, log files and custom output tables generated from Interact must be deleted by the Interact user.
  7. Let us assume in examples cited in this guide that all files and executable related to GDPR are available at the <GDPR_HOME> location.
  8. If the Database loader utility is configured in Interact, then the customer data will not be deleted from staging files by the GDPR utility.
  9. If the data from Interact staging tables is loaded into Campaign tables through the ETL process then the Campaign GDPR utility needs to be used to remove the records, instead of the Interact GDPR utility.
  10. If you have generated certain SQL scripts on the Windows systems using the Interact GDPR utility and then wish to execute them in the Unix environment, ensure that you either remove the new-line characters manually or by using the dos2unix command prior to execution.