--- title: "EU Data Act B2G Compensation and Costs FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/b2g-compensation-and-costs" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/b2g-compensation-and-costs" author: "Sorena AI" description: "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." published_at: "2026-05-06" updated_at: "2026-05-25" keywords: - "EU Data Act" - "Regulation (EU) 2023/2854" - "B2G data sharing" - "exceptional need" - "public emergency" - "fair compensation" - "Compensation" --- **[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 B2G Compensation and Costs FAQ 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. *FAQ* *EU Data Act* *B2G exceptional need* ## EU Data Act B2G Compensation and Costs FAQ When a public authority can ask a data holder for Data Act B2G data, compensation depends on whether the request is for a public emergency or another exceptional need. Use this FAQ to separate free emergency responses, fair compensation for non-emergency requests, cost evidence, confidentiality safeguards, and complaint records. Chapter V of the EU Data Act lets public sector bodies, the Commission, the European Central Bank, and Union bodies request data from legal-person data holders only where an exceptional need is demonstrated. This FAQ focuses on the cost question: when the response must be free, when fair compensation may be claimed, which cost categories are supportable, and what records should show the calculation. ## Can a data holder charge for a Data Act B2G request during a public emergency? 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. The emergency route is narrow. The requester must show that the requested data is necessary to respond to the public emergency and cannot be obtained by alternative means in a timely and effective manner under equivalent conditions. A data holder should therefore classify the request before discussing any fee. - 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? 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. The request should not be treated as a shortcut around normal procurement. The Data Act text lists prior market purchase at market rates, existing data-availability obligations, and new legislative measures as examples of means that may need to be exhausted before Article 15(1)(b) is used. - 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? 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. The cost file should therefore show the request-specific work needed to make the data available, not a general price list for the value of the dataset. If the public body asks, the data holder must provide information on the basis for the calculation of costs and the reasonable margin. - 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? 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. For non-emergency requests, Article 15(2) removes the Chapter V obligation for microenterprises and small enterprises entirely. A request file should therefore record the holder's size status before any compensation discussion. - 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? 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. That carveout is narrow. The request file should show both the official-statistics purpose and the national-law position on purchase before the compensation answer is closed. - 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? 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. Confidentiality and data-protection work can affect the cost calculation when it is needed to comply with a non-emergency request. For example, Article 20 expressly allows costs for anonymisation, pseudonymisation, aggregation, and technical adaptation where applicable. The same controls should also be documented for emergency requests even where the response is free of charge. - 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? 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. Article 18 allows a data holder to decline or seek modification without undue delay, with a five-working-day outside limit for public-emergency requests and a 30-working-day outside limit for other exceptional-need requests. Article 20 also gives the receiving body a complaint route to the competent authority if it disagrees with the compensation level. - 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? 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. A useful response letter should state the request type, the data scope, whether compensation is unavailable or claimed, the cost basis if compensation is claimed, the confidentiality and personal-data safeguards, and the records the data holder will retain. It should not include unsupported penalty amounts or invented fee thresholds. - 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? 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. That record should be specific enough that a reviewer can see why the response was free, why compensation was limited to technical and organisational costs, or why a request was declined or modified. - 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. ## How should teams assign ownership for Data Act B2G Compensation And Costs implementation work? 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. That owner should be responsible for ensuring the request is logged, the compensation route is checked against Article 20, and any competence issues are escalated to the competent authority or data coordinator where needed. - 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. ## Which Data Act implementation evidence makes the B2G Compensation And Costs answer usable later? 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. The file should also preserve the public body's acknowledgement request, any modification or decline notice, and any complaint or authority correspondence, so a later reviewer can understand the full decision path. - 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. ## When should the Data Act B2G Compensation And Costs FAQ answer be reviewed again by the team? 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. The team should also revisit the answer after any actual Chapter V request, because the Data Act requires the file to be specific to the request, the compensable work, and the applicable deadline and complaint path. - 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. ## Primary sources - [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. ## Topic Guides - [Data Act and Common European Data Spaces](/artifacts/eu/data-act/data-act-and-common-european-data-spaces.md): How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring. - [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. - [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. - [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. - [Data Act B2B Data-Sharing Contract Clauses](/artifacts/eu/data-act/b2b-data-sharing-contract-clauses.md): Clause guide for EU Data Act B2B data sharing: FRAND terms, compensation, trade secret safeguards, recipient limits, termination, logs, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Template](/artifacts/eu/data-act/b2b-data-sharing-contract-template.md): A usable EU Data Act B2B data-sharing template outline covering access requests, data schedules, permitted use, trade secrets, security, compensation, GDPR boundaries, audit records, and termination. - [Data Act B2G Exceptional-Need Requests](/artifacts/eu/data-act/b2g-exceptional-need-requests.md): A grounded guide to EU Data Act Chapter V requests from public bodies: exceptional need, public emergencies, request contents, limits, safeguards, costs, and records. - [Data Act Cloud Switching Compliance Checklist](/artifacts/eu/data-act/cloud-switching-compliance-checklist.md): A grounded EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence. - [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. - [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. - [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. - [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. - [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. - [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. - [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. - [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. - [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. - [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. - [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. - [Data Act Smart Contracts for Data Sharing](/artifacts/eu/data-act/smart-contracts-for-data-sharing.md): Data Act Article 36 smart contract guide for data-sharing agreements: scope, robustness, access control, termination, interruption, archiving, standards status, and conformity evidence. - [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. - [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. - [Data Act Trade Secrets and Protection Measures](/artifacts/eu/data-act/trade-secrets-and-protection.md): Data Act guide for protecting trade secrets during access and sharing: classification, safeguards, refusal thresholds, notices, evidence records, and reviews. - [Data Act Unfair Contractual Terms | Article 13 B2B Contract Review](/artifacts/eu/data-act/unfair-contractual-terms.md): Review B2B data-sharing clauses under EU Data Act Article 13: unilateral terms, always unfair examples, presumed unfair terms, model clauses, evidence, and remediation. - [Data Act Vehicle Data Guidance](/artifacts/eu/data-act/vehicle-data-guidance.md): Commission-grounded guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries. - [Data Act vs GDPR: connected-product data access](/artifacts/eu/data-act/data-act-vs-gdpr.md): Compare EU Data Act connected-product access duties with GDPR personal-data rules: scope, roles, lawful basis, data subject rights, third-party sharing, trade secrets, and conflicts. - [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. - [EU Data Act Applicability Test](/artifacts/eu/data-act/applicability-test.md): Check whether a product, related service, data holder, cloud service, data-space role, smart contract, or B2G request is in scope of the EU Data Act. - [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. - [EU Data Act Article 3 Pre-Contract Information](/artifacts/eu/data-act/pre-contractual-information-obligations.md): What Article 3 of the EU Data Act requires before connected-product purchase, rent, lease, or related-service contracting: data categories, access, data holder identity, third-party sharing, complaints, and evidence. - [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. - [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. - [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. - [EU Data Act Checklist for Product, Cloud, and Contract Teams](/artifacts/eu/data-act/checklist.md): A grounded EU Data Act checklist for connected-product data access, third-party sharing, B2G requests, cloud switching, unfair terms, smart contracts, personal data boundaries, evidence, and owners. - [EU Data Act Cloud Switching and Exit Plans](/artifacts/eu/data-act/cloud-switching-and-exit-plans.md): A grounded EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records. - [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. - [EU Data Act Compliance Program](/artifacts/eu/data-act/compliance.md): Build a Data Act compliance program for connected-product data access, contracts, B2G requests, cloud switching, smart contracts, GDPR boundaries, records, and ownership. - [EU Data Act Connected Product Scope and Data Types](/artifacts/eu/data-act/scope-connected-products-and-data-types.md): Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs. - [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. - [EU Data Act Data Processing Service Switching](/artifacts/eu/data-act/data-processing-services-switching.md): A grounded EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure. - [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. - [EU Data Act deadlines and compliance calendar](/artifacts/eu/data-act/deadlines-and-compliance-calendar.md): A source-linked calendar for EU Data Act application dates, product design timing, contract remediation, cloud switching charges, response periods, standards work, and evidence records. - [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. - [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. - [EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates](/artifacts/eu/data-act/faq.md): 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. - [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. - [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. - [EU Data Act Penalties and Enforcement](/artifacts/eu/data-act/penalties-and-fines.md): Grounded guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary. - [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. - [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. - [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. - [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. - [EU Data Act requirements](/artifacts/eu/data-act/requirements.md): Source-grounded EU Data Act requirements for connected-product data access, B2B sharing terms, B2G exceptional needs, cloud switching, smart contracts, interoperability, GDPR boundaries, and records. - [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. - [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. - [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. - [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. - [EU Data Act User Access and Portability Rights](/artifacts/eu/data-act/access-rights-and-portability.md): Practical guide to EU Data Act user access, connected-product data portability, third-party sharing, trade secret safeguards, and the GDPR boundary. - [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. - [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. - [EU Data Act vs Data Governance Act](/artifacts/eu/data-act/data-act-vs-data-governance-act.md): Compare the EU Data Act with the Data Governance Act: connected-product access, cloud switching, B2B/B2G duties, protected public-sector reuse, intermediaries, altruism, governance, and enforcement. *Recommended next step* *Placement: after implementation section* ## Prepare a Data Act B2G compensation file Build a request file that separates public-emergency and non-emergency exceptional-need requests, documents eligible costs, and records confidentiality safeguards before the next public-sector request arrives. - [Open Research Copilot](/solutions/research-copilot.md): Check Chapter V request wording, compensation calculations, and source citations for Data Act B2G responses. - [Discuss B2G compensation](/contact.md): Review emergency, non-emergency, cost, confidentiality, and evidence handling for Data Act public-sector requests. --- [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/b2g-compensation-and-costs