Close this search box.
AI-based solution designed to automate personal data discovery and classification
Discover personal data across multiple systems in the cloud or on-premise
Harbor cooperation between DPO, Legal Services, IT and Marketing
Turn data subject request into an automated workflow with a clear insight into data every step of the way
Collaborate with stakeholders and manage DPIA and LIA in real-time with Assessment Automation
Guide your partners trough vendor management process workflow
Identifying the risk from the point of view of Data Subject
Quickly respond, mitigate damage and maintain compliance
Consolidate your data and prioritize your relationship with customers
Privacy portal allows customers to communicate their requests and preferences at any time
Introducing end-to end automation of personal data removal

Latest Blog posts

Learn the terms

General Data Protection Regulation

Here you can find the official content of the Regulation (EU) 2016/679 (General Data Protection Regulation) in the current version. All Articles of the GDPR are linked with suitable recitals.

Latest papers

GDPR Requirements for Compliant Data Erasure

GDPR Requirements for Compliant Data Erasure (2)

Data removal or data erasure is triggered by the expiry of the data retention period. When the data retention period expires, any further processing of the data by the Organization becomes illegal.

Data retention refers to keeping or storing the Organization’s data for different purposes, such as everyday business operations, demonstrating compliance with the supervisory authority, or complying with a particular law.

To minimize the risk of non-compliance, once the data retention period expires, the organization must remove personal data from its systems.

Data removal is executed either by deleting the data or, more often, by anonymizing identifiable data.

In order to schedule data removal in a compliant way, the prerequisite is to keep compliant records of processing activities and to have a 360° view of the Data Subject’s personal data processing.

We have discussed new challenges in keeping a compliant ROPA (Record of processing activities) in real-life situations.

[RELATED TOPIC: Records of data processing activities]

Collected data sets will go through the typical personal data lifecycle journey.

Personal data lifecycle


The journey ends with data destruction in the form of anonymization or deletion.

To go through this entire journey completely compliant, there are specific steps you need to take. This time we will be focusing on requirements for GDPR-compliant personal data erasure, which involves:

  • Keeping compliant records of processing activities
  • Defining the purpose of data processing
  • And the lawful basis for data processing

Compliant Records of processing activities

If you are a DPO, you already know that the Records of processing activities should represent documentation of all activities around personal data processing within your Organization.

As it is described in Article 30, that includes some of the following;

  • WHO is processing the data: the name of the Data Controller and, where applicable, the joint controller, the controller’s representative, and the DPO;
  • a description of the processing, explaining HOW the Organization is processing personal data
  • the purpose of processing is to explain WHY the Organization is processing personal data
  • a description of the categories of data subjects and the categories of personal data;
  • the categories of recipients to WHOM the personal data have been or will be disclosed
  • For HOW LONG do you need to keep the data after the initial processing purpose expiry

However, having control over technical execution is far more complicated. As a DPO, you need to understand and monitor how data retention and data erasure policies are implemented.

The Purpose of Processing Activities

Defining the purpose of the processing activities is one of the mandatory requirements for keeping compliant records of processing activities.

The purpose is always connected to a business process, either administrative, regulatory, or related to the core business.

Answering why you are processing personal data calls out for the next important question; what lawful basis do you rely on when processing personal data?

The Lawful Basis for Processing

As you already know, there can only be six possible lawful bases for personal data processing;

  1. Consent
  2. Contract
  3. Legal obligation
  4. Vital interests
  5. Public task
  6. Legitimate interests

Organizations need to conduct an assessment to specify the lawful basis for processing, and the result must be one clear and documented lawful basis for every processing activity.

[RELATED TOPIC: How to conduct Legitimate Interests Assessment (LIA)?]

You must ensure that you do not process personal data without a lawful basis.

It may seem like we are deterring from the topic, but it is important to notice

One of the key pieces of information that you need to define to have a compliant ROPA is a data retention period for each processing activity.

Requirements for compliant data erasure:

  1. Compliant Records of processing activities
  2. Defining the purpose of processing activities
  3. Defining the lawful basis

Request a Data Privacy Manager demo

Let us navigate you through the Data Privacy Manager solution and showcase functionalities that will help you overcome your compliance challenges.

Scroll to Top