--- 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/11" 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 11 of 24. Showing 20 of 469 items.* ### [What evidence should teams keep for a Data Act and common European data spaces decision?](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md#what-evidence-should-teams-keep-for-a-data-act-and-common-european-data-spaces-decision) *Module: [EU Data Act and Common European Data Spaces](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md)* For a Data Act and common European data spaces decision, keep the source clause, Commission guidance, actor role, dataset or service, request or contract trigger, and the owner who approved the interpretation. - Link the decision to a cited Data Act source URL and the relevant Article 33 requirement. - Store the owner, affected workflow, evidence artifact, and review trigger. - Keep unresolved assumptions and the review date together with the implementation record. 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 Article 33 data-space interoperability duties, smart-contract references, and broader fair-access context. - [European Commission - Data Governance Act explained](https://digital-strategy.ec.europa.eu/en/policies/data-governance-act-explained?ref=sorena.io) - Explains Data Governance Act trust mechanisms for voluntary sharing, protected public-sector data reuse, intermediaries, and data altruism. - [European Commission staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Defines common European data spaces as infrastructure plus governance in strategic sectors and public-interest domains. - [European Commission second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Provides current data-space context, including sector initiatives, support actions, Simpl, EDICs, standards, and interoperability work. - [Publications Office report on European data spaces](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Explains data-space design concepts such as decentralisation, automation, common standards, governance, and protected access. - [data.europa.eu - Public Procurement Data Space](https://data.europa.eu/en/PPDS?ref=sorena.io) - Sector example for public procurement data, TED resources, APIs, open data services, and procurement standards. - [data.europa.eu - European Legal Data Space](https://data.europa.eu/en/ELDS?ref=sorena.io) - Sector example for legal data, legal depositories, case-law collections, EUR-Lex material, and legal identifiers. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ### [Who should own Data Act implementation work for common European data spaces?](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md#who-should-own-data-act-implementation-work-for-common-european-data-spaces) *Module: [EU Data Act and Common European Data Spaces](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md)* For Data Act and common European data spaces work, the workflow should name the legal, product, procurement, cloud, support, or security owner who can change the affected process. - Assign one accountable owner per action. - Record the affected workflow and the implementation artifact. - Keep consulted teams and dependencies in a separate note, not as the owner. 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 Article 33 data-space interoperability duties, smart-contract references, and broader fair-access context. - [European Commission - Data Governance Act explained](https://digital-strategy.ec.europa.eu/en/policies/data-governance-act-explained?ref=sorena.io) - Explains Data Governance Act trust mechanisms for voluntary sharing, protected public-sector data reuse, intermediaries, and data altruism. - [European Commission staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Defines common European data spaces as infrastructure plus governance in strategic sectors and public-interest domains. - [European Commission second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Provides current data-space context, including sector initiatives, support actions, Simpl, EDICs, standards, and interoperability work. - [Publications Office report on European data spaces](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Explains data-space design concepts such as decentralisation, automation, common standards, governance, and protected access. - [data.europa.eu - Public Procurement Data Space](https://data.europa.eu/en/PPDS?ref=sorena.io) - Sector example for public procurement data, TED resources, APIs, open data services, and procurement standards. - [data.europa.eu - European Legal Data Space](https://data.europa.eu/en/ELDS?ref=sorena.io) - Sector example for legal data, legal depositories, case-law collections, EUR-Lex material, and legal identifiers. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ### [When should the Data Act and common European data spaces FAQ answer be reviewed again?](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md#when-should-the-data-act-and-common-european-data-spaces-faq-answer-be-reviewed-again) *Module: [EU Data Act and Common European Data Spaces](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md)* Review the Data Act and common European data spaces answer when the product, service model, dataset, customer role, public-sector request path, contract wording, or sector rulebook changes. - Review on any material change to the data space exchange or governance model. - Review when standards, APIs, or access terms change. - Review when the owner or the legal basis for the exchange 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 Article 33 data-space interoperability duties, smart-contract references, and broader fair-access context. - [European Commission - Data Governance Act explained](https://digital-strategy.ec.europa.eu/en/policies/data-governance-act-explained?ref=sorena.io) - Explains Data Governance Act trust mechanisms for voluntary sharing, protected public-sector data reuse, intermediaries, and data altruism. - [European Commission staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Defines common European data spaces as infrastructure plus governance in strategic sectors and public-interest domains. - [European Commission second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Provides current data-space context, including sector initiatives, support actions, Simpl, EDICs, standards, and interoperability work. - [Publications Office report on European data spaces](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Explains data-space design concepts such as decentralisation, automation, common standards, governance, and protected access. - [data.europa.eu - Public Procurement Data Space](https://data.europa.eu/en/PPDS?ref=sorena.io) - Sector example for public procurement data, TED resources, APIs, open data services, and procurement standards. - [data.europa.eu - European Legal Data Space](https://data.europa.eu/en/ELDS?ref=sorena.io) - Sector example for legal data, legal depositories, case-law collections, EUR-Lex material, and legal identifiers. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ### [Which EU Data Act obligations follow a connected-product dataset when it enters a common European data space?](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md#which-eu-data-act-obligations-follow-a-connected-product-dataset-when-it-enters-a-common-european-data-space) *Module: [EU Data Act and Common European Data Spaces](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md)* Under the Data Act, the access, use, and trade-secret rules that attach to connected-product and related-service data do not disappear when that data is contributed to a data space; the Article 33 interoperability duties apply on top, but the underlying user access right and any safeguards still travel with the dataset. The data space is a sharing venue, not a way to shed those obligations. - Carry the Data Act access, use, and trade-secret obligations with the dataset into the data space. - Layer the Article 33 interoperability descriptions on top without displacing user and recipient rights. 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 Article 33 data-space interoperability duties, smart-contract references, and broader fair-access context. - [European Commission - Data Governance Act explained](https://digital-strategy.ec.europa.eu/en/policies/data-governance-act-explained?ref=sorena.io) - Explains Data Governance Act trust mechanisms for voluntary sharing, protected public-sector data reuse, intermediaries, and data altruism. - [European Commission staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Defines common European data spaces as infrastructure plus governance in strategic sectors and public-interest domains. - [European Commission second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Provides current data-space context, including sector initiatives, support actions, Simpl, EDICs, standards, and interoperability work. - [Publications Office report on European data spaces](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Explains data-space design concepts such as decentralisation, automation, common standards, governance, and protected access. - [data.europa.eu - Public Procurement Data Space](https://data.europa.eu/en/PPDS?ref=sorena.io) - Sector example for public procurement data, TED resources, APIs, open data services, and procurement standards. - [data.europa.eu - European Legal Data Space](https://data.europa.eu/en/ELDS?ref=sorena.io) - Sector example for legal data, legal depositories, case-law collections, EUR-Lex material, and legal identifiers. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ### [When does the EU Data Act generally start to apply, and what is the default application date?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#when-does-the-eu-data-act-generally-start-to-apply-and-what-is-the-default-application-date) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* The general application date is 12 September 2025. From that date, teams should treat the Data Act as live unless a specific article provides a different transition rule. - Record 12 September 2025 as the default application date. - Separate duties with their own transition rule instead of applying one date to every Data Act topic. - Keep evidence of updated request handling, customer notices, contract clauses, cloud-switching controls, and owner approval. 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 50 states the general application date and the chapter-specific transition rules. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission implementation page confirming that the Data Act applies since 12 September 2025. ### [Which product-design obligation is delayed until after 12 September 2026 under the Data Act?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#which-product-design-obligation-is-delayed-until-after-12-september-2026-under-the-data-act) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* The Data Act context is the starting point for this answer. Article 50 delays the obligation resulting from Article 3(1). It applies to connected products and related services placed on the market after 12 September 2026. - Keep a product-market-placement record for releases around 12 September 2026. - Tie Article 3(1) design work to the specific connected product and related service, not to the company as a whole. - Preserve release approvals, data-access design notes, and customer-facing information used at launch. 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 50 delays Article 3(1) for connected products and related services placed on the market after 12 September 2026. ### [When do Chapter III data-making obligations become relevant under the Data Act?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#when-do-chapter-iii-data-making-obligations-become-relevant-under-the-data-act) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* The Data Act context is the starting point for this answer. Article 50 says Chapter III applies in relation to obligations to make data available under Union law or national legislation adopted in accordance with Union law, where that law enters into force after 12 September 2025. - Do not apply Chapter III merely because a data-sharing request exists. - Record the Union or national legal obligation and its entry-into-force date. - Keep the data-sharing arrangement, fee position, transparency note, and approval evidence with the cited legal trigger. 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 50 limits Chapter III timing to obligations under Union or national law that enter into force after 12 September 2025. ### [How do the Chapter IV unfair-contract-term transition rules work under the Data Act?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#how-do-the-chapter-iv-unfair-contract-term-transition-rules-work-under-the-data-act) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* The Data Act context is the starting point for this answer. Chapter IV applies to contracts concluded after 12 September 2025. For contracts concluded on or before that date, Chapter IV applies from 12 September 2027 only if the contract is of indefinite duration or is due to expire at least 10 years from 11 January 2024. - Flag contracts concluded after 12 September 2025 for Chapter IV review at negotiation. - For pre-application contracts, evidence whether the contract is indefinite or expires at least 10 years from 11 January 2024. - Keep redlines, fallback clauses, negotiation notes, and the reason a term is treated as in or out of Chapter IV. 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 50 sets separate Chapter IV dates for new contracts and certain older indefinite or long-duration contracts. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ explains that the Chapter IV transition gives parties time to renegotiate older covered contracts. ### [What records should teams keep for Data Act application dates, cloud switching, and evidence review?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#what-records-should-teams-keep-for-data-act-application-dates-cloud-switching-and-evidence-review) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* For the Data Act, the best evidence file is a date-by-date register. It should show the legal trigger, the exact deadline, the action taken, the owner, and the source URL so a later reviewer can see why the team chose that date. - Keep a single timeline with the article number, date, action owner, and source URL for each milestone. - Track cloud switching separately from product-design and contract-transition deadlines. - Add a review trigger when an implementation date depends on a Commission repository publication or a contract 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) - Binding source for the application dates, transition rules, and switching-charge phase-out that should be cited in the evidence register. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission source for implementation context across connected products, contracts, cloud switching, and support tools. ### [What source evidence should teams keep for an EU Data Act application-date or transition decision?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#what-source-evidence-should-teams-keep-for-an-eu-data-act-application-date-or-transition-decision) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* Under the Data Act, keep the specific legal source that sets the date, not just a general note that the Regulation applies. The evidence should show the article, the deadline, and the exact source URL or official guidance used to make the decision. - Link each deadline to the exact Data Act article or recital used. - Store the owner, affected workflow, evidence artifact, and review trigger. - Keep the cited external URL, decision date, reviewer, and unresolved assumptions together. 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 Article 50 application and transition rules, Article 29 switching-charge phase-out, Article 40 penalty-rule notification, Article 41 model terms, and Article 49 evaluation. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation confirming application since 12 September 2025 and summarizing cloud switching, contracts, connected products, and implementation support. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ support for Chapter IV contract transition treatment and practical contract interpretation. - [European Commission - EU Data Act gives users control over data from connected devices](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release on the Data Act starting to apply and implementation tools such as helpdesk, guidance, model terms, and cloud standard clauses. ### [How should teams assign ownership for Data Act application-date and transition work?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#how-should-teams-assign-ownership-for-data-act-application-date-and-transition-work) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* Under the Data Act, the right owner for an application-date or transition decision is the team that can actually change the affected process. That is usually legal, product, procurement, cloud operations, security, or compliance, depending on the obligation. - Assign one accountable owner per deadline decision. - Map the application date to the team that can change the workflow or contract. - Record consulted teams and evidence dependencies separately from the owner. 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 Article 50 application and transition rules, Article 29 switching-charge phase-out, Article 40 penalty-rule notification, Article 41 model terms, and Article 49 evaluation. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation confirming application since 12 September 2025 and summarizing cloud switching, contracts, connected products, and implementation support. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ support for Chapter IV contract transition treatment and practical contract interpretation. - [European Commission - EU Data Act gives users control over data from connected devices](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release on the Data Act starting to apply and implementation tools such as helpdesk, guidance, model terms, and cloud standard clauses. ### [Which evidence makes an EU Data Act transition answer reusable and auditable later?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#which-evidence-makes-an-eu-data-act-transition-answer-reusable-and-auditable-later) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* Under the Data Act, capture the source, the decision, and the implementation proof in one place. Without those three parts, a later reviewer cannot tell whether the deadline was based on Article 50, Article 29, Article 25, or another provision. - Keep source URL, decision date, and implementation artifact together. - Capture contract clauses, release notes, notices, or control updates. - Store the reviewer name and the next review trigger with the record. 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 Article 50 application and transition rules, Article 29 switching-charge phase-out, Article 40 penalty-rule notification, Article 41 model terms, and Article 49 evaluation. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation confirming application since 12 September 2025 and summarizing cloud switching, contracts, connected products, and implementation support. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ support for Chapter IV contract transition treatment and practical contract interpretation. - [European Commission - EU Data Act gives users control over data from connected devices](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release on the Data Act starting to apply and implementation tools such as helpdesk, guidance, model terms, and cloud standard clauses. ### [When should the Data Act application-dates answer be reviewed again?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#when-should-the-data-act-application-dates-answer-be-reviewed-again) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* Under the Data Act, review the answer again when the product, service model, contract wording, or legal source changes. A transition answer can go stale as soon as a new product is launched, a contract is renewed, or the Commission publishes interoperability references. - Review after product, service, contract, or legal-source changes. - Set both a date-based review and an event-based trigger. - Update the record when a Commission publication changes the compliance clock. 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 Article 50 application and transition rules, Article 29 switching-charge phase-out, Article 40 penalty-rule notification, Article 41 model terms, and Article 49 evaluation. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation confirming application since 12 September 2025 and summarizing cloud switching, contracts, connected products, and implementation support. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ support for Chapter IV contract transition treatment and practical contract interpretation. - [European Commission - EU Data Act gives users control over data from connected devices](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release on the Data Act starting to apply and implementation tools such as helpdesk, guidance, model terms, and cloud standard clauses. ### [What should teams avoid when applying the Data Act transition FAQ answer?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#what-should-teams-avoid-when-applying-the-data-act-transition-faq-answer) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* Teams should avoid using one deadline for every Data Act topic. The Regulation has different clocks for general application, product design, cloud switching, contract transition, and interoperability. - Do not copy one date across unrelated obligations. - Do not rely on internal notes without a source URL. - Do not treat the general application date as overriding specific transition rules. 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 Article 50 application and transition rules, Article 29 switching-charge phase-out, Article 40 penalty-rule notification, Article 41 model terms, and Article 49 evaluation. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation confirming application since 12 September 2025 and summarizing cloud switching, contracts, connected products, and implementation support. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ support for Chapter IV contract transition treatment and practical contract interpretation. - [European Commission - EU Data Act gives users control over data from connected devices](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release on the Data Act starting to apply and implementation tools such as helpdesk, guidance, model terms, and cloud standard clauses. ### [By when must cloud providers remove switching charges under the EU Data Act transition timeline?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#by-when-must-cloud-providers-remove-switching-charges-under-the-eu-data-act-transition-timeline) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* Under the Data Act, switching charges, including data egress fees, must be fully removed by 12 January 2027, and during the interim period any charge a provider imposes must not exceed the costs it actually incurs. Teams should track this date separately from the general 12 September 2025 application date. - Track 12 January 2027 as the date switching charges must be removed. - Cap any interim switching charge at the provider's actual costs until then. 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 Article 50 application and transition rules, Article 29 switching-charge phase-out, Article 40 penalty-rule notification, Article 41 model terms, and Article 49 evaluation. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation confirming application since 12 September 2025 and summarizing cloud switching, contracts, connected products, and implementation support. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ support for Chapter IV contract transition treatment and practical contract interpretation. - [European Commission - EU Data Act gives users control over data from connected devices](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release on the Data Act starting to apply and implementation tools such as helpdesk, guidance, model terms, and cloud standard clauses. ### [How should teams treat existing contracts under the EU Data Act unfair-term transition rule?](/artifacts/eu/data-act/faq/application-dates-and-transition.md#how-should-teams-treat-existing-contracts-under-the-eu-data-act-unfair-term-transition-rule) *Module: [EU Data Act Application Dates And Transition](/artifacts/eu/data-act/faq/application-dates-and-transition.md)* Under the Data Act, the unfair-contract-term controls in Chapter IV apply to new contracts from the application date, while contracts concluded on or before 12 September 2025 are given a longer runway before the controls bite, provided they are of indefinite duration or still have time to run. Teams should classify each contract by its conclusion date. - Classify each contract by conclusion date to apply the right Chapter IV transition rule. - Flag legacy indefinite or long-running contracts for renegotiation before the transition window closes. 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 Article 50 application and transition rules, Article 29 switching-charge phase-out, Article 40 penalty-rule notification, Article 41 model terms, and Article 49 evaluation. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation confirming application since 12 September 2025 and summarizing cloud switching, contracts, connected products, and implementation support. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ support for Chapter IV contract transition treatment and practical contract interpretation. - [European Commission - EU Data Act gives users control over data from connected devices](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release on the Data Act starting to apply and implementation tools such as helpdesk, guidance, model terms, and cloud standard clauses. ### [When does EU Data Act Article 36 apply to a smart contract for Article 36 Smart Contract Controls implementation evidence?](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md#when-does-eu-data-act-article-36-apply-to-a-smart-contract-for-article-36-smart-contract-controls-implementation-evidence) *Module: [EU Data Act Article 36 Smart Contract Controls](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md)* Article 36 applies when a smart contract is used in the context of executing an agreement, or part of an agreement, to make data available. The trigger is not simply using blockchain, automation, or an electronic ledger. The trigger is the use of smart-contract functionality for execution of a data-sharing agreement covered by the Data Act context. - Keep in scope: smart-contract logic that executes data-sharing terms or makes data available under the agreement. - Do not treat every internal automation or in-house-only smart contract as automatically covered by this FAQ. - Record whether the responsible party is the application vendor or, where no vendor exists, the person deploying smart contracts for others. 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 36 identifies the covered actors and the data-sharing-agreement context for smart contracts. ### [What controls does Article 36 require for smart contracts used in data-sharing agreements under the Data Act?](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md#what-controls-does-article-36-require-for-smart-contracts-used-in-data-sharing-agreements-under-the-data-act) *Module: [EU Data Act Article 36 Smart Contract Controls](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md)* The Data Act context is the starting point for this answer. Article 36 lists five essential requirements. The smart contract must be designed for robustness and access control; support safe termination and interruption; allow archiving and continuity when terminated or deactivated; be protected by rigorous governance-layer and smart-contract-layer access controls; and remain consistent with the terms of the data-sharing agreement it executes. - Robustness: test for functional errors and manipulation attempts by third parties. - Termination and interruption: define who can stop or reset operation and what mutual-consent condition applies under the agreement. - Archiving and continuity: preserve transactional data, smart contract logic, and code needed to audit past operations. 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 36(1) lists the essential requirements for covered smart contracts. ### [How should Article 36 access control be implemented and evidenced under the Data Act?](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md#how-should-article-36-access-control-be-implemented-and-evidenced-under-the-data-act) *Module: [EU Data Act Article 36 Smart Contract Controls](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md)* The Data Act context is the starting point for this answer. Article 36 mentions access control twice: first as part of robustness against errors and third-party manipulation, and again as a requirement for rigorous access control at both the governance and smart contract layers. That means access control should not be limited to wallet ownership or a single administrator key. - Governance layer: approvers, role assignment, segregation of duties, emergency authority, and change approval. - Smart contract layer: privileged functions, key management, multi-party approval, event logs, and upgrade or pause controls. - Review trigger: any change to agreement terms, deployer/vendor role, permission model, code version, or data route. 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 36 requires access control mechanisms and protection at governance and smart contract layers. ### [What does Article 36 mean by safe termination and interruption under the Data Act?](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md#what-does-article-36-mean-by-safe-termination-and-interruption-under-the-data-act) *Module: [EU Data Act Article 36 Smart Contract Controls](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md)* The Data Act context is the starting point for this answer. Article 36 requires a mechanism to terminate continued execution of transactions and internal functions that can reset, stop, or interrupt operation, especially to avoid future accidental executions. This is a technical-control requirement, not a license for one party to rewrite the commercial bargain unilaterally. - Define the exact functions that can stop, interrupt, reset, or prevent future execution. - Tie each intervention to the contractual trigger and party approval process. - Log the reason, authority, affected transactions, data availability impact, and restoration or archiving step. 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 36(1)(b) requires termination and interruption mechanisms; Recital 104 explains the mutual-consent context. ## 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: 11 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/10.md) | [Next page](/artifacts/eu/data-act/faq/items/page/12.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/11