Skip to content
PROOF48
All answers
automation

How to actually fulfil a GDPR data deletion request without manual digging

To fulfil a GDPR deletion request, confirm who is asking, find their data in every tool you use, check whether an Article 17(3) exception applies, delete it, tell recipients and reply within one month (Article 12(3)). Software can run the intake, the search and the deadline clock. A person makes the exception call. PROOF48's automation page lists any compliance decision with legal accountability as a poor fit.

Founder, PROOF48Updated 2026-11-136 min read

01What the regulation requires, in plain terms

Article 17(1) of the GDPR gives a person the right to have their personal data erased without undue delay where one of six grounds applies. Among them: the data is no longer needed for the purpose it was collected for, the person withdrew consent and no other legal ground exists, they objected under Article 21 and nothing overrides the objection, or the data was processed unlawfully. Article 12(3) sets the clock. You must act without undue delay and in any event within one month of receiving the request. If you need longer, the period can be extended by two further months where necessary, but you must tell the person within the first month and give the reasons.

  • One month from receipt, extendable by two further months where necessary, with notice inside the first month (Art. 12(3))
  • Free of charge, unless the request is manifestly unfounded or excessive, and then you must be able to show it (Art. 12(5))
  • Doubts about who is asking: you may request the extra information needed to confirm identity (Art. 12(6))
  • If you do not act, you tell the person within the month, with reasons, and name their right to complain to a supervisory authority and to seek a judicial remedy (Art. 12(4))

02Where the manual digging comes from

The slow part of a deletion request is rarely the deleting. It is not knowing where the person is. A customer who booked once can sit in your booking tool, your CRM, a newsletter list, the mailbox where the enquiry arrived, an invoicing system and a chat transcript. The fix is a list written once: every tool that holds personal data, what it holds, the field that identifies a person (usually the email address), and who in the business can delete from it. With that list a request stops being a hunt and becomes a checklist that anyone on the team can run.

  • List every tool holding personal data, with the identifying field and the person who can delete from it
  • Log each request on arrival with its date and an internal due date set well inside the month
  • Search every tool on the list by that one identifier and record what was found
  • Delete, or write down the exception that applies and who approved it
  • Reply to the person in writing and keep the log

03What software can run and what a person must decide

Intake, search by identifier, reminders and the paper trail repeat on every request, so a tool can run them: a form or inbox rule that opens a record, one task per system, a countdown that warns before the deadline, a drafted reply. The decision is different. Article 17(3) says erasure does not apply where processing is necessary for a legal obligation, for legal claims, for freedom of expression and information, for a public interest task, for public health, or for archiving and research. Whether a record you must keep, or a dispute you are in, falls under one of those is a judgement call. It belongs to you and your data protection adviser. Article 19 adds a step: tell each recipient the data was disclosed to, unless that is impossible or takes disproportionate effort, and tell the person who those recipients are if they ask.

  • Automate: intake, deadline countdown, one task per system, search by identifier, drafted reply, the log
  • Keep with a person: doubts about identity, Art. 17(3) exceptions, anything refused or extended
  • Art. 19: notify recipients of the erasure, unless that is impossible or disproportionate effort
  • Ask each vendor in writing how deletion works in their tool

04What PROOF48 builds here, and when it is the wrong choice

PROOF48's AUTOMATE plan, at 2,997 EUR a month, covers a website chatbot, DM and email auto-responders, booking automation, a CRM and two custom automations a month. A deletion-request tracker is not a listed feature. It is the kind of repeatable flow we would map first, and whether it fits is decided after that mapping, not promised here. Our automation page says plainly that a compliance decision with legal accountability is not a good fit, so the exception call stays with you. If you get one request a year, a shared spreadsheet and the list above beat any build. The same goes if you run a few tools and already know where every customer sits.

  • Possible as custom work after mapping the process, and not a listed feature of any plan
  • Compliance decisions with legal accountability stay with you and your adviser
  • The wrong choice: one request a year, few tools, or no written list of where data sits yet
  • Sources read for this article: gdpr-info.eu (Art. 12, 17 and 19), dataprotection.ro (ANSPDCP) and edpb.europa.eu
From a build we shipped

No deletion workflow built yet, and the nearest build we have

We have not built a data deletion workflow for a client, and the case study makes no claim about one. The nearest real build is the ordering system for Rotiseria Baba Novac in Bucharest: menu, cart, Stripe checkout, pickup slots and email confirmations through Resend, with orders the restaurant keeps in full. An order there touches the ordering system, Stripe checkout and the email service, which is the kind of list a deletion request has to walk through. We publish no order volume and no request figures.

See the build: Rotiseria Baba Novac

Questions, answered

How long do I have to answer a deletion request?

Without undue delay and in any event within one month of receiving it (Article 12(3)). The period can be extended by two further months where necessary, but you must tell the person within the first month and say why.

Can I refuse a request, or charge for it?

Information and actions under these articles are free of charge. For requests that are manifestly unfounded or excessive, particularly if repetitive, you may charge a reasonable fee or refuse, and the burden of showing that is on you. Any refusal must reach the person within the month, with reasons and their right to complain. Whether a case qualifies is for your data protection adviser.

Does a CRM or a chatbot make deletion automatic?

No. A tool only deletes from the place it controls. A chatbot transcript or a CRM record that holds a name or contact detail is one more place on your list, and the list is what makes the process fast.

Are regulators actually checking how erasure requests are handled?

In March 2025 the European Data Protection Board announced a coordinated enforcement action on the right to erasure, with 30 data protection authorities and the European Data Protection Supervisor taking part. They look at how controllers handle erasure requests and apply the conditions and exceptions. We do not know what any single authority will check at your business.

Who supervises this in Romania?

ANSPDCP, the national data protection authority. Its published list of rights under Regulation (EU) 2016/679 includes the right to erasure (the right to be forgotten) and the right to lodge a complaint with the national supervisory authority. For your own case, ask your data protection adviser.

Where PROOF48 fits

A deletion request goes smoothly when you know where personal data sits before anyone asks. Write the list, log every request with a due date, let a tool search and remind, and keep the Article 17(3) decision with a person. The one-month clock in Article 12(3) is the same for one request or twenty. PROOF48 gives no legal advice and no compliance guarantee: it maps the repeatable steps and says so when a process is not ready to automate.

· Founder, PROOF48

Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.

Related articles