--- title: "Data Act Complaints and Dispute Settlement FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/complaints-and-dispute-settlement" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/complaints-and-dispute-settlement" author: "Sorena AI" description: "FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act complaints" - "Data Act dispute settlement" - "competent authority" - "data coordinator" - "B2B data sharing" - "cloud switching" - "EU Data Act" - "Regulation (EU) 2023/2854" - "competent authorities" - "dispute settlement bodies" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # Data Act Complaints and Dispute Settlement FAQ FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records. *FAQ* *EU* *Data Act* ## EU Data Act Complaints and Dispute Settlement FAQ How to route Data Act complaints and disputes without overclaiming national enforcement detail. Use this FAQ to 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. The Data Act gives natural and legal persons a complaint route to competent authorities, preserves judicial remedies, and creates access to certified dispute settlement bodies for specified data-sharing and data-processing-service disputes. This FAQ focuses on routing and evidence: who can complain, when a dispute settlement body fits, what remains for courts or authorities, and what records product, legal, procurement, support, and cloud teams should keep. Timings in this page are source-linked; verify current legal source language before implementation decisions. ## Who can complain to a Data Act competent authority for Complaints And Dispute Settlement implementation evidence? Natural and legal persons can lodge a Data Act complaint with the relevant competent authority 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 competent authority 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 38 gives natural and legal persons the complaint right and explains the data coordinator's routing role. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer states that data coordinators act as national one-stop shops and that the Commission maintains a register. ## What should a competent authority do with a Data Act complaint for Complaints And Dispute Settlement implementation evidence? 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 internal 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 37 defines competent-authority tasks, including complaint handling, investigations, cooperation, and switching-charge enforcement. ## 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. This is not a mandatory first step. The Commission FAQ explains that recourse to a dispute settlement body is voluntary and requires agreement by both parties. The Data Act also preserves access to courts. - Use this route for FRAND data-sharing terms, transparent data availability terms, trade-secret or safety/security handbrake disputes, 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 10 defines the disputes that can go to certified dispute settlement bodies and preserves court remedies. - [European Commission - Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Question 40 explains who can rely on the dispute settlement mechanism and under which conditions. ## Are dispute settlement body decisions binding under the Data Act? The Data Act context is the starting point for this answer. 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. - 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 10 sets the fee-disclosure rule, procedural participation rights, 90-day decision period, reasoned decision requirement, and binding-consent rule. ## 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 competent authority 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 competent authority 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 38 and 39 preserve administrative and judicial remedies and set the effective judicial remedy route. ## 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 competent authority, 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 10 covers FRAND and transparent data-availability disputes; Article 41 points to model terms for data access, compensation, trade secrets, and cloud contracts. - [European Commission - Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 39 to 42 explain compensation, dispute settlement, and unfair B2B data-sharing terms. ## How should B2G request disputes be evidenced under the Data Act for Complaints And Dispute Settlement implementation evidence? 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. Do not add unsupported national enforcement details. 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 37 gives competent authorities the task of examining Chapter V requests and Article 38 provides the complaint route. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer describes Chapter V exceptional-need requests, public emergencies, non-emergency requests, and the once-only principle. ## How should cloud switching and data-processing-service disputes be routed under the Data Act? The Data Act context is the starting point for this answer. 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 10 and 37 connect cloud switching disputes to certified dispute settlement bodies and specialist competent-authority experience. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer describes Chapter VI switching, portability, contract transparency, open interfaces, functional equivalence, and switching charges. ## 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 competent authority, 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, competent authority 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. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 10, 37, 38, and 39 support the evidence fields for complaint handling, dispute settlement, authority decisions, and judicial remedies. - [European Commission - Data Act Legal Helpdesk](https://digital-strategy.ec.europa.eu/en/policies/data-act-legal-helpdesk?ref=sorena.io) - Commission helpdesk page identifies common support topics, including data access, sharing obligations, user rights, cloud switching, and interoperability. ## What Data Act source evidence should teams keep for the Complaints And Dispute Settlement FAQ decision? For complaints and dispute settlement, teams should keep the exact Data Act article or Commission guidance that supports the answer, plus the issue type, the affected workflow, and the date the decision was made. The most useful evidence is a source URL, a short rationale for why the provision applies, and a linked implementation record showing who reviewed the question and what follow-up action was assigned. - Map each FAQ answer to the relevant Data Act article or Commission FAQ question rather than to a generic source placeholder. - Store the source URL, issue type, decision date, reviewer, and implementation artifact in the same record so the answer can be checked later. - If the answer depends on Member State routing, note the competent authority or data coordinator source used for that routing decision. ## How should teams assign ownership for Data Act Complaints And Dispute Settlement implementation work? Ownership of the Data Act question should sit with the team that can actually change the process: legal for the interpretation, product or engineering for technical access, procurement for vendor terms, support for intake routing, and cloud operations for switching or portability issues. One owner should be named for each action item, with consulted teams and evidence dependencies listed separately so a later reviewer can see who approved the position and who has to execute it. - Assign one accountable owner for the legal interpretation, one for the operational fix, and one for evidence retention when the issue spans multiple teams. - Record the affected workflow, the decision maker, the due date, and the next review trigger instead of repeating a generic template sentence. - If the matter touches complaints, dispute settlement, or authority escalation, note who will contact the competent authority or data coordinator. ## Which Data Act implementation evidence makes the Complaints And Dispute Settlement answer usable later? Data Act evidence is usable later when a reviewer can tell what decision was made, why it was made, and what concrete record supports it. That means the file should show the applicable article, the affected data or service, the route chosen, and the follow-up action. Useful evidence is specific: source URLs, contract clauses, complaint records, dispute settlement forms, authority correspondence, switching logs, and implementation notes that show the decision can be recreated without guessing. - Keep the source URL, issue summary, decision date, owner, and follow-up task together. - Attach the contract clause, complaint reference, authority email, or switching log that supports the answer. - Add the review trigger so the answer can be checked again if the Data Act source, FAQ, or guidance changes. ## Primary sources - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding Data Act text for Articles 10, 37, 38, 39, 40, 41, and related cloud switching and B2G provisions. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview used for competent authorities, data coordinators, certified dispute settlement bodies, B2G requests, and cloud switching context. - [European Commission - Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for stakeholder-facing explanations of dispute settlement, unfair B2B terms, compensation, and complaint routing. - [European Commission - Data Act Legal Helpdesk](https://digital-strategy.ec.europa.eu/en/policies/data-act-legal-helpdesk?ref=sorena.io) - Commission helpdesk page used for practical support topics and routing context for Data Act implementation questions. ## Topic Guides - [Data Act and Common European Data Spaces](/artifacts/eu/data-act/data-act-and-common-european-data-spaces.md): How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring. - [Data Act and Data Governance Act Overlap FAQ](/artifacts/eu/data-act/faq/data-governance-act-overlap.md): FAQ explaining where the EU Data Act and Data Governance Act overlap, how they differ, and how to route product, cloud, public-sector reuse, intermediary, and data altruism workflows. - [Data Act and GDPR Personal Data Overlap FAQ](/artifacts/eu/data-act/faq/gdpr-personal-data-overlap.md): 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. - [Data Act Audit Evidence And Request Logs FAQ](/artifacts/eu/data-act/faq/audit-evidence-and-request-logs.md): FAQ for Data Act request logs covering user and third-party access, B2G exceptional need requests, cloud switching records, contract terms, trade secrets, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Clauses](/artifacts/eu/data-act/b2b-data-sharing-contract-clauses.md): 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](/artifacts/eu/data-act/b2b-data-sharing-contract-template.md): 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](/artifacts/eu/data-act/b2g-exceptional-need-requests.md): A grounded 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](/artifacts/eu/data-act/cloud-switching-compliance-checklist.md): A grounded EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence. - [Data Act Cloud Switching Contract Terms FAQ](/artifacts/eu/data-act/faq/cloud-switching-contract-terms.md): FAQ on EU Data Act cloud switching contract terms: Article 25 clauses, assistance, notice, transition, charges, export, termination, interoperability, and records. - [Data Act Cloud Switching Fees And Deadlines FAQ](/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines.md): FAQ on EU Data Act cloud switching charges, 2027 fee removal, notice periods, transition windows, data retrieval, contract terms, and evidence records. - [Data Act Exportable Data and Metadata FAQ](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md): FAQ explaining which product, related service, metadata, and cloud switching data must be exportable under the EU Data Act, and which data can be excluded. - [Data Act FAQ for Aftermarket Repair and Mobility Services](/artifacts/eu/data-act/faq/aftermarket-repair-and-mobility-services.md): FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services. - [Data Act Functional Equivalence FAQ](/artifacts/eu/data-act/faq/functional-equivalence.md): FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence. - [Data Act Indirect Access Request Flows FAQ](/artifacts/eu/data-act/faq/indirect-access-request-flows.md): FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited. - [Data Act International Government Access FAQ](/artifacts/eu/data-act/faq/international-government-access.md): FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers. - [Data Act Interoperability Standards FAQ](/artifacts/eu/data-act/faq/interoperability-standards.md): FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614. - [Data Act Model Contractual Terms FAQ](/artifacts/eu/data-act/faq/model-contractual-terms.md): 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. - [Data Act Public Emergency Requests FAQ](/artifacts/eu/data-act/faq/public-emergency-requests.md): FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records. - [Data Act Smart Contracts for Data Sharing](/artifacts/eu/data-act/smart-contracts-for-data-sharing.md): 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 SME Exceptions and Startups FAQ](/artifacts/eu/data-act/faq/sme-exceptions-and-startups.md): 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](/artifacts/eu/data-act/faq/trade-secret-technical-protection-measures.md): FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence. - [Data Act Trade Secrets and Protection Measures](/artifacts/eu/data-act/trade-secrets-and-protection.md): 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](/artifacts/eu/data-act/unfair-contractual-terms.md): 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](/artifacts/eu/data-act/vehicle-data-guidance.md): Commission-grounded 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](/artifacts/eu/data-act/data-act-vs-gdpr.md): 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 and Common European Data Spaces FAQ](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md): 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 Applicability Test](/artifacts/eu/data-act/applicability-test.md): 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 Application Dates And Transition FAQ](/artifacts/eu/data-act/faq/application-dates-and-transition.md): 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 3 Pre-Contract Information](/artifacts/eu/data-act/pre-contractual-information-obligations.md): 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 Article 36 Smart Contract Controls FAQ](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md): 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](/artifacts/eu/data-act/faq/compensation-for-b2b-data-sharing.md): 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](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md): 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](/artifacts/eu/data-act/faq/b2g-exceptional-need.md): 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 Checklist for Product, Cloud, and Contract Teams](/artifacts/eu/data-act/checklist.md): A grounded 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](/artifacts/eu/data-act/cloud-switching-and-exit-plans.md): A grounded EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records. - [EU Data Act Cloud Switching Procurement FAQ](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md): 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 Compliance Program](/artifacts/eu/data-act/compliance.md): 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](/artifacts/eu/data-act/scope-connected-products-and-data-types.md): Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs. - [EU Data Act Connected Product Scope FAQ](/artifacts/eu/data-act/faq/scope-connected-products.md): 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 Processing Service Switching](/artifacts/eu/data-act/data-processing-services-switching.md): A grounded EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure. - [EU Data Act data spaces interoperability FAQ](/artifacts/eu/data-act/faq/data-spaces-interoperability.md): 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 deadlines and compliance calendar](/artifacts/eu/data-act/deadlines-and-compliance-calendar.md): A source-linked 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 Direct Access by Design FAQ](/artifacts/eu/data-act/faq/direct-access-by-design.md): 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](/artifacts/eu/data-act/faq/enforcement-and-competent-authorities.md): 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 FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates](/artifacts/eu/data-act/faq.md): Grounded EU Data Act FAQ index covering connected-product data access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, trade secrets, and application dates. - [EU Data Act Non-Emergency Public-Sector Requests FAQ](/artifacts/eu/data-act/faq/non-emergency-public-sector-requests.md): 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 Non-Personal Data and Mixed Datasets FAQ](/artifacts/eu/data-act/faq/non-personal-data-and-mixed-datasets.md): 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. - [EU Data Act Penalties and Enforcement](/artifacts/eu/data-act/penalties-and-fines.md): Grounded guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary. - [EU Data Act Pre-Contractual Information FAQ](/artifacts/eu/data-act/faq/pre-contractual-information.md): 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](/artifacts/eu/data-act/faq/product-data-and-service-data.md): 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 Readily Available Data FAQ](/artifacts/eu/data-act/faq/readily-available-data.md): 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](/artifacts/eu/data-act/faq/related-services.md): 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 requirements](/artifacts/eu/data-act/requirements.md): Source-grounded EU Data Act requirements for connected-product data access, B2B sharing terms, B2G exceptional needs, cloud switching, smart contracts, interoperability, GDPR boundaries, and records. - [EU Data Act Smart Contracts for Data Sharing FAQ](/artifacts/eu/data-act/faq/smart-contracts-for-data-sharing.md): 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](/artifacts/eu/data-act/faq/third-party-data-sharing.md): 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](/artifacts/eu/data-act/faq/trade-secrets-safeguards.md): 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](/artifacts/eu/data-act/faq/unfair-contractual-terms.md): 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 User Access and Portability Rights](/artifacts/eu/data-act/access-rights-and-portability.md): 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 Users, Data Holders, and Recipients FAQ](/artifacts/eu/data-act/faq/users-data-holders-and-recipients.md): 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](/artifacts/eu/data-act/faq/vehicle-data-guidance.md): 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 vs Data Governance Act](/artifacts/eu/data-act/data-act-vs-data-governance-act.md): 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. *Recommended next step* *Placement: after evidence section* ## 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. - [Open Research Copilot](/solutions/research-copilot.md): Get cited answers on Data Act complaints, dispute settlement, B2B data sharing, B2G requests, and cloud switching. - [Discuss Data Act disputes](/contact.md): Review complaint-routing and evidence impacts across product, contract, procurement, support, and cloud operations. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/data-act/faq/complaints-and-dispute-settlement