AI-generated subject access request

Monday morning. The data protection inbox receives an email from a customer angry about an invoice: nine pages, a law-firm tone, a reference to a Californian statute, a court ruling nobody can find, and a demand for “all my data, including metadata, backups, call recordings and CCTV logs” within ten days. Everything suggests it was written by AI. The temptation is to reply that this is not a serious request. That would be a mistake.

The short answer: a subject access request written with AI is as valid as any other. The deadline is one month, and a long or confusing request is not enough to extend it. You must check the address you reply to, decide and document a reasonable search scope and, whenever possible, talk to the requester. That is what the UK data protection authority (ICO) has just reminded organisations in guidance published on 11 November 2026, and almost all of it applies in Spain because Articles 12 and 15 of the GDPR use the same wording.

Got a difficult access request on your desk? We analyse it, define the scope and prepare the response on time. Tell us about your case →

SAR, DSAR and the right of access: what we mean

In English, these are called SARs (subject access requests) or DSARs (data subject access requests). In Spanish, it is the solicitud de derecho de acceso: the right of any person to know whether an organisation processes their personal data, obtain a copy, and learn what it is used for, who receives it and how long it is kept (Article 15 GDPR). Same right, different name.

What the ICO has published on AI-generated subject access requests

The Information Commissioner’s Office (ICO), the UK supervisory authority, has published Subject access requests generated by artificial intelligence. It addresses a problem every DPO now sees daily: endless, repetitive access requests that mix several rights, cite foreign laws and quote decisions that do not exist. The ICO calls them, plainly, “hallucinations”.

Westminster and Big Ben, London
Logo de la ICO

Official source · United Kingdom
Subject access requests generated by artificial intelligence
Information Commissioner’s Office (ICO) · 11 November 2026

Read the full guidance →

ICO logo reproduced only to identify the source. The ICO has not reviewed or endorsed this article.

One important point: the ICO applies the UK GDPR, not the EU GDPR, and its guidance does not bind the Spanish Data Protection Agency (AEPD). But the right of access is worded the same way on both sides of the Channel, so its criteria are a useful reference. At the time of writing we have not found equivalent AEPD guidance on AI-generated requests. Spain also has its own rules, which we explain below.

Eight key points from the guidance, applied in Spain

IssueWhat the ICO saysHow we apply it in Spain
ValidityA request is not invalid because AI wrote itSame: it is enough that the person clearly wants their data
Errors and invented lawThey do not invalidate the requestSame. You can politely explain what the law does and does not require
DeadlineOne month; using AI does not make a request complexOne month, extendable by two further months for complexity or number of requests, notifying within the first month (Art. 12(3) GDPR)
Reply addressCheck it against your records or with the requesterSame: sending data to the wrong address is the controller’s breach
ClarificationYou may ask, but cannot force a narrower requestYou may ask the requester to specify where you hold a large volume of data (Recital 63 GDPR); if they insist on “everything”, you must provide it
Search scopeThe controller decides: a reasonable and proportionate searchSame, documenting the criteria. The controller must be able to prove it responded (Art. 12(4) LOPDGDD)
MetadataMust be considered if specifically requestedSame: access logs, call records or location data can be personal data
Manifestly unfounded or excessiveUsing AI or asking for a lot is not enoughSame; the burden of proof is on the controller (Art. 12(5) GDPR). Spanish law adds repeated requests

1. The request is valid even if AI wrote it

No specific wording is needed and the law does not have to be cited correctly. What matters is whether it is clear the person wants access to their data. Wrong citations, misnamed rights or invented case law do not invalidate the request. Nor does an aggressive tone: many people use AI precisely because they do not know how to ask for their data.

2. The deadline is one month, and AI does not extend it

Article 12(3) GDPR sets one month from receipt, extendable by two further months “where necessary, taking into account the complexity and number of the requests”. The ICO is clear: length, unclear wording or legal references do not make a request complex. What may justify an extension is genuine difficulty: data spread across many systems, third-party information that must be protected, or several rights exercised at once. If you extend, you must tell the requester within the first month and explain why.

3. Check the address before sending anything

This is the most practical advice in the guidance. AI happily invents email addresses and contact details. If the request gives an address different from the one in your records, confirm it with the requester. If you send payslips or a personnel file to a stranger, the data breach will be yours, not the AI’s. The same applies to letters of authority from representatives: if one looks AI-generated, check directly with the data subject.

As for identity, Article 12(6) GDPR allows you to ask for additional information only where there are reasonable doubts. It is not an excuse to demand an ID document from someone already fully identified, such as an employee writing from their corporate email.

4. You may ask for clarification, but not impose a cut

If it is unclear what is being requested or which right is exercised, you may ask for clarification. The ICO adds that you cannot force the requester to narrow the request. In the EU, Recital 63 GDPR allows the controller to ask the data subject to specify the information where large amounts of data are processed, and the EDPB Guidelines 01/2022 on the right of access make clear this cannot be used to restrict the right: if the data subject insists on all their data, it must be provided.

The ICO considers that the deadline is paused while waiting for clarification. The GDPR has no equivalent express rule, so in Spain the prudent approach is not to count on that pause and to ask for clarification as early as possible.

5. You decide the search scope, and you must document it

When a request demands “metadata, backups, cameras and platforms you may not even use”, the requester can suggest where to look but cannot impose it. The controller must carry out a reasonable and proportionate search wherever the data is likely to be held, including processors.

The key word is accountability. Record whether you consulted the requester, what you included, what you excluded and why. In Spain there is an extra reason: Article 12(4) of the Spanish Data Protection Act (LOPDGDD) places on the controller the burden of proving that it responded to the request.

6. Metadata can be personal data

A general request for “all my data” does not require you to trawl every piece of metadata in every system. But if metadata is specifically requested, or is reasonably likely to contain the person’s data, you must consider it. For an employee, access logs, clock-in records, call logs or the location of a vehicle or of photos can be personal data.

7. What is not access is handled separately

AI often mixes access with complaints, general questions or requests about other people. Parts that do not concern the requester’s own data do not need a response as an access request, although it helps to explain this. Employment or commercial complaints follow their own route.

8. “Manifestly unfounded or excessive” requires evidence

Using AI does not make a request unfounded or excessive, and nor does asking for a lot of information. What may justify a refusal or a reasonable fee is a request that is clearly malicious, abusive or designed to disrupt the business. As the ICO notes, using AI does not relieve the requester of responsibility for what they send. In any case, the burden of proof is on the controller (Article 12(5) GDPR).

What is different in Spain: three rules the ICO does not mention

  1. Repeated requests. Article 13(3) LOPDGDD allows a request for access made more than once within six months to be treated as repetitive, unless there is a legitimate reason. It is useful against serial requests, assessed case by case.
  2. Remote access. Under Article 13(2) LOPDGDD, if the company offers a remote, direct and secure system giving access to all the data, the request is deemed fulfilled, although the requester may still ask for the Article 15 information that the system does not include.
  3. The motive does not matter. The Court of Justice of the EU confirmed in case C-307/22 (FT v DW, 26 October 2023) that the data subject does not need to justify why they want their data and that the first copy is free. An employee using access to prepare a claim cannot be refused on that ground.

Who sends these requests: three typical profiles

In our work as DPO, AI-generated access requests mostly come from three profiles. The legal basis is the same; what changes is where to look and which risks to watch.

ProfileWhat they usually wantWhere to lookWhat to watch
Dissatisfied customerEvidence for a complaint: calls, emails, incident historyCRM, customer service recordings, email, processors such as the call centreSeparate the commercial complaint from the access request and answer each through its own route
Debtor in a collection processWho holds their data, where it came from and who it was shared withDebt file, data source, disclosures to collection agencies or credit reference filesReport the source and recipients, and do not use the reply to chase the debt
Employee or former employeeMaterial for an employment dispute: payslips, working-time records, emails, appraisalsHR, payroll, clock-in records, corporate email, camerasProtect colleagues’ data and do not refuse access because they are preparing a claim

If the requester is a former employee asking about their email, who accessed it or their Teams photo: Guide to former employee requests →

Case study: an employee asks for “all their data” in an AI-written request

This is the order we follow when a client forwards a request like this:

  1. Day 1. Log the request with its date of receipt and alert the DPO. The one-month period starts.
  2. Check identity and address. If the person writes from a personal email and asks for the reply elsewhere, confirm before sending anything.
  3. Call or write to the employee. Without pressing them to give anything up, ask what they are looking for: payslips, working-time records, emails about a specific matter. In our experience, this conversation defuses many of the most aggressive requests.
  4. Separate what is not access: employment complaints, questions about colleagues or requests for documents that do not contain their data.
  5. Define and document the scope: HR systems, payroll, corporate email, clock-in records, cameras if footage is still retained, processors.
  6. Protect third parties. Access must not adversely affect the rights of others (Article 15(4) GDPR): emails containing colleagues’ or clients’ data are reviewed and, where appropriate, redacted.
  7. Respond within the month, with the information required by Article 15 (purposes, categories of data, recipients, retention period, source and rights) and a copy of the data. If there is genuine complexity, notify a reasoned extension before the first month ends.
  8. Keep the file: request, communications, search criteria and the response sent.

Common mistakes with AI-generated access requests

  • Ignoring it or replying that it is “not valid” because AI wrote it or it cites laws that do not exist.
  • Extending the deadline just because the request is long. Length is not complexity.
  • Sending the data to the address in the request without checking it belongs to the data subject.
  • Rebutting every legal hallucination point by point. It is enough to explain clearly what the GDPR requires and answer what applies.
  • Not documenting the search scope. If the person complains to the AEPD, the company will have to show what it did and why.
  • Calling it abusive without evidence. Tone does not prove bad faith.

How to prepare your company

The ICO recommends simple measures any organisation can adopt: a clear procedure for exercising rights and a contact point, basic training so all staff can recognise an access request, and more thorough training for those who handle them. It also suggests explaining that specific requests are answered faster and better, and warning about the risks of entering personal data into AI tools.

How we can help

We handle data subject requests every day from customers, debtors, employees and families for companies, schools and public bodies, more and more of them written with AI. As external data protection officers, we analyse the request, define the scope, prepare the response and document every step in case a complaint reaches the AEPD. If you have a difficult request on your desk right now, tell us about your case.

Frequently asked questions

Is an access request written with ChatGPT or another AI valid?

Yes. There are no formal requirements: it is enough that the person clearly wants access to their personal data. Legal errors or invented citations do not invalidate it.

Can I extend the deadline if the request is very long or confusing?

Not for that reason. The one-month period can only be extended by two further months for genuine complexity or the number of requests, and the requester must be told within the first month, with reasons.

Do I have to search every system mentioned in the request?

Not necessarily. The controller decides on a reasonable and proportionate search where the data is likely to be held, and must document those criteria. If metadata or footage is specifically requested, it must be considered.

Can I ask the requester to specify which data they want?

Yes, especially where a large volume of information is involved. But you cannot force them to narrow the request: if they insist on all their data, it must be provided.

Can I refuse if the requester wants the data to sue the company?

No. The Court of Justice of the EU has confirmed that data subjects do not have to explain why they want their data. A refusal is only possible if the request is manifestly unfounded or excessive, and the company must be able to prove it.

This article provides general information and is not a substitute for legal advice on a specific case.