Blog

Subject Access Requests (SARs): How They Work Under UK GDPR

A Subject Access Request lets people ask for a copy of their personal data and related information. The DUAA makes clear that organisations must make a reasonable and proportionate search for information in scope, while still searching for other relevant information if a particular search would be disproportionate. It sits within the wider framework of UK GDPR rights and connects closely to transparency, accountability, and day-to-day data handling.

Estimated reading time: 6 minutesTopic: Individual rightsRelated term: SAR
Quick answer

What A Subject Access Request Means In Practice

A Subject Access Request, usually shortened to SAR, is a request from an individual asking for access to their personal data. Under Article 15 of the UK GDPR, they can ask whether their data is being processed, receive a copy of it, and obtain supplementary information about how it is used. Organisations must make a reasonable and proportionate search for the information. The Data (Use and Access) Act 2025 made this search standard explicit. SARs connect closely to personal data, transparency, accountability, and controller responsibilities.

Main focus

Access to personal data, response handling, and organisational readiness.

Works with

UK GDPR rights, transparency duties, accountability, and internal records.

Usually relevant when

A person asks what data you hold about them or requests a copy of it.

Section one

What A SAR Covers

The right of access under UK GDPR is about more than sending over a spreadsheet or forwarding a few documents. A SAR is about whether an organisation can identify the requester’s personal data, explain how it is used, and respond in a structured and legally sound way. In practice, this often overlaps with transparency and accountability.

Area one

Access to personal data

The person can ask whether you process their personal data and, if you do, receive a copy of it. The search must be reasonable and proportionate to the request; this is not a duty to search every possible source regardless of relevance or burden.

Area two

Supporting information

The response must also include supplementary information, such as the purposes of processing, categories of data, recipients, retention period or criteria, and the person’s relevant rights.

Area three

Operational control

A SAR tests whether your organisation actually knows where data sits across inboxes, systems, files, and platforms, and whether it can retrieve it safely.

In most organisations, the practical issue is not whether SARs exist, but whether teams can recognise them quickly and handle them consistently.

Section two

When A SAR Applies

A SAR does not need special wording, a particular form, or legal terminology. It can be made verbally or in writing, and the person does not need to use the phrase “subject access request”. It is enough that they clearly ask for their personal information. Organisations should make sure staff can recognise and promptly escalate requests received through ordinary channels.

Email and messages

SARs are often made by email or message because those are fast, informal routes. A casual message can still be a valid request if the person is asking for their personal data.

Verbal requests

A request made verbally can still count. Teams need enough awareness and internal process to recognise this and escalate it properly.

Identity checks

If you have reasonable doubts about identity, you may ask for information needed to confirm it. Ask only for what is necessary; the response period starts when you receive the information needed to confirm identity. Do not request ID automatically when the person’s identity is already clear.

Search scope

A SAR gives access to the requester’s personal data, not automatically every complete document. However, you may need to provide a document or enough surrounding context where that is necessary to make the personal data intelligible. Identify the likely relevant sources and make a reasonable and proportionate search; do not treat the search standard as permission to exclude relevant data without considering it.

Section three

Time Limits And What Organisations Must Provide

You must respond without undue delay and within one month, subject to the rules on when the response period starts and any permitted extension. If the request is complex, or the person has made a number of requests, you may extend the period by up to two further months where necessary. The response is not just a data dump: provide the personal data and supplementary information in a clear, accessible form.

Response timing

One month is the starting point

The usual deadline is one month. Where necessary, a complex request or a number of requests from the same person can justify an extension of up to two further months. Tell the person within the first month and explain why. If you reasonably need clarification, the response period pauses until the person replies.

What should be included

More than just raw documents

Provide the personal data and the Article 15 supplementary information, including purposes, categories, recipients, retention period or criteria, and relevant rights. Present it clearly and accessibly, with context where needed to make the information understandable.

The practical way to think about it

A useful way to approach SARs is as an organisational workflow rather than a one-off legal event. If your systems, ownership, and record keeping are unclear, SAR handling becomes much harder. This is why the topic connects strongly to accountability and to current regulatory developments around complaints handling, including ICO complaint handling expectations and the ICO’s new complaints process requirement.

Section four

When Organisations Can Refuse Or Limit A Request

You must usually respond to a SAR free of charge. You may charge a reasonable fee for administrative costs, or refuse to act, if the request is manifestly unfounded or excessive. A reasonable fee may also be charged for further copies of information already provided. These are limited exceptions: assess the facts and be ready to explain and document the decision. A search that would be unreasonable or disproportionate does not, by itself, mean the whole SAR can be refused; continue with reasonable searches for the remaining in-scope data.

Limited exceptions

Not every request is identical

The right of access is subject to specific exceptions. Separately, the search duty is limited to searches that are reasonable and proportionate. Consider the request, the likely location of the data, the value of finding it, and the effort involved; keep searching other relevant sources if one particular search would be disproportionate.

Documented decisions

Weak reasoning creates risk

If clarification is reasonably needed, ask the person promptly and explain what would help. You cannot require them to narrow the request; if they do not, continue with reasonable and proportionate searches. If relying on an exception, charging a fee, or deciding that a particular search is disproportionate, record the reasons and explain the decision clearly.

The practical takeaway

A refusal or limitation should feel like a carefully documented compliance decision, not an annoyed reaction. If teams are relying on vague instinct rather than evidence and process, that is usually a sign the SAR workflow needs strengthening.

Section five

Common SAR Handling Mistakes

SAR failures often happen because organisations underestimate the operational work, fail to make a reasonable and proportionate search, delay internal escalation, or disclose information without proper review. The search standard gives organisations room to apply judgement, but that judgement should be reasoned, documented, and based on the circumstances of the request.

Missing the request entirely

Teams sometimes fail to recognise a valid SAR because the person does not use legal language or because the request arrives through an informal channel.

Searching too narrowly

Searching just one inbox or system may miss relevant personal data. Identify likely sources based on the request and the organisation’s systems, then make and document reasonable and proportionate searches. You do not have to search every source automatically, but should be able to explain why the searches you chose were appropriate. If one search would be disproportionate, continue searching other relevant sources.

Delaying internal escalation

A SAR can lose days very quickly if nobody knows who owns it, who should coordinate it, or how the response process works.

Reviewing disclosure too casually

Responses need care, especially where third party data appears. Rushed disclosure can create new compliance problems rather than solving the original request.

Why these mistakes matter

SAR handling is often one of the clearest practical tests of whether an organisation understands its own data environment. If systems, roles, and records are messy, a SAR tends to expose that quickly. For wider context on related regulatory change, see DUAA data protection changes and ICO guidance updates.

Grounded in

What this article is grounded in

This article is based on ICO guidance on subject access requests and the right of access under UK GDPR, together with the core legal provisions that explain what organisations must provide, how request handling should work in practice, and when limits or refusals may apply. For related regulatory developments affecting complaints handling and organisational readiness, see our updates on ICO complaint handling expectations and the ICO’s new complaints process requirement.

Related concepts

Explore connected topics

Next step

Keep building your understanding

Use the glossary for key terms, or browse the Learn section if you want a practical next step for building your understanding of UK GDPR rights and compliance.

Future Implementation Support Waitlist