Subject Access Requests in the UK: Template, Timelines and What to Do When an Organisation Refuses
subject access requestsSAR templateUK GDPRICO complaintsdata protection

Subject Access Requests in the UK: Template, Timelines and What to Do When an Organisation Refuses

CComplains.uk Editorial Team
2026-11-13
8 min read

Use this UK SAR template to request personal data, track the one-month deadline and respond when an organisation refuses or sends an incomplete reply.

A subject access request (SAR) lets you ask an organisation for a copy of the personal data it holds about you, together with information about how that data is used. This guide explains what you can request, the usual UK GDPR timetable, how to track a response, and what to do if a company refuses, redacts too much or misses the deadline. It includes an adaptable subject access request template and a practical escalation checklist.

Overview

You can make a SAR to an organisation that processes your personal data. The request can cover information such as account records, correspondence, call recordings, complaint notes, personnel records, transaction histories, photographs, online identifiers and data obtained from other sources. You can also ask for supporting information, including the purposes of processing, categories of personal data, likely retention periods and details of recipients, where applicable.

You do not usually need to use the words “subject access request”. A clear request for your personal data should be recognisable as a SAR. It can normally be made in writing or verbally, although writing is safer because it creates a record. Send it to the organisation’s privacy, data protection or customer service contact, and keep evidence of when and how it was delivered.

The right is not unlimited. An organisation may withhold or restrict some information where a legal exemption applies. Common issues include another person’s personal data, legally privileged material, confidential references and information connected with crime prevention or legal proceedings. A restriction should not be used as a general reason to withhold everything: the organisation should explain the outcome sufficiently for you to understand what has been provided and why anything has been removed, subject to the relevant exemption.

A SAR is different from a general complaint. If you are also disputing a refund, service failure or contract, keep those issues separate and use the appropriate complaint or pre-action route. For wider complaint strategy, see our guide to GDPR complaints, SARs and ICO escalation.

What to track

1. The request and delivery date

Record the exact wording of your SAR, the organisation or department addressed, the email address or postal address used, and the date it was sent. Save delivery receipts, screenshots, automated acknowledgements and any reference number. If you submit the request through an online account, download or photograph the confirmation page.

You can ask for all personal data, but a focused request is often easier to process and assess. For example, you might specify a date range, a particular account, a complaint reference, customer-service calls or correspondence about a named issue. Avoid limiting the request accidentally: explain whether you want the full scope of your personal data or only certain categories.

2. Identity checks and clarification

An organisation may ask for information reasonably needed to confirm your identity, particularly where the request involves sensitive data. Provide only what is reasonably necessary and use a secure method where possible. Track the date you supplied the requested information. If the organisation asks you to clarify an unusually broad or unclear request, reply promptly and state whether you are narrowing the request or confirming that you want the full search.

CheckpointWhat to recordWhat it usually means
Request sentDate, channel and wordingThis starts your evidence trail. The response period generally runs from receipt, subject to identity or clarification issues.
AcknowledgementReference number and named contactAn acknowledgement is useful, but the key requirement is the substantive response within the applicable period.
Identity or clarification requestQuestion asked and your reply dateDeal with it promptly. The timetable may depend on when the organisation has the information reasonably needed to process the request.
Usual response pointOne calendar month from the relevant starting pointThe organisation should provide the data and information required by the UK GDPR, or explain a lawful reason for restriction.
Possible extensionNotice and reason for delayFor a complex or numerous request, the organisation may need up to two further months, but it should tell you within the first month and explain why.

There is not normally a separate fixed deadline for acknowledgement. Focus on the date by which a proper response is due. If the organisation requests clarification, keep a copy of both sides of the exchange and ask it to identify precisely what part of the request is unclear.

4. What you actually received

Check whether the response includes the data itself, not merely a privacy notice or a list of general categories. Record missing formats, unexplained redactions, references to documents that were not supplied, and any apparent gaps in dates or systems searched. A response may be delivered in several files or through a secure portal, so save each file and note when access expires.

Cadence and checkpoints

Use a simple SAR log. A spreadsheet or note should contain: request date, delivery evidence, identity-check date, clarification date, stated response deadline, extension notice, response date, documents received, issues found and next action. Review the log at these points:

  • At submission: confirm the request is addressed to the correct organisation and clearly describes the data sought.
  • After acknowledgement: check whether the organisation has asked for identity evidence or clarification, and answer without unnecessary delay.
  • Near the one-month point: check whether a complete response or a valid extension explanation has arrived.
  • After disclosure: compare the material with your request and identify specific omissions rather than making a general accusation.
  • After a follow-up: give the organisation a clear list of unresolved points and retain its response.

Do not send repeated identical requests simply because the first email was not acknowledged. That can create confusion about which request is being processed. Instead, send a dated follow-up referring to the original request and attach proof of delivery if needed.

Subject access request template UK

Adapt the following wording to your circumstances:

Subject: Subject access request – [full name and account/reference number]

I am making a subject access request under the UK GDPR and Data Protection Act 2018. Please provide a copy of the personal data you hold about me and the supplementary information required by data protection law.

Please search the following systems and records: [for example, customer account, complaint file, emails, call recordings and online messages]. The relevant period is [date] to [date]. If you need clarification about the scope, please contact me promptly and identify exactly what is unclear.

My identifying details are: [full name, address, email, account or reference number]. Please tell me if you reasonably require further information to verify my identity. I would prefer the response in [electronic] format.

Please confirm receipt and provide the response within the applicable UK GDPR timeframe. If you consider an extension or exemption applies, explain the reason and identify the information affected.

Yours faithfully,
[name]
[date]

Do not include unnecessary sensitive information in an ordinary email. If identity documents are requested, ask how they should be sent securely and whether less intrusive evidence would be accepted.

How to interpret changes

A delay does not automatically mean the organisation has acted unlawfully. The request may genuinely be complex, involve multiple systems or require careful review of other people’s information. However, an extension should be communicated within the initial response period and should not be used as an unexplained indefinite delay.

If the response is incomplete, write back with a short numbered list. For example: “The response refers to two recorded calls, but only one file was supplied”; “Please explain whether the complaint mailbox was searched”; or “Please identify the exemption relied on for the redacted section.” Specific questions make it easier to resolve a processing error and create a useful record if you later complain.

If the organisation refuses the request, ask it to state the legal basis for the refusal, whether the restriction applies to all or only part of the data, and how you can complain. Some information may properly be withheld, but a blanket refusal should be examined carefully. If the material contains another person’s data, the organisation may need to balance that person’s privacy with your access rights rather than automatically withholding the entire document.

If your follow-up does not resolve the issue, you can complain to the Information Commissioner’s Office (ICO), which supervises data protection in the UK. Include the original SAR, proof of delivery, identity or clarification correspondence, the response, your follow-up and a concise explanation of what remains wrong. Check the ICO’s current complaint instructions and any stated time limits before submitting. The ICO may assess compliance but does not usually act as a substitute for a court deciding compensation or unrelated contractual disputes.

When to revisit

Revisit this article whenever you make a SAR, receive a partial disclosure or are deciding whether an ICO complaint is appropriate. At the start of each request, check the current ICO guidance on response periods, identity verification, exemptions and complaint routes because regulatory guidance and legislation can change.

For recurring data issues, review your SAR log monthly until the matter is closed. For organisations that process your information regularly, a quarterly review can help you notice changes in privacy contacts, account systems, retention information or the type of records being disclosed. Keep the article’s template as a starting point, but tailor the scope and dates to each request.

Next step: save your evidence, send a focused SAR, mark the likely one-month checkpoint in your calendar, and follow up with numbered questions if the disclosure is late or incomplete. If the dispute also involves money or a contract, preserve that evidence separately and consider the appropriate complaint or civil route rather than relying on a SAR alone.

Related Topics

#subject access requests#SAR template#UK GDPR#ICO complaints#data protection
C

Complains.uk Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.