FAQEU Data ActB2G 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.

This FAQ helps separate free emergency responses, for non-emergency requests, cost evidence, confidentiality safeguards, and complaint records.

Author
Sorena AI
Published
May 6, 2026
Updated
Oct 15, 2026
Overview

Classify the Chapter V request before calculating compensation. Regulation (EU) 2023/2854 has applied since 12 September 2025. For public-emergency requests, data holders other than micro and small enterprises must provide the necessary data free of charge; under Article 20(3), a micro or small enterprise may claim under the Article 20(2) calculation, including technical and organisational costs plus a reasonable margin. For a qualifying non-emergency request, the data holder is entitled to the same calculation, but Article 15(2) excludes micro and small enterprises from that request route entirely. The official-statistics exception may also remove compensation where national law does not allow the public body to buy the data.

Search this module

Find a question or answer quickly

8 of 8 questions
Question 1

Can a data holder charge for a Data Act B2G request during a public emergency?

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.
Question 2

When can fair compensation be claimed for a non-emergency Data Act B2G request?

For non-emergency exceptional-need requests under Article 15(1)(b), a data holder is entitled to 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. Article 15(2) excludes microenterprises and small enterprises from this route.

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.
Recommended next step

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.

Question 3

Which costs can be included in fair compensation for a non-emergency exceptional-need request under the Data Act?

Article 20 says 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.
Question 4

Are microenterprises and small enterprises treated differently for Data Act B2G compensation?

Yes, for public-emergency requests. Article 20(1) requires data holders other than microenterprises and small enterprises to make public-emergency data available free of charge. Article 20(3) applies the Article 20(2) compensation rule when a microenterprise or small enterprise makes a claim, so the calculation covers the technical and organisational costs incurred to comply plus a reasonable margin. Micro and small enterprises are outside the non-emergency Article 15(1)(b) route.

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.
Question 5

Is compensation available for non-emergency requests used to produce official statistics under the Data Act?

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.
Question 6

How do confidentiality, trade secrets, and personal data affect the cost response under the Data Act?

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.
Question 7

What records should a data holder keep for Data Act B2G compensation and cost disputes?

Keep a request file that lets a later reviewer reconstruct the classification and calculation. The record 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.
Question 8

Why must a Data Act B2G request be classified before quoting compensation?

A fee quoted before request classification may apply the wrong Article 20 rule. 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.

  • 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.
  • Assign one accountable request owner and record the legal, data, security, and procurement contributors. Keep the response, source passages, calculation workpapers, approval date, and authority correspondence in the same file.
  • Reassess when the Article 15 route, holder size, data scope, purpose, confidentiality controls, or official-statistics purchase rule changes, and after a real request reveals a gap.
Primary sources

References and citations

eur-lex.europa.eu9 citations
Referenced sections
  • 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.
  • 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.
  • Article 15 defines non-emergency exceptional need and Article 20 gives data holders a fair-compensation entitlement for Article 15(1)(b) requests.
Show 6 more
  • Article 20 identifies eligible cost categories for non-emergency B2G compensation and requires calculation information when requested.
  • 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.
  • Article 20(4) removes compensation for certain official-statistics requests where national law does not allow purchase of the data.
  • Articles 17, 18, 19, and 20 connect proportional requests, trade-secret safeguards, personal-data measures, and eligible cost categories.
  • Articles 17, 18, 19, 20, and 21 support the recommended records for request content, response timing, erasure, onward sharing, and compensation disputes.
  • Chapter V provides different rules for emergency requests, non-emergency exceptional need, small-business status, official statistics, and compensation disputes.
digital-strategy.ec.europa.eu6 citations
Referenced sections
  • 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.
  • Commission guidance explains that Chapter V covers exceptional-need B2G access, including public emergencies such as disasters, pandemics, and cybersecurity incidents.
  • The Commission explainer summarizes Chapter V compensation by distinguishing public-emergency requests from non-emergency requests.
Show 3 more
  • The Commission overview distinguishes emergency and non-emergency treatment for micro and small companies; Article 20 is the binding source for the calculation.
  • The Commission explainer states that Chapter V requests must be specific, transparent, proportionate, protect trade secrets, and delete data when no longer needed.
  • The Commission explainer frames Chapter V as exceptional-need access and distinguishes emergency from non-emergency requests.
ec.europa.eu4 citations
Referenced sections
  • Commission FAQ used for practical checks on Chapter V request justification, market-purchase exhaustion, official-statistics context, and reuse limits.
  • The Commission FAQ explains that non-emergency Chapter V access should not displace market purchase where data can be bought at market rates.
  • The Commission FAQ discusses market purchase and the Article 15(3) exception for official statistics in Chapter V requests.
Show 1 more
  • The Commission FAQ identifies practical checks for whether a Chapter V request is justified and lawful, including requester identity, scope, purpose, proportionality, and notifications.
Show all related guides (61)

Data Act FAQ for Aftermarket Repair and Mobility Services

FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services.

Data Act SME Exceptions and Startups FAQ

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

FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence.

EU Data Act and Common European Data Spaces FAQ

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 and GDPR: Personal Data Overlap FAQ

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.

EU Data Act Application Dates and Transition FAQ

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 32: Foreign Government Access FAQ

FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers.

EU Data Act Article 36 Smart Contract Controls FAQ

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

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

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 Cloud Switching Procurement FAQ

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 Connected Product Scope FAQ

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 spaces interoperability FAQ

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 Direct Access by Design FAQ

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

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 Functional Equivalence: IaaS Switching FAQ

FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence.

EU Data Act Indirect Access Request Workflow FAQ

FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited.

EU Data Act Interoperability Standards: Articles 33-36

FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614.

EU Data Act Model Terms and Cloud Clauses FAQ

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.

EU Data Act Non-Emergency Public-Sector Request FAQ

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 Pre-Contractual Information FAQ

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 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 Public Emergency Request FAQ

FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records.

EU Data Act Readily Available Data FAQ

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

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 Smart Contracts for Data Sharing FAQ

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

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

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

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 Users, Data Holders, and Recipients FAQ

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

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: Non-Personal Data and Mixed Datasets

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.

Data Act and Common European Data Spaces

How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring.

Data Act B2B Data-Sharing Contract Clauses

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

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

A 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

A cited EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence.

Data Act Smart Contracts for Data Sharing

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 Trade Secrets and Protection Measures

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

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

Commission-cited 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

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 Applicability Test

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 Article 3 Pre-Contract Information

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 Checklist for Product, Cloud, and Contract Teams

A cited 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

A cited EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records.

EU Data Act Compliance Program

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

Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs.

EU Data Act Data Processing Service Switching

A cited EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure.

EU Data Act deadlines and compliance calendar

A cited 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 FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates

EU Data Act FAQ index covering connected-product access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, and application dates.

EU Data Act Penalties and Enforcement

Guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary.

EU Data Act Requirements by Workstream

EU Data Act requirements for connected-product access, B2B terms, B2G exceptional need, cloud switching, smart contracts, interoperability, GDPR boundaries, and records.

EU Data Act User Access and Portability Rights

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 vs Data Governance Act

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.