What is a subject access request?

Key takeaways

  • A subject access request gives you confirmation that an organization processes your data, a copy of it, and details such as purposes, recipients, and retention.
  • Under the UK framework you can ask verbally or in writing, with no special form, and organizations cannot force you to narrow the request.
  • Organizations must normally respond within one calendar month and can extend by up to two further months for complex requests, with most requests handled free.
  • Handle requests by logging, verifying proportionately, defining the search, reviewing exemptions and third party data, and recording each decision before responding securely.

A subject access request (SAR), also called a data subject access request (DSAR), lets someone ask an organization for their personal information and details about how it is used. It provides visibility into data handling, not just a download of account details. This article explains the UK framework, offers a reusable request template, and outlines a practical process for organizations handling requests. (ico.org.uk)

What does a subject access request cover?

A subject access request covers confirmation that an organization processes your personal data, a copy of that data, and supporting information about its use. Under the UK framework, that supporting information includes processing purposes, recipients or recipient categories, retention periods or criteria, and relevant privacy rights. The aim is to help you understand how your information is handled and check whether that handling is lawful. (cy.ico.org.uk)

For example, a request could seek personal information within customer service correspondence, employment records, or account activity. However, access is a right to your personal information, not an automatic entitlement to every complete document containing your name. Whether copies of documents must be provided depends on their contents. (ico.org.uk)

A data access request should therefore describe the information sought rather than assume that an entire file must be released unchanged. For a customer service issue, you might identify the account, relevant dates, and conversations you want reviewed.

The applicable law matters

This article focuses on ordinary requests under the UK GDPR framework. UK regulators describe this right as subject access, while California’s CCPA provides a right to know for eligible consumers dealing with covered businesses. California generally uses a 45-calendar-day response period, so UK deadlines should not be applied universally. Check the law governing the request before setting expectations. (ico.org.uk)

How do you make a subject access request?

Under the UK framework, you can make a subject access request verbally or in writing, including through social media. You do not need to quote legislation, use legal terminology, or complete a particular subject access request form. What matters is making clear that you want access to your own personal information. (ico.org.uk)

For a useful written record, consider sending an email or using the organization’s privacy request channel. Keep a copy of your submission and note when you sent it. Structure your request around these details:

  • Who you are: Include your name and an existing account or reference number where helpful.
  • What you want: Describe the records, interactions, or personal information you are seeking.
  • Relevant dates: Add a date range if it reflects what you need.
  • How to contact you: Specify a suitable reply address and preferred response format.

Avoid sending identity documents automatically. An organization should seek additional identification only where needed and should make proportionate checks rather than collect unnecessary information. (ico.org.uk)

A subject access request template

Adapt this subject access request template to your circumstances. Replace the brackets with useful details, and remove any optional limits that do not reflect your request.

Subject: Subject access request

Dear Privacy Team,

I am requesting access to the personal information your organization holds about me, together with the supporting information required under the applicable right of access.

My name is [full name]. My account or reference number is [reference, if applicable].

I am particularly seeking [describe the personal information, interactions, or records]. The relevant period is [date range, if applicable].

Please provide your response electronically to [email address]. If you reasonably need further information to confirm my identity or understand this request, please let me know promptly.

Kind regards, [Name]

A focused request can help explain your priorities, but do not narrow it simply because you think broad requests are invalid. UK guidance says organizations cannot force someone to reduce the scope of a request. (ico.org.uk)

How long does an organization have to respond?

Under the UK framework, an organization must respond without undue delay and normally within one calendar month. Where necessary, it can extend the period by up to two further months because of complexity or multiple requests from the same person. It must notify the requester and explain the extension within the initial month. (ico.org.uk)

Necessary identity verification can affect when the response period starts. UK rules also allow the clock to pause for reasonably required clarification; this is not permission to delay every broad request. Organizations should record the reason for clarification and calculate the revised deadline carefully. (ico.org.uk)

Most requests are free. Limited circumstances may justify a reasonable fee, including certain manifestly unfounded or excessive requests and requests for additional copies. A routine processing charge should not be treated as the default. (ico.org.uk)

Handling requests from intake to secure delivery

For organizations, use the following workflow as a practical checklist, adapting it to the applicable law. Give each request a named owner and maintain a record of decisions, searches, and communications. The ICO’s preparation guidance emphasizes staff training, suitable information management systems, and secure delivery. (ico.org.uk)

  1. Log and assign. Capture the original wording, receipt date, submission channel, responsible owner, and applicable deadline.
  2. Verify proportionately. Check identity or a representative’s authority where necessary, using information already available when sufficient.
  3. Define the search. Identify likely systems, record holders, date ranges, and search terms. Record any reasonably required clarification.
  4. Collect and document. Conduct reasonable, proportionate searches and note what was checked, including relevant locations beyond the main customer database.
  5. Review before disclosure. Assess third-party information and applicable exemptions. Record why information is withheld or redacted.
  6. Respond securely. Supply accessible information and the required explanation, then retain an appropriate record of the response. (ico.org.uk)

For an internal checklist, make each step observable: “review completed by named reviewer” is more useful than “almost finished.” Treat a status label as a prompt for evidence, not a substitute for it.

Limits, redactions, and incomplete responses

Subject access is not unlimited. An organization may need to protect another person’s information or apply an exemption, such as legal professional privilege. Exemptions require case-specific assessment, and the organization must be able to justify relying on them. (ico.org.uk)

A large request is not automatically excessive, and an organization should not use a blanket refusal policy. Current ICO guidance requires strong, evidence-based justification for treating a request as manifestly unfounded or excessive. Consider the circumstances rather than relying only on the volume of material requested. (ico.org.uk)

If your response appears incomplete, write back with specific gaps: for example, identify a missing period or interaction. Ask the organization to explain its handling and any refusal. UK guidance requires refusal notices to explain the reasons and relevant complaint and court routes, including the right to complain to the ICO. (ico.org.uk)

Choosing tools that support the process

When evaluating data subject access request management software, start with a sample workflow rather than a feature list. Ask a vendor to demonstrate a request moving from intake to delivery, including a clarification, a reassignment, and a redaction review. Use that exercise to test whether the proposed tool fits your process.

For a data subject access request (DSAR) workflow management system, consider these fields and status controls:

Field or control What to test
Receipt date and jurisdiction Can the team identify the applicable deadline?
Owner and assigned tasks Is responsibility clear at every stage?
Verification status Can staff see whether a necessary check remains outstanding?
Scope and search record Are searches and clarification decisions documented?
Review and approval status Can reviewers distinguish collected data from approved disclosure?
Delivery and closure record Is there evidence of what was sent and when?

Evaluate data subject access request software for controlled access, usable exports, and a review history your team can follow. Do not assume automation makes a legal assessment correct. Keep a named reviewer responsible for disclosure decisions and deadline exceptions.

The practical takeaway

For requesters, describe the information you need and keep a clear submission record. For organizations, establish ownership, document the search, review disclosure carefully, and deliver the response securely. Use the template or workflow above as a starting point, then adapt it to the request and governing law.

Sources

  1. ico.org.uk: What is the right of access
  2. cy.ico.org.uk: Right of access 1 0 20240919
  3. ico.org.uk: When can we consider a sar to be manifestly unfounded or excessive
  4. ico.org.uk: A guide to subject access
  5. ico.org.uk: Ic 454988 l5z0 disclosure
  6. ico.org.uk: What should we consider when responding to a request
  7. ico.org.uk: A guide to subject access