GDPR regulations mandate any data processor - that handles user data - must provide two core functions:
1. The data that they have about a user - what do you know about me?
2. Deletion of user data - what I don’t want you to keep.
However, both these mandates are not easy for a data processor to comply with because they require the processor to have robust data management practices from day one of their operations. Making a company GDPR-compliant retrospectively is very hard since architects typically focus on designing for scalability, maintainability and data security in the early stages of a company.
We invite talks from practitioners who have gone through the journey of data engineering and how they have managed to balance the difficult goals of privacy, utility and scale within their organizations.
Who should participate:
1. Data engineering architects
2. Data Privacy Officers
3. Data engineers
4. Product managers
Data Deletion: Explaining the legal requirements: timelines and exceptions and case laws.
Whether your products and services are B2B or a B2C, you need to be aware of legal requirements that your technological solutions are required and expected to fulfil so that you can design those products and services in accordance with those requirements from the beginning.
Right of Deletion is not absolute. To be able to comply with the requirements for deletion of data, one needs to be aware of the situations in which deletions are necessary under CCPA and GDPR, the timelines within which deletions must take place, and exceptions that permit you to refuse to delete data in certain situations. While dealing with exceptions, it is important to carefully consider what is and what is not permitted, and how to act when taking the benefit of an exemption. One of the exceptions that permits retention of data under GDPR is if you have a legitimate interest that overrides the rights and freedoms of the person whose data is concerned. In one case in Hungary, a person had made a request for deletion of telephone numbers. The company refused to delete that data stating that they have a right to retain it until the debt due from the person to the company is paid off. The Hungarian DPA ruled against the company and held that for legal procedures, it would be sufficient for the company to retain that person’s address, so the company’s justification for retention of telephone numbers is not sufficient, and those numbers must be deleted.
In addition to the above, you need to be aware of all agreements with all service providers and must ensure that measures have been taken to ensure that compliance can take place in the entire chain. For example, if you delete the data within the permitted time limit, but your service provider maintains copies of the data beyond the permitted time limit, then you would be in violation of your legal obligations.
Within an organization, there are multiple roles that must be made aware of these requirements. These include the developers, marketing department, customer service, acquisitions, and legal, as each of them is responsible for separate parts of the overall compliance requirements. The weakest link in compliance is the customer service department as seen from experience.
In this talk, we will discuss the above with regards to the deletion of data under CCPA and GDPR, as well as the outcomes of a few cases that have been decided in EU. Best practices to be implemented.
The right is not limited to users but extends to ex-employees also. Verification of the deletion request is another important aspect.
In India too courts have recognized Right to deletion. Therefore, in coming times this request could from multiple jurisdictons across the globe.