GDPR access and erasure requests: how to automate handling

A customer request such as “send me all the data you hold about me” or “delete me” sounds simple. In practice, though, their data is scattered across the online shop, the CRM, the newsletter tool, invoicing and support e-mails. When requests are handled manually, it is easy to forget one system, miss the deadline or send the data to the wrong person.

Automating GDPR requests does not make the legal assessment for you. It does, however, handle the register, deadlines, identity verification, data collection from every system and the audit trail. People then decide only where a decision is genuinely needed. This article gives you a process, an example, a decision table and a checklist. It is not legal advice – discuss specific exemptions and response wording with your data protection officer or a lawyer.

What a business must comply with

In its guide for small and medium-sized businesses, the European Data Protection Board (EDPB) states that a data subject request must be answered within one month. If a request is complex, the deadline can be extended by two further months, but the person must be informed of this within the first month (EDPB: Respect individuals’ rights).

According to EDPB Guidelines 01/2022, the period as a rule starts on the date the request is received. The EDPB considers it good practice to confirm receipt in writing and state from which day to which day the period runs (EDPB Guidelines 01/2022).

Handling a request is generally free of charge. A fee or refusal is only an option for a manifestly unfounded or excessive request, for example because it is repetitive, and the business must be able to prove this. Where there are reasonable doubts about identity, the business may ask for additional information, for example if the request came from a different e-mail address than the one the customer usually uses.

According to the EDPB, the right of access has three components: confirmation of whether the business processes data about the person, the data itself, and information about the processing, such as purposes, categories of data, recipients and retention period. In the case of erasure, recipients to whom the business disclosed the data must also be informed, unless this is impossible or involves disproportionate effort.

Example: a request from an online shop customer

The following example is illustrative. A small WooCommerce shop uses a separate CRM, a newsletter tool, an invoicing system and a helpdesk. A customer writes via the contact form that she wants a copy of her data and then to be removed from marketing.

Without a process, the e-mail gets lost in a shared inbox, someone exports the orders but forgets the helpdesk, and the reply goes out after five weeks. With automation, a record with a deadline is created on receipt, the customer receives a confirmation with the dates, and verification runs through the e-mail address stored in her shop account. Connectors then prepare material from all five systems and the responsible person reviews it before it is sent.

Removal from the newsletter and CRM is carried out automatically. Invoices are kept because the business may have a legal obligation to retain them, and the reply explains this to the customer in plain language.

How to design the automated process step by step

1. One entry point and a request register

The EDPB recommends making it easy to exercise rights electronically, for example through a form on the website. A form is useful because it immediately captures the type of request and the contact details. Requests may also arrive by e-mail or post, however, so they must be logged in the same register.

Each record should contain the date of receipt, the type of right, the calculated deadline, the status, the responsible person and the history of steps. Automatic reminders before the deadline are the simplest protection against missing it.

2. Identity verification proportionate to the situation

The EDPB guidelines stress that verification must be proportionate and must not require more data than necessary. The EDPB considers a copy of an identity document disproportionate if the business has already authenticated the person in another way, for example through an account login.

In practice, a confirmation link sent to the e-mail address held for the customer, or a request submitted from a logged-in account, is sufficient. Leave exceptions, such as a request from an unknown address, to a person.

3. A system map and connectors

List every system that holds customers’ personal data and, for each one, define the identifier used for searching, the export method and the erasure method. This is typically an e-mail address, phone number or customer number.

Where an API is available, connect it. Where it is not, create a task for a named person with a deadline and mandatory confirmation. WordPress has had built-in tools for exporting and erasing personal data since version 4.9.6. Plugins can add their own exporters via the wp_privacy_personal_data_exporters filter and process data page by page to avoid timeouts (WordPress Plugin Handbook: exporter).

4. Data collection and human review before sending

Automation should assemble the material, not send it without review. The material may contain data about other people, such as colleagues’ names in an e-mail thread. According to the EDPB, protecting the rights of others leads to redacting or omitting the affected parts, not to refusing the whole request.

The EDPB also points out that a business must not deliberately erase or modify data while an access request is being handled. If a system deletes data automatically after a short period, the process must ensure that the material for the request is not lost before it is handed over.

5. Erasure with exemptions and notifying recipients

The right to erasure is not absolute. The EDPB guide lists exemptions, such as compliance with a legal obligation or the establishment, exercise or defence of legal claims. The process should therefore distinguish, for each system, what is erased, what is retained and why.

The WordPress erasure interface is a good model. Each module returns the number of items removed, whether items were retained and a message explaining why they were retained (WordPress Plugin Handbook: eraser). We recommend the same structure for CRM or newsletter connectors.

6. Secure delivery and an audit trail

Never send a copy of the data as a plain attachment to an address you have not verified. A link with limited validity or delivery into a logged-in account is safer. The EDPB recommends replying in writing so that the business can prove it responded.

Record who did what and when, including the reasons why any part of a request was not granted. Do not store the audit record together with a full copy of the export, however, or you will create another unnecessary store of personal data.

What to automate and what to leave to people

Step Suitable for automation Decided by a person
Receiving the request Form, register entry, confirmation with deadline Logging requests received by post or phone
Identity verification Confirmation link to a known e-mail, logged-in account Unusual cases and doubts
Data collection API exports from all systems Checking for other people’s data and redaction
Erasure Marketing lists, profiles with no retention obligation Exemptions, such as accounting records or disputes
Deadlines Deadline calculation and reminders Extending the deadline and justifying it

Common mistakes

  • Requiring a copy of an ID card from a customer who is logged in to their account.
  • Exporting only from the online shop although data also sits in the helpdesk, CRM or accounting.
  • Sending an export automatically without checking for other people’s data.
  • Erasing the whole customer record, including documents the business must retain.
  • No register, so the business cannot prove when and how it responded.
  • Forgetting to notify external recipients to whom the business disclosed the data.

Pre-launch checklist

  • We have one request register with the date of receipt, deadline and status.
  • The confirmation of receipt states the period during which the deadline runs.
  • Identity verification uses an existing login or a known contact.
  • Every system holding personal data has a defined export method, erasure method and owner.
  • A human review takes place before a copy is sent.
  • Erasure records which data was retained and why.
  • The copy is delivered securely and the link has limited validity.
  • We have tested the process with a test customer across all systems.

Frequently asked questions

Is automation worth it for just a few requests a year?

Full integration is not always worth it. A register with deadlines, reply templates and a system map always pay off, however, because with rare requests nobody remembers the procedure. Add connectors to the systems holding the most data.

Can we ask for an identity document?

Only if it is proportionate. According to the EDPB, a copy of an ID document is disproportionate if you have already authenticated the person, for example through an account login. Use existing verification first and ask for further information only where there are reasonable doubts.

Do we have to delete invoices too when erasing data?

Not always. The right to erasure has exemptions, such as compliance with a legal obligation. We recommend flagging the retained data, not using it for other purposes such as marketing, and explaining the reason for retention in the reply.

Can WordPress handle this without another tool?

For data stored in WordPress, yes: the built-in tools cover both export and erasure, including confirmation of the request by e-mail. External systems such as a CRM or invoicing, however, need to be connected separately or handled through tasks for a person.

Next step

Start with a system map and a request register, then automate verification and exports from your largest data sources. If you need to connect your online shop, CRM and other tools into one controlled process, see Webiant’s process automation and API integration services and other articles on our blog. For a larger internal workload, a custom web application can also help. Get in touch via our contact form and we will propose an approach based on your systems.

Sources

Choose which cookies to allow. You can change your choice at any time using the footer link or cookie button.

Privacy policy and cookie details