Art. 15 · Art. 12 GDPR

Subject access request under Art. 15 GDPR: how your company responds

Anyone who asks for access under Art. 15 GDPR learns from your company whether you process data about them. They get a copy of that data and information on purposes, recipients, storage period and their rights. You answer without undue delay, within one month at the latest; the first copy is free of charge.

Simon OrzelSimon Orzel·

What do you have to provide on a request under Art. 15?

According to the European Data Protection Board (EDPB), the right of access has three parts. You confirm whether you process data about the person. You give access to that data, usually as a copy, and inform them about the processing (Art. 15(1) and (3)).

That information covers purposes, categories of data, recipients, storage period, the person's rights, the right to complain, the source of the data and automated decisions (Art. 15(1)). If you transfer data to a third country, also name the safeguards for it (Art. 15(2)).

The person does not have to give a reason, and you do not check what they want the information for (EDPB). The first copy is free of charge; for further copies you may charge a reasonable fee based on administrative costs (Art. 15(3)).

Art. 15(1) to (3) GDPR

Which deadline applies, and how do you check who is asking?

You answer without undue delay and within one month of receipt at the latest (Art. 12(3)). The period starts when the request reaches you through one of your official channels, even if nobody has read it yet. The EDPB counts like this: received on 5 March, answered by 5 April at the latest.

If requests are complex or numerous, you may extend by two months, provided you say so with reasons within the first month. If you refuse, give the reasons within one month and point to the authority and the courts (Art. 12(4)).

If you have reasonable doubts about identity, you may ask for additional information (Art. 12(6)). If you ask straight away, the EDPB says the period is suspended until you have it. It generally considers a copy of an ID document unsuitable.

Art. 12(3), (4) and (6) GDPR

Where do you search, and what goes into the copy?

The request covers all data about the person unless they narrow it. The EDPB expects you to search all systems, digital and on paper, with search terms such as name and customer number. That includes emails, logs and data you have derived, such as an assessment.

What counts is the state of things on receipt. Inaccurate data belongs in the answer too; data you have already deleted under your retention rules cannot be provided. Explain codes and abbreviations.

The answer comes in a lasting form, and for a request by email in a commonly used electronic format (Art. 15(3)). According to the EDPB you may send it by email if the necessary safeguards are in place.

Art. 15(3) GDPR

When may you limit access?

The copy must not adversely affect the rights and freedoms of others (Art. 15(4)). According to the EDPB you then redact individual passages, such as a colleague's name, and hand over the rest.

You may refuse manifestly unfounded or excessive requests, or charge a fee for them (Art. 12(5)). The EDPB reads both narrowly, and the burden of proof is yours.

National law may restrict the right of access (Art. 23 GDPR), in Germany § 34 BDSG, for example for data you keep only because of statutory retention duties. Further conditions have to be met as well. You document the reasons for a refusal (§ 34(2) BDSG).

Art. 12(5) · Art. 15(4) · Art. 23 GDPR · § 34 BDSG

An example: a former employee asks

The fictional Berger Haustechnik GmbH has 90 staff and no legal department. On 5 March a fitter it dismissed a week earlier writes to its data protection address. He wants all the data about him.

The head of HR confirms receipt and gives the deadline of 5 April, as the EDPB recommends. She does not ask for ID, because the email comes from the address in his personnel file. She searches the payroll software, the time recording, the personnel file and the mailboxes.

In one performance review she redacts a colleague's name. As a recipient she names the specific tax adviser's office that runs payroll. Mistakes here would be asking for the reason because a lawsuit looms, or holding back the whole review.

With an AI assistant

An AI assistant such as Claude, ChatGPT or Copilot can prepare the answer. It compiles the information under Art. 15(1) from your record of processing activities and your privacy notice, works out the deadline and marks passages about third parties. The EDPB also names both documents as a basis that you tailor to the person.

Whether the person is who they claim to be, what you redact and whether a restriction applies is your company's decision as controller.

Giving a person's data to an assistant is itself processing; check first that a data processing agreement with its vendor is in place (Art. 28 GDPR). A GDPR walkthrough on nisd2.eu is in the works, with the same MCP server as the NIS 2 walkthrough.

Common questions

Does a subject access request have to be in writing or on a form?

No. The GDPR sets no particular form, the EDPB says, and the person does not have to use your form; an email to an official contact address is enough. You do not have to act on requests sent to random or clearly wrong addresses if you have offered a suitable channel.

What do we answer if we hold no data about the person?

You tell them so, because confirming whether you process data is itself part of access (Art. 15(1)). If details are missing to find the person, tell them; they can provide them (EDPB).

Is the right to a copy a separate right alongside access?

No, says the EDPB: the copy is how you give access, not an additional right. If the person wishes, information given orally or inspection on site are possible too.

How often can someone request access?

The GDPR sets no fixed number. A request can be excessive if it is repeated often (Art. 12(5)). The EDPB adds: the more often your data about the person changes, the more often they may ask.

Do we also have to provide data from backups?

In principle, yes. § 34(1) no. 2(b) BDSG exempts data that serves only backup purposes. That applies only if answering would take disproportionate effort and any other use is ruled out by technical and organisational measures. You document the reasons (§ 34(2) BDSG).

Sources

  • Regulation (EU) 2016/679 (GDPR), Art. 12, 15, 23 and 28, CELEX 32016R0679, publications.europa.eu
  • European Data Protection Board, Guidelines 01/2022 on data subject rights, Right of access, version 2.1 (adopted 28 March 2023, corrected 30 May 2024), edpb.europa.eu
  • Federal Data Protection Act (BDSG), § 34, gesetze-im-internet.de

In the works

The GDPR walkthrough

After the NIS 2 walkthrough, nisd2.eu is building a GDPR walkthrough. It will work with the same MCP server, so your own AI assistant can fill it in too. We are not naming a date yet. Join the waitlist and we will write to you once it is ready.

With a free account on nisd2.eu. You can leave the waitlist at any time on the same page.

Been asked to handle NIS2?

In the end you have everything in one document: what is done, what is still open, and your management's approval with name and date. The app writes the texts.

Get started
Simon OrzelCory Hisey

Book a call

Pricing and terms
The NIS2 walkthrough: your path step by step, the first items done