Differences

This shows you the differences between two versions of the page.

--- vendors:cisco:uc:ece:gdprutility [2021/01/08 15:39] – [Sample Extracts of ECE Tables - highlighting how ECE anonymizes (Masks) the data] gerardorourke
+++ vendors:cisco:uc:ece:gdprutility [2021/01/08 17:30] (current) – [Sample Extracts of ECE Tables - highlighting how ECE anonymizes (Masks) the data] gerardorourke
@@ Line 150: / Line 150: @@
 ==== Sample Extracts of ECE Tables - highlighting how ECE anonymizes (Masks) the data ====
-In summary, the Email and Chat Content is effectively deleted by the GDPR anonymize tool. No rows are deleted from teh database, but the delete flag where relevant is marked as deleted. but content such as the actually email or chat content is overwritten and / or masked.
+In summary, the Email and Chat Content is effectively deleted by the GDPR anonymize tool. No rows are deleted from the database, but the delete flag where relevant is marked as deleted and content such as the actual email or chat content is overwritten and / or masked and personally identifiable information is masked / overwritten (such as email, name etc.)
 The EGLV_SESSION_CONTENT which stores the chat session content does have its database overwritten. Not very obvious when you review it (as it is encoded in HTML Character set) - but I have confirmed this it is the case.
@@ Line 159: / Line 159: @@
 The below shows an extract of the Case Management Content Person Table - where you can see that the contact has been masked / anonymized
+Email attachment Content is also overwritten - in the below I confirmed that the content changed for the **ExampleTxtFile.txt**
+{{:vendors:cisco:uc:ece:emailattachment.png?400|}}
 {{:vendors:cisco:uc:ece:ece-contact_person.png?400|}}
+==== Note =====
+If you delete a customer and then that customer sends new emails / chat in - the user will get recreated a new customer contact.
+However if you then try to delete the same customer again - you will get an error as the masking for the email address will be a duplicate with previous account deleted. (I should get the exact error and  table here...)
+To get around this issue, just update the mask value from "xxxx" to another value such as "xxxxa"