Handling Data Subject Requests
Access, erasure, objection and other requests under Articles 12 to 22 GDPR handled within the deadline, with identity checks, exemptions weighed and a reviewed answer.
- By
- By Bart Lieben, Attorney-at-Law
- Published
- Updated
The question
A former employee asks for every e-mail that mentions her. A customer wants his account deleted, including his order history. Someone objects to your newsletter and asks what you know about him. The clock is running. What do you have to give, what may you keep, and how do you answer in time?
The GDPR gives individuals a set of rights in Articles 15 to 22: access, rectification, erasure, restriction, portability, objection, and rights around automated decisions, including profiling. Article 12 sets the procedure. You must act on a request without undue delay and at the latest within one month of receipt. Where necessary, given the complexity and number of requests, that period may be extended by two further months, but you must tell the person about the extension, with the reasons, within the first month. If you decide not to act, you must say so within one month, with the reasons and the possibility to complain to the supervisory authority or go to court.
Answering is free of charge. A request that is manifestly unfounded or excessive can be refused, or a reasonable fee charged, but you must be able to show why. Where you have reasonable doubts about who is asking, you may ask for additional information to confirm their identity (Article 12(6)).
The rights have limits. The copy of the data provided under Article 15 may not adversely affect the rights and freedoms of others, so third-party data often has to be redacted. Erasure under Article 17 does not apply where processing is needed, for example, to comply with a legal obligation or for the establishment, exercise or defence of legal claims. An objection to direct marketing, on the other hand, always ends the use of the data for that purpose (Article 21(3)). Member State law may add restrictions under Article 23.
Our approach
We set up a route before the first request arrives, and then handle requests with you as they come in.
Each request is logged in our data subject request function on the day it arrives, through the client portal, with the channel, the right invoked and the deadline. From then on, everyone sees what is open and how many days are left. If an extension is justified, we record the reasons and prepare the notice for the first month.
Next, identity. We check it in proportion to the request: matching an address the person already uses with you is often enough, while a request for sensitive data or a request made through a third party needs more. Unclear requests get a short question back, so that you answer what was really asked.
For an access request, we collect the data held in your linked records into an export and review it item by item: what must be redacted to protect others, what is privileged, and what falls outside the request. The answer also gives the information Article 15(1) requires, such as purposes, recipients and retention periods, which we take from your record of processing. Our guide to access requests walks through the steps.
For erasure, we trace the person's data across your records and propose, per record, deletion, anonymisation or retention with the legal reason. Accounting and employment rules often require some records to be kept for a set period (see retention periods).
We use our own technology and our own AI to collect, sort and draft. A lawyer decides on every exemption and every redaction, and reviews the answer before it goes out.
What you get
- A request procedure and template answers your team can use, in English and Dutch.
- Each request in its own file, with deadline, identity check, decisions and answer.
- For access and portability requests, a reviewed export with redactions explained.
- For erasure requests, a record of what was deleted, what was kept and why.
- A status list of requests for your DPO or management.
Limits apply. We can only answer from the data you give us access to: e-mail boxes, shared drives and systems we cannot see stay your team's task, and we tell you where to look. Where a request is part of a wider dispute, such as with a former employee, the answer may need to be coordinated with the litigation, and we will flag that first.
Next step
Forward us the request you received, with the date it arrived and the systems that may hold the person's data. If you want a procedure in place before the first request, send us your privacy notice.
In short
- Every request logged with its deadline from day one
- Identity checked in proportion to the request
- Exemptions and the rights of others weighed per item
- Data collected, redacted and explained in a clear answer
- A file you can show the authority if the person complains
- Reviewed by a lawyer