Guide
When a subject access request can be refused or cut down
Updated
Most apparent refusals are a controller applying an exemption to part of the material without saying which. Knowing the few routes helps you tell honest redaction from unexplained.
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.
Manifestly unfounded or excessive
Article 12(5) makes free of charge the default. Where requests are manifestly unfounded or excessive, in particular because repetitive, the controller may charge a reasonable fee for administrative costs, or refuse to act.
The next sentence is the one that matters: "the controller shall bear the burden of demonstrating the manifestly unfounded or excessive character of the request".
Demonstrating is a higher bar than asserting; saying a request is excessive without saying why has not met it. The threshold is manifestly, not merely: a large request is not automatically excessive.
Other people's data
Article 15(4) provides that "the right to obtain a copy referred to in paragraph 3 shall not adversely affect the rights and freedoms of others". That is where redaction of colleagues' names, other customers' details and third-party correspondence comes from.
It is a balancing provision, not a blanket one. It does not let a controller withhold a whole document because somebody else is mentioned. Nor does it cover routinely redacting people acting in a professional capacity.
Ask of a heavily redacted response which right or freedom of which other person each redaction protects.
Confidential references
Schedule 2 paragraph 24 of the Data Protection Act 2018 disapplies the listed GDPR provisions for references given, or to be given, in confidence. It covers the data subject's education, training or employment, volunteer placement, appointment to any office, or provision of any service. Prospective cases are covered in every limb.
The exemption travels with the reference rather than with the organisation, so requesting it from the recipient instead of the author does not get round it. What it does not cover is the material around the reference: the decision, the correspondence about the process, and the fact that a reference was sought are not the reference.
The exemptions in the Act
Schedules 2 to 4 of the Data Protection Act 2018 carry the rest, and they are specific. Crime and taxation, legal professional privilege, management forecasts, negotiations with the data subject, confidential references, and a long list of regulatory functions.
The important structural point is that they are exemptions from particular provisions for particular data, not permissions to ignore a request. A controller relying on one is still answering the request, still inside the deadline, and still obliged under Article 12(4) to tell you the reasons if it is not acting.