{"id":2918,"date":"2026-09-21T15:27:06","date_gmt":"2026-09-21T13:27:06","guid":{"rendered":"https:\/\/blog.eprivacy.eu\/?p=2918"},"modified":"2026-10-19T10:09:36","modified_gmt":"2026-10-19T08:09:36","slug":"designing-a-gdpr-deletion-policy","status":"publish","type":"post","link":"https:\/\/blog.eprivacy.eu\/?p=2918","title":{"rendered":"From retention periods to erasure requests: deletion concepts that actually work"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Writing a deletion policy is one thing. Ensuring that personal data is actually removed from the systems in a timely manner is another. It is precisely this practical implementation that is increasingly becoming the focus of data protection supervisory authorities.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In February 2026, the European Data Protection Board (EDPB) published the results of its Europe-wide audit on the right to erasure: 32 participating supervisory authorities, 764 organizations that responded, and seven recurring vulnerabilities. Five of these are not legal issues, but rather implementation issues &#8211; lack of processes, training, backups, and anonymization. German supervisory authorities have announced that they will use the report\u2019s recommendations as a guideline when engaging with controllers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A documented deletion policy alone is therefore not enough.&nbsp;What matters is that deletion rules can actually be implemented in day-to-day business operations. This is exactly where our webinar comes in:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What regulators expect:<\/strong>&nbsp;the seven vulnerabilities identified in the EDSA audit &#8211; and which common assumptions do not hold up to scrutiny. From deactivated accounts to the operating system\u2019s delete command to masking, which is mistaken for anonymization.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>From a directory to an actionable deletion rule:<\/strong>&nbsp;how data categories, retention periods, and start dates are transformed into a rule that can be technically implemented &#8211; and why a retention period without a start date is not actionable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The challenging areas:<\/strong>&nbsp;backups, legal holds and proof of erasure, anonymization as an alternative to erasure\u2014and handling erasure requests under Article 17 of the GDPR, where partial erasure is the norm rather than the exception.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We\u2019ll also share an example from a project, including the points we would approach differently in hindsight, as well as a 30-60-90-day roadmap for getting started.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Your Speaker:<\/strong><br>Stefanie Bauer, CEO, ePrivacy GmbH<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>When<\/strong>:<br>Date: Tuesday, November 3rd 2026 | Time: 4.00pm -5.00pm CEST<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/events.teams.microsoft.com\/event\/2a897367-d1a0-4d09-959e-ed7113f42dcc@ef9db3d4-9134-416e-aace-116d440d493a\" data-type=\"URL\" target=\"_blank\" rel=\"noreferrer noopener\">Registration teams<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We are looking forward to your participation and your questions!<br>Your ePrivacy Team<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Writing a deletion policy is one thing. Ensuring that personal data is actually removed from the systems in a timely manner is<\/p>\n<p class=\"link-more\"><a class=\"myButt \" href=\"https:\/\/blog.eprivacy.eu\/?p=2918\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":2921,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-2918","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-eprivacy-events"],"_links":{"self":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2918","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2918"}],"version-history":[{"count":5,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2918\/revisions"}],"predecessor-version":[{"id":2956,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2918\/revisions\/2956"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/media\/2921"}],"wp:attachment":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2918"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2918"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2918"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}