Guide
Subject access request deadline: what Article 12A changed
Updated
Learned the SAR deadline as one month from sending, plus two for complex requests? That is the pre-2026 rule. Since 5 February 2026 new rules set its start and pauses.
Question 1
Whose personal data are you asking for?
The right of access belongs to the data subject. Who is asking changes what the organisation may reasonably want before it starts.
Email me this result
We will send you these figures and a link back to them. One email, nothing else unless you tick the box.
Where the rule now lives
Article 12(3) of the UK GDPR used to carry the time limit itself. It now says the controller shall provide information on action taken "without undue delay and in any event before the end of the applicable time period (see Article 12A)".
Article 12A was inserted by section 76(3) of the Data (Use and Access) Act 2025 and came into force on 5 February 2026. It is headed "Meaning of applicable time period", and it is where the whole of the timing question now sits.
When the month starts
Article 12A(1) sets the applicable time period as "the period of one month beginning with the relevant time".
Article 12A(2) makes the relevant time the latest of three things. When the controller receives the request; when it receives any identity information it asked for under Article 12(6); and when any fee charged under Article 12(5) is paid.
The practical effect is that a request sent without identification to an organisation that reasonably cannot place you does not start a month at all. It starts a correspondence, and the month begins when that correspondence resolves. Sending identification with the original request is the cheapest thing you can do to protect the deadline.
The stop-the-clock rule
Article 12A(5) is the genuinely new mechanic. It applies where a controller "reasonably requires further information in order to identify the information or processing activities to which a request under Article 15 relates".
It may ask, and the period from the day it asks to the day it receives your answer does not count towards the applicable time period.
Note what it does not say. It stops the clock; it does not restart it. Ten days spent before the question still counted, and the remaining twenty resume when you answer.
The power is tied to identifying what the request relates to. Article 12A(6) offers the intended example: a controller that processes a large amount of information concerning the data subject.
A question about why you want the data does not engage Article 12A(5) at all. Nor does an offer to give you less if you drop the rest. Neither asks for information to identify what the request relates to.
The extension, and the notice that has to come with it
Article 12A(3) allows two further months "where that is necessary by reason of the complexity of requests made by the data subject, or the number of such requests".
Article 12A(4) attaches two conditions that are easy to overlook and easy to check. Notice must come before the end of the one month beginning with the relevant time, and it must state the reasons for the delay.
An extension announced in month two is not an extension. A notice that says only that the request is complex has not stated reasons.