FAQEU GDPR

EU GDPR DSAR Exceptions

Controllers should treat refusal as exceptional: first check identity, scope, timing, duplicate requests, and third-party rights before limiting access.

Based on GDPR Articles 12, 15, and 23 plus EDPB right-of-access guidance on narrow interpretation, partial redaction, extensions, and evidence.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

EU GDPR exceptions are narrow. A controller normally has to provide access, answer without undue delay and within one month, and may extend, charge, or refuse only where the GDPR conditions and supporting facts are documented.

Search this module

Find a question or answer quickly

5 of 5 questions
Question 1

When can a controller extend a DSAR response?

Article 12(3) requires the controller to provide information on action taken without undue delay and in any event within one month of receiving the request. The controller may extend that period by two further months only where necessary, taking into account the complexity and number of requests.

The extension is not automatic. The controller must tell the data subject within one month of receipt that it is extending the response period and must give the reasons for the delay.

  • Record the date the request was received and the first one-month response deadline.
  • Identify the concrete complexity or request volume that makes the extension necessary.
  • Send the extension notice within the first month, with reasons for the delay.
  • Do not extend merely because a processor or internal team is slow to retrieve information.

Can an EU GDPR deadline be extended because the request is complex?

Yes, but only under Article 12(3). The controller may extend by up to two further months where necessary because of the complexity and number of requests, and it must notify the data subject within one month of receiving the with the reasons for the delay.

Question 2

When can a controller ask for identity information?

A controller may request additional information only where it has reasonable doubts about the identity of the person making the request. The additional information must be necessary to confirm identity, not a routine barrier to exercising rights.

If the controller cannot identify the data subject in Article 11 circumstances, Article 12 says the controller does not have to act unless the data subject provides additional information enabling identification. The identity check should be proportionate to the data and risk involved. EDPB guidance allows the response period to be suspended while necessary identity information is outstanding, but only if the controller asks for it without undue delay.

  • Do not demand extra identity documents for every by default.
  • Record the reasonable doubt that triggered the identity check.
  • Ask only for information necessary to confirm the requester's identity or authority.
  • For third-party or proxy requests, verify authority before disclosing personal data.

Can a controller pause a while checking identity?

The GDPR allows extra identity information where the controller has reasonable doubts about the requester. EDPB guidance says the response period may be suspended until the controller receives the necessary information if it asked without undue delay. The request must still be targeted and proportionate, not a blanket demand for identity documents.

Question 3

When can a controller charge a fee or refuse a DSAR?

Article 12(5) starts from a free-of-charge rule. A controller may charge a reasonable fee or refuse to act only where the request is , in particular because of its repetitive character. The controller bears the burden of demonstrating that condition. Any fee is limited to the administrative cost of providing the information, communication, or action requested.

EDPB guidance says these concepts must be interpreted narrowly and assessed case by case. Lack of reasons, inconvenience, large internal effort, or the possibility that the requester may use the data in a dispute does not by itself make the request excessive.

  • Test whether Article 15 is clearly not met before calling a request manifestly unfounded.
  • For repetitive requests, compare the interval, data-change frequency, data sensitivity, processing purpose, and overlap with prior requests.
  • Consider whether combining overlapping requests or charging administrative costs is more appropriate than refusal.
  • If refusing, tell the data subject the reasons, complaint right, and judicial remedy route no later than one month after receipt.

Can a controller refuse a because it is burdensome?

Not on burden alone. Under Article 12(5), refusal requires a request, and the controller must prove that character. EDPB guidance says a large amount of time and effort does not by itself make an access request excessive.

Can a controller charge before refusing an excessive ?

Article 12(5) permits either a reasonable fee based on administrative costs or refusal. EDPB guidance treats a fee as often more appropriate for excessive repetitive requests and says controllers should indicate the planned fee so the data subject can decide whether to withdraw the request.

Question 4

Can access be narrowed to protect other people's rights?

Article 15(4) says the right to obtain a copy must not adversely affect the . That is not a general permission to reject the whole . The controller should assess the concrete conflict and provide access in an adjusted form where reconciliation is possible.

Typical handling is to leave out or render illegible the parts that would adversely affect others, while still providing the data subject's accessible personal data and Article 15 information where the GDPR allows it.

  • Identify the specific rights or freedoms of others that would be affected.
  • Assess the likelihood and severity of the adverse effect.
  • Use redaction, extraction, or partial disclosure where those measures solve the conflict.
  • Document why any withheld part could not be disclosed without adversely affecting others.

Does Article 15(4) let a controller reject the whole ?

Generally no. EDPB guidance says Article 15(4) should not result in refusing the request altogether; it should result in omitting or rendering illegible the parts that would adversely affect .

Question 5

What evidence should a DSAR exceptions record keep?

The record should show that the controller started from the right of access and applied only the GDPR limit needed for the specific request. It should be usable by privacy, legal, support, and product teams without adding unsupported national derogations or authority-specific procedures.

Where a controller relies on Union or Member State restrictions under Article 23, identify the applicable legislative measure and check its scope, conditions, necessity, and proportionality. Keep that analysis separate from the Article 12 and 15 assessment; a general reference to national law is not enough to establish a restriction.

  • Request receipt date, channel, requester, authority or proxy check, and identity-check rationale.
  • Data stores searched and whether the request covered all or only part of the data subject's personal data.
  • Any extension notice, its date, and the concrete complexity or volume reasons.
  • Any Article 12(5) fee or refusal decision, with facts proving character.
  • Any Article 15(4) redactions, the affected third-party rights, and why partial disclosure was sufficient or not.
  • If a legal restriction is invoked, the Union or Member State provision, conditions checked, and when the restriction should be lifted.
Primary sources

References and citations

edpb.europa.eu6 citations
Referenced sections
  • EDPB guidance source for right-of-access assessment, proportional identity checks, narrow interpretation of Article 12(5), repetitive-request handling, Article 15(4) redaction, and Article 23 caution.
  • EDPB access-right guidance explains that access must be fulfilled as soon as possible and that extension depends on complexity and number of requests.
  • EDPB guidance says identity checks must be proportionate, must avoid excessive data collection, and may suspend the response period only when necessary information was requested without undue delay.
Show 3 more
  • EDPB access-right guidance explains narrow interpretation, repetitive-request assessment, fee handling, and refusal notice content.
  • EDPB access-right guidance explains balancing and adjusted disclosure under Article 15(4).
  • EDPB access-right guidance recommends case-by-case documentation for manifestly unfounded or excessive access requests and cautions controllers to check Article 23 restriction conditions carefully.
"There are no further exemptions or derogations"
More quoted passages
"fulfilled as soon as possible and in any event within one month"
"proportionate to the type of data processed"
"These concepts have to be interpreted narrowly"
"leaving out or rendering illegible those parts"
"considered on a case by case basis"
eur-lex.europa.eu6 citations
Referenced sections
  • Binding GDPR source for Article 12 DSAR modalities, identity checks, extensions, refusal, fees, burden of proof, Article 15 copies and third-party rights, and Article 23 restrictions.
  • Article 12(3) sets the one-month DSAR response period and the two-month extension rule.
  • Article 12(2) and 12(6) cover facilitation of rights, inability to identify the data subject, and additional identity information where reasonable doubts exist.
Show 3 more
  • Article 12(5) sets the manifestly unfounded or excessive threshold, fee/refusal options, and controller burden of proof.
  • Article 15(3) requires a copy of personal data undergoing processing, and Article 15(4) limits copies where rights and freedoms of others would be adversely affected.
  • Articles 12, 15, and 23 provide the GDPR-level rules for DSAR modalities, copies, refusal, fees, identity checks, and legal restrictions.
"Where requests from a data subject are manifestly unfounded or excessive"
More quoted passages
"That period may be extended by two further months where necessary"
"reasonable doubts concerning the identity"
"manifestly unfounded or excessive"
"shall not adversely affect the rights and freedoms of others"
"The controller shall bear the burden"
Show all related guides (39)

EU GDPR Applicability Test for Products, Vendors, and Data Flows

A concrete GDPR scope test for personal data, controller and processor roles, EU establishment, EU targeting or monitoring, special-category and child data, transfers, vendors, and evidence.

EU GDPR Article 30 RoPA Intake Workflow

This GDPR Article 30 RoPA intake workflow helps capture controller and processor fields, owners, transfers, retention, security measures, and evidence before a processing activity goes live.

EU GDPR Automated Decision-Making and Profiling: Article 22 Scope, Safeguards, and Evidence

GDPR guide to profiling and Article 22 decisions: scope, transparency, lawful basis, DPIA triggers, safeguards, human intervention, challenge rights, and evidence.

EU GDPR Breach Notification 72 Hours: Article 33 and 34 workflow

EU GDPR breach notification workflow covering awareness, 72-hour supervisory authority notices, processor escalation, high-risk data-subject communication, delay reasons, and evidence logs.

EU GDPR Breach Notification Workflow: 72-hour clock, risk assessment, and records

A concrete EU GDPR breach notification workflow for detecting and triaging incidents, starting the awareness clock, assessing risk, notifying authorities or data subjects, and keeping Article 33 records.

EU GDPR Checklist: scope, lawful basis, DSARs, DPIA, RoPA, transfers

This GDPR checklist helps review scope, lawful basis, notices, DSAR handling, DPIAs, RoPA, processor contracts, SCC transfers, breach notification, retention, security, and evidence.

EU GDPR Children and Special-Category Data Guide

GDPR guide to children's consent and special-category data: Article 8 national age variation, Article 9 conditions, transparency, DPIA triggers, safeguards, and evidence.

EU GDPR Compliance Checklist: scope, rights, DPIA, RoPA, transfers

Practical EU GDPR compliance guide for mapping scope, lawful basis, notices, data-subject rights, DPIAs, RoPA, processor terms, breaches, transfers, retention, security, and penalties.

EU GDPR Controller, Processor, and Joint Controller Roles

Classify GDPR controllers, processors, and joint controllers from actual decision-making, then document Article 26 allocation, Article 28 terms, instructions, and vendor evidence.

EU GDPR Data Subject Rights and DSAR Workflow

GDPR rights-request workflow for intake, identity checks, request scope, the one-month response clock, extensions, refusals, processor coordination, and evidence.

EU GDPR deadlines and compliance calendar

EU GDPR calendar for calculating rights-request deadlines, breach notification, DPIA and prior-consultation gates, transfer reviews, and retention checks.

EU GDPR DPIA and Prior Consultation Workflow

Screen high-risk processing, run a GDPR Article 35 DPIA, record mitigation, and identify when Article 36 prior consultation is required.

EU GDPR DPIA and risk management under Articles 35 and 36

EU GDPR DPIA guide covering Article 35 triggers and contents, CNIL and DPC PIA methods, residual risk, mitigation records, and prior consultation limits.

EU GDPR DSAR Workflow: Intake, Clock, Rights, and Evidence

Run a GDPR DSAR workflow for intake, identity checks, rights scoping, one-month response timing, extensions, refusals, processor handoffs, and evidence records.

EU GDPR FAQ: scope, lawful basis, rights, DPIA, breaches, transfers

Direct EU GDPR FAQ answers on scope, controller and processor roles, lawful basis, data subject rights, DPIAs, breach notification, international transfers, and Article 83 fine tiers.

EU GDPR International Transfers and SCCs: Chapter V evidence guide

GDPR Chapter V guide to adequacy decisions, SCCs, transfer assessments, supplementary measures, Article 49 derogations, and EU-US DPF checks.

EU GDPR Lawful Basis and Consent Guide

Focused GDPR guide to Article 6 lawful bases, consent conditions, legitimate interests, special category data, withdrawal, and evidence records.

EU GDPR Lawful Basis and LIA Workflow for Article 6(1)(f)

Assess GDPR legitimate interests with a purpose, necessity, balancing, Article 21 objection, and evidence-record workflow based on Article 6(1)(f).

EU GDPR Lead Supervisory Authority and One-Stop-Shop

How GDPR main establishment, cross-border processing, Article 56 lead authority competence, and Article 60 cooperation fit together.

EU GDPR LIA Template for Article 6(1)(f)

This EU GDPR legitimate interests assessment template helps document Article 6(1)(f) purpose, necessity, balancing, safeguards, objection rights, and evidence.

EU GDPR penalties and fines: Article 83 tiers and evidence

EU GDPR penalties guide covering Article 83 fine ceilings, the EDPB calculation method, CJEU conditions, Article 58 powers, and evidence.

EU GDPR Processor Contracts and Vendor Management | Article 28 Evidence Guide

EU GDPR Article 28 guide for processor contracts, sub-processor controls, controller-processor role boundaries, vendor evidence, and SCC transfer clauses where applicable.

EU GDPR Record of Processing Activities Template: Article 30 RoPA Fields

Build a GDPR Article 30 record of processing activities with separate controller and processor fields for purposes, data categories, recipients, transfers, erasure time limits, and security measures.

EU GDPR Requirements: scope, rights, security, DPIA, RoPA, and transfers

Overview of core EU GDPR requirements covering scope, principles, lawful basis, notices, data-subject rights, processors, RoPA, security, breaches, DPIAs, and international transfers.

EU GDPR Retention and Erasure Schedule

Build an EU GDPR retention and erasure schedule with purpose-based periods, expiry actions, Article 17 decisions, recipient notices, and deletion evidence.

EU GDPR Transfer TIA and SCC Workflow

A GDPR workflow for checking adequacy, selecting SCC modules, documenting transfer impact assessments, and recording supplementary measures for third-country transfers.

EU GDPR Transparency Notices: Articles 12, 13 and 14

GDPR privacy-notice guide for Articles 12, 13, and 14: direct collection, other data sources, purposes, lawful bases, recipients, transfers, retention, rights, and timing.

EU GDPR vs Brazil LGPD: scope, legal bases, rights, incidents, and transfers

Compare EU GDPR and Brazil LGPD scope, actors, legal bases, rights timing, security incidents, international transfers, evidence, regulators, and penalties.

EU GDPR vs California CCPA: scope, rights, opt-outs, and evidence

Compare EU GDPR and California CCPA scope, roles, consumer rights, response times, sale and sharing opt-outs, risk assessments, contracts, transfers, and enforcement.

EU GDPR vs ePrivacy Directive: personal data, cookies, consent, and communications

Compare the EU GDPR and ePrivacy Directive for personal data processing, consent and lawful basis, cookies and terminal access, electronic communications, and parallel compliance.

EU GDPR vs UK GDPR: Scope, Rights, Transfers, and Evidence

Compare the EU GDPR and amended UK GDPR across scope, rights, automated decisions, accountability, breaches, regulators, and international transfers.

GDPR vs EU AI Act: privacy controls for AI systems

Map the GDPR work that remains necessary when an AI system processes personal data, including lawful basis, notices, DPIAs, Article 22, rights, security, records, and transfers.

GDPR vs EU Data Act: personal data, connected products, and access rights

Compare GDPR privacy duties with EU Data Act rights and duties for connected-product data, third-party access, data holders, users, contracts, cloud switching, and enforcement.