Irish businesses, SMEs, and enterprises processing personal data of customers, employees, or visitors, especially those receiving deletion requests or concerned about GDPR fines from the DPC.
Readers will gain practical guidance on complying with erasure requests, recognizing exemptions, managing challenges like backups and partial deletions, and implementing workflows to ensure regulatory compliance and avoid complaints.
Key Takeaways
- The right to erasure under GDPR Article 17 requires deleting personal data when specified grounds apply, such as withdrawn consent or no longer necessary.
- Exceptions allow refusal for legal obligations, public interest research, legal claims, and Irish-specific rules like tax records.
- Respond to requests within one month, notifying third parties and handling backups appropriately.
- Build a structured process: intake, triage, data mapping, deletion, notifications, and logging.
- EDPB 2025 enforcement and thousands of DPC complaints highlight priority on erasure compliance.

When a customer, employee, or website visitor asks you to delete their personal data, you need to know whether you must comply and how to do it properly. The right to erasure in Ireland under GDPR is one of the most frequently exercised data protection rights, and the Data Protection Commission (DPC) has received thousands of erasure-related complaints since the regulation came into force. This guide explains when the right applies, when you can refuse, and how to build a deletion process that keeps your business compliant.
What is the right to erasure?
The right to erasure is the right of an individual to have their personal data deleted by a data controller. Set out in Article 17 of the GDPR, it is also known as the "right to be forgotten," though the two concepts are not identical. The right to be forgotten originally arose from a 2014 Court of Justice ruling against Google concerning search results. The GDPR's right to erasure is broader: it covers all personal data held by any controller, not just search engine listings.
Anyone whose data you process can make an erasure request. Like subject access requests, there is no required format. A request can be made by email, letter, phone, or in person. The person does not need to cite Article 17 or use specific legal language. If someone asks you to delete their data, treat it as an erasure request.
The European Data Protection Board (EDPB) selected the right to erasure as the focus of its 2025 Coordinated Enforcement Action. This signals that regulators consider erasure compliance a priority area.
When must you comply with an erasure request?
You must erase personal data without undue delay if any of the following grounds apply under Article 17(1):
- The personal data is no longer necessary for the purpose it was collected
- The individual withdraws consent and there is no other legal basis for processing
- The individual objects to processing under Article 21 and there are no overriding legitimate grounds
- The individual objects to processing for direct marketing purposes
- The personal data has been unlawfully processed
- Erasure is required to comply with a legal obligation
- The data was collected from a child in relation to information society services
If even one of these grounds applies and no exemption overrides it, you must delete the data. You do not get to choose whether the request is convenient.
When you have shared the data with third parties, Article 17(2) requires you to take reasonable steps to inform those recipients of the erasure request. This includes any processors handling data on your behalf under a data processing agreement.
Author's tip: Keep a record of which third parties have received personal data. When an erasure request arrives, you will need this list to notify recipients under Article 17(2).
When can you refuse an erasure request?
The right to erasure is not absolute. Article 17(3) sets out exceptions where you can lawfully refuse to delete data:
- Freedom of expression and information - Where the data is necessary for journalistic, academic, artistic, or literary purposes
- Legal obligation - Where you are required by law to retain the data, such as employment records, tax records, or company law filings
- Public health - Where processing is necessary for public health purposes under Article 9(2)(h) or (i)
- Archiving and research - Where the data is processed for archiving in the public interest, scientific research, historical research, or statistical purposes
- Legal claims - Where the data is necessary for the establishment, exercise, or defence of legal claims
The Data Protection Act 2018 adds further Irish-specific restrictions, including exemptions for the prevention or detection of criminal offences and the assessment of tax or duty.
If you refuse an erasure request, you must inform the individual of the reasons, their right to complain to the DPC, and their right to a judicial remedy. In our experience, you should document your reasoning thoroughly.
Please note: "We might need this data later" is not a valid reason to refuse. You must point to a specific exemption under Article 17(3) or the Data Protection Act 2018.
What is the response timeline?
You must respond to an erasure request without undue delay and at the latest within one month of receipt. This mirrors the timeline for subject access requests.
If the request is complex or you have received a high volume of requests, you can extend the deadline by a further two months. You must notify the individual of the extension and the reasons within the initial one-month period.
Before acting on the request, verify the requester's identity using proportionate measures. The same principles apply as for access requests: do not demand excessive identification, but ensure you are deleting the right person's data.
Once you have confirmed the request is valid:
- Identify all systems and locations where the individual's data is stored
- Delete the data from live systems
- Notify any third parties who have received the data
- Confirm the deletion to the individual in writing
Need help building your GDPR deletion processes? Open Forest helps Irish businesses set up compliant data protection workflows, from erasure handling to breach response. Talk to us about getting your processes in order.
What are the practical challenges of deletion?
Deleting data from a live database is straightforward. We tend to see that the complications arise everywhere else.
Backups and archives - Most businesses maintain regular backups. Deleting data from live systems does not automatically remove it from backup tapes or cloud snapshots. You need a documented approach to how backup data is handled when an erasure request is received. Some organisations flag the data for deletion on the next backup rotation cycle rather than immediately purging all backup copies.
Third-party processors - If you have shared the data with processors, you must inform them and ensure they delete it too. Your data processor agreement should include provisions for handling erasure requests.
Partial erasure - Sometimes you must retain certain data while deleting the rest. For example, you may need to keep transaction records for tax purposes while deleting the customer's marketing preferences. This requires careful data mapping so you know exactly which fields to erase and which to keep.
Anonymisation as an alternative - Where full deletion is impractical, anonymisation can be an acceptable alternative. If the data is truly anonymised, meaning the individual can no longer be identified from it even in combination with other data, it falls outside the scope of the GDPR compliance. Be careful here: pseudonymised data is not anonymous and remains subject to the regulation.
If you have a document retention policy, it should already map where personal data lives and how long it is kept. This mapping is your starting point for handling erasure requests efficiently.
How to build an erasure request process
A structured erasure process protects your business and ensures you respond consistently within the legal deadline. Follow the steps below to build an erasure request process.
- Create an intake channel - Make it easy for individuals to submit erasure requests. A dedicated email address or web form reduces the risk of requests being missed. A DPC case study showed that a controller's request was missed during a process transition, leading to a complaint that was only resolved through amicable engagement.
- Triage each request - Verify the requester's identity, confirm which data is affected, and assess whether an exemption applies. Log the request immediately.
- Map your data holdings - Know where personal data sits across every system: CRM, email, HR platform, marketing tools, backups, and third-party processors. Without this map, you cannot guarantee complete deletion.
- Execute the deletion - Remove the data from all identified systems. Where partial retention is required, delete only the data that falls within the scope of the request.
- Notify third parties - Contact any recipients of the data and instruct them to erase it as well.
- Confirm and log - Send written confirmation to the requester and record the outcome in your request log for accountability purposes.
If your business is already managing GDPR compliance, integrating an erasure process should be a natural extension of your existing data protection framework.
Your next step
The right to erasure is a routine part of GDPR compliance, not an edge case. With thousands of erasure complaints filed with the Irish DPC since 2018 and the EDPB making it a coordinated enforcement priority, the message is clear: controllers need robust deletion processes.
Start by mapping your data, documenting your retention rules, and building a repeatable workflow for handling requests. Open Forest can help you put these foundations in place so your business is ready when a deletion request arrives.

Laura Ryan is a practising Barrister at the Bar of Ireland. She graduated from the Honourable Society of King’s Inns in 2024, having previously qualified and practised as a Chartered Accountant in a big four accounting firm.













