FAQEUData Act

EU Data Act Complaints and Dispute Settlement FAQ

Choose the competent-authority, certified dispute-settlement, or court route for a Data Act complaint.

This FAQ helps separate competent-authority complaints, voluntary dispute settlement, court remedies, B2B data-sharing disputes, B2G request objections, cloud switching disputes, and the evidence record behind each route.

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

Since Regulation (EU) 2023/2854 began applying on 12 September 2025, a natural or legal person who considers that its Data Act rights were infringed may complain to the relevant in the Member State of its habitual residence, place of work, or establishment. Certified dispute settlement is a separate, voluntary route for the disputes listed in Article 10, including specified data-sharing disputes and breaches of cloud-customer rights under Articles 23 to 31. It does not remove access to a court, and a decision binds the parties only if they agreed to that effect before the proceeding began.

Search this module

Find a question or answer quickly

9 of 9 questions
Question 1

Who can complain to a Data Act competent authority?

Natural and legal persons can lodge a Data Act complaint with the relevant if they consider that their rights under the Regulation have been infringed. The complaint can be individual or, where relevant, collective.

The complaint may be lodged with the in the Member State of the person's habitual residence, place of work, or establishment. If the right authority is unclear, the data coordinator must provide the information needed to lodge the complaint with the appropriate competent authority.

  • Record whether the complainant is a user, data holder, data recipient, cloud customer, provider, public sector body, or other affected person.
  • Route the complaint by residence, place of work, establishment, or the relevant Data Act competence rule; do not invent a national authority name unless it is confirmed from the Commission register or the Member State source.
  • Keep the complaint text, date received, affected Data Act right, counterparty, product or service, and the authority or coordinator contacted.
Question 2

What should a competent authority do with a Data Act complaint?

Competent authorities must handle complaints about alleged Data Act infringements, investigate the subject matter to the extent appropriate, and keep complainants informed of progress and outcome in accordance with national law. They also cooperate with other competent authorities, the Commission, the EDIB, data protection authorities, sectoral authorities, and electronic-communications authorities where the issue crosses regimes.

For an implementation playbook, avoid promising a fixed national procedure unless the specific Member State source confirms it. The Data Act itself supports a practical intake record: complaint, alleged infringement, authority route, investigation status, cooperation needs, outcome, and any corrective action.

  • Separate the original commercial dispute from the authority complaint record.
  • Flag whether the complaint concerns trade secrets, personal data, sector-specific data access, cloud switching, switching charges, or a Chapter V public-sector request.
  • Track progress updates from the authority without adding unsupported national deadlines, penalty amounts, or procedural guarantees.
Recommended next step

Build a Data Act complaint and dispute record

Map complaint intake, authority routing, dispute settlement consent, court-preserved remedies, B2B and cloud dispute evidence, and corrective actions into one maintained Data Act register.

Question 3

When is a certified dispute settlement body the right route under the Data Act?

A certified dispute settlement body can be used for specified Data Act disputes between users, data holders, data recipients, customers, and providers of data processing services. The route covers disputes under Articles 4 and 5, disputes about fair, reasonable, non-discriminatory and transparent terms for making data available under Chapter III and Chapter IV, and disputes between cloud or other data-processing-service customers and providers about Articles 23 to 31.

Recourse to a dispute settlement body is voluntary and requires both parties' agreement. The Data Act also preserves access to courts.

  • This route supports FRAND data-sharing terms, transparent data availability terms, trade-secret withholding, suspension or refusal disputes, safety/security restrictions, unfair B2B data-access terms, and cloud switching or porting disputes.
  • Before referral, record the parties, disputed Data Act provision, requested outcome, current contract clause, fee or compensation position, and whether both sides agree to use the body.
  • Check that the dispute has not already been brought before another dispute settlement body or a Member State court or tribunal.
Question 4

Are dispute settlement body decisions binding under the Data Act?

A dispute settlement body decision is binding only if the parties explicitly consent to its binding nature before the proceeding starts. The body must give the parties a chance to express their views, share the other side's submissions and expert statements, and allow comments on those materials.

The body must adopt its decision within 90 days of receiving a covered request. The decision must be in writing or on a durable medium and supported by reasons. Fees or fee-calculation mechanisms must be known before the parties request a decision. The body must refuse a request already brought before another dispute settlement body or a Member State court or tribunal.

  • Keep a written record of whether the parties consented to a binding decision before the proceeding started.
  • Preserve submissions, expert statements, comments, fee disclosures, the decision, reasons, and implementation actions.
  • Do not describe dispute settlement as replacing judicial remedies; Article 10 and Article 39 preserve court routes.
Question 5

How do complaints, dispute settlement, and courts fit together under the Data Act?

The Data Act uses parallel routes. A person can complain to a without losing other administrative or judicial remedies. Affected natural and legal persons also have a right to an effective judicial remedy against legally binding competent-authority decisions.

If a fails to act on a complaint, affected persons must have, in accordance with national law, either an effective judicial remedy or access to review by an impartial body with appropriate expertise. Proceedings are brought before the courts or tribunals of the Member State of the competent authority against which the judicial remedy is sought.

  • Do not force all Data Act disputes into a single internal escalation path.
  • For each matter, tag the route as authority complaint, voluntary dispute settlement, court remedy, or internal commercial escalation.
  • Keep the legally binding authority decision, failure-to-act evidence, appeal deadline source, and court or review route separately from the business negotiation file.
Question 6

What changes for B2B data-sharing and unfair-contract disputes under the Data Act?

For mandatory B2B data sharing, Data Act disputes often concern whether terms for making data available are fair, reasonable, non-discriminatory, and transparent. The dispute file should show the legal obligation to make data available, the data requested, compensation basis, technical conditions, transparency information, and the counterparty category used for non-discrimination analysis.

For unfair contractual terms, focus on the specific term concerning access to and use of data, or liability and remedies for data-related obligations. The Commission FAQ states that, if a party disputes the unfairness assessment and does not withdraw the term, the matter can be brought to a , courts, or a dispute settlement body if the other party agrees.

  • Do not treat every commercial disagreement as a Data Act dispute; identify the Data Act chapter, term, data, party role, and alleged unfairness or FRAND issue.
  • For SMEs and non-profit research organisations, record the compensation position carefully because the Commission FAQ says reasonable compensation cannot include a profit margin for those recipients.
  • Keep the imposed clause, negotiation history, comparable recipient analysis, calculation inputs, withdrawal request, and response.
Question 7

How should a dispute about a business-to-government request be documented?

For business-to-government requests, the complaint or objection record should focus on whether the Chapter V request is specific, transparent, proportionate, tied to an exceptional need, and limited to the data and duration required for the public-interest task. The Data Act also gives competent authorities the task of examining Chapter V requests.

If a public-sector request is challenged, keep the request, legal basis, exceptional-need explanation, requested data categories, purpose, duration, confidentiality measures, personal-data analysis, response, and any competent-authority or court route.

  • Separate public-emergency requests from non-emergency exceptional-need requests.
  • Record whether the request is from a Member State public sector body, the Commission, the ECB, or a Union body.
  • Preserve any notification, publication, refusal, or authority correspondence connected with the request.
Question 8

How should cloud switching and data-processing-service disputes be routed under the Data Act?

Customers and providers of data processing services can use certified dispute settlement bodies for disputes about breaches of customer rights and provider obligations under Articles 23 to 31. These include switching, porting, contractual transparency, assistance, service continuity, exportable data, switching charges, and technical aspects of switching.

Competent authorities responsible for Articles 23 to 31 and Articles 34 and 35 must have experience in data and electronic communications services. They also cooperate to enforce those provisions consistently with other Union law and self-regulation applicable to providers of data processing services.

  • Keep the switching request, notice period, requested destination or on-premises route, exportable data list, digital assets, assistance given, continuity risks, security measures, and completion or failure date.
  • If the provider claims the 30-day transitional period is technically unfeasible, preserve the customer notification, justification, and proposed alternative transitional period.
  • For charges, keep standard service fees, early termination penalties, any reduced switching charges, cost basis, and the date range that controls the charge.
Question 9

What evidence should teams keep for a Data Act complaint or dispute?

A useful evidence file lets a reviewer identify the Data Act role, route, legal issue, disputed data or service, affected counterparty, chronology, source basis, decision maker, and outcome without reconstructing the matter from informal messages.

Keep facts separate from legal conclusions. The same complaint may involve a , a data coordinator, a certified dispute settlement body, GDPR supervisory authority involvement, sectoral authority coordination, or a court remedy.

  • Intake: complainant, counterparty, Data Act role, Member State link, product, related service, cloud service, or public-sector request.
  • Issue: alleged infringement, affected article or chapter, disputed term, refusal, suspension, switching charge, technical obstacle, compensation, trade secret, personal-data issue, or B2G request defect.
  • Route: independent review owner, or data coordinator contacted, dispute settlement consent, court or review route, and cross-authority coordination.
  • Outcome: decision, reasons, corrective action, resumed sharing or switching, rejected claim, authority update, settlement body decision, court result, and repeat root cause.
  • Keep the exact article or Commission FAQ passage, source URL and version, decision date, reviewer, national authority-routing source, and linked clause, complaint, correspondence, or switching record.
  • Assign accountable legal, operational-fix, and evidence-retention owners with due dates, consulted teams, authority-contact responsibility, and a review trigger when the facts or official position change.
Primary sources

References and citations

eur-lex.europa.eu10 citations
Referenced sections
  • Binding Data Act text for Articles 10, 37, 38, 39, 40, 41, and related cloud switching and B2G provisions.
  • Article 38 gives natural and legal persons the complaint right and explains the data coordinator's routing role.
  • Article 37 defines competent-authority tasks, including complaint handling, investigations, cooperation, and switching-charge enforcement.
Show 7 more
  • Article 10 defines the disputes that can go to certified dispute settlement bodies and preserves court remedies.
  • Article 10 sets the fee-disclosure rule, procedural participation rights, 90-day decision period, reasoned decision requirement, and binding-consent rule.
  • Articles 38 and 39 preserve administrative and judicial remedies and set the effective judicial remedy route.
  • Article 10 covers FRAND and transparent data-availability disputes; Article 41 points to model terms for data access, compensation, trade secrets, and cloud contracts.
  • Article 37 gives competent authorities the task of examining Chapter V requests and Article 38 provides the complaint route.
  • Articles 10 and 37 connect cloud switching disputes to certified dispute settlement bodies and specialist competent-authority experience.
  • Articles 10, 37, 38, and 39 support the evidence fields for complaint handling, dispute settlement, authority decisions, and judicial remedies.
digital-strategy.ec.europa.eu4 citations
Referenced sections
  • Commission overview used for competent authorities, data coordinators, certified dispute settlement bodies, B2G requests, and cloud switching context.
  • Commission explainer states that data coordinators act as national one-stop shops and that the Commission maintains a register.
  • Commission explainer describes Chapter V exceptional-need requests, public emergencies, non-emergency requests, and the once-only principle.
Show 1 more
  • Commission explainer describes Chapter VI switching, portability, contract transparency, open interfaces, functional equivalence, and switching charges.
ec.europa.eu3 citations
Referenced sections
  • Commission FAQ used for stakeholder-facing explanations of dispute settlement, unfair B2B terms, compensation, and complaint routing.
  • Commission FAQ Question 40 explains who can rely on the dispute settlement mechanism and under which conditions.
  • Commission FAQ Questions 39 to 42 explain compensation, dispute settlement, and unfair B2B data-sharing terms.
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Commission helpdesk page used for practical support topics and routing context for Data Act implementation questions.
  • Commission helpdesk page identifies common support topics, including data access, sharing obligations, user rights, cloud switching, and interoperability.
Show all related guides (61)

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 Enforcement and Competent Authorities FAQ

FAQ on who enforces the EU Data Act, how complaints work, how Member States set penalties, when dispute settlement can be used, and when GDPR authorities remain responsible.

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.