--- 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/13" 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 13 of 24. Showing 20 of 469 items.* ### [Can a data holder charge for a Data Act B2G request during a public emergency?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#can-a-data-holder-charge-for-a-data-act-b2g-request-during-a-public-emergency) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act context is the starting point for this answer. For a public-emergency request under Article 15(1)(a), data holders other than microenterprises and small enterprises must make the necessary data available free of charge. If the data holder asks, the receiving public sector body, Commission, European Central Bank, or Union body must provide public acknowledgement. - Record whether the request cites Article 15(1)(a) public-emergency response. - Do not invoice ordinary technical, export, or handling costs for a qualifying public-emergency request if the data holder is not a microenterprise or small enterprise. - If acknowledgement is requested instead of compensation, keep the acknowledgement request and the public body's response in the request file. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 15 and 20 set the public-emergency trigger and require covered data holders to provide emergency-response data free of charge, with public acknowledgement on request. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission guidance explains that Chapter V covers exceptional-need B2G access, including public emergencies such as disasters, pandemics, and cybersecurity incidents. ### [When can fair compensation be claimed for a non-emergency Data Act B2G request?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#when-can-fair-compensation-be-claimed-for-a-non-emergency-data-act-b2g-request) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act context is the starting point for this answer. For non-emergency exceptional-need requests under Article 15(1)(b), a data holder is entitled to fair compensation for making data available. That route applies only to non-personal data and only where the requesting body acts on a legal public-interest task, identifies specific missing data, and has exhausted other means to obtain it. - Check whether the request is non-emergency Article 15(1)(b), not public-emergency Article 15(1)(a). - Confirm the request is limited to non-personal data and states the legal public-interest task. - Keep evidence that the public body explained why other routes to the same data were unavailable or insufficient. 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 15 defines non-emergency exceptional need and Article 20 gives data holders a fair-compensation entitlement for Article 15(1)(b) requests. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ explains that non-emergency Chapter V access should not displace market purchase where data can be bought at market rates. ### [Which costs can be included in fair compensation for a non-emergency exceptional-need request under the Data Act?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#which-costs-can-be-included-in-fair-compensation-for-a-non-emergency-exceptional-need-request-under-the-data-act) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act context is the starting point for this answer. Article 20 says fair compensation covers the technical and organisational costs incurred to comply with the request and a reasonable margin. The text specifically mentions costs of anonymisation, pseudonymisation, aggregation, and technical adaptation where they apply. - Separate data extraction, formatting, secure transfer, anonymisation, pseudonymisation, aggregation, and technical-adaptation effort. - Do not include unsupported penalty amounts, speculative damages, or fees for data value unless the cited basis supports them. - Keep enough calculation detail for the public body to assess the cost basis and margin. 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 20 identifies eligible cost categories for non-emergency B2G compensation and requires calculation information when requested. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explainer summarizes Chapter V compensation by distinguishing public-emergency requests from non-emergency requests. ### [Are microenterprises and small enterprises treated differently for Data Act B2G compensation?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#are-microenterprises-and-small-enterprises-treated-differently-for-data-act-b2g-compensation) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act context is the starting point for this answer. Yes. Article 20(1) says data holders other than microenterprises and small enterprises must make public-emergency data available free of charge, while Article 20(3) says the fair-compensation rule also applies where a microenterprise or small enterprise claims compensation. - Record whether the data holder is a microenterprise, small enterprise, or neither. - For a public-emergency request, check whether the free-of-charge rule or the micro/small-enterprise rule applies before quoting any fee. - If a microenterprise or small enterprise does claim compensation, use Article 20 cost categories instead of a flat fee. 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 15(2) excludes microenterprises and small enterprises from Article 15(1)(b), while Article 20(1) and 20(3) distinguish compensation treatment for public-emergency requests. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission's summary table shows that micro and small companies are exempt from the non-emergency obligation and that their emergency compensation is limited to technical and organisational costs. ### [Is compensation available for non-emergency requests used to produce official statistics under the Data Act?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#is-compensation-available-for-non-emergency-requests-used-to-produce-official-statistics-under-the-data-act) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act context is the starting point for this answer. Article 20(4) says data holders are not entitled to compensation for an Article 15(1)(b) request where the specific task is producing official statistics and national law does not allow the purchase of the data. - Ask the requester to identify whether the task is production of official statistics. - Record any statement that national law does not allow purchase of the requested data. - Do not extend the official-statistics carveout to other public-interest analytics without support in the request. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 20(4) removes compensation for certain official-statistics requests where national law does not allow purchase of the data. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ discusses market purchase and the Article 15(3) exception for official statistics in Chapter V requests. ### [How do confidentiality, trade secrets, and personal data affect the cost response under the Data Act?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#how-do-confidentiality-trade-secrets-and-personal-data-affect-the-cost-response-under-the-data-act) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act context is the starting point for this answer. The request must respect the data holder's legitimate aims, including trade-secret protection and the cost and effort required to make data available. If trade secrets must be disclosed, Article 19 limits disclosure to what is strictly necessary and requires the data holder or trade-secret holder to identify protected data, including relevant metadata. - Identify trade secrets before disclosure and record the technical or organisational confidentiality measures requested or agreed. - For personal data in a public-emergency request, record whether anonymisation is possible and, if not, what pseudonymisation and safeguards are required. - Tie confidentiality, anonymisation, pseudonymisation, aggregation, or technical-adaptation costs to the request facts rather than using a generic surcharge. 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, 18, 19, and 20 connect proportional requests, trade-secret safeguards, personal-data measures, and eligible cost categories. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explainer states that Chapter V requests must be specific, transparent, proportionate, protect trade secrets, and delete data when no longer needed. ### [What records should a data holder keep for Data Act B2G compensation and cost disputes?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#what-records-should-a-data-holder-keep-for-data-act-b2g-compensation-and-cost-disputes) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act context is the starting point for this answer. Keep a request file that lets a later reviewer reconstruct the classification and calculation without relying on chat history. The file should include the written request, the Article 15 route, requester identity, data scope, purpose, duration, erasure expectation, sharing recipients, delivery deadline, the data holder's response, and the compensation calculation or free-of-charge rationale. - Keep the written request and evidence that it met, or failed to meet, the Article 17 request conditions. - Keep any decline, modification request, duplicate-request evidence, delivery record, erasure notice, and confidentiality measures. - For compensation disputes, keep the amount requested, cost basis, reasonable-margin explanation, public body's questions, and any competent-authority complaint correspondence. 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, 18, 19, 20, and 21 support the recommended records for request content, response timing, erasure, onward sharing, and compensation disputes. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ identifies practical checks for whether a Chapter V request is justified and lawful, including requester identity, scope, purpose, proportionality, and notifications. ### [What is the main mistake to avoid when responding to a Data Act B2G compensation request?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#what-is-the-main-mistake-to-avoid-when-responding-to-a-data-act-b2g-compensation-request) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act context is the starting point for this answer. The main mistake is quoting a fee before classifying the request. The compensation answer changes depending on whether the request is for public-emergency response, another non-emergency exceptional need, official statistics, or a micro or small enterprise scenario. - Classify the Article 15 route before discussing price. - Explain any claimed compensation through Article 20 cost categories and a request-specific calculation. - Escalate unclear or disputed requests through the competent-authority complaint route rather than inventing a fee or refusal basis. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Chapter V provides different rules for emergency requests, non-emergency exceptional need, small-business status, official statistics, and compensation disputes. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explainer frames Chapter V as exceptional-need access and distinguishes emergency from non-emergency requests. ### [What Data Act source evidence should teams keep for the B2G Compensation And Costs FAQ decision?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#what-data-act-source-evidence-should-teams-keep-for-the-b2g-compensation-and-costs-faq-decision) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act source evidence should make the decision auditable later. Keep the legal basis for the request, the route under Article 15, the cost basis under Article 20, any confidentiality measures under Article 19, and the complaint route under Articles 18 and 20 together with the final decision. - Map the request to the exact Article 15 category and keep the cited Data Act source URL in the file. - Store the requester, data holder, purpose, deadline, cost breakdown, and any acknowledgement or complaint correspondence. - Keep the confidentiality or anonymisation measures that were applied so the compensation basis is tied to the actual work performed. 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 Chapter V exceptional-need requests, Article 15 request types, Article 17 request content, Article 18 response timing, Article 19 confidentiality and erasure duties, Article 20 compensation, and Article 21 onward sharing. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for plain-language context on Chapter V exceptional-need B2G access, public emergency versus non-emergency requests, and the compensation summary table. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for practical checks on Chapter V request justification, market-purchase exhaustion, official-statistics context, and reuse limits. ### [How should teams assign ownership for Data Act B2G Compensation And Costs implementation work?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#how-should-teams-assign-ownership-for-data-act-b2g-compensation-and-costs-implementation-work) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The team should assign one accountable owner who can coordinate legal, procurement, security, and data teams for a Chapter V request. The Data Act asks the request to be handled in a specific, transparent, and proportionate way, so someone has to own the file from intake to closure. - Assign one owner for each request file and note the teams consulted on legal, technical, and confidentiality issues. - Keep the request log, evidence bundle, and response draft together so the calculation can be reproduced later. - Use the competent authority or data coordinator route for unresolved lawfulness or compensation disputes. 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 Chapter V exceptional-need requests, Article 15 request types, Article 17 request content, Article 18 response timing, Article 19 confidentiality and erasure duties, Article 20 compensation, and Article 21 onward sharing. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for plain-language context on Chapter V exceptional-need B2G access, public emergency versus non-emergency requests, and the compensation summary table. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for practical checks on Chapter V request justification, market-purchase exhaustion, official-statistics context, and reuse limits. ### [Which Data Act implementation evidence makes the B2G Compensation And Costs answer usable later?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#which-data-act-implementation-evidence-makes-the-b2g-compensation-and-costs-answer-usable-later) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* For Data Act B2G compensation and costs, the most useful evidence is the material that shows why the request met Chapter V and how the compensation number was built. That includes the written request, the Article 15 classification, the Article 20 cost breakdown, and any confidentiality or anonymisation steps. - Keep source URLs, request dates, requester identity, and the legal basis cited in the file. - Store the cost workpapers that support extraction, formatting, transfer, anonymisation, pseudonymisation, aggregation, or technical adaptation. - Retain any acknowledgement, refusal, modification, or complaint correspondence with 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) - Binding source for Chapter V exceptional-need requests, Article 15 request types, Article 17 request content, Article 18 response timing, Article 19 confidentiality and erasure duties, Article 20 compensation, and Article 21 onward sharing. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for plain-language context on Chapter V exceptional-need B2G access, public emergency versus non-emergency requests, and the compensation summary table. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for practical checks on Chapter V request justification, market-purchase exhaustion, official-statistics context, and reuse limits. ### [When should the Data Act B2G Compensation And Costs FAQ answer be reviewed again by the team?](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md#when-should-the-data-act-b2g-compensation-and-costs-faq-answer-be-reviewed-again-by-the-team) *Module: [EU Data Act B2G Compensation and Costs](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md)* The Data Act answer should be reviewed whenever the request route changes, the team learns new facts about the data holder's size or control over the data, or the public body starts asking for a different data scope or purpose. The same applies if national law changes the ability to purchase data for official statistics or if the request involves new confidentiality or personal-data constraints. - Review after any change in request type, holder size, data scope, or legal basis. - Re-check the answer when national law, complaint handling, or acknowledgement practice changes. - Set a review trigger tied to the next Chapter V request so the file 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 source for Chapter V exceptional-need requests, Article 15 request types, Article 17 request content, Article 18 response timing, Article 19 confidentiality and erasure duties, Article 20 compensation, and Article 21 onward sharing. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for plain-language context on Chapter V exceptional-need B2G access, public emergency versus non-emergency requests, and the compensation summary table. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for practical checks on Chapter V request justification, market-purchase exhaustion, official-statistics context, and reuse limits. ### [When does the EU Data Act allow a public-sector body to request business-held data because of an exceptional need?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#when-does-the-eu-data-act-allow-a-public-sector-body-to-request-business-held-data-because-of-an-exceptional-need) *Module: [EU Data Act B2G Exceptional Need](/artifacts/eu/data-act/faq/b2g-exceptional-need.md)* The EU Data Act allows a Chapter V request only where the requesting public body or EU institution demonstrates an exceptional need to use certain data, including metadata needed to interpret and use it, for a statutory public-interest task. The need must be limited in time and scope. - Emergency route: necessary data for response to a declared or determined public emergency, including natural disasters, pandemics, or major cybersecurity incidents. - Non-emergency route: specific non-personal data needed for a public-interest task such as official statistics or mitigation of or recovery from a public emergency. - Not enough: a broad policy interest, routine procurement preference, repeated reporting demand, or request that can be satisfied from public databases, voluntary provision, existing obligations, or market purchase under equivalent conditions. 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 exceptional-need obligation, including the public-emergency route and the separate non-emergency route for non-personal data. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation confirming that Chapter V covers public-sector access in exceptional-need situations and distinguishes emergency from non-emergency requests. ### [Who can make a Data Act B2G exceptional-need request, and who can receive one?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#who-can-make-a-data-act-b2g-exceptional-need-request-and-who-can-receive-one) *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. The request side is limited to public-sector bodies of Member States, the Commission, the European Central Bank, and Union bodies. The receiving side is a data holder that is a legal person, other than a public-sector body, and that holds the requested data. - Verify the requester's identity and whether it is one of the entities allowed to use Chapter V. - Confirm that the company controls the requested data at the time of the request; lack of control is a ground to decline or seek modification. - For cross-border requests, retain the notification and competent-authority review record before treating the request as ready for fulfilment. 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, 17, 18, and 22 identify the requesting entities, the legal-person data holder, the control-over-data condition, and cross-border examination route. - [European Commission - Frequently Asked Questions about the Data Act](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ explains that Chapter V requests may be cross-border and that Article 22 protects data holders through ex ante examination. ### [What must a valid EU Data Act B2G exceptional-need request contain?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#what-must-a-valid-eu-data-act-b2g-exceptional-need-request-contain) *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. A valid request must be written in clear, concise, plain language and must be specific about the data requested, the data holder chosen, the public-interest task, the purpose and intended use, the duration of use, any planned onward sharing, and the deadlines for making data available and for declining or seeking modification. - Required data scope: data type, relevant metadata, data holder control, granularity, volume, and access frequency. - Required legal and purpose scope: exceptional-need basis, public-interest task, legal provision, intended use, duration, and expected erasure timing where possible. - Required safeguards: personal-data measures where relevant, trade-secret protection commitment, publication or notification steps, penalties notice, and best efforts to avoid creating liability for the data holder. 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 contents and formal requirements for a Chapter V request, including purpose, use, duration, legal basis, deadlines, proportionality, and safeguards. - [European Commission - Frequently Asked Questions about the Data Act](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ describes how data holders can verify a Chapter V request by checking requester identity, justification, scope, duration, public task, and proportionality. ### [How should a data holder document, share, and review an EU Data Act exceptional-need request?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#how-should-a-data-holder-document-share-and-review-an-eu-data-act-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. A data holder should keep the written request, the basis for accepting or challenging it, the response deadline, the data disclosed or withheld, and the safeguards applied to the transfer. The record should also show any cross-border notification and any competent-authority contact. - Keep the Article 17 request elements together with the Article 18 response and any authority correspondence. - Record whether the request was for a public emergency or another exceptional need, because the response clock is five or 30 working days depending on that distinction. - Preserve evidence of erasure, notification, or authorised onward sharing so the file shows how the data was used after disclosure. 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, 18, 19, and 21 set out the request record, response windows, safeguards, erasure duties, and onward-sharing notices that should be retained. - [European Commission - Frequently Asked Questions about the Data Act](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ explains the practical checks data holders should use when assessing and documenting Chapter V requests. ### [Can a Data Act B2G exceptional-need request include personal data?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#can-a-data-act-b2g-exceptional-need-request-include-personal-data) *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. For non-emergency requests, only non-personal data may be requested. For public-emergency requests, the request should concern non-personal data first, and personal data may only be included if non-personal data is insufficient to respond to the need. In that case, the data holder must anonymise the data where possible, or pseudonymise it where disclosure of personal data is strictly necessary. - Check whether the request is emergency or non-emergency before reviewing any personal-data fields. - Require a clear explanation of why non-personal data is insufficient and why the personal-data element is strictly necessary. - Keep the anonymisation or pseudonymisation decision, the safeguards named in the request, and any supervisory-authority notification where personal data is involved. 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 15, 17, and 18 require the emergency-first, non-personal-data default and set the anonymisation or pseudonymisation rules. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation states that non-emergency requests may only cover non-personal data and that emergency requests should use non-personal data where possible. ### [When may a data holder refuse or ask to modify a Data Act B2G exceptional-need request?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#when-may-a-data-holder-refuse-or-ask-to-modify-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. A data holder may decline or seek modification without undue delay, and in any event within five working days for data necessary to respond to a public emergency or within 30 working days for other exceptional-need requests. - Respond on the correct clock: five working days for public-emergency response data and 30 working days for other exceptional-need requests. - If relying on a previous similar request, identify the earlier requesting body or EU institution. - If the requester challenges a refusal, or the data holder challenges the request and no modification resolves it, the matter goes to the competent authority where the data holder is established. 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 five-working-day and 30-working-day response windows, refusal and modification grounds, and competent-authority challenge route. - [European Commission - Frequently Asked Questions about the Data Act](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ confirms data holders may ask for clarification and ultimately refuse or seek modification when request conditions are in justified doubt. ### [How do confidentiality, trade secrets, and onward sharing work for Data Act B2G exceptional-need data?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#how-do-confidentiality-trade-secrets-and-onward-sharing-work-for-data-act-b2g-exceptional-need-data) *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. Data received under Chapter V does not become open public-sector information for general reuse. It must be used only for the purpose stated in the request, protected with technical and organisational measures, and erased once no longer necessary for that stated purpose unless archiving is required under transparency rules. - Do not treat Chapter V data as open data or general public-sector information for reuse. - Identify any public bodies, EU bodies, or third parties that will receive the data in the original request or in the later Article 21 notification. - For trade secrets, record the identified protected data, confidentiality measures, transfer controls, and the stated purpose that makes disclosure strictly necessary. 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, 19, and 21 control purpose limitation, erasure, onward sharing, trade-secret confidentiality measures, and research or statistics sharing. - [European Commission - Frequently Asked Questions about the Data Act](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ explains that requested data does not become open public-sector information and that onward sharing must remain tied to the stated purpose. ### [Can businesses receive compensation for making data available under a Data Act B2G exceptional-need request?](/artifacts/eu/data-act/faq/b2g-exceptional-need.md#can-businesses-receive-compensation-for-making-data-available-under-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. For a public-emergency request, data holders other than microenterprises and small enterprises must make the necessary data available free of charge, but may request public acknowledgement. The Commission's explanation states that micro and small companies may ask for reasonable remuneration not exceeding incurred technical and organisational costs, plus public acknowledgement upon request. - Separate the compensation record by request type: public emergency or non-emergency exceptional need. - For non-emergency requests, document the cost calculation basis and reasonable margin because the requester may ask for it. - Do not charge for the data itself; keep compensation tied to the costs and margin allowed by Article 20. 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 20 sets the free-of-charge rule for most public-emergency requests and the fair-compensation rule for Article 15(1)(b) non-emergency requests. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission compensation table explains what businesses, including micro and small companies, may request for public-emergency and non-emergency Chapter V data sharing. ## FAQ Pagination - Canonical index (page 1): [/artifacts/eu/data-act/faq/items](/artifacts/eu/data-act/faq/items.md) - Page 1 rule: `/page/1` is intentionally not generated; use the canonical index markdown URL. - Current page: 13 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/12.md) | [Next page](/artifacts/eu/data-act/faq/items/page/14.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/13