--- 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/14" 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 14 of 24. Showing 20 of 469 items.* ### [What evidence should a data holder keep for a Data Act B2G exceptional-need request?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#what-evidence-should-a-data-holder-keep-for-a-data-act-b2g-exceptional-need-request) *Module: [EU Data Act B2G Exceptional Need](/artifacts/eu/data-act/faq/b2g-exceptional-need.md)* The Data Act context is the starting point for this answer. Keep enough evidence to show whether the request was valid, how the company responded, what data was made available or withheld, and which safeguards governed the data after transfer. The evidence file should be built around the Article 17 request contents and the Article 18 response, not around generic compliance notes. - For emergency requests, keep the public-emergency basis, alternative-means analysis, five-working-day response record, and any public-acknowledgement request. - For non-emergency requests, keep the non-personal-data classification, exhausted-means evidence, market-purchase record where relevant, 30-working-day response record, and compensation basis. - For safeguards, keep anonymisation or pseudonymisation decisions, security measures, trade-secret protections, purpose limitation, onward-sharing notifications, and deletion confirmations. 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 17 through 21 define the request fields, response windows, safeguards, compensation records, onward-sharing notices, and erasure obligations that drive the evidence file. - [European Commission - Frequently Asked Questions about the Data Act](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ identifies the checks data holders should perform when validating whether a Chapter V request is justified and lawful. ### [What records should teams keep to support a Data Act B2G exceptional-need decision?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#what-records-should-teams-keep-to-support-a-data-act-b2g-exceptional-need-decision) *Module: [EU Data Act B2G Exceptional Need](/artifacts/eu/data-act/faq/b2g-exceptional-need.md)* For b2g exceptional need, the Data Act record should identify the source clause, Commission guidance, actor role, dataset, request or contract trigger, and the owner who approved the interpretation. - Record the b2g exceptional-need decision together with the cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger in the same file set. 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 source for scope, definitions, access rights, B2B sharing, B2G requests, cloud switching, smart contracts, enforcement, and application dates. - [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. ### [How should teams assign ownership for Data Act B2G exceptional-need implementation work?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#how-should-teams-assign-ownership-for-data-act-b2g-exceptional-need-implementation-work) *Module: [EU Data Act B2G Exceptional Need](/artifacts/eu/data-act/faq/b2g-exceptional-need.md)* For b2g exceptional need, the Data Act workflow should name the legal, product, procurement, cloud, support, or security owner who can change the affected process. - Record the owner for the b2g exceptional-need decision next to the cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger as part of 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 source for scope, definitions, access rights, B2B sharing, B2G requests, cloud switching, smart contracts, enforcement, and application dates. - [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 records make the Data Act B2G exceptional-need answer usable later?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#which-records-make-the-data-act-b2g-exceptional-need-answer-usable-later) *Module: [EU Data Act B2G Exceptional Need](/artifacts/eu/data-act/faq/b2g-exceptional-need.md)* For b2g exceptional need, the Data Act evidence should be concrete enough for a later reviewer to reconstruct why the team classified the product, service, request, or contract in scope. - Keep the cited source URL, the decision memo, and the implementation evidence together. - Preserve the review trigger and the named owner so the decision can be revisited when the facts 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 Data Act source for scope, definitions, access rights, B2B sharing, B2G requests, cloud switching, smart contracts, enforcement, and application dates. - [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 B2G exceptional-need FAQ answer be reviewed again?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#when-should-the-data-act-b2g-exceptional-need-faq-answer-be-reviewed-again) *Module: [EU Data Act B2G Exceptional Need](/artifacts/eu/data-act/faq/b2g-exceptional-need.md)* For b2g exceptional need, the Data Act answer should be reviewed when the product, service model, dataset, customer role, public-sector request path, or contract wording changes. - Trigger a review when the Data Act source, request process, or affected workflow changes. - Keep the owner, review date, and cited source URL with the record so the answer stays current. 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 source for scope, definitions, access rights, B2B sharing, B2G requests, cloud switching, smart contracts, enforcement, and application dates. - [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. ### [What should procurement check first under the EU Data Act cloud-switching rules?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#what-should-procurement-check-first-under-the-eu-data-act-cloud-switching-rules) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Start by confirming that the supplier is providing a data processing service to a customer, such as cloud or edge services using configurable, scalable computing resources. The Commission FAQ explains that the Data Act concept covers common IaaS, PaaS, and SaaS delivery models when the service has the Article 2(8) characteristics. - Record the service model reviewed: IaaS, PaaS, SaaS, edge service, custom-built service, or limited test service. - Identify the source provider, possible destination provider, and whether the buyer may also switch to on-premises ICT infrastructure. - Check whether any custom-built or non-production exemption is claimed, and request the supplier's explanation before contracting. 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 23 is the binding source for the obstacles providers must remove to enable effective switching. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ support for treating IaaS, PaaS, and SaaS as data processing services when the Article 2(8) characteristics are present. ### [Which mandatory cloud-switching contract terms should be visible before signature under the Data Act?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#which-mandatory-cloud-switching-contract-terms-should-be-visible-before-signature-under-the-data-act) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* The Data Act context is the starting point for this answer. Article 25 requires the customer's switching rights and the provider's obligations to be clearly set out in a written contract that the customer can store and reproduce before signing. Procurement should therefore reject exit language that is only in a help-center article, commercial slide, or support policy outside the contract pack. - Ask for a clause matrix against Article 25(2)(a) to (i), with contract references for each item. - Require a maximum notice period for initiating switching that does not exceed two months. - Confirm that the contract states when termination occurs after a successful switch or after erasure where the customer does not switch. 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 25 lists the minimum written contract content for switching between data processing services. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission material identifies non-binding SCC modules for switching and exit, termination, security and business continuity, and related fair-contract topics. ### [What exit and export support should a buyer require from a cloud provider under the Data Act?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#what-exit-and-export-support-should-a-buyer-require-from-a-cloud-provider-under-the-data-act) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* The Data Act context is the starting point for this answer. For switching or porting, Article 25 requires reasonable assistance, due care to maintain business continuity, clear information on known continuity risks, and high security during transfer and retrieval. A procurement checklist should ask for named support channels, technical documentation, migration tooling, continuity risk notices, and security controls during the switch. - Request the export runbook, supported export formats, API or interface documentation, and known technical limitations. - Ask for evidence of the online register covering data structures, formats, standards, and open interoperability specifications. - Require the supplier to state what assistance is included in the Data Act switching obligation and what extra services would be separately chargeable. 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 25 and 26 support the procurement checks for assistance, continuity, security, switching procedures, formats, restrictions, and the online register. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer describes cloud-switching barriers such as data egress charges, lengthy procedures, and lack of interoperability. ### [What implementation records and review triggers should teams keep after agreeing the Data Act answer?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#what-implementation-records-and-review-triggers-should-teams-keep-after-agreeing-the-data-act-answer) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* For cloud switching procurement checklist, the Data Act record should identify the source clause, Commission guidance, affected service, decision owner, and the evidence used to approve the supplier's switching terms. Keep the contract pack, supplier redlines, export tests, fee schedule, and online-register snapshot together so the decision can be checked later. - Save the signed clause set, supplier responses, approval notes, export tests, fee schedule, online-register snapshot, and erasure confirmation requirements. - Assign procurement, legal, security, architecture, and service-owner sign-off for high-risk services. - Set a renewal review date and an event trigger for changes to the service model, export path, or provider 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) - Binding Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [How should procurement test a cloud provider's switching charges and egress fees under the EU Data Act?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#how-should-procurement-test-a-cloud-providers-switching-charges-and-egress-fees-under-the-eu-data-act) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Under the Data Act, Article 29 phases out switching charges, including data egress fees, so that from 12 January 2027 providers cannot impose them, and in the interim period any charge must not exceed the costs the provider actually incurs. Procurement should ask the supplier to confirm which date its contract reflects and how any interim charge is calculated. - Confirm the contract removes switching charges from 12 January 2027 and caps any interim charge at actual cost. - Ask for the cost basis of any reduced switching charge so it can be checked against the Article 29 limit. 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 Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [Which exportable data and digital assets must a cloud provider hand over on exit under the EU Data Act?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#which-exportable-data-and-digital-assets-must-a-cloud-provider-hand-over-on-exit-under-the-eu-data-act) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Under the Data Act, exportable data covers the data the customer generated or imported and the digital assets it is entitled to, but it excludes assets protected by third-party intellectual property rights or that would reveal the provider's own trade secrets. Procurement should ask the supplier to define the boundary in the contract rather than discovering it during a migration. - Require a written list of exportable data categories, digital assets, and the formats they will be delivered in. - Clarify which provider-internal data is excluded and why, so the exclusion is not used to gut the export. 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 Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [When does the EU Data Act require functional equivalence rather than just a raw data export on switching?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#when-does-the-eu-data-act-require-functional-equivalence-rather-than-just-a-raw-data-export-on-switching) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Under the Data Act, functional equivalence applies to switching between services of the same service type, mainly IaaS, where the destination should deliver a materially comparable outcome after the customer has reconfigured the service. For PaaS and SaaS the obligation is the lighter duty to export the data and digital assets in a structured, commonly used, machine-readable format. - Classify the service type so the right export or functional-equivalence duty is applied. - Confirm in the contract whether functional equivalence is owed and what reconfiguration the customer must do. 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 Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [What retrieval period and data erasure terms should a buyer require on cloud exit under the EU Data Act?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#what-retrieval-period-and-data-erasure-terms-should-a-buyer-require-on-cloud-exit-under-the-eu-data-act) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Under the Data Act, the contract should give the customer a minimum 30-day retrieval period to recover its exportable data after the switch is initiated, after which the provider erases the data unless a longer period is agreed or another legal duty applies. Procurement should make sure the retrieval window and the erasure trigger are both explicit. - Require at least a 30-day retrieval period and a clear erasure trigger in the contract. - Ask how the provider confirms erasure after retrieval so the customer has evidence of deletion. 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 Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [How should procurement check interoperability and the open specifications a cloud provider relies on under the EU Data Act?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#how-should-procurement-check-interoperability-and-the-open-specifications-a-cloud-provider-relies-on-under-the-eu-data-act) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Under the Data Act, Article 30 expects providers of the same service type to support interoperability through open interoperability specifications and harmonised standards listed in a central repository, and Article 26 requires the provider to reference an up-to-date register of data structures, formats, and standards. Procurement should ask which standards the export actually uses. - Ask which open interoperability specifications and harmonised standards the export and interfaces follow. - Verify the online register reference is current and matches the formats offered at exit. 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 Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [Which cloud services fall outside the EU Data Act switching rules, and how should a buyer test the exemption?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#which-cloud-services-fall-outside-the-eu-data-act-switching-rules-and-how-should-a-buyer-test-the-exemption) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Under the Data Act, custom-built services not offered at broad commercial scale and services supplied as a non-production test version are treated differently, and providers may claim that some Chapter VI duties do not apply. Procurement should require the supplier to state the exemption it relies on and the factual basis, rather than accepting a bare assertion. - Require the supplier to identify any exemption claimed and the factual reasons for it. - Record the exemption decision and weigh the reduced exit protection in the procurement risk assessment. 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 Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [How should a buyer plan unbundling and parallel running when switching cloud providers under the EU Data Act?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#how-should-a-buyer-plan-unbundling-and-parallel-running-when-switching-cloud-providers-under-the-eu-data-act) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Under the Data Act, switching should be technically feasible and the provider should support a managed transition, which in practice means a buyer can run the old and new services in parallel for a period and unbundle interdependent services where feasible. Procurement should ask how the supplier supports a phased cutover rather than a single hard switch. - Ask how the provider supports parallel running and a phased cutover during the switch. - Confirm what unbundling of interdependent services is technically feasible and contractually supported. 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 Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [Which EU Data Act dates and triggers should a procurement team track across a cloud contract's lifecycle?](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md#which-eu-data-act-dates-and-triggers-should-a-procurement-team-track-across-a-cloud-contracts-lifecycle) *Module: [EU Data Act Cloud Switching Procurement](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md)* Under the Data Act, the core cloud-switching obligations apply from 12 September 2025, and switching charges must be removed by 12 January 2027, so procurement should track which obligations a contract already meets and which depend on a future date. A renewal or new signature is the moment to align the contract with the applicable date. - Track the 12 September 2025 application date and the 12 January 2027 removal of switching charges. - Set event triggers for architecture, format, or documentation changes that require a contract recheck. 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 Chapter VI source for cloud-switching obligations, written contract terms, timing, information duties, charges, interoperability, retrieval, erasure, and exemptions. - [European Commission - Frequently asked questions about the Data Act](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source for practical interpretation of Chapter VI, including service scope, exportable data, timing, charges, IaaS/PaaS/SaaS distinctions, and functional-equivalence limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for cloud-switching policy context, data egress charges, interoperability barriers, and Data Act application context. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model terms and standard contractual clauses that can support cloud-switching procurement clause review. ### [What counts as a connected product under the EU Data Act, and which items fall outside that test?](/artifacts/eu/data-act/faq/scope-connected-products.md#what-counts-as-a-connected-product-under-the-eu-data-act-and-which-items-fall-outside-that-test) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Under the Data Act, a connected product is an item that obtains, generates, or collects data concerning its use or environment and can communicate product data through an electronic communications service, a physical connection, or on-device access. The definition also excludes items whose primary function is storing, processing, or transmitting data for a party other than the user. - Check what data the item obtains, generates, or collects about use, performance, status, or environment. - Check whether the item can communicate product data by network connection, cable, maintenance interface, or on-device access. - Do not treat servers, routers, or other products primarily used to store, process, or transmit another party's data as connected products for Chapter II unless the user owns, rents, or leases the relevant product. 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 2(5) defines connected product; Recital 14 gives examples and explains communication routes. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Question 7 explains connected-product examples and the exclusion for products whose primary function is storing, processing, or transmitting data. ### [Does the product have to be placed on the EU market under the Data Act?](/artifacts/eu/data-act/faq/scope-connected-products.md#does-the-product-have-to-be-placed-on-the-eu-market-under-the-data-act) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Yes. For connected-product scope, the Data Act applies to manufacturers of connected products placed on the market in the Union and providers of related services, regardless of where those manufacturers or providers are established. It also applies to users in the Union of those connected products or related services. - Classify each individual product, not only the product type or model line. - For mobile products such as cars, trains, ships, or aircraft, mere circulation in EU territory or EU waters is not enough if the product was not placed on the Union market. - If a connected product was placed on the EU market and later generates data outside the EU, the Commission FAQ says the generated data should still be made available to the user under the Data Act. 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 1(3) sets territorial scope for manufacturers, providers, and users; Article 2(21)-(22) defines making available and placing on the market. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 8 and 9 explain EU market placement, mobile connected products, and use outside the EU after EU placement. ### [Who is the EU Data Act user for connected-product access rights, and how is that status established?](/artifacts/eu/data-act/faq/scope-connected-products.md#who-is-the-eu-data-act-user-for-connected-product-access-rights-and-how-is-that-status-established) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Under the Data Act, a user is a natural or legal person that owns the connected product, has contractually received temporary rights to use it, or receives related services. The user can be a consumer, business, or public sector body; the key point is a stable ownership, rental, lease, or related-service position rather than casual physical interaction. - Identify owners, renters, lessees, and recipients of related services before processing an access request. - Expect multiple users in some arrangements, such as fleet leasing, rentals, or layered business use. - Verify only what is necessary to establish that the requester is a user; avoid turning scope checks into unnecessary data collection. 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 2(12) defines user; Recital 18 explains owners, renters, lessees, multiple users, and related-service recipients. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 14, 16, and 30 explain users, multiple users, and user verification. ## 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: 14 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/13.md) | [Next page](/artifacts/eu/data-act/faq/items/page/15.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/14