--- 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/8" 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 8 of 24. Showing 20 of 469 items.* ### [What does presumption of conformity actually mean for an EU Data Act interoperability requirement?](/artifacts/eu/data-act/faq/interoperability-standards.md#what-does-presumption-of-conformity-actually-mean-for-an-eu-data-act-interoperability-requirement) *Module: [Data Act Interoperability Standards](/artifacts/eu/data-act/faq/interoperability-standards.md)* Under the Data Act, a harmonised standard whose reference is published in the Official Journal gives a presumption of conformity for the essential requirements it covers, which means a team that follows it is presumed to meet those requirements unless shown otherwise. It is a rebuttable presumption tied to the specific requirements the standard addresses. - Apply the presumption only to the essential requirements the referenced standard actually covers. - Keep mapping evidence showing how the implementation meets those specific requirements. 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 Article 33 data-space interoperability, Article 35 data-processing service interoperability, and Article 36 smart-contract requirements. - [Commission Implementing Decision C(2025) 4135 - standardisation request annexes](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Lists M/614 European Trusted Data Framework deliverables and explains how entries 1, 2, and 3 support Article 33 essential requirements. - [CEN-CENELEC - Data Act standardization request accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Confirms CEN and CENELEC acceptance of the Data Act standardisation request under Mandate M/614 and planned development of seven deliverables. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Provides Commission context for data interoperability, data quality, data governance, and common European data spaces. - [Commission Notice - 2026 annual Union work programme for standardisation](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ%3AC_202601695&ref=sorena.io) - Identifies planned standardisation work for interoperability of data-processing services in support of Data Act Articles 30 and 35. - [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 a smart-contract vendor evidence conformity with the Article 36 essential requirements under the EU Data Act?](/artifacts/eu/data-act/faq/interoperability-standards.md#how-should-a-smart-contract-vendor-evidence-conformity-with-the-article-36-essential-requirements-under-the-eu-data-act) *Module: [Data Act Interoperability Standards](/artifacts/eu/data-act/faq/interoperability-standards.md)* Under the Data Act, an Article 36 vendor or deployer must carry out a conformity assessment and draw up an EU declaration of conformity covering robustness, access control, safe termination and interruption, data archiving, and consistency with the data-sharing agreement. The declaration is the artifact that demonstrates the essential requirements were tested. - Produce an EU declaration of conformity mapping each Article 36 essential requirement to test evidence. - Version the smart contract so the conformity claim can be revalidated after 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 source for Article 33 data-space interoperability, Article 35 data-processing service interoperability, and Article 36 smart-contract requirements. - [Commission Implementing Decision C(2025) 4135 - standardisation request annexes](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Lists M/614 European Trusted Data Framework deliverables and explains how entries 1, 2, and 3 support Article 33 essential requirements. - [CEN-CENELEC - Data Act standardization request accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Confirms CEN and CENELEC acceptance of the Data Act standardisation request under Mandate M/614 and planned development of seven deliverables. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Provides Commission context for data interoperability, data quality, data governance, and common European data spaces. - [Commission Notice - 2026 annual Union work programme for standardisation](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ%3AC_202601695&ref=sorena.io) - Identifies planned standardisation work for interoperability of data-processing services in support of Data Act Articles 30 and 35. - [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 Article 33 metadata and semantic assets must a data space participant publish under the EU Data Act?](/artifacts/eu/data-act/faq/interoperability-standards.md#which-article-33-metadata-and-semantic-assets-must-a-data-space-participant-publish-under-the-eu-data-act) *Module: [Data Act Interoperability Standards](/artifacts/eu/data-act/faq/interoperability-standards.md)* Under the Data Act, an Article 33 participant offering data or data services must describe dataset content, use restrictions, licences, collection methodology, data quality, and uncertainty in machine-readable form, and describe data structures, formats, vocabularies, taxonomies, and code lists in a public and consistent way where available. These descriptions are what make a data-space offer interoperable. - Publish machine-readable metadata covering content, licences, quality, and uncertainty where applicable. - Document API access, terms of use, and quality of service for the offered data or services. 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 Article 33 data-space interoperability, Article 35 data-processing service interoperability, and Article 36 smart-contract requirements. - [Commission Implementing Decision C(2025) 4135 - standardisation request annexes](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Lists M/614 European Trusted Data Framework deliverables and explains how entries 1, 2, and 3 support Article 33 essential requirements. - [CEN-CENELEC - Data Act standardization request accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Confirms CEN and CENELEC acceptance of the Data Act standardisation request under Mandate M/614 and planned development of seven deliverables. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Provides Commission context for data interoperability, data quality, data governance, and common European data spaces. - [Commission Notice - 2026 annual Union work programme for standardisation](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ%3AC_202601695&ref=sorena.io) - Identifies planned standardisation work for interoperability of data-processing services in support of Data Act Articles 30 and 35. - [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 a team revisit its EU Data Act interoperability standards position as references are published?](/artifacts/eu/data-act/faq/interoperability-standards.md#when-should-a-team-revisit-its-eu-data-act-interoperability-standards-position-as-references-are-published) *Module: [Data Act Interoperability Standards](/artifacts/eu/data-act/faq/interoperability-standards.md)* Under the Data Act, the interoperability position should be revisited whenever a harmonised standard reference is published in the Official Journal, a common specification is adopted by implementing act, or a repository reference for data processing services is added. Each event can change what a team must support and what merely supports conformity. - Revisit the position when a harmonised standard, common specification, or repository reference is published. - Recheck when an M/614 deliverable advances or a referenced standard is amended or superseded. 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 Article 33 data-space interoperability, Article 35 data-processing service interoperability, and Article 36 smart-contract requirements. - [Commission Implementing Decision C(2025) 4135 - standardisation request annexes](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Lists M/614 European Trusted Data Framework deliverables and explains how entries 1, 2, and 3 support Article 33 essential requirements. - [CEN-CENELEC - Data Act standardization request accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Confirms CEN and CENELEC acceptance of the Data Act standardisation request under Mandate M/614 and planned development of seven deliverables. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Provides Commission context for data interoperability, data quality, data governance, and common European data spaces. - [Commission Notice - 2026 annual Union work programme for standardisation](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ%3AC_202601695&ref=sorena.io) - Identifies planned standardisation work for interoperability of data-processing services in support of Data Act Articles 30 and 35. - [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. ### [Are the EU Data Act model contractual terms mandatory, or can parties amend them freely?](/artifacts/eu/data-act/faq/model-contractual-terms.md#are-the-eu-data-act-model-contractual-terms-mandatory-or-can-parties-amend-them-freely) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* No. Under the Data Act, the Commission recommends the model contractual terms and cloud clauses as non-binding drafting tools, and parties can amend them to fit the deal. Their value is as a source-linked baseline for review, not as a compulsory template. - Treat the Commission terms as a clause library and gap-checking tool. - Mark any deviation from the Commission wording with the business reason and approver. - Check that amended wording still respects mandatory Data Act provisions and unfair-term controls. Sources for this answer: - [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 page stating that use of the MCTs and cloud SCCs is voluntary and open to amendment. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 41 is the legal basis for Commission-recommended non-binding model terms and cloud clauses. ### [What do the Commission model contractual terms cover for data access and use under the Data Act?](/artifacts/eu/data-act/faq/model-contractual-terms.md#what-do-the-commission-model-contractual-terms-cover-for-data-access-and-use-under-the-data-act) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* The Commission material separates Data Act data sharing into three mandatory-sharing relationships under Chapters II and III: Data Holder to User, User to Data Recipient, and Data Holder to Data Recipient. It also includes a separate Data Sharer to Data Recipient set for voluntary data sharing. - Identify the parties using Data Act roles, not only customer, supplier, or partner labels. - Map the data categories and permitted use before selecting model clauses. - Separate mandatory Data Act sharing from voluntary data sharing so the wrong model set is not copied into the contract. Sources for this answer: - [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 listing the three mandatory data-sharing MCT sets and the voluntary Data Sharer to Data Recipient set. - [European Commission - Innovative technologies and data in contracts](https://commission.europa.eu/topics/business-and-industry/doing-business-eu/contract-rules/digital-contracts/innovative-technologies-and-data-contracts_en?ref=sorena.io) - Commission contract-law context explaining that the MCTs help parties, especially SMEs, draft and negotiate data-sharing contracts. ### [Are the Data Act model contractual terms mainly for B2B contracts?](/artifacts/eu/data-act/faq/model-contractual-terms.md#are-the-data-act-model-contractual-terms-mainly-for-b2b-contracts) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Yes. Under the Data Act, the Commission says the terms were mainly drafted for business-to-business contracts. It also says they can be used in business-to-consumer relationships if relevant consumer-protection rules are added. - Use the MCTs first for enterprise data-sharing contracts and enterprise negotiation playbooks. - Do not present the model wording as consumer-ready without a consumer-law review. - For SMEs, use the model terms to reduce drafting effort but still record negotiated changes and mandatory-law checks. Sources for this answer: - [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 page explaining the main B2B drafting focus and possible B2C use where consumer protection rules are added. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 13 applies unfair-term controls to enterprise contracts concerning data access, data use, liability, remedies, breach, or termination of data-related obligations. ### [How should teams use the model terms for Data Act access, use, compensation, and trade-secret clauses?](/artifacts/eu/data-act/faq/model-contractual-terms.md#how-should-teams-use-the-model-terms-for-data-act-access-use-compensation-and-trade-secret-clauses) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Under the Data Act, Article 41 specifically calls out model terms on data access and use, including reasonable compensation and the protection of trade secrets. Those topics should therefore be visible in the contract review file: what data is covered, who may use it, for what purpose, whether compensation is charged, and what confidentiality or technical measures protect trade secrets. - Create a clause map for access, use, compensation, confidentiality, trade-secret measures, liability, remedies, and termination. - Attach each clause to the relevant Data Act party relationship and data category. - Keep a redline showing where the company accepted, amended, or rejected the Commission wording. 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 41 identifies data access and use, reasonable compensation, and trade-secret protection as topics for non-binding model contractual terms. - [European Commission - Data Act FAQ publication page](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission page positioning the MCTs and SCCs as part of broader implementation guidance for the Data Act. ### [What should a contract reviewer do first when a Data Act model terms issue comes in?](/artifacts/eu/data-act/faq/model-contractual-terms.md#what-should-a-contract-reviewer-do-first-when-a-data-act-model-terms-issue-comes-in) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Start by classifying the deal. Decide whether it is a data-sharing contract or a cloud-switching contract, and then identify the Data Act roles on each side. That tells you which Commission model set to use and which mandatory provisions need a closer look. - Pick the right model set before editing clauses. - Map the relationship type and the parties' Data Act roles. - Check mandatory Data Act rules before negotiating deviations. 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 41 on model terms, Article 13 on unfair terms, and Article 25 on cloud switching provide the legal starting points. - [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 listing the model terms for data access and use and the cloud SCC groups. ### [Which EU Data Act cloud switching clauses should a contract reviewer check first?](/artifacts/eu/data-act/faq/model-contractual-terms.md#which-eu-data-act-cloud-switching-clauses-should-a-contract-reviewer-check-first) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* For cloud contracts under the Data Act, start with the switching and exit wording, the termination mechanics, the notice period, and the data retrieval and erasure terms. Those points line up with Article 25's written-contract requirements and the broader switching obligations in Chapter VI. - Check that the contract includes a switching and exit clause, not only a generic termination clause. - Map exportable data, digital assets, exemptions, retrieval periods, erasure, assistance, and security duties. - Keep the cloud clause set aligned with Article 25 and the switching charge rules. Sources for this answer: - [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 listing the cloud SCC sets for switching, termination, security, business continuity, non-dispersion, non-amendment, and liability. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 25 sets minimum written-contract content for switching between data processing services or to on-premises ICT infrastructure. ### [How do the model terms relate to unfair contractual terms under the Data Act?](/artifacts/eu/data-act/faq/model-contractual-terms.md#how-do-the-model-terms-relate-to-unfair-contractual-terms-under-the-data-act) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Under the Data Act, the Commission says the mandatory-sharing model sets are compliant with Chapter IV on unfair contractual terms, but that does not make every negotiated contract fair automatically. Article 13 still requires a term-by-term check where one enterprise supplied a term and the other enterprise could not influence it despite trying to negotiate. - Record whether contested data-access and data-use terms were negotiated or unilaterally imposed. - Screen liability, remedies, termination, data-use, data-copy, unilateral-change, and conformity-interpretation clauses against Article 13. - Do not treat price adequacy or the contract's main subject matter as covered by Article 13 where the Data Act excludes those points. 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 13 sets the Data Act unfairness test for unilaterally imposed enterprise contract terms concerning data access, use, liability, remedies, breach, or termination. - [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 page stating that the mandatory-sharing MCT sets are compliant with Chapter IV unfair-contract-term rules. ### [What evidence should teams keep when using or deviating from the Commission model terms under the Data Act?](/artifacts/eu/data-act/faq/model-contractual-terms.md#what-evidence-should-teams-keep-when-using-or-deviating-from-the-commission-model-terms-under-the-data-act) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Keep evidence that shows the contract team used the model terms as a grounded drafting aid and checked the mandatory Data Act rules that matter to the deal. The file should let a reviewer see the party roles, relationship type, data categories, clause set selected, redlines, reason for deviations, unfair-term review, and cloud-switching review where relevant. - Maintain a model-term mapping table with party roles, clause references, accepted text, deviations, rationale, approver, and date. - Keep negotiation evidence showing whether a contested term was negotiable or unilaterally imposed. - For cloud deals, retain the switching and exit checklist alongside the signed contract and pre-contract information. 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, 26, and 29 support keeping cloud-switching evidence covering contractual switching terms, porting information, and switching-charge disclosures. - [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 explaining that the recommended MCTs and SCCs were developed to help parties implement Data Act provisions. ### [Which official sources should be checked first under the Data Act?](/artifacts/eu/data-act/faq/model-contractual-terms.md#which-official-sources-should-be-checked-first-under-the-data-act) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Start with the Data Act itself for the binding rule. Use Article 41 for the Commission's mandate, Articles 12 and 13 for data-sharing and unfair-term controls, and Articles 23 to 31 for cloud switching and porting. - Use the regulation for mandatory rights, obligations, exclusions, and enforcement context. - Use the Commission model-terms page for voluntary MCT and cloud SCC structure. - Use Commission FAQ and contract-law pages for implementation context and source discovery. 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 regulation covering Data Act contract, unfair-term, cloud-switching, and Article 41 model-term provisions. - [European Commission - Data Act FAQ publication page](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission page linking the Data Act FAQs, model terms, cloud SCCs, vehicle data guidance, and legal helpdesk as implementation materials. ### [How do the cloud standard contractual clauses differ from the EU Data Act data-sharing model terms?](/artifacts/eu/data-act/faq/model-contractual-terms.md#how-do-the-cloud-standard-contractual-clauses-differ-from-the-eu-data-act-data-sharing-model-terms) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Under the Data Act, the Commission published two distinct sets: model contractual terms for data access and use under Chapters II to IV, and standard contractual clauses for cloud computing and other data processing services under Chapter VI switching. They address different contracts and should not be mixed in a single review. - Use the cloud SCCs for data processing service and switching contracts under Chapter VI. - Use the data-sharing model terms for connected-product and B2B data-sharing contracts. 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 Article 41 model terms, Article 13 unfair contractual terms, Article 25 cloud-switching contract content, and related cloud-switching provisions. - [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 publication describing the voluntary MCTs, the mandatory and voluntary data-sharing model sets, and the cloud SCC groups. - [European Commission - Innovative technologies and data in contracts](https://commission.europa.eu/topics/business-and-industry/doing-business-eu/contract-rules/digital-contracts/innovative-technologies-and-data-contracts_en?ref=sorena.io) - Commission context page explaining why data-sharing contracts raise data-specific issues and how non-binding MCTs help parties draft and negotiate. - [European Commission - Data Act FAQ publication page](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission implementation page positioning the Data Act FAQs, MCTs, SCCs, vehicle guidance, and legal helpdesk as supporting materials. - [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. ### [Can the EU Data Act model contractual terms override a mandatory data-sharing obligation in a contract?](/artifacts/eu/data-act/faq/model-contractual-terms.md#can-the-eu-data-act-model-contractual-terms-override-a-mandatory-data-sharing-obligation-in-a-contract) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Under the Data Act, voluntary model wording cannot be used to contract out of mandatory protections, and Article 12 prevents a data-sharing agreement from excluding or varying Chapter III obligations to the detriment of a covered party or user. The model terms are a drafting aid, not a way to weaken statutory rights. - Do not let amended model wording exclude or vary mandatory Chapter III obligations. - Record the compliance reasoning for any deviation that touches a statutory right. 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 Article 41 model terms, Article 13 unfair contractual terms, Article 25 cloud-switching contract content, and related cloud-switching provisions. - [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 publication describing the voluntary MCTs, the mandatory and voluntary data-sharing model sets, and the cloud SCC groups. - [European Commission - Innovative technologies and data in contracts](https://commission.europa.eu/topics/business-and-industry/doing-business-eu/contract-rules/digital-contracts/innovative-technologies-and-data-contracts_en?ref=sorena.io) - Commission context page explaining why data-sharing contracts raise data-specific issues and how non-binding MCTs help parties draft and negotiate. - [European Commission - Data Act FAQ publication page](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission implementation page positioning the Data Act FAQs, MCTs, SCCs, vehicle guidance, and legal helpdesk as supporting materials. - [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 teams re-check their EU Data Act model contractual terms as guidance and standards evolve?](/artifacts/eu/data-act/faq/model-contractual-terms.md#when-should-teams-re-check-their-eu-data-act-model-contractual-terms-as-guidance-and-standards-evolve) *Module: [Data Act Model Contractual Terms](/artifacts/eu/data-act/faq/model-contractual-terms.md)* Under the Data Act, the model contractual terms and cloud standard contractual clauses are Commission recommendations that can be updated, so teams should re-check their contract library when the Commission revises the model sets or issues new implementation guidance. A version note in the contract file makes that easier to track. - Re-check the contract library when the Commission revises the model terms or cloud SCCs. - Update wording when an underlying Data Act obligation, such as switching charges, 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 source for Article 41 model terms, Article 13 unfair contractual terms, Article 25 cloud-switching contract content, and related cloud-switching provisions. - [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 publication describing the voluntary MCTs, the mandatory and voluntary data-sharing model sets, and the cloud SCC groups. - [European Commission - Innovative technologies and data in contracts](https://commission.europa.eu/topics/business-and-industry/doing-business-eu/contract-rules/digital-contracts/innovative-technologies-and-data-contracts_en?ref=sorena.io) - Commission context page explaining why data-sharing contracts raise data-specific issues and how non-binding MCTs help parties draft and negotiate. - [European Commission - Data Act FAQ publication page](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission implementation page positioning the Data Act FAQs, MCTs, SCCs, vehicle guidance, and legal helpdesk as supporting materials. - [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 makes a Data Act request a public emergency request for Public Emergency Requests implementation evidence?](/artifacts/eu/data-act/faq/public-emergency-requests.md#what-makes-a-data-act-request-a-public-emergency-request-for-public-emergency-requests-implementation-evidence) *Module: [Data Act Public Emergency Requests](/artifacts/eu/data-act/faq/public-emergency-requests.md)* A public emergency request is one branch of the Data Act's exceptional-need mechanism. Article 15 treats an exceptional need as limited in time and scope, and the public emergency branch applies where the requested data are necessary to respond to a public emergency and the requester cannot obtain them by alternative means in a timely and effective way under equivalent conditions. - Check that the requester is a public sector body of a Member State, the Commission, the European Central Bank, or a Union body. - Confirm that the request is for response to a public emergency, not mitigation, recovery, official statistics, procurement, or a routine policy task. - Record why the requested data cannot be obtained quickly and effectively by another equivalent 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) - Articles 14 and 15 define the Chapter V obligation and the public emergency branch of exceptional need. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Explains that Chapter V covers exceptional need, including public emergencies, and gives examples of emergency situations. ### [What must the request say before a data holder treats it as valid under the Data Act?](/artifacts/eu/data-act/faq/public-emergency-requests.md#what-must-the-request-say-before-a-data-holder-treats-it-as-valid-under-the-data-act) *Module: [Data Act Public Emergency Requests](/artifacts/eu/data-act/faq/public-emergency-requests.md)* The Data Act context is the starting point for this answer. Article 17 requires the requester to put the request in writing, in clear, concise, plain language, and to specify the data required, including relevant metadata needed to interpret and use the data. The request must also explain the purpose, intended use, duration of use, requester authority, deadline for making data available, and the deadline for the data holder to decline or seek modification. - Reject intake forms that ask for a broad data lake, undefined telemetry, or all emergency-related records without specifying the data and metadata needed. - Ask for clarification where the request does not explain exceptional need, purpose, duration, legal task, sharing recipients, or personal-data safeguards. - Keep the original written request, later clarifications, and the final agreed data scope 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) - Article 17 lists the required content and form of a request for data under Chapter V. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ says data holders should verify the requesting entity, justification, purpose, duration, data scope, proportionality, and required notifications. ### [How fast must a data holder respond under the Data Act for Public Emergency Requests implementation evidence?](/artifacts/eu/data-act/faq/public-emergency-requests.md#how-fast-must-a-data-holder-respond-under-the-data-act-for-public-emergency-requests-implementation-evidence) *Module: [Data Act Public Emergency Requests](/artifacts/eu/data-act/faq/public-emergency-requests.md)* The Data Act context is the starting point for this answer. A data holder that receives a Chapter V request must make the data available without undue delay, taking account of necessary technical, organisational, and legal measures. If the data holder declines or seeks modification of a public emergency request, Article 18 requires it to do so without undue delay and no later than five working days after receipt. - Timestamp receipt and assign a legal and operational owner on the same day the request arrives. - Decide quickly whether the company controls the requested data, whether the request is repetitive, or whether Article 17 conditions are missing. - Escalate unresolved refusal or modification disputes to the competent authority route described in Article 18. 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 18 sets the data holder's duty to make data available and the five-working-day window for declining or seeking modification of public emergency requests. ### [When can the data holder decline or seek modification under the Data Act?](/artifacts/eu/data-act/faq/public-emergency-requests.md#when-can-the-data-holder-decline-or-seek-modification-under-the-data-act) *Module: [Data Act Public Emergency Requests](/artifacts/eu/data-act/faq/public-emergency-requests.md)* The Data Act context is the starting point for this answer. Article 18 gives three grounds: the data holder does not control the requested data, a similar request for the same purpose has already been submitted by another eligible body and erasure has not been notified, or the request does not meet the Article 17 request-content and form conditions. - Document the exact Article 18 ground for any refusal or modification request. - If relying on a prior similar request, identify the earlier requesting body as Article 18 requires. - If the dispute cannot be resolved by modification, preserve the record for referral to the competent authority. 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 18 lists the grounds for declining or seeking modification and the dispute referral path. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ explains that data holders may ask for clarification and may ultimately refuse or seek modification when justified doubts remain. ## 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: 8 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/7.md) | [Next page](/artifacts/eu/data-act/faq/items/page/9.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/8