Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.1 · Control for PII controllers

A.1.3.10 Handling requests

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

A municipal utility receives privacy requests through many routes: email, letter, the call centre and comments under social media posts. One customer asks there for access to his consumption data. The comment lands in the marketing inbox, and a phone request from the same person ends up as free text in the customer system. After seven weeks nobody has replied, and the complaint is with the supervisory authority. A.1.3.10 requires defined and documented rules for how requests from data subjects are received, handled and answered on time.

The control is the operating system for all data subject rights. Access, copy, correction, erasure, objection and complaint all run through the same procedure with the same deadlines.

What does the standard require?

The control is brief and governs the handling of all legitimate requests.

  • Document rules and procedures. The organization decides how it handles and answers legitimate requests from data subjects and records this in writing.
  • Many kinds of request. They include, for example, asking for a copy of the data or making a complaint.
  • Fees only where allowed. Some jurisdictions permit a charge in certain cases, for example for excessive or repeated requests.
  • Fixed deadlines. Requests are handled within defined response times.
  • Deadlines by law and volume. Some jurisdictions make the deadline depend on the complexity and number of requests and require data subjects to be told about delays. The applicable response times are set out in the organization’s privacy policy.

In practice

Involve all employees. Requests rarely arrive where they are handled. Short training sessions for reception, call centre, sales and the social media team explain how to recognize a privacy request and where to forward it at once.

Break the procedure into steps. Logging, identity check, clarifying the request, handling in the departments, reviewing the reply, sending and filing. Each step has a responsible role and an internal deadline, so that the statutory deadline does not become tight only at the end.

Announce delays early. If a complex or extensive request will clearly take longer, the person receives a message within the first deadline with the reasons and the new date. Templates for such messages are ready.

Justify fees and refusals. A fee or a refusal is only an option for manifestly unfounded or excessive requests. Record the reasoning in writing and tell the person about their right to complain to the supervisory authority.

Take complaints seriously. A complaint about how data is handled is a legitimate request too. It goes to the data protection officer, is examined and answered, and the outcome feeds into improving the procedures.

Typical audit evidence

For A.1.3.10, auditors typically expect:

  • Documented rules and procedures with response times, responsibilities and escalation (→ Document Control Register)
  • Request register with date of receipt, type of request, deadlines and reply date
  • Training records for employees in contact with customers (→ Training Register)
  • Templates for acknowledgement, identity queries, delay notices and refusals
  • Reasons for fees, refusals and extensions

KPI

% of data subject requests responded to within statutory deadline

The measurement starts from the moment the request reached the organization, even if it was logged in the register later. The target is 100%. An extended deadline only counts if the extension was communicated in time and with reasons.

Supporting KPIs:

  • Average handling time per type of request
  • Average time from receipt to logging in the register
  • Share of extensions communicated to the person in time

Article 12 GDPR governs deadlines and form. Under paragraph 3, the controller responds without undue delay and at the latest within one month of receipt. The deadline can be extended by two months where the complexity and number of requests make this necessary, and the person is told within the first month, with reasons. Paragraph 4 requires reasons and a note on complaint and judicial remedy if the controller does not act. Paragraph 5 makes handling free of charge in principle and allows a fee or refusal for manifestly unfounded or excessive requests, and paragraph 6 allows follow-up questions where identity is in doubt. The right to complain to the supervisory authority follows from Article 77, and the content of access from Article 15 (→ GDPR General Data Protection Regulation).

The request process carries all individual data subject rights:

Sources

Frequently asked questions

When does the deadline start?

As a rule, when the request reaches the organization, whatever the channel and whichever department receives it. That is why all employees need to know where to forward a request. A request that sits in the wrong mailbox for two weeks has only about two weeks left after that.

Does the person have to give reasons for the request?

No. Data subjects do not have to explain why they exercise their rights. In 2023, the Court of Justice confirmed that the first copy is free of charge even if the person pursues other aims with it, such as preparing litigation (C-307/22).

When may a request be refused?

Under Article 12(5) GDPR, for manifestly unfounded or excessive requests, in particular because of their repetitive character. The organization has to demonstrate this and tell the person the reasons and their right to complain. Statutory exceptions for individual rights come on top, in Germany for example in sections 32 to 37 of the Federal Data Protection Act.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.