FAQEUData Act

EU Data Act Enforcement and Competent Authorities FAQ

Who enforces the Data Act, where complaints go, and how penalties and dispute settlement fit together.

This FAQ helps separate Member State enforcement, routing, certified dispute settlement, and GDPR supervisory-authority responsibilities.

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

Each Member State designates one or more Data Act and, if it designates more than one, a as the national single point of contact. A complainant may file in the Member State of habitual residence, place of work, or establishment. The entity under investigation is generally supervised where it is established or has its ; a non-EU entity offering covered products or services in the Union must designate an EU . National law supplies the authority procedures and penalty amounts.

Search this module

Find a question or answer quickly

8 of 8 questions
Question 1

Which national authorities are responsible for enforcing the EU Data Act in each Member State?

Each Member State must designate one or more for Data Act application and enforcement. A Member State can create a new authority or rely on an existing public body, so companies should not assume that the same office is responsible in every country.

If a Member State designates more than one competent authority, it must designate a from among them. The data coordinator is the national single point of contact for Data Act application questions and helps route people and businesses to the appropriate competent authority. Article 37 requires the Commission to maintain a public register of designated authorities.

To identify the authority, first select the Member State using the jurisdiction and complaint-venue rules below. Search that government's official legislation portal for Regulation (EU) 2023/2854 and its national implementing or authority-designation measure. Read the provisions allocating tasks, then confirm the named body's Data Act remit and complaint channel on its official website. Keep the measure, relevant provision, authority name, covered chapter, contact route, and date checked. If the allocation is unclear, ask the designated for routing information before submitting the substantive complaint.

  • If using a Commission register entry, retain the entry and date checked, then confirm the current task allocation and contact route against the national measure and authority website.
  • For cross-border issues, the helps identify the right authority in the Member State concerned.
  • Do not guess sector-specific responsibility where another authority may have competence under Article 37.
Question 2

Which Member State supervises an entity under the EU Data Act?

An entity is generally subject to the Member State where it is established. If it is established in more than one Member State, Article 37 assigns competence to its : the head office or registered office from which its principal financial functions and operational control are exercised.

An entity outside the Union that makes connected products available or offers covered services in the Union must designate a in one Member State. It is then under that Member State's competence. Until it designates a representative, it can be subject to all Member States where applicable, subject to the rule against parallel enforcement proceedings under the Data Act for the same facts.

  • Distinguish the complainant's Article 38 filing venue from the entity-supervision rules in Article 37.
  • Record establishment, main-establishment, and legal-representative facts before assigning the enforcement route.
  • For cross-border cases, check whether another authority has already opened Data Act proceedings on the same facts.
Question 3

How can a person or company lodge a complaint about an EU Data Act infringement?

Natural and legal persons can lodge a complaint, individually or collectively where relevant, with the relevant competent authority if they consider that their Data Act rights have been infringed. The correct Member State is tied to the complainant's habitual residence, place of work, or establishment.

The must, on request, provide the information needed to lodge the complaint with the appropriate competent authority. After a complaint is lodged, the competent authority must inform the complainant of the progress and the decision in accordance with national law.

  • Collect the contract, request history, dates, and the exact Data Act issue before filing.
  • If you are unsure which authority is responsible, start with the .
  • Complaints can be made without giving up the right to go to court.
Question 4

Are penalties for EU Data Act infringements harmonised across all EU Member States?

No single EU penalty table is set in the Data Act. Member States set the rules on penalties for Data Act infringements and must make sure the penalties are effective, proportionate, and dissuasive.

The Data Act lists criteria for penalties, including the nature, gravity, scale, and duration of the infringement, mitigation or remediation, previous infringements, financial benefits gained or losses avoided, other aggravating or mitigating factors, and the infringing party's EU annual turnover in the preceding financial year.

  • Do not cite a euro amount, percentage cap, or national maximum unless it comes from the relevant Member State penalty measure.
  • Track national penalty rules separately from the Data Act text because Member States can update their measures.
  • For GDPR-related Data Act infringements within a data protection authority's competence, check the separate GDPR fine route.
Question 5

When can EU Data Act dispute settlement be used instead of a competent-authority complaint?

Under the Data Act, certified dispute settlement bodies are a voluntary route. Users, data holders, and data recipients can use them for the Article 4 and 5 disputes identified in Article 10, disputes about fair, reasonable, and non-discriminatory terms and transparent data sharing under Chapters III and IV, and disputes under Articles 23 to 31 on data processing services.

A decision binds the parties only if they explicitly consented to its binding nature before proceedings began. The route does not remove the right to seek an effective remedy before a Member State court or tribunal.

  • Use certified dispute settlement when both parties agree and the dispute falls within Article 10; review the disclosed fees and the 90-day decision period before referral.
  • Do not use it for a dispute already before another or a court or tribunal.
  • A complaint to the competent authority is still available where the Data Act gives that route.
Question 6

Where is the boundary between Data Act competent authorities and GDPR supervisory authorities?

Data Act do not replace GDPR supervisory authorities. Under Article 37, the authorities responsible for monitoring the GDPR are responsible for monitoring the Data Act insofar as protection of personal data is concerned.

That boundary matters when a Data Act access, sharing, or complaint file involves personal data. The GDPR authority remains responsible for checking whether the data are personal, whether a valid GDPR legal basis exists, and how the personal-data rules apply in the case.

  • Route personal-data protection questions to the GDPR supervisory authority path.
  • Keep the Data Act and GDPR records aligned so the same facts are described consistently.
  • For mixed datasets, record the personal-data assessment and the legal basis analysis.
Question 7

What evidence should a Data Act enforcement file contain to support a complaint or inquiry?

A useful enforcement file should be narrow and factual. It should show which Data Act right or obligation is involved, which Member State authority path is relevant, whether a should route the issue, whether dispute settlement is available, and whether GDPR or sectoral authorities have separate competence.

For complaints, refusals, penalties, or authority inquiries, keep enough evidence to reconstruct the issue without relying on chat history or unsupported assumptions.

  • Keep the exact legal issue, the date, the actor involved, and the request or decision that triggered the file.
  • Record the authority contacted, including the if used.
  • Attach the cited Data Act source, any Commission guidance used, and the current version of the national penalty rule if relevant.
  • Keep the exact Article 37 to 40 passage, Commission guidance, authority-register entry and date checked, source URLs, decision date, approving reviewer, unresolved assumptions, and national penalty source where relevant.
  • Assign a named owner for each complaint, operational correction, authority communication, and record. Record consulted teams and who can reopen the decision.
  • Review after changes to establishment, representative, product, service, customer base, authority designation, national penalty rule, guidance, or GDPR/dispute-settlement involvement.
Question 8

How do EU Data Act competent authorities cooperate across borders and with the European Data Innovation Board?

Under the Data Act, must cooperate with each other and with authorities in other Member States, sharing relevant information so a cross-border issue does not fall between national gaps. The supports consistency, including coordinating on the approach to penalties so they remain comparable across the Union.

For a complainant, this means a matter involving providers or users in several Member States can be coordinated rather than duplicated, and the helps route the issue to the authority with competence.

  • Expect to cooperate and exchange information on cross-border Data Act matters.
  • Use the to route a multi-Member-State issue to the right authority.
Primary sources

References and citations

eur-lex.europa.eu8 citations
Referenced sections
  • Binding Data Act text for competent authorities, data coordinators, complaint rights, judicial remedies, penalties, GDPR supervisory-authority boundaries, dispute settlement, and EDIB coordination.
  • Article 37 sets out competent authorities, data coordinators, cooperation duties, and the public register.
  • Article 37(10) to (13) sets the establishment, main-establishment, legal-representative, and pre-designation competence rules.
Show 5 more
  • Article 38 gives the complaint right and explains the Member State link and data coordinator support.
  • Article 40 says Member States set Data Act penalty rules and lists non-exhaustive penalty criteria.
  • Article 10 covers dispute settlement scope, timing, refusal rules, binding effect, and court-preservation rules.
  • Article 37(3) preserves GDPR supervisory authority responsibility where Data Act application concerns personal-data protection.
  • Articles 37 to 40 support authority routing, complaints, cooperation, and penalty evidence.
digital-strategy.ec.europa.eu4 citations
Referenced sections
  • Commission explainer for the practical role of data coordinators, the Commission public register, EDIB penalty coordination, and certified dispute settlement bodies.
  • The Commission explains that the data coordinator is the national single point of contact when several authorities are designated.
  • The Commission explains dispute settlement as a practical route for parties that cannot agree on FRAND terms.
Show 1 more
  • The Commission explains the role of the public register, the data coordinator, and the EDIB in enforcement.
ec.europa.eu4 citations
Referenced sections
  • Commission FAQ used for practical explanations of enforcement bodies, complaint routing, penalties, DPAs, EDIB support, and dispute settlement limits.
  • The Commission FAQ says the data coordinator can help stakeholders with complaints and routing.
  • The Commission FAQ confirms that penalties are set by Member States, with EDIB coordination for consistency.
Show 1 more
  • The Commission FAQ says the DPAs monitor Data Act matters within their personal-data protection competence.
Show all related guides (61)

Data Act FAQ for Aftermarket Repair and Mobility Services

FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services.

Data Act SME Exceptions and Startups FAQ

FAQ on where the EU Data Act gives micro, small, medium-sized, startup, and SME actors narrower treatment for access duties, compensation, and B2B terms.

Data Act Trade Secret Technical Protection Measures FAQ

FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence.

EU Data Act and Common European Data Spaces FAQ

FAQ on how EU Data Act interoperability duties, Data Governance Act rules, and sector data-space governance fit together without treating participation as a general obligation.

EU Data Act and GDPR: Personal Data Overlap FAQ

FAQ on how the EU Data Act works when connected-product or related-service data includes personal data, mixed datasets, GDPR roles, lawful basis, trade secrets, and third-party sharing.

EU Data Act Application Dates and Transition FAQ

FAQ on when the EU Data Act applies, which obligations are delayed, and what product, contract, cloud, and evidence records teams should maintain.

EU Data Act Article 32: Foreign Government Access FAQ

FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers.

EU Data Act Article 36 Smart Contract Controls FAQ

FAQ explaining when EU Data Act Article 36 applies to smart contracts for data-sharing agreements and what controls, conformity evidence, and limits it requires.

EU Data Act B2B Data Sharing Compensation FAQ

FAQ on when Data Act data holders may charge B2B data recipients, what reasonable compensation can include, SME limits, unfair terms, disputes, and trade secret safeguards.

EU Data Act B2G Compensation and Costs FAQ

FAQ on when Data Act B2G exceptional-need requests are free, when fair compensation may be claimed, which costs can be included, and what records to keep.

EU Data Act B2G Exceptional Need FAQ

When public-sector bodies can request business-held data under the EU Data Act, what a valid request must contain, and how data holders handle limits, trade secrets, compensation, and evidence.

EU Data Act Cloud Switching Procurement FAQ

Procurement checklist FAQ for EU Data Act cloud switching: contract terms, exit support, exportable data, switching charges, interoperability, termination, and supplier evidence.

EU Data Act Connected Product Scope FAQ

FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope.

EU Data Act data spaces interoperability FAQ

FAQ explaining Article 33 Data Act interoperability requirements for data-space participants, common European data spaces, standards, APIs, metadata, and architecture evidence.

EU Data Act Direct Access by Design FAQ

FAQ for product and legal teams designing user access to connected-product and related-service data under the EU Data Act.

EU Data Act Functional Equivalence: IaaS Switching FAQ

FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence.

EU Data Act Indirect Access Request Workflow FAQ

FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited.

EU Data Act Interoperability Standards: Articles 33-36

FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614.

EU Data Act Model Terms and Cloud Clauses FAQ

FAQ on the EU Data Act non-binding model contractual terms for data access and use, cloud switching clauses, B2B use, unfair terms, and evidence.

EU Data Act Non-Emergency Public-Sector Request FAQ

FAQ on EU Data Act requests where a public body claims exceptional need outside a public emergency, including scope, request contents, limits, compensation, confidentiality, and evidence.

EU Data Act Pre-Contractual Information FAQ

FAQ on EU Data Act Article 3 pre-contract information for connected products and related services, including data categories, access methods, data holder identity, third-party sharing, and GDPR boundaries.

EU Data Act Product Data vs Related-Service Data

FAQ explaining how the EU Data Act separates connected product data, related service data, readily available raw and pre-processed data, metadata, and inferred or derived outputs.

EU Data Act Public Emergency Request FAQ

FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records.

EU Data Act Readily Available Data FAQ

FAQ on what counts as readily available data under the EU Data Act, including product data, related service data, metadata, inferred data, and access mechanics.

EU Data Act Related Services FAQ

FAQ explaining when software is a Data Act related service, how it links to connected products, which product and service data are in scope, and what exclusions apply.

EU Data Act Smart Contracts for Data Sharing FAQ

Answers on Article 36 Data Act smart-contract requirements for data sharing: scope, robustness, access control, termination, archiving, conformity assessment, contract terms, and standards status.

EU Data Act Third-Party Data Sharing FAQ

FAQ on user-directed third-party data sharing under the EU Data Act, covering data holder duties, recipient limits, trade secrets, security, GDPR, and gatekeepers.

EU Data Act Trade Secret Safeguards FAQ

FAQ on protecting trade secrets when handling EU Data Act user and third-party data access requests, including safeguards, withholding, suspension, refusal, notices, and records.

EU Data Act Unfair Contractual Terms FAQ

FAQ on Article 13 of the EU Data Act: B2B unfair contract terms, unilateral take-it-or-leave-it clauses, always-unfair terms, presumed-unfair terms, SMEs, model terms, and review evidence.

EU Data Act Users, Data Holders, and Recipients FAQ

FAQ explaining Data Act users, data holders, data recipients, connected products, related services, user access, third-party limits, and GDPR boundaries.

EU Data Act Vehicle Data Guidance FAQ

FAQ on EU Data Act vehicle data guidance for connected vehicles, aftermarket repair, mobility services, third-party access, trade secrets, security, and GDPR boundaries.

EU Data Act: Non-Personal Data and Mixed Datasets

FAQ on how the EU Data Act treats non-personal data, mixed datasets, GDPR precedence, user and third-party access, trade-secret limits, and evidence records.

Data Act and Common European Data Spaces

How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring.

Data Act B2B Data-Sharing Contract Clauses

Clause guide for EU Data Act B2B data sharing: FRAND terms, compensation, trade secret safeguards, recipient limits, termination, logs, and GDPR boundaries.

Data Act B2B Data-Sharing Contract Template

A usable EU Data Act B2B data-sharing template outline covering access requests, data schedules, permitted use, trade secrets, security, compensation, GDPR boundaries, audit records, and termination.

Data Act B2G Exceptional-Need Requests

A guide to EU Data Act Chapter V requests from public bodies: exceptional need, public emergencies, request contents, limits, safeguards, costs, and records.

Data Act Cloud Switching Compliance Checklist

A cited EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence.

Data Act Smart Contracts for Data Sharing

Data Act Article 36 smart contract guide for data-sharing agreements: scope, robustness, access control, termination, interruption, archiving, standards status, and conformity evidence.

Data Act Trade Secrets and Protection Measures

Data Act guide for protecting trade secrets during access and sharing: classification, safeguards, refusal thresholds, notices, evidence records, and reviews.

Data Act Unfair Contractual Terms | Article 13 B2B Contract Review

Review B2B data-sharing clauses under EU Data Act Article 13: unilateral terms, always unfair examples, presumed unfair terms, model clauses, evidence, and remediation.

Data Act Vehicle Data Guidance

Commission-cited guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries.

Data Act vs GDPR: connected-product data access

Compare EU Data Act connected-product access duties with GDPR personal-data rules: scope, roles, lawful basis, data subject rights, third-party sharing, trade secrets, and conflicts.

EU Data Act Applicability Test

Check whether a product, related service, data holder, cloud service, data-space role, smart contract, or B2G request is in scope of the EU Data Act.

EU Data Act Article 3 Pre-Contract Information

What Article 3 of the EU Data Act requires before connected-product purchase, rent, lease, or related-service contracting: data categories, access, data holder identity, third-party sharing, complaints, and evidence.

EU Data Act Checklist for Product, Cloud, and Contract Teams

A cited EU Data Act checklist for connected-product data access, third-party sharing, B2G requests, cloud switching, unfair terms, smart contracts, personal data boundaries, evidence, and owners.

EU Data Act Cloud Switching and Exit Plans

A cited EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records.

EU Data Act Compliance Program

Build a Data Act compliance program for connected-product data access, contracts, B2G requests, cloud switching, smart contracts, GDPR boundaries, records, and ownership.

EU Data Act Connected Product Scope and Data Types

Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs.

EU Data Act Data Processing Service Switching

A cited EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure.

EU Data Act deadlines and compliance calendar

A cited calendar for EU Data Act application dates, product design timing, contract remediation, cloud switching charges, response periods, standards work, and evidence records.

EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates

EU Data Act FAQ index covering connected-product access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, and application dates.

EU Data Act Penalties and Enforcement

Guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary.

EU Data Act Requirements by Workstream

EU Data Act requirements for connected-product access, B2B terms, B2G exceptional need, cloud switching, smart contracts, interoperability, GDPR boundaries, and records.

EU Data Act User Access and Portability Rights

Practical guide to EU Data Act user access, connected-product data portability, third-party sharing, trade secret safeguards, and the GDPR boundary.

EU Data Act vs Data Governance Act

Compare the EU Data Act with the Data Governance Act: connected-product access, cloud switching, B2B/B2G duties, protected public-sector reuse, intermediaries, altruism, governance, and enforcement.