Process for deleting technical data in relation to GDPR
Project duration: 3 months
Brief description
The customer works with a CRM system. Part of this system includes data exchange with other customer systems developed by third parties. Due to this transfer, technical data containing sensitive customer information is stored in the system. With regards to GDPR, not only must sales data for potential Customers be deleted after a certain period of time, but also the technical data used to create that sales data.
Supplement
The services installed in the cloud use so-called technical data to create sales-relevant entities – leads, opportunities and offers. If the sales-related entities are deleted, these technical data in JSON, XML and CSV formats must also be deleted as they also contain customer data. The connection between the entities storing the customer data and the technical data in the system was established and the cleansing process was developed as a WebJob in Azure. This WebJob monitors whether the deadline has been met and, if so, deletes the prospect data and then deletes any technical data that was associated with the prospect data. In addition, the cleansing process is also used to delete other technical data that does not necessarily contain customer information but is no longer needed because it was associated with the entities that are being deleted due to GDPR.
Subject description
Various information about potential customers is available in the CRM system. This information comes via the technical interfaces. As part of this communication, technical files containing customer information are also stored. After the GDPR deadline has expired, all sales-relevant positions that did not lead to the conclusion of a contract with the customer must be deleted and the associated technical data must also be deleted.