Free · self-check
Do you need a data protection officer?
Find out in two minutes whether the GDPR and the German BDSG require you to appoint one and which duties then apply, with the legal reference for every point.
Up to 8 questions · 2 minutes
Create structured deletion concepts under Art. 17 GDPR. Define deletion classes, deletion rules, deletion deadlines, deletion procedures, and responsibilities systematically. Reminders alert you automatically to due deletion reviews – and the task log documents the actual execution as robust evidence.
Deletion Concepts
Create deletion concepts with all required components: deletion deadlines, deletion procedures, responsibilities, and technical implementation. Link deletion classes to the affected processing activities and take over numerous details from them; tasks on deletion rules trigger manual deletions or verify automatic ones.
Automation
Set reminders for regular deletion reviews. Reminders prompt you about due deletion reviews. Create tasks directly from reminders and assign them to responsible persons.
Features
From creation to deadline monitoring to export – all the tools for a complete deletion concept.
Define deletion deadlines for various data categories and processing purposes. Consider statutory retention periods (HGB, AO) and contractual obligations.
Describe deletion processes for various systems, data carriers, and backup media. Define when deletion, anonymization, or archiving should take place.
The system automatically shows which deletion deadlines apply to which processing activities. No inconsistencies between the processing register and the deletion concept.
All deletion concepts centrally in a filterable overview. Status, responsible persons, and last update at a glance.
Revision-proof export as PDF or DOCX with all deadlines, procedures, and responsibilities as well as the task log of the deletion rules as evidence of execution – including automatic revision upon every approval. Directly usable as complete evidence for audits and supervisory authorities.
FAQ
A deletion concept consists of deletion classes and deletion rules. Deletion classes link to one or more processing activities. Deletion rules link to one or more deletion classes and use a structured form to define the specific deletion process. Retention periods, procedures and responsibilities are thus recorded in one place. The result is a concept that matches your record of processing activities.
No. Because deletion classes are linked to processing activities, you take over numerous details directly from the record. This avoids maintaining the same information twice and keeps the deletion concept and the record of processing activities consistent. The relationships tab shows at any time which processing activities a deletion class covers.
You set retention periods per data category and processing purpose, taking into account statutory retention obligations, for example under German commercial and tax law (HGB and AO), as well as contractual obligations. For each system, storage medium and backup medium you describe whether data is deleted, anonymized or archived. This shows that data is not kept longer than necessary while retention obligations are still met.
Through tasks attached to the deletion rules. A task triggers a manual deletion or serves to check an automatic deletion; the person responsible completes it and documents the result. The task log of the deletion rules is included in the export of the deletion concept. This lets you show auditors and the supervisory authority not only the concept but also how it has been carried out.
With follow-up reminders. You set the date of the next check on the deletion concept or on a task. On that date you receive an email, and the reminder appears on your dashboard as a new task. You can assign it to the person responsible, so regular deletion runs do not depend on individual calendar entries.
You export the deletion concept as PDF or DOCX with all retention periods, procedures and responsibilities as well as the task log of the deletion rules. Logo, font, header and footer follow your document settings. The document therefore works as evidence under Art. 5(2) GDPR for audits, for management and for enquiries from the supervisory authority.
We will show you how preeco | data protection systematically supports your deletion concepts under Art. 17 GDPR.