Lead supervisory authority

Also known as: GDPR one-stop-shop mechanism

On this page 7

A lead supervisory authority is the national data protection authority that takes the leading role in supervising cross-border processing carried out by a controller or processor in the European Union. Under the GDPR, the lead authority is normally the regulator of the Member State where the organization has its main establishment, and it coordinates investigations and decisions with every other authority whose residents are affected.

The concept sits at the heart of the one-stop-shop mechanism set out in Article 56 GDPR. Instead of answering to up to 27 regulators separately, a company with operations in several Member States deals with a single interlocutor for its cross-border activities, while the other authorities keep a formal say through cooperation and consistency procedures.

How the lead supervisory authority is identified

The lead supervisory authority is identified by locating the main establishment defined in Article 4(16) GDPR. For a controller, this is the place of its central administration in the EU, unless decisions on the purposes and means of processing are actually taken in another EU establishment that has the power to implement them. For a processor, it is the place of central administration or, if there is none, the establishment where the main processing activities take place.

The test is factual, not formal. Regulators and the European Data Protection Board (EDPB) look at where effective decision-making power over the processing actually sits. A letterbox subsidiary that only hosts a registered office does not create a main establishment, and forum shopping through paper structures is routinely rejected.

The following table summarizes how the main establishment is determined in typical corporate situations.

SituationMain establishmentResulting lead authority
Controller with EU headquarters deciding on processingEU headquartersAuthority of the headquarters State
Decisions taken in another EU subsidiarySubsidiary that decides purposes and meansAuthority of that subsidiary’s State
Processor with central administration in the EUPlace of central administrationAuthority of that State
Group with several decision centersAssessed per processing activityMay differ by activity
Non-EU company with only a representativeNo main establishmentNo lead authority; each authority competent
Determining the main establishment

The last row matters in practice. An organization established outside the EU that merely appoints an Article 27 representative cannot benefit from the one-stop shop, so it may face parallel proceedings in every Member State where it targets or monitors individuals.

Cross-border processing and the authorities concerned

The lead supervisory authority is competent only for cross-border processing, defined in Article 4(23) GDPR. Processing is cross-border when it takes place in the context of establishments in more than one Member State, or when a single establishment’s processing substantially affects data subjects in more than one Member State.

Every other regulator with a link to the case becomes a supervisory authority concerned under Article 4(22). That status arises when the organization has an establishment in its territory, when its residents are substantially affected, or when a complaint was lodged with it. The complainant always deals with the authority where the complaint was filed, which acts as a local point of contact even when another authority leads.

The roles involved in a cross-border case are compared below.

RoleMain functionLegal basis
Lead supervisory authorityInvestigates and drafts the decisionArticles 56 and 60
Supervisory authority concernedReviews drafts and may objectArticles 4(22) and 60
Authority receiving the complaintInforms and represents the complainantArticles 60(7) to 60(9) and 77
European Data Protection BoardResolves disputes with binding decisionsArticles 63 and 65
Roles in a cross-border GDPR case

The cooperation procedure under Article 60

The cooperation procedure in Article 60 GDPR requires the lead supervisory authority to work toward consensus with the authorities concerned. It must share relevant information, may request mutual assistance and joint operations, and must submit a draft decision to all authorities concerned before adopting it.

Each authority concerned then has four weeks to raise a relevant and reasoned objection. If the lead authority does not follow the objection, or considers it not relevant and reasoned, the matter goes to the consistency mechanism, and the EDPB adopts a binding decision under Article 65. A revised draft triggers a shorter two-week objection period.

The main procedural steps and their typical timing are set out in the next table.

StepResponsible bodyTypical timing
Complaint lodged or own-initiative inquiryAny authority concernedStart of case
Identification of the lead authorityAuthorities, with EDPB if disputedWeeks to months
Investigation and preliminary findingsLead supervisory authorityMonths to years
Draft decision circulatedLead supervisory authorityAfter investigation
Objection periodAuthorities concernedFour weeks
Dispute resolution, if neededEuropean Data Protection BoardOne to two months
Final decision notifiedLead or complaint-receiving authorityWithout undue delay
Main steps of a one-stop-shop case

Where a complaint is rejected or dismissed, the authority that received the complaint adopts and notifies that decision to the complainant, which preserves the individual’s right to an effective remedy before the courts of their own Member State.

Exceptions and limits of the lead authority’s competence

The lead supervisory authority does not hold exclusive power in every situation. The GDPR keeps several exceptions that return competence to other regulators or remove the one-stop shop altogether.

  • Local cases under Article 56(2): a complaint that relates only to an establishment in one Member State, or that substantially affects only its residents, may be handled locally if the lead authority does not take it over.
  • Urgency procedure under Article 66: any authority concerned may adopt provisional measures for up to three months when rights and freedoms need urgent protection.
  • Public authorities and public-interest processing under Article 55(2): processing based on a legal obligation or a public task is supervised only by the authority of the relevant Member State.
  • Organizations without an EU establishment: no main establishment exists, so every competent authority can act independently.
  • National rules outside the GDPR, such as cookie rules implementing the ePrivacy Directive, often fall to national regulators without any one-stop shop.

The last exception explains why some large technology companies receive cookie-related fines from several national authorities even though one regulator leads their GDPR supervision. Misreading the scope of the one-stop shop is a common compliance error.

Strengths, criticism and reform of the one-stop shop

The lead supervisory authority model delivers legal certainty and consistency for multinational organizations, but it also concentrates workload on a few regulators. Because many global technology firms place their EU headquarters in Ireland or Luxembourg, those authorities carry a disproportionate share of high-profile cross-border cases.

Critics point to slow investigations, divergent national procedural rules and frequent disagreements resolved only through Article 65 binding decisions. In response, EU lawmakers agreed in 2025 on additional procedural rules for cross-border enforcement, covering admissibility of complaints, the right to be heard and harmonized deadlines. The table below weighs the main arguments.

AspectBenefitDrawback
Point of contactOne regulator for cross-border issuesDistance from affected residents
ConsistencySingle decision valid across the EUDisputes escalate to the EDPB
ResourcesExpertise concentrated in leading authoritiesBottlenecks at heavily loaded regulators
SpeedAvoids duplicated investigationsMulti-year timelines in complex cases
Assessment of the lead authority model

The simple explanation

Imagine a company that sells to customers in many European countries. Without a common rule, it could be questioned by a different privacy regulator in each country, all at once. The lead supervisory authority solves this: one national regulator, usually in the country where the company makes its key decisions, takes charge of the case.

The other regulators are not ignored. They can review the lead regulator’s draft decision and object to it, and if they cannot agree, a European board settles the dispute. In short, one regulator leads, but all affected regulators have a voice.

How it is used in practice

A streaming service has its European headquarters in Dublin, where its privacy decisions are made, and subscribers in 20 Member States. A user in Germany complains to a German authority that the service ignored an access request. Because the processing is cross-border, the German authority forwards the complaint, and the Irish Data Protection Commission acts as lead supervisory authority.

The Irish regulator investigates, finds a systemic delay in handling access requests, and circulates a draft decision. The French and Italian authorities, also concerned through other complaints, raise objections about the proposed fine. After the lead authority revises the draft, all authorities accept it. The company receives a single decision covering every Member State, orders a fix to its request-handling process within 60 days, and the German user is informed of the outcome by the German authority.