Any organisation holding personal data may at some point receive a Data Subject Access Request (DSAR). Whether it comes from a current employee, a former customer, or someone involved in a dispute with your organisation, the legal obligation to respond is the same: clear, complete, and generally within one month.
Yet DSARs in the UK are among the most common data protection issues organisations face, 39% of the complaints received by the ICO in 2022-23 relating to Article 15 UK GDPR. The consequences for organisations range from formal reprimands and enforcement action to reputational damage and litigation. For any organisation that holds personal data, understanding how to handle a Data Subject Access Request correctly is a legal requirement.
This article explains what a DSAR is, what obligations are under Article 15 of the UK General Data Protection Regulations (UK GDPR), how recent changes under the Data (Use and Access) Act 2025 (DUAA) affect those rules, and what practical steps your organisation can take to handle SARs confidently.
What is a Data Subject Access Request?
The right of access is in Article 15 UK GDPR and represents one of the most fundamental rights in UK data protection law. Indeed, it allows any individual the right to obtain a copy of their personal data and to understand how it is being used. Specifically, a data subject is entitled to:
- Confirmation that their personal data is processed;
- A copy of their personal data; and
- Other supplementary information.
Where confirmation that their personal data is being processed is obtained, individuals have the right to receive the following, as further detailed by Recital 63 UK GDPR:
- The purposes of processing;
- The categories of data processed;
- The specific recipients or categories of recipients to whom the data has been or will be disclosed;
- The envisaged retention period, or the criteria used to determine it;
- Information about the individual’s rights to rectification, erasure, restriction, and objection;
- The right to lodge a complaint with the ICO;
- Where data was not collected directly from the data subject, any available information about the source;
- Whether any automated decision-making (including profiling) is being applied, and meaningful information about the logic involved; and
- Appropriate measures in place if the information has or will be subject to international data transfers.
Importantly for organisations, data subjects are only entitled to access their own information, except where:
- their personal data relates to other individuals who have consented to disclosure or where it is reasonable to disclose the information without the other individual’s consent; or
- when exercising one’s right on their behalf, so long as the third party is entitled to act on the person’s behalf.
Article 15(4) states that the right to obtain a copy of your personal data should not adversely affect the rights or freedoms of others. For this reason, organisations must identify whether personal data is held and whom it relates to. Where possible, it is encouraged to comply with the request without revealing another person’s information, such as by deleting their names or redacting identifiable information which are not part of the request. That said, the decision in Harrison confirmed that Article 15(1)(c) UK GDPR requires organisations, as a default, to disclose the specific identities of recipients to whom personal data has been or will be disclosed. Defaulting to categories is only permissible where it is genuinely impossible to name specific recipients, or where an exemption applies, which is discussed below.
Who can make a DSAR and how?
Any data subject whose personal data is processed may exercise their right of access. There is no formal requirements nor obligation to provide a reason for the request to be valid. A valid Data Subject Access Request can be made verbally, in writing, by email, through social media, or via a third party acting with the data subject’s authority; it does not even have to mention that it is a subject access request regarding the right of access under Article 15 UK GDPR. Individuals may also use platforms such as Zolteria to make and manage their data rights requests including DSARs. Through Zolteria, a person can search for the organisation they wish to contact, select the relevant data right, and submit their request through the platform. The platform also allows individuals to track their DSAR from submission through to completion, giving them visibility over the progress of their right of access request and a record of its status throughout the process. It is generally expected that the organisation processing the personal data responds to a DSAR in the same way the request was made, or in the way requested by the individual.

The ICO notes that organisations may have a designated DSAR inbox or a formal online form to make it easier for them to recognise such requests and locate relevant information. However, those mechanisms are not compulsory for data subjects as individuals can request access to their information via any means. This format informality can be a source of operational risk as any employee may receive a valid DSAR and should be able to identify and handle it correctly; meaning that organisations should train all staff accordingly.
In terms of responsibility, controllers, meaning the entity determining the purposes and means of the processing, are accountable for complying with DSARs. Processors, being entities processing personal data on behalf of controllers, have a legal obligation to help controllers comply with DSAR obligations under Article 28(3)(e) UK GDPR, which is often further detailed in the Data Processing Agreement with the controller.
The compliance timeline
Under Article 12A UK GDPR, the default response period is one calendar month from receipt of the request and without undue delay. The ICO highlights that the calendar month runs from the day of receipt, regardless of whether it is received on a weekend or bank holiday, to the corresponding day of the following month. That said, if the end date lands on a weekend or public holiday, the calendar month ends on the following working day. Furthermore, where a request is complex or the organisation has received a number of requests from the same individual, the response period may be extended by a further two months, bringing the maximum response time to three months in total. Critically, the organisation must notify the individual within the first month of the extension and the reasons for it.
A significant change introduced by DUAA is the ability for organisations to pause the one month deadline where further information from the data subject is needed to respond effectively. The clock pauses on the day clarification is sought and resumes when the response is received. This change significantly improves the position of organisations dealing with broad or ambiguous requests, but it must not be used as a mechanism to delay responses where the request is clear.
Conducting the search
Section 78 DUAA provides that controllers only need to conduct reasonable and proportionate searches to the nature, volume, relevance, and context of the data requested. Ittihadieh further confirms that data controllers are not required to go so far to leave “no stone unturned”. Nonetheless, the scope of a DSAR search is broad: organisations must search across all systems and formats in which personal data about the requester may be held. Identifying which systems are most likely to contain personal data relevant to the request allows organisations to start the search and prioritise sources where the data subject had frequent interactions, which could include HR and payroll systems, email archives, collaboration tools such as Teams, Slack, or SharePoint or paper records among others.
The breadth of this obligation justifies why an up-to-date Record of Processing Activities (ROPA) is an operational necessity, as it constitutes an internal inventory of what personal data the organisation collects, stores and handles. Organisations that cannot identify where personal data is held are likely unable to respond to SARs completely or accurately.
Now while data subjects cannot be required to pay a fee to exercise their right of access, organisations may charge a reasonable fee for the administrative costs of complying with the request, specifically where the initial request is manifestly unfounded or excessive.
Manifestly unfounded and excessive requests
Under Article 12(5) UK GDPR, where a request is manifestly unfounded or excessive, an organisation may either charge a reasonable fee or refuse to respond altogether, either wholly or partly.
“Manifestly unfounded” requests arise where there is clear evidence that the individual is not genuinely seeking to exercise their right to object, but is instead acting with malicious intent or attempting to disrupt the organisation. However, the Court of Appeal in Ittihadieh considered that even where there is an alternative motive in making the request such as litigation, it is generally not enough to invalidate the DSAR or to consider a request manifestly unfounded.
A request may be “excessive” where it repeats the subject matter of previous requests or significantly overlaps with them. Nonetheless, repetition alone does not automatically make a request excessive. Organisations must therefore assess proportionality and context carefully rather than assuming that repeated or overlapping requests are inherently excessive.
In such cases, the controller may refuse to comply with a request or charge a fee, provided they can demonstrate the manifestly unfounded or excessive character of the request, inform the data subject of the reasons for non-compliance or fee without undue delay and within one month of receipt, alongside their right to complain to the ICO or seek judicial remedy.
Exemptions
The right of access is not absolute. Schedule 2 of the Data Protection Act 2018 contains a list of specific exemptions which may apply once the search has been conducted and when the controller decides what information to withhold which may allow to refuse compliance with the request wholly or partly. The most commonly applicable exemptions in a commercial context include:
- The rights of others exemption arises frequently in practice: where disclosing personal data about the requester would necessarily reveal personal data about a third party who has not consented, the organisation must balance the requester’s right of access against the third party’s reasonable expectation of privacy. Usually, the requester’s data may be provided where third-party information is entirely redacted.
- Legal professional privilege protects confidential communications between an organisation and its legal advisers made for the purpose of obtaining legal advice.
- The self-incrimination exemption establishes that controllers may refuse to provide data if it would require them to disclose information that would incriminate themselves in a criminal offence
- Management information exemptions may apply where disclosure would prejudice the carrying out of negotiations, management forecasting, or the planning of future business activities. This requires case-by-case analysis and cannot be applied as a blanket exemption to commercially sensitive material.
- Crime and taxation exemptions apply where disclosure would be likely to prejudice the prevention or detection of crime, the apprehension or prosecution of offenders, or the assessment or collection of tax.
How to respond to the Data Subject Access Request?
When the organisation has assessed the request, conducted the search and identified potential exemptions where relevant, a response must be issued to the requester. The response must be in the same format as the original request, and may contain:
- a summary of the request;
- the decision and whether the request has been granted or refused;
- reasons for any redactions, exemptions or reasons for refusing to grant a request where relevant;
- a copy of the data if no exemptions apply;
- any additional information required to comply with a request; and
- information on how to submit a complaint if they are unhappy with the response, including information about how they can submit a complaint to the ICO.
Managing DSARs using Zolteria®
Organisations can use digital platforms such as Zolteria to centralise and manage DSARs throughout the request lifecycle. Once a request has been received, the organisation can review the request, check the relevant details, add internal notes, record actions taken and, where necessary, communicate with the individual about the request.
Zolteria also provides pre-verified identities, helping organisations reduce the manual work involved in identity verification. Requests can be tracked by status, request type, due date and other relevant information, giving organisations a clear overview of outstanding DSARs and their progress through to completion.
Enforcement and the consequences of non-compliance
The ICO has consistently reviewed DSAR compliance in its enforcement activity in recent years. For instance, it issued a formal reprimand to an NHS Trust in December 2024 after finding that 32% of DSARs had not been responded to within the one-month statutory deadline. The underlying failures were systemic: inadequate logging processes, inefficient management system, and inadequate quantitative data. This case is instructive as it demonstrates the structural weaknesses the ICO may look for across sectors.
Beyond formal reprimands, the ICO has the power to issue enforcement notices requiring organisations to take specific remedial action and to impose monetary penalties, which we cover in our article on GDPR fines. For SAR non-compliance, fines of up to £17.5 million or 4% of annual global turnover (whichever is higher) can apply under the UK GDPR. Separately, individuals retain the right to bring claims for failure to comply with a SAR, and may be entitled to compensation for both material and non-material damage under Article 82 UK GDPR.
Conclusion
DSARs are common and organisations should implement processes to tackle them efficiently. When assessing a Data Subject Access Request, the controller should focus on establishing a reasonable and proportionate search scope. A proportionality-based approach, considering systems searched, burden, costs, likelihood of relevant data, and the individual’s cooperation will help organisations justify decisions if challenged.
Exemptions may apply once the search is conducted and the controller assesses what information to disclose; but this must be assessed on a case-by-case basis. Finally, controllers have the ability to refuse to comply wholly or partly with requests that are manifestly unfounded or excessive, although a data subject’s motivation does not automatically invalidate a request. Ultimately, the above should be communicated to the data subject in a formal letter within the statutory timelines, otherwise organisations may face enforcement actions from the ICO.
Further support
Managing DSARs effectively requires both a sound understanding of the applicable requirements and a process that works in practice. At IGS, we support organisations in developing practical and effective information governance processes.
If you would like support reviewing your DSAR procedures, identifying potential information governance risks, or providing training for your team, please contact us at info@informationgovernanceservices.com or 0208 106 7936.
Alternatively, if you would like to make a Data Subject Access Request or are looking to centralise your organisation’s DSAR management, you can contact Zolteria team here.
SOURCES
UK GDPR
DUAA 2025
DPA 2018
Ittihadieh v. 5 to11 Cheyne Gardens RTM Company Limited and Others [2017] EWCA Civ 121
Harrison v Cameron and ACL [2024] EWHC 1377
ICO, A guide to subject access
ICO, What is the right of access?
ICO, When can an exemption apply to information about other people in a SAR?
ICO, How do we recognise a subject access request (SAR)?
ICO, Manifestly unfounded and excessive requests
ICO, Information Commissioner’s Annual Report and Financial Statements 2022/23, p.58
Irish Data Protection Commission, The Right of Access
Data Protection Network, Data Subject Access Requests – what are people entitled to?



