--- title: "EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/items/page/4" author: "Sorena AI" description: "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." published_at: "2026-05-06" updated_at: "2026-05-25" keywords: - "EU Data Act FAQ" - "Data Act scope" - "connected product data" - "B2G data sharing" - "cloud switching" - "GDPR Data Act" - "EU Data Act" - "Data Act FAQ" - "Regulation (EU) 2023/2854" --- **[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) --- # EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates 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. *FAQ* *EU* *Data Act* ## EU Data Act FAQ hub Answers to the recurring EU Data Act questions that decide whether connected-product data, related-service data, B2G requests, cloud contracts, or smart-contract tooling need a compliance review. Use this index to orient product, legal, cloud, procurement, data protection, security, and public-sector request teams before opening the deeper topic modules. The EU Data Act, Regulation (EU) 2023/2854, creates horizontal rules for fair access to and use of data. Its FAQ set is not only about IoT data portability: it also covers mandatory B2B sharing terms, unfair contractual terms, public-sector access in exceptional need, cloud and edge switching, safeguards against unlawful third-country government access to non-personal data, interoperability, smart contracts, enforcement, and the boundary with GDPR. ## Browse sub-FAQ modules ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [Data Act Complaints and Dispute Settlement FAQ](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md) FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 13 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items Browse all indexed questions: [/artifacts/eu/data-act/faq/items](/artifacts/eu/data-act/faq/items.md) ## All FAQ items *Page 4 of 24. Showing 20 of 469 items.* ### [Who can complain to a Data Act competent authority for Complaints And Dispute Settlement implementation evidence?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#who-can-complain-to-a-data-act-competent-authority-for-complaints-and-dispute-settlement-implementation-evidence) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#what-should-a-competent-authority-do-with-a-data-act-complaint-for-complaints-and-dispute-settlement-implementation-evidence) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#when-is-a-certified-dispute-settlement-body-the-right-route-under-the-data-act) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#are-dispute-settlement-body-decisions-binding-under-the-data-act) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#how-do-complaints-dispute-settlement-and-courts-fit-together-under-the-data-act) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#what-changes-for-b2b-data-sharing-and-unfair-contract-disputes-under-the-data-act) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#how-should-b2g-request-disputes-be-evidenced-under-the-data-act-for-complaints-and-dispute-settlement-implementation-evidence) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#how-should-cloud-switching-and-data-processing-service-disputes-be-routed-under-the-data-act) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#what-evidence-should-teams-keep-for-a-data-act-complaint-or-dispute) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#what-data-act-source-evidence-should-teams-keep-for-the-complaints-and-dispute-settlement-faq-decision) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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. Sources for this answer: - [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. ### [How should teams assign ownership for Data Act Complaints And Dispute Settlement implementation work?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#how-should-teams-assign-ownership-for-data-act-complaints-and-dispute-settlement-implementation-work) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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. Sources for this answer: - [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. ### [Which Data Act implementation evidence makes the Complaints And Dispute Settlement answer usable later?](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md#which-data-act-implementation-evidence-makes-the-complaints-and-dispute-settlement-answer-usable-later) *Module: [Data Act Complaints and Dispute Settlement](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md)* 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. - 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. Sources for this answer: - [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. ### [What does the Data Act mean by readily available product and related service data?](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md#what-does-the-data-act-mean-by-readily-available-product-and-related-service-data) *Module: [Data Act Exportable Data and Metadata](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md)* The Data Act context is the starting point for this answer. For connected products and related services, the key scope term is readily available data. It means product data and related service data that a data holder lawfully obtains, or can lawfully obtain, from the connected product or related service without disproportionate effort beyond a simple operation. - Include sensor and status data that the product or related service generates and the data holder can access without disproportionate effort. - Treat pre-processed data as in scope when the processing makes the data understandable and usable before later analysis. - Do not label data as out of scope merely because the company calls it telemetry, logs, diagnostics, or operational data. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Defines product data, related service data, and readily available data, and sets the Article 3 and 4 access duties. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Explains that Chapter II covers raw and pre-processed connected-product and related-service data, including relevant metadata. ### [What metadata has to be provided with Data Act product and related service data?](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md#what-metadata-has-to-be-provided-with-data-act-product-and-related-service-data) *Module: [Data Act Exportable Data and Metadata](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md)* The Data Act context is the starting point for this answer. The metadata obligation is not a separate nice-to-have documentation exercise. Article 3 requires product data and related service data to include relevant metadata necessary to interpret and use the data. Article 4 uses the same standard where the user cannot directly access the data and the data holder must make readily available data accessible. - Map field names, units, timestamps, device or service identifiers, collection frequency, retention limits, and known quality constraints. - Explain data structures, data formats, vocabularies, classification schemes, taxonomies, and code lists where those are available and needed for use. - Flag trade-secret or security-related metadata only where a grounded Data Act limitation applies; do not use vague confidentiality labels to strip interpretive context. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Requires relevant metadata necessary to interpret and use connected-product and related-service data. - [Commission standardisation request for a European Trusted Data Framework](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Grounds practical metadata categories for discoverability, data structures, formats, vocabularies, taxonomies, code lists, and auditability in Data Act-related standardisation work. ### [Which export format should be used for connected-product and related-service data under the Data Act?](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md#which-export-format-should-be-used-for-connected-product-and-related-service-data-under-the-data-act) *Module: [Data Act Exportable Data and Metadata](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md)* The Data Act does not name one universal file type for every connected product or related service. Instead, it requires access in a comprehensive, structured, commonly used and machine-readable format. Where relevant and technically feasible, Article 3 also expects direct access by default, and Article 4 expects continuous and real-time access where relevant and technically feasible. - Document the chosen format and why it is commonly used and machine-readable for the data category. - Test that a user or authorized third party can parse the export with the published metadata, not just receive a file. - State any technical limits on continuous or real-time access in the access documentation. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Sets the required format standard for connected-product and related-service data access. ### [What must be disclosed before a connected product or related service contract is concluded under the Data Act?](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md#what-must-be-disclosed-before-a-connected-product-or-related-service-contract-is-concluded-under-the-data-act) *Module: [Data Act Exportable Data and Metadata](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md)* The Data Act context is the starting point for this answer. Before a connected product purchase, rent, or lease contract is concluded, the seller, renter, or lessor must give the user clear and comprehensible information about the type, format, and estimated volume of product data the product can generate, whether it can generate data continuously and in real time, where it can store data, retention information, and how the user can access, retrieve, or erase data. - Keep pre-contract copy aligned with the actual export catalogue and access route. - Use stable documentation or a durable web page where the user can store and reproduce the information. - Refresh the disclosure when product updates, related service changes, or retention changes affect generated or accessible data. 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 3 lists pre-contract information duties for connected products and related services. ### [What does exportable data mean for cloud and other data processing services under the Data Act?](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md#what-does-exportable-data-mean-for-cloud-and-other-data-processing-services-under-the-data-act) *Module: [Data Act Exportable Data and Metadata](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md)* The Data Act context is the starting point for this answer. For cloud and other data processing services, exportable data is a defined term used for switching obligations. It covers input and output data, including metadata, directly or indirectly generated or cogenerated by the customer's use of the data processing service. It excludes assets or data protected by intellectual property rights, or constituting a trade secret, of the provider or third parties. - List customer input data, output data, customer-generated digital assets, and metadata needed to restore use after switching. - Separate provider-owned service internals from customer exportable data so exclusions are narrow and reviewable. - Cover both switching to another provider and porting to on-premises ICT infrastructure. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Defines exportable data for Articles 23 to 31 and sets cloud switching and porting obligations. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Explains that cloud switching data includes input and output data, including metadata, generated by customer use of the service. ### [What cloud switching format and register information should customers receive under the Data Act?](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md#what-cloud-switching-format-and-register-information-should-customers-receive-under-the-data-act) *Module: [Data Act Exportable Data and Metadata](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md)* The Data Act context is the starting point for this answer. A provider of data processing services must give customers information on available switching and porting procedures, including available methods and formats, and known restrictions or technical limitations. The provider must also refer customers to an up-to-date online register with details of data structures, data formats, relevant standards, and open interoperability specifications in which the exportable data is available. - Publish a register that names data structures, formats, standards, and open interoperability specifications for exportable data. - Put known switching restrictions and technical limitations in the customer documentation before they become an exit dispute. - Keep the register current when interfaces, formats, common specifications, or harmonised standards change. 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 26 and 30 require switching procedure information, an online register, and machine-readable export where standards are not yet published. ### [Which data can be excluded from Data Act exports for exportability records?](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md#which-data-can-be-excluded-from-data-act-exports-for-exportability-records) *Module: [Data Act Exportable Data and Metadata](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md)* The Data Act context is the starting point for this answer. For connected products and related services, the ordinary access scope does not include inferred or derived information that results from additional investments into assigning values or insights, particularly through proprietary complex algorithms, unless the user and data holder agree otherwise. The Commission gives examples such as highly enriched data and content being outside the Chapter II scope. - Do not exclude raw or pre-processed connected-product data just because it is commercially sensitive. - Do not include films, media content, proprietary algorithms, provider service internals, or protected third-party assets simply because they appear in the same system. - Document each exclusion with the specific category: inferred or derived data, protected intellectual property, trade secret, security and integrity risk, or unavailable data. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Distinguishes in-scope raw and pre-processed data from inferred or derived information and excludes protected provider or third-party assets in cloud switching. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Explains that inferred or derived data and content are out of scope, and gives practical connected-product examples. ### [How should trade secrets and security limits be handled without blocking legitimate exports under the Data Act?](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md#how-should-trade-secrets-and-security-limits-be-handled-without-blocking-legitimate-exports-under-the-data-act) *Module: [Data Act Exportable Data and Metadata](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md)* The Data Act preserves trade secrets, but it does not allow a broad confidentiality label to erase the access right. For user access and third-party sharing, the data holder or trade secret holder must identify protected data, including in the relevant metadata, and agree proportionate technical and organisational measures to preserve confidentiality. - Identify trade-secret data and related metadata precisely before applying confidentiality measures. - Use proportionate safeguards such as confidentiality agreements, access controls, technical standards, and strict protocols where supported by the facts. - Keep written reasons for any withholding, suspension, refusal, or security restriction. 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 4 and 5 set trade-secret safeguards, withholding and refusal conditions, and security restriction rules. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Summarizes the Data Act trade-secret and security limitation mechanisms for connected-product data sharing. ## FAQ Pagination - Canonical index (page 1): [/artifacts/eu/data-act/faq/items](/artifacts/eu/data-act/faq/items.md) - Page 1 rule: `/page/1` is intentionally not generated; use the canonical index markdown URL. - Current page: 4 of 24 Pages: [1](/artifacts/eu/data-act/faq/items.md) | [2](/artifacts/eu/data-act/faq/items/page/2.md) | [3](/artifacts/eu/data-act/faq/items/page/3.md) | [4](/artifacts/eu/data-act/faq/items/page/4.md) | [5](/artifacts/eu/data-act/faq/items/page/5.md) | [6](/artifacts/eu/data-act/faq/items/page/6.md) | [7](/artifacts/eu/data-act/faq/items/page/7.md) | [8](/artifacts/eu/data-act/faq/items/page/8.md) | [9](/artifacts/eu/data-act/faq/items/page/9.md) | [10](/artifacts/eu/data-act/faq/items/page/10.md) | [11](/artifacts/eu/data-act/faq/items/page/11.md) | [12](/artifacts/eu/data-act/faq/items/page/12.md) | [13](/artifacts/eu/data-act/faq/items/page/13.md) | [14](/artifacts/eu/data-act/faq/items/page/14.md) | [15](/artifacts/eu/data-act/faq/items/page/15.md) | [16](/artifacts/eu/data-act/faq/items/page/16.md) | [17](/artifacts/eu/data-act/faq/items/page/17.md) | [18](/artifacts/eu/data-act/faq/items/page/18.md) | [19](/artifacts/eu/data-act/faq/items/page/19.md) | [20](/artifacts/eu/data-act/faq/items/page/20.md) | [21](/artifacts/eu/data-act/faq/items/page/21.md) | [22](/artifacts/eu/data-act/faq/items/page/22.md) | [23](/artifacts/eu/data-act/faq/items/page/23.md) | [24](/artifacts/eu/data-act/faq/items/page/24.md) [Previous page](/artifacts/eu/data-act/faq/items/page/3.md) | [Next page](/artifacts/eu/data-act/faq/items/page/5.md) *Recommended next step* *Placement: before sources* ## Turn a Data Act FAQ answer into a scoped review Review one product, dataset, cloud contract, public-sector request, or smart-contract deployment against the cited Data Act source and keep the scope, role, evidence, and unresolved questions together. - [Open Research Copilot](/solutions/research-copilot.md): Check Data Act scope, GDPR boundaries, cloud switching, and contract questions with cited source outputs. - [Talk through Data Act implementation](/contact.md): Review one connected product, data-sharing contract, cloud switch, or public-sector request before committing to an implementation path. --- [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/items/page/4