Guide
What to write in a subject access request
Updated
The law demands no particular words. A template matters because a badly scoped request invites clarification, which since 5 February 2026 costs you days off your own deadline.
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.
The four sentences that are doing the work
Identify yourself well enough to be found. Not just a name: whatever reference the organisation actually files you under, such as an employee number, an account number, or the email address you dealt with them from.
Say what it is. A line saying you are making a subject access request under Article 15 of the UK GDPR removes any argument about whether they understood what arrived.
Say what you want, as tightly as you honestly can. Everything is a lawful request. A named system, a date range and a subject matter is a request that gets answered faster and more completely.
Ask for it electronically. Article 15(3) provides that where the request is made by electronic means, "the information shall be provided in a commonly used electronic form" unless you request otherwise.
Two lines worth adding
Ask expressly for the Article 15(1) information as well as the data. That is confirmation that processing is happening, the purposes, the categories of personal data, the recipients or categories of recipient, and the envisaged retention period.
It also covers the source of the data where it did not come from you, and any automated decision-making. Responses most often leave this out, and it is frequently more useful than the data itself, because it tells you who else has your information.
Note the date and the method of sending. The relevant time under Article 12A(2)(a) is when the controller receives the request. A route with a delivery record settles the only deadline fact worth arguing over.
What not to put in
A reason. You do not have to give one, and giving one invites a discussion about whether it is a good reason, which is not a test the legislation applies.
A threat about the deadline before anything has gone wrong. It changes the tone of the reply and it buys nothing: the deadline exists whether or not you mention it.
A dispute. If the request is part of a grievance or a claim, keep the two separate. Mixing them makes it easier for the response to answer the argument instead of the request.
Where to send it
To the controller. The privacy notice for the service you used names it and gives a data protection contact route. Using it is the fastest way to reach somebody who knows what a subject access request is.
Where more than one organisation was involved, each is a separate controller needing its own request. One letter to the brand does not reach the payment processor or the delivery firm. Unsure who holds what? Ask first for the categories of recipients under Article 15.