Sooner or later, a customer, employee or former user will ask what personal data you hold about them. Under the GDPR, that question is a legal request with a deadline. Get it wrong, and a routine email can turn into a complaint to a data protection authority.

This guide explains how to handle a GDPR data subject access request (DSAR) step by step. We cover every right individuals can exercise, the deadlines, identity checks, what your response must include, erasure requests, working with vendors and the mistakes regulators find most often.

The short version: You generally have one month to respond, free of charge. Verify the person’s identity in a proportionate way, search every system that holds their data, give them a copy plus the information Article 15 requires and document everything. A written, tested process is what separates organizations that handle requests calmly from those that scramble.

What a Data Subject Access Request Is

A data subject access request is a request from an individual to see the personal data an organization holds about them. Under Article 15 of the GDPR, they’re entitled to confirmation that you process their data, a copy of it and specific details about how you use it.

Any channel
No special form
Requests can arrive by email, web form, phone, social media or letter. The person doesn’t need to say “GDPR” or “DSAR.”
Anyone
Customers and staff
Customers, prospects, employees, job applicants and former users can all make requests.
On behalf
Authorized third parties
A lawyer, relative or app can make a request for someone, if you can confirm their authority.

Why DSARs matter more now

Regulators have been paying close attention. European data protection authorities ran a coordinated enforcement action on the right of access in 2024 and on the right to erasure in 2025. For guidance, the European Data Protection Board’s Guidelines 01/2022 on the right of access are the most detailed reference available.

If you’re new to the regulation, start with our plain-English guide to what GDPR is.

The Rights Individuals Can Exercise

Access is the most common request, but it’s not the only one. Your process should handle every right:

Right GDPR article What the person can ask for
Access Art. 15 A copy of their data and details about how it’s used
Rectification Art. 16 Correction of inaccurate or incomplete data
Erasure Art. 17 Deletion of their data, when certain grounds apply
Restriction Art. 18 A pause on processing while a dispute is resolved
Portability Art. 20 Their data in a machine-readable format, in certain cases
Objection Art. 21 An end to processing based on legitimate interests or for direct marketing
Automated decisions Art. 22 Human review of significant decisions made solely by automated means

Requests often come combined

In practice, one email may ask for access and deletion together, or for access followed by deletion. Therefore, log each right separately so none gets missed. Note also that some rights apply only under certain lawful bases. For example, portability applies mainly to data processed on the basis of consent or a contract.

Deadlines and Ground Rules

Article 12 sets the rules that apply to every data subject access request:

Day 1
The clock starts when you receive the request, even if it arrives at an unmonitored inbox.
Within 1 month
Respond without undue delay and within one month.
Up to 2 more months
Extend only for complex or numerous requests, and tell the person within the first month why you need more time.
  • Free of charge: First, you can’t charge a fee for a normal request. You may charge a reasonable fee for extra copies.
  • Unfounded or excessive requests: Also, you can charge a reasonable fee or refuse a request that’s manifestly unfounded or excessive, such as repetitive demands. However, you must be able to justify that decision.
  • Explain refusals: In addition, if you won’t act on a request, tell the person why within one month, and explain their right to complain to a supervisory authority or seek a judicial remedy.
  • Clear language: Finally, respond in a concise, intelligible and easily accessible way.

Identity verification

Verify identity only when you have reasonable doubts, and keep the check proportionate. For instance, if a logged-in customer submits a request through their account, extra ID is rarely needed. Asking for a passport copy by default can itself create unnecessary risk and delay.

How to Respond to a DSAR Step by Step

A repeatable process makes every data subject access request manageable. Follow these steps:

  1. Log the request: Record the date received, the requester, the rights requested and the deadline in a central register.
  2. Acknowledge it: Confirm receipt and explain the next steps and timeline.
  3. Verify identity: Then confirm who the person is, using information you already hold where possible.
  4. Clarify only if needed: If you hold a large amount of data, you may ask the person to specify what they want. The deadline doesn’t simply stop while you wait, so ask early.
  5. Search every system: Next, search CRMs, email, support tickets, HR systems, backups, logs, analytics tools and vendor systems.
  6. Review and redact: After that, remove information about other people and confidential material that would harm others’ rights.
  7. Respond securely: Also, send the response through a secure channel, in a commonly used electronic format if the request came electronically.
  8. Record what you did: Finally, document your searches, decisions and the date you responded.

Know where the data lives

Step 5 is where most organizations struggle. A current data map, built from your records of processing activities, tells you which systems to search. Our post on why data classification matters explains how to organize data so it’s easier to find.

What Your Response Must Include

A response to a data subject access request isn’t complete with a data export alone. Article 15 also requires the following information. Use this checklist before you send:

Protecting other people

The right to a copy can’t adversely affect the rights of others. As a result, you may need to redact other customers’ names or colleagues’ personal details from emails and records. Even so, redact only what’s necessary, and don’t use it as a reason to withhold the requester’s own data.

Handling Erasure Requests

Erasure, often called the right to be forgotten, is one of the most frequently exercised rights. According to the EDPB’s report on its 2025 coordinated action, 32 data protection authorities took part, and they identified seven recurring challenges, including weak internal procedures and reliance on ineffective anonymization instead of deletion.

When erasure applies

  • No longer needed: For example, the data is no longer necessary for its original purpose.
  • Consent withdrawn: Also, the person withdraws consent and no other lawful basis applies.
  • Successful objection: In addition, the person objects and you have no overriding legitimate grounds.
  • Unlawful processing: Finally, the data was processed unlawfully or must be erased under a legal obligation.

When you can refuse

Erasure isn’t absolute. You can keep data when you need it to comply with a legal obligation, such as tax or financial record retention, or to establish, exercise or defend legal claims. In addition, tell any recipients you’ve shared the data with, so they can erase it too, and plan how deletion works for backups.

Processors, Vendors and U.S. Companies

Most organizations store personal data with vendors, so DSARs rarely stay inside one system.

  • If you’re the controller: First, you own the response and the deadline, even when a vendor holds the data. Your contracts should require processors to help you respond promptly.
  • If you’re the processor: Also, forward requests to your customer quickly and help them respond, rather than answering the individual yourself, unless your contract says otherwise.
  • Vendor inventory: In addition, keep a list of processors that hold personal data, and make sure each can search, export and delete it.

U.S. companies

GDPR can apply to U.S. businesses that offer goods or services to people in the EU or monitor their behavior. As a result, a U.S. company may receive DSARs from European customers or employees of EU subsidiaries. Our post on scoping a GDPR audit explains how to confirm whether and how GDPR applies, and our guide to vendor management covers oversight of processors.

Common Mistakes and Building a Repeatable Process

From an assessor’s perspective, these mistakes cause most data subject access request problems:

  • No process: For example, nobody owns requests, so they sit in a shared inbox past the deadline.
  • Incomplete searches: Also, teams search the main database but miss email, support tickets and vendor systems.
  • Partial responses: In addition, organizations send a data export without the required Article 15 information.
  • Heavy identity checks: Similarly, demanding excessive ID delays responses and can deter legitimate requests.
  • No records: Finally, failing to document decisions leaves you unable to show regulators what happened.

Make it repeatable

Assign an owner, publish a clear request channel, keep a request register, prepare response templates and test the process once or twice a year with a mock request. Notably, failures to respect individual rights fall within the GDPR’s higher fine tier, which can reach up to €20 million or 4% of worldwide annual turnover, whichever is higher.

For the broader program, use our GDPR compliance checklist. If you also hold a SOC 2 report, our post on GDPR vs. SOC 2 and our guide to SOC 2 Privacy explain where the two overlap. Audit Peak can assess your data subject request process as part of a GDPR assessment.

Please reach out if you would like to learn more about how Audit Peak can assist you with your GDPR compliance or for a free consultation. WE WILL TAKE YOU TO THE PEAK.