Applicability TestEUData Act

EU Data Act Applicability Test

Classify whether a connected product, related service, data holder, cloud service, data-space role, smart contract, or public-sector request is in scope.

Use the test to separate Chapter II product-data duties from B2B, B2G, cloud switching, interoperability, smart-contract, and exclusion questions.

Author
Sorena AI
Published
May 6, 2026
Updated
May 6, 2026
Sections
8

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 6, 2026
Updated May 6, 2026
Overview

Use this applicability test before promising Data Act access, portability, switching, contract remediation, or public-sector response work. The useful output is a scoped answer for a specific product, service, contract, data request, or technical role, not a generic statement that the organization is or is not covered.

Section 1

Start with the Data Act chapter, not the brand or business unit

The Data Act applies through different role and scenario tests. Article 1 covers manufacturers of connected products placed on the Union market, providers of related services, users in the Union, data holders making data available to data recipients in the Union, public-sector exceptional-need requests, providers of data processing services to customers in the Union, data-space participants, and vendors or deployers of smart contracts used to execute data-sharing agreements.

A single company can therefore be out of scope for one workflow and in scope for another. For example, a manufacturer may have Chapter II duties for a connected machine, Chapter IV exposure in a data-sharing contract, and Chapter VI duties only if it also provides a qualifying data processing service.

  • Identify the concrete scenario: connected product, related service, B2B data-sharing term, B2G request, data processing service, data-space participation, or smart-contract deployment.
  • Name the actor role in that scenario: manufacturer, provider, user, data holder, data recipient, customer, public-sector body, data-space participant, smart-contract vendor, or smart-contract deployer.
  • Record the EU nexus: placed on the Union market, user or recipient in the Union, services provided to customers in the Union, non-personal data held in the Union, or public authority request covered by Chapter V.
  • Keep separate conclusions for each chapter; do not use a product-family or corporate-level answer as the applicability decision.
Section 3

Data Act Classify users, data holders, and recipients before promising access

A user is a natural or legal person that owns a connected product, has temporary contractual rights to use it, or receives related services. The FAQ warns that ordinary use of a product inside a service, such as being a passenger, does not automatically make that person the Data Act user of the connected product.

A data holder is the person with the right or obligation to use and make available data under the Data Act or other applicable EU or national law. A data recipient is a business actor, other than the user, to whom the data holder makes data available. Data Act Chapter II third-party sharing is limited to recipients in the Union, and DMA gatekeepers cannot be the third party under that mandatory IoT data-sharing route.

  • Tie the user role to ownership, rental, lease, temporary contractual use rights, or receipt of a related service.
  • Identify every likely data holder, including a manufacturer, related-service provider, fleet operator, or service provider that lawfully obtains readily available data.
  • Check whether the requested recipient is in the Union and is not relying on the Article 5 route as a DMA gatekeeper.
  • Where the request involves personal data and the user is not the data subject, require a separate GDPR legal-basis check before access or onward sharing.
Section 4

Data Act Separate in-scope product data from derived, protected, or unavailable material

Chapter II is about product data and related-service data that are readily available to a data holder. The Commission describes the core in-scope set as raw and pre-processed data, including metadata needed to understand and use it. Data does not leave scope simply because privacy-enhancing technologies such as anonymisation, pseudonymisation, or encryption were applied.

Do not treat all analytics as user-access data. The FAQ places highly enriched data, inferred or derived data, data resulting from additional investments, and content often protected by intellectual property rights outside the Chapter II access set. The test should therefore distinguish sensor measurements, status logs, usage events, and necessary metadata from proprietary scores, predictions, models, reports, or creative content.

  • List product data, related-service data, and metadata separately.
  • Mark whether each category is raw, pre-processed, inferred, derived, content, personal data, non-personal data, or trade-secret material.
  • Record why data is readily available or not readily available, including whether it can be lawfully obtained without disproportionate effort beyond a simple operation.
  • For edge processing, document whether raw or pre-processed data was stored, retrievable, or transmitted externally at any point.
Recommended next step

Data Act Turn the applicability test into a working record

Use the chapter, actor, EU nexus, data category, exclusion, and safeguard fields from this page to create a cited Data Act applicability worksheet for product launches, contract reviews, request handling, and cloud switching.

Section 5

Data Act Check exclusions, safeguards, and delayed Chapter II design duties

Chapter II does not apply to data generated through connected products manufactured or designed, or related services provided, by a microenterprise or small enterprise, unless the enterprise is linked to a larger enterprise or is subcontracted to manufacture, design, or provide the service. A medium-sized enterprise has a narrower temporary carveout for products placed on the market during the first year after it first qualifies as medium-sized.

Even when Chapter II applies, access is not absolute. The Data Act preserves GDPR and privacy law, allows narrowly framed security restrictions, and protects trade secrets through proportionate technical and organisational measures. Article 50 also delays the Article 3(1) design-by-default duty for connected products and related services placed on the market after 12 September 2026.

  • Check microenterprise, small-enterprise, linked-enterprise, partner-enterprise, and subcontracting facts before applying the Chapter II SME exclusion.
  • Do not use the SME exclusion for other chapters unless the specific chapter supports that result.
  • Escalate personal-data requests where the requester is not the data subject or where several users or data subjects are involved.
  • For trade secrets, record the protected data, the confidentiality measures offered, and whether any refusal is based on the Data Act's exceptional serious-economic-damage test.
Section 6

Data Act Run a separate test for cloud and data processing services

Chapter VI does not depend on a connected product. It applies to providers of data processing services that provide qualifying services to customers in the Union, including cloud and edge models that enable on-demand network access to configurable, scalable, and elastic computing resources.

For cloud applicability, identify the source provider, customer, service type, exportable data, digital assets, switching route, and any custom-built or testing-only service status. Article 31 excludes non-production testing and evaluation services provided for a limited period, and gives certain custom-built services a lighter regime rather than removing every Chapter VI duty.

  • Classify the service as IaaS, PaaS, SaaS, edge, or another data processing service only if it meets the Article 2 definition.
  • Map the contract, service catalogue entry, exportable data, digital assets, source provider, destination provider, and any on-premises target.
  • Check whether the service is custom-built for one customer and not offered at broad commercial scale, or is a non-production testing and evaluation service for a limited period.
  • Do not apply connected-product raw-data rules to cloud switching; use the Chapter VI switching, portability, open-interface, and contract tests instead.
Section 7

Data Act Check B2G requests, data spaces, and smart contracts only when those facts exist

A public-sector request is in the Data Act's Chapter V route only where a public sector body, the Commission, the European Central Bank, or a Union body demonstrates an exceptional need for specific data to perform a statutory public-interest task. Non-emergency requests are limited to non-personal data and require the requester to show why other means were exhausted.

Data-space and smart-contract scope is a different test. Article 33 applies to participants in data spaces that offer data or data services to other participants. Article 36 applies to vendors of applications using smart contracts, or deployers of smart contracts for others, where the smart contract executes all or part of an agreement to make data available.

  • For B2G requests, capture the requesting body, statutory task, exceptional-need basis, data categories, metadata, proportionality, purpose, deadline, erasure plan, and trade-secret or personal-data safeguards.
  • For data spaces, confirm the organization offers data or data services to other participants before applying Article 33 interoperability requirements.
  • For smart contracts, confirm the program automates execution of a data-sharing agreement before applying Article 36 requirements such as robustness, access control, safe interruption, archiving, continuity, and consistency with the agreement.
  • If the facts only show ordinary voluntary sharing, procurement, analytics, hosting, or a blockchain component not used to execute data sharing, do not label the scenario as Article 33 or Article 36 scope.
Section 8

Data Act Write the applicability result as a scoped conclusion

The final record should say exactly what is in scope, what is out of scope, what chapter applies, and which facts remain unresolved. A useful conclusion is specific enough for product, legal, procurement, cloud, security, and support teams to act without re-litigating the whole scenario.

Use exclusion labels carefully. The Data Act does not apply to areas outside Union law, certain criminal-law, customs, taxation, public-security, defence, and national-security matters, and it does not supersede GDPR, privacy, IP, consumer-protection, or sector-specific data-access rules. Those overlaps should be recorded as parallel legal checks, not as shortcuts around the Data Act.

  • State the conclusion as in scope, out of scope, partly in scope, or unresolved pending named facts.
  • Attach the chapter and article basis, actor role, EU nexus, data categories, exclusions, safeguards, and owner for the next action.
  • Keep launch, contract, request-response, and cloud-switching decisions in separate rows if they rely on different facts.
  • Update the record when product architecture, service packaging, market placement, customer location, data flows, or official guidance changes.
Primary sources

References and citations

digital-strategy.ec.europa.eu
Referenced sections
  • The Commission explainer summarizes B2G exceptional-need conditions, data-space interoperability, and smart-contract requirements.
ec.europa.eu
Referenced sections
  • The FAQ supplies practical boundary examples for Chapter II, Chapter IV, Chapter V, Chapter VI, enforcement, and legal-representative analysis.
Related guides

Explore more topics

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 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 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.
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 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 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
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
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 Functional Equivalence FAQ
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
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
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
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
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
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
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
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.
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-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
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
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 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 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 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 Checklist for Product, Cloud, and Contract Teams
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
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
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
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 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 Processing Service Switching
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
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
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
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 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.
EU Data Act Non-Emergency Public-Sector Requests 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 Non-Personal Data and Mixed Datasets FAQ
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
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
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
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
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 requirements
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
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 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 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 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.