EU Data Act
Understand EU Data Act rules for connected products, and third-party access, B2B and B2G data sharing, unfair terms, smart contracts and cloud switching.
This hub explains when a is in scope of the EU Data Act, what product data must be made available, which exceptions apply, and which chapter controls the next action.
Regulation (EU) 2023/2854 has applied since 12 September 2025. Use the chapter guides to validate product scope, access, B2B terms, public-sector requests, and cloud switching against the binding text and the facts of the case.
The Regulation applies from 12 September 2025. Article 3(1) design duties apply to connected products and related services placed on the market after 12 September 2026. Chapter IV reaches certain older long-term contracts from 12 September 2027, and the switching-charge ban starts 12 January 2027.
Chapter II focuses on raw and pre-processed data from connected products and related services that is readily available to the , including relevant metadata. Content and highly enriched inferred or derived outputs normally sit outside this access set; personal data, trade secrets, security restrictions, and the Article 7 SME exclusion need separate checks.
The page cluster covers and third-party access, B2B terms and compensation, B2G exceptional-need requests, cloud switching, data-space interoperability, smart contracts, and enforcement pathways.
Check whether the item generates or collects use or environment data, can communicate that data, and is not primarily a data-storage, processing, or transmission service. Then separate raw and pre-processed data from content and inferred or derived outputs.
Identify the through ownership, contractual use rights, or receipt of a ; identify who has the legal right or duty to make data available; and record the recipient, requester, customer, provider, or data-space role for the specific chapter.
Check B2B data-sharing terms, unfair unilaterally imposed clauses, B2G exceptional-need responses, cloud exit clauses, switching charges, and Article 36 smart-contract controls.
Track the Regulation's entry into force, general application date, Article 3(1) connected-product design date, Chapter IV contract transition, and the cloud switching-charge phase-out.
Start by deciding whether the Data Act applies to the product, service, data, contract, request, or cloud service in front of you. Then move to the access, contract, switching, evidence, deadline, or comparison guide that matches that decision.
Identify the regulated situation, the or , the data in scope, and whether the organisation is acting as , , data recipient, third party, or service provider.
Build the correct disclosure and contract path for users, recipients, public-sector bodies, and automated data-sharing arrangements while protecting security and trade secrets.
Map the customer exit process, contractual clocks, exportable data and digital assets, switching charges, functional-equivalence boundary, and applicable interoperability work.
Translate the assigned chapter into owned controls, retained evidence, application dates, enforcement decisions, and sector-specific implementation work.
Keep the Data Act separate from GDPR and the Data Governance Act, or use the FAQ when you already know the specific scope, access, contract, switching, or enforcement question to resolve.
Next steps
Confirm the product, data, contract, or request in question. Then assign the applicable Data Act chapter, request path, contract update, technical control, and retained record to the responsible team.
Answer EU Data Act scope, role, timing, contract, B2G, cloud switching, and smart-contract questions with cited outputs.
Keep Data Act sources, product facts, request records, contract evidence, cloud exit plans, and approvals connected.
Align Data Act application dates with product releases, contract renewals, and cloud switching milestones.
Review your connected-product, B2B sharing, B2G request, cloud switching, and evidence model.