Artifact GuideEUData Act

EU Data Act B2G Exceptional Need Requests

Review public-sector requests under Data Act Chapter V before exporting data: identify the , check the requester, narrow the dataset, protect personal data and trade secrets, and record the response.

Based on Regulation (EU) 2023/2854, the Commission Data Act explainer, and Commission Data Act FAQs. Use it as implementation support, not for legal interpretation.

Author
Sorena AI
Published
May 6, 2026
Updated
Jul 24, 2026
Overview

Chapter V of the EU Data Act lets public sector bodies, the Commission, the European Central Bank, and Union bodies request data from data holders only where an exists. The route is narrow: the request must be written, justified, proportionate, purpose-limited, protective of confidentiality and trade secrets, and closed with deletion or onward-sharing records.

Section 1

When a Chapter V exceptional-need request can be used

A Data Act B2G request starts with Article 14: the requester must demonstrate an for certain data, including metadata needed to interpret and use it, to carry out statutory duties in the public interest. The data holder must be a legal person other than a and must hold the requested data.

Article 15 limits to two routes. The first is data necessary to respond to a when the requester cannot obtain it by alternative means in a timely and effective way under equivalent conditions. The second is a non-emergency route for only, where a legally assigned public-interest task cannot be fulfilled without specific data and the requester has exhausted other means, including market purchase where available. That non-emergency route does not apply to microenterprises or small enterprises.

A must be an officially determined or declared exceptional situation that is limited in time and risks serious, lasting effects on living conditions, stability, or economic assets. Article 2 examples include a public-health emergency, a natural disaster, a human-induced major disaster, and a major cybersecurity incident; an event label alone does not satisfy the Article 15 necessity and alternative-means test.

  • Classify the request as public-emergency response or non-emergency before scoping data.
  • For non-emergency requests, check that the requested data is non-personal and that the requester explains the legal public-interest task.
  • Treat mitigation or recovery from a as a non-emergency Article 15(1)(b) case unless the request is for direct emergency response.
  • Do not direct a non-emergency Article 15(1)(b) request to a microenterprise or small enterprise.
  • Do not treat Chapter V as a general procurement shortcut, open-data route, audit power, or investigative authority.
Section 2

Which public functions fall outside Chapter V?

Chapter V does not replace reporting duties, access-to-information rules, or powers used to demonstrate or verify compliance under other Union or national law. A requester should use the legal route that actually grants the power instead of relabelling an existing obligation as .

Chapter V also does not apply when public bodies, the Commission, the European Central Bank, or Union bodies act to prevent, investigate, detect, or prosecute criminal or administrative offences, execute criminal penalties, or administer customs or taxation. Those activities remain governed by their own Union and national laws.

  • Identify the statutory task and confirm whether another reporting, audit, investigative, customs, taxation, or access-to-information power controls the request.
  • Return a request for clarification when the stated purpose mixes Chapter V with a separate enforcement power.
  • Keep the Chapter V analysis limited to the public-interest task and exceptional-need facts stated in the request.
Section 3

What a valid Chapter V request must include

Article 17 makes the request itself the control point. It must identify the data required, the metadata needed to interpret it, the , the purpose and intended use, the expected duration of use, the data holder chosen, any onward recipients, the legal provision assigning the public task, and the deadlines for both delivery and any decline or modification response.

The request must be written in clear, concise, plain language. It must be specific about data type, correspond to data the holder controls at the time of the request, and be proportionate in granularity, volume, and frequency. It must also address trade secrets, cost and effort, penalties for non-compliance, publication by the relevant data coordinator or EU body, and supervisory-authority notice where personal data is requested.

For a request directed to a data holder established in another Member State, Article 22 requires the requester to notify the competent authority in that Member State first. That authority examines the request and either transmits it to the data holder, with coordination advice where needed, or rejects it on substantiated Chapter V grounds.

  • Require requester identity, authority, public-interest task, purpose, requested data fields, metadata, period, and deadline.
  • Ask for the Article 15 facts that justify , not just a reference to the Data Act.
  • Check whether onward sharing with another body, researcher, statistical body, or third party is named in the request.
  • For a cross-border request, keep the prior notification, the establishment-state authority's examination, and its transmission, advice, or rejection.
  • Record whether the request was or should be made publicly available, unless publication would create a public-security risk.
Section 4

Chapter V data scope and personal-data limits

For response, the request should seek first. Personal data may be requested only if non-personal data is shown to be insufficient for the emergency need, and the request must specify necessary and proportionate technical and organisational measures, including pseudonymisation and whether anonymisation can be applied before disclosure.

For non-emergency , Chapter V is limited to . The request should therefore be narrowed to the specific data and metadata needed for the public-interest task, with unsuitable fields removed before extraction.

  • Separate non-personal, anonymised, pseudonymised, and personal data before delivery approval.
  • For emergency personal-data requests, document why is insufficient and whether anonymisation is possible.
  • For non-emergency requests, decline or seek modification if the request includes personal data.
  • Record source systems, fields, time range, format, metadata, transformations, exclusions, and unavailable data.
Section 5

How data holders can comply, decline, or seek modification

Article 18 requires the data holder to make data available without undue delay, taking account of technical, organisational, and legal measures. It also gives a controlled route to decline or seek modification where the holder does not control the data, a similar same-purpose request is already outstanding without erasure notice, or the request does not meet Article 17 requirements.

The response window is shorter for public emergencies: a decline or modification request must be made without undue delay and no later than five working days after receipt. For other exceptional-need requests, the outer limit is 30 working days. If the matter cannot be resolved by modification, either side may refer it to the competent authority in the Member State where the data holder is established.

  • Answer with delivery, narrowing questions, modification request, refusal, or competent-authority escalation.
  • Use the five-working-day outer limit for emergency decline or modification decisions.
  • Use the 30-working-day outer limit for other exceptional-need decline or modification decisions.
  • If relying on a previous same-purpose request, identify the earlier requester and keep the missing erasure notice in the file.
Section 6

Confidentiality, trade secrets, and use restrictions

Data received under Chapter V does not become open public-sector information. Article 17 bars reuse under the Data Governance Act and Open Data Directive frameworks, and Article 19 limits use to the purpose stated in the request. The receiving body must protect confidentiality, integrity, transfer security, personal data rights, and trade secrets.

Trade secrets may be disclosed only to the extent strictly necessary for the Article 15 purpose. The data holder or trade secret holder should identify protected data, including relevant metadata. Before disclosure, the public body or EU body must take necessary and appropriate technical and organisational measures to preserve confidentiality.

  • Mark trade-secret fields and confidentiality restrictions before transfer.
  • Require transfer-security, access-control, confidentiality, and deletion terms in the delivery note.
  • Do not allow the recipient to use data or insights to develop or improve a competing connected product or related service.
  • Do not treat Chapter V data as open-data material unless another lawful route independently applies.
Section 7

Compensation rules and cost records for B2G disclosures

For response, Article 20 requires data holders other than microenterprises and small enterprises to provide the necessary data free of charge, with public acknowledgement if requested. A microenterprise or small enterprise responding to an emergency request may claim fair compensation under the Article 20(2) calculation: technical and organisational costs, including specified transformation costs, plus a reasonable margin.

For non-emergency exceptional-need requests under Article 15(1)(b), the data holder is entitled to the same fair-compensation calculation. However, Article 15(2) excludes microenterprises and small enterprises from that non-emergency request route. No compensation is due for an official-statistics task where national law does not allow purchase of the data.

  • Classify the request before discussing compensation because emergency and non-emergency rules differ.
  • Keep a cost basis for extraction, security, transformation, anonymisation, pseudonymisation, aggregation, and technical adaptation.
  • Record whether the data holder is a microenterprise or small enterprise.
  • Escalate disputes about compensation to the competent authority where the data holder is established.
Recommended next step

Keep Chapter V requests as reviewable records

This guide helps structure intake, legal review, data scoping, safeguard terms, delivery or refusal records, compensation notes, and deletion evidence for Data Act B2G requests.

Section 8

Closure records and limits on onward sharing

The response file should close the loop. Article 19 requires the public body or EU body to erase data once it is no longer necessary for the stated purpose and to inform the data holder and onward recipients without undue delay, unless archiving is required under public-access-to-documents law.

Onward sharing is possible only within Chapter V limits. Article 21 allows sharing for compatible scientific research or analytics, or with national statistical institutes and Eurostat for official statistics. The data holder must be notified of onward sharing, including recipient identity, purpose, use period, and protection measures. Research or statistical recipients must follow the same core obligations and may keep the data for up to six months after the original recipient erases it.

  • Keep the original request, legal task, exceptional-need classification, data scope, and requester correspondence.
  • Keep delivery logs, transformation notes, confidentiality terms, compensation records, and acknowledgement requests.
  • Keep modification, refusal, or escalation records with dates and Article 18 grounds.
  • Keep erasure notices, onward-sharing notices, recipient safeguards, and any competent-authority complaint record.
Primary sources

References and citations

eur-lex.europa.eu9 citations
Referenced sections
  • Binding source for Chapter V B2G exceptional-need requests, including Articles 14 to 22 on request scope, content, response, safeguards, compensation, onward sharing, and cross-border cooperation.
  • Articles 14 and 15 define the duty to provide data and the two exceptional-need routes.
  • Article 16 preserves other legal duties and excludes specified offence-prevention, investigation, prosecution, criminal-penalty, customs, and taxation activities from Chapter V.
Show 6 more
  • Article 17 lists request contents, proportionality requirements, publication requirements, and notice duties; Article 22 sets the prior competent-authority route for cross-border requests.
  • Articles 17 and 18 set the non-personal data default, emergency personal-data conditions, anonymisation, and pseudonymisation rules.
  • Article 18 sets response duties, modification/refusal grounds, response timing, and competent-authority escalation.
  • Articles 17 and 19 set reuse limits, purpose limitation, security duties, and trade-secret safeguards.
  • Article 20 sets compensation rules for public emergency and non-emergency exceptional-need requests.
  • Articles 19 and 21 set erasure, notice, onward-sharing, and recipient-obligation rules.
ec.europa.eu6 citations
Referenced sections
  • Commission FAQ source for practical Chapter V validation checks, mitigation and recovery interpretation, cross-border request handling, onward-use limits, repetitive requests, and rights safeguards.
  • FAQ 43 explains that mitigation or recovery from emergencies is distinct from public emergency response.
  • FAQ 46 gives practical checks for verifying that a Chapter V request is justified and lawful.
Show 3 more
  • FAQ 49 explains the protection against repetitive same-purpose Chapter V requests.
  • FAQ 48 confirms requested Chapter V data does not become open public-sector information.
  • FAQ 48 explains purpose limitation, onward sharing, and deletion timing for Chapter V data.
digital-strategy.ec.europa.eu4 citations
Referenced sections
  • Commission explainer for Chapter V scenarios, public emergency and non-emergency distinctions, data types, stakeholders, deletion, once-only publication logic, and compensation summary.
  • Explains Chapter V as a public-interest access mechanism for exceptional need situations.
  • Summarises that non-emergency Chapter V requests may only concern non-personal data.
Show 1 more
  • The Commission explainer summarises what businesses may request for providing data under Chapter V.
Show all related guides (61)

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.

Data Act and Data Governance Act Overlap FAQ

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 Audit Evidence and Request Logs FAQ

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 Cloud Switching Contract Terms FAQ

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

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

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

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

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

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.