To respond to a subject access request, confirm whether you hold the person's data, verify their identity only as far as you need to, carry out a reasonable and proportionate search, and send them a copy of their personal data plus the supporting information required by Article 15, normally free of charge and within one month. You can extend by two further months for complex or multiple requests, and in the UK the clock now formally pauses while you wait for clarification you genuinely need.

This how-to covers the UK GDPR as amended by the Data (Use and Access) Act 2025 (DUAA) and the position under the EU GDPR. It is general information, not legal advice.

The right of access under GDPR in brief

Article 15 gives individuals the right to obtain:

  • confirmation that you are processing their personal data;
  • a copy of that data;
  • supporting information: purposes, categories of data, recipients, retention period, their other rights, the right to complain, the source of the data if not collected from them, any automated decision-making and safeguards for international transfers.

Most of the supporting information should already be in your privacy notice, so you can draw on it. If yours is thin, our guide to a privacy policy for an affiliate website will help. A request doesn't need to use the words "subject access" or cite the law. An email, a contact-form message, a live chat or a social media message asking "what data do you hold on me?" counts.

How to respond to a subject access request: step by step

  1. Recognise and log it. Record the date received, the channel and what was asked. Make sure anyone handling support knows a SAR when they see one.
  2. Check identity proportionately. If the request comes from the email address on the account, that may be enough. Ask for more only where you have genuine doubt, and ask promptly. Don't demand a passport scan from someone you only know by email; that creates more risk than it removes.
  3. Clarify if you really need to. If you hold a lot of data and the request is unclear, you can ask the person what they want. You cannot force them to narrow it.
  4. Search. Search the places the data is likely to be: account database, support tickets, email, CRM, payment and subscription records, tracker and analytics data tied to their ID, backups if they are readily accessible, and processors' systems.
  5. Review and redact. Remove other people's personal data unless they consent or it is reasonable to disclose. Consider whether any exemption applies.
  6. Respond. Send the data in a concise, intelligible form, electronically if the request was electronic, together with the Article 15 information. Explain anything you have withheld and why, and tell the person about their right to complain to you and to the regulator.
  7. Record what you did. Keep a note of searches, decisions and dates.

The DSAR deadline: one month, extensions and stop-the-clock

SituationTime limit
Standard requestWithout undue delay and within one month of receipt
You need ID or proof of a representative's authorityOne month from when you receive it
Complex request, or several requests from the same personExtend by up to two further months; tell the person within the first month and explain why
UK: you reasonably need clarification of scopeThe clock pauses until the person replies

The DUAA put these timing rules into the UK GDPR through a new Article 12A, in force since 5 February 2026 for requests received on or after that date. Most of it reflects what the ICO's guidance already said, but it is now statute. The "month" runs to the corresponding date in the next month: a request received on 3 March is due by 3 April.

In the EU, the same one-month and two-month extension rules apply under Article 12(3). The EDPB's guidelines on the right of access allow clarification requests for large datasets, but there is no statutory stop-the-clock equivalent to the UK's.

Section 78 of the DUAA added Article 15(1A) to the UK GDPR: a person is entitled only to the data and information you can provide after a reasonable and proportionate search. The amendment is treated as having been in force since 1 January 2024. See the text of section 78 on legislation.gov.uk and the ICO's guide to subject access.

This is not a licence to do a light search. "Reasonable and proportionate" is judged against the circumstances, including the importance of the information to the requester and the resources you have. In practice:

  • search all the systems where their data is likely to be, not just the main database;
  • you don't need to restore deleted data from archived backups at great expense if that is disproportionate;
  • document what you searched and why you stopped where you did;
  • small operators get no automatic pass, but a sole trader's systems are simpler, so a proportionate search is usually quick.

Exemptions, refusals and fees

You can withhold information only where an exemption or restriction applies. The ones small web businesses meet most often are:

  • Third-party data: information about other people, such as another user who reported the requester.
  • Legal professional privilege: advice from your lawyer about a dispute with the requester.
  • Crime prevention: for example, fraud-detection details where disclosure would prejudice prevention of fraud.

You can refuse, or charge a reasonable fee, if a request is manifestly unfounded or excessive, but the threshold is high. A request made as part of a dispute, or by someone you find difficult, is not automatically either. You can also charge a reasonable administrative fee for further copies. Otherwise, access is free.

Adult and creator platforms: requests often come from former members worried about what you keep, or from creators involved in disputes. Treat them seriously and discreetly: confirm you are sending the data to the right person, use secure delivery, and avoid sending sensitive content by unencrypted attachment.

A simple subject access request response template

A cover letter that works for most small sites:

Thank you for your request of [date] for a copy of your personal data. We confirm that we process personal data about you. Attached is a copy of that data. The purposes, recipients, retention periods and your rights are set out below [or: in our privacy notice at link]. We have withheld [description] because [exemption]. If you are unhappy with our response, you can complain to us at [address] and to the [ICO / supervisory authority].

Since 19 June 2026, UK controllers have also had to run a formal complaints process for data protection complaints; see our guide to the UK data protection complaints procedure.

Frequently asked questions

Can I ask why someone wants their data?

You can ask, but they don't have to tell you, and their motive does not normally affect your duty to respond.

Do I have to include data held by my processors?

Yes. Data held on your behalf by processors such as hosts, email platforms or tracking tools is still your data. Your contracts should require them to help.

Can a third party make a request for someone?

Yes, with the person's authority. Check that the authority is genuine before disclosing anything.

Next steps

Set up a SAR log, a short internal procedure and a cover-letter template now. For how the UK and EU rules are drifting apart in other areas, read UK GDPR vs EU GDPR, and if you collect identity documents from creators, check KYC checks on affiliate payouts for how that data should be handled.