GDPR: Can I make a subject access request for information that I obviously already know?
<p>The GDPR guidance states that subject access requests can only be refused if they are manifestly unfounded or excessive.</p>
<p>The detailed guidance on what constitutes manifestly unfounded or excessive can be found <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-law-enforcement-processing/individual-rights/manifestly-unfounded-and-excessive-requests" rel="nofollow noreferrer">here</a></p>
<p>In summary a manifestly unfounded or excessive request is:</p>
<ul>
<li><p>Malicious or intends to cause disruption</p>
</li>
<li><p>Repeats previous subject access requests</p>
</li>
<li><p>Overlaps with other subject access requests</p>
</li>
</ul>
<p>The guidance makes no mention about whether or not it would be excessive to request information clearly already known to the subject.</p>
<p>When I say information already known, I mean for example:</p>
<p>Asking a previous employer for information such as:</p>
<ul>
<li><p>My salary while I worked there</p>
</li>
<li><p>My start and leaving date</p>
</li>
<li><p>My job title</p>
</li>
</ul>
<p>This would be useful in a situation for example, where a person needs to prove their income for the last several months and the previous employer is refusing to provide an employers letter.</p>
<p>Of particular interest is the following paragraph:</p>
<blockquote>
<p>An individual may also want to receive another copy of information they have requested previously. In this situation a controller can charge a reasonable fee for the administrative costs of providing this information again and it is unlikely that this is an excessive request.</p>
</blockquote>
<p>This seems to imply that I can ask an organization for another copy of information that I already know. They can charge a fee, but not refuse to comply.</p>

<p>A data subject access request can be valid even if it wouldn't disclose new information. The right to access ties in with the GDPR's transparency principle (finding out which data is being processed) and with the right to rectification (are there any mistakes in the data being processed?). For rectification, it's pretty much ideal if you get back exactly the data you expect – but you're allowed to check with an access request.</p>
<p>The Art 12(5) limitations on excessive or manifestly unfounded requests do put a limit on the right to access, but this limit helps controllers respond to legitimate requests. For example, if a request is clearly intended to harass the controller with busywork, it can be denied as unfounded. Similarly, requesting access to the same data very frequently would be excessive. However, the controller has burden of proof to show that the request is excessive or unfounded – basically impossible for a one-time request for specific data. A request is not automatically excessive just because it is likely to only return data you already know. But ultimately, detailed guidance on the interpretation of “excessive” is up to the supervisory authorities – the GDPR itself provides no guidance.</p>
<p>Aside from the above exception, access can only be denied if it would adversely affect the rights and freedoms of others. For example, you could be denied access to non-anonymous performance reviews. There would be no such adverse effect for basic information about your employment.</p>
<p>If a data controller improperly considers your request as excessive or unfounded, you can lodge a complaint with your supervisory authority, e.g. the ICO in the UK. Most controllers are suddenly extremely helpful once contacted about an official complaint.</p>

gdpr