A sweeping new European law is reshaping the rules around data — who can access it, who can share it, and on what terms. The EU Data Act, which entered into force in January 2024 and became fully applicable in September 2025, is one of the most ambitious data-sharing frameworks ever enacted. While it originates in Brussels, its reach extends far beyond the European Union. If your company manufactures connected products sold in the EU, operates a cloud or data-processing service used by European customers, or provides software that generates or processes data on behalf of EU-based users, the EU Data Act applies to your business — regardless of where your company is headquartered.
Understanding this law is not optional for US companies with meaningful European operations or sales. The obligations it creates are substantial, the penalties for non-compliance are significant, and the structural changes it demands — from product design to contract terms to data portability infrastructure — take time to implement properly. This overview explains what the EU Data Act is, why it was created, who it affects, what it requires, and how it interacts with other EU regulations you may already be managing, including the GDPR.
Background: Why the EU Data Act Exists
The EU Data Act did not emerge in a vacuum. It is part of a broader European data strategy that includes the General Data Protection Regulation, the Data Governance Act, and the Digital Markets Act, all of which together aim to establish the EU as a trusted, competitive, and well-regulated digital economy. The Data Act specifically addresses a problem that regulators identified in the explosion of connected devices and data-driven services: enormous volumes of commercially valuable data are generated every day by products and services that consumers and businesses use, yet the people and companies that generate or purchase those products and services often have no practical ability to access, use, or benefit from that data.
Consider a factory that purchases industrial machinery equipped with sensors. That machinery constantly generates performance data, maintenance alerts, and operational metrics. Under the old rules, that data often belonged exclusively to the manufacturer — not the factory owner who paid for the equipment and whose operations generated the data. The factory owner could not take that data to a third-party maintenance provider, could not feed it into their own analytics systems, and had no leverage to demand access. The EU Data Act changes that by establishing a legal right of data access that runs in favor of users of connected products and services.
Beyond connected products, the regulation also addresses data sharing between businesses and government, the portability of data across cloud providers, unfair contractual terms in data-sharing agreements, and the legal reliability of smart contracts. These are not minor regulatory tweaks — they represent a fundamental repositioning of data rights across the European economy, and US companies operating in that space need to understand the landscape in detail.
Who the EU Data Act Applies To
The EU Data Act applies to a broad range of actors, and the extraterritorial scope is one of the first things US businesses need to grasp. You do not need to have a European subsidiary or a physical office in the EU to be subject to this law. What matters is whether your products or services generate, process, or handle data in connection with EU-based users.
The regulation applies to manufacturers and suppliers of connected products that are placed on the EU market. A connected product, in this context, means any physical device that collects and transmits data by design — smart home devices, wearables, industrial sensors, agricultural equipment, vehicles, medical devices, and countless other categories. If your company manufactures any such product and sells it in the EU, you are a data holder under the Act and are subject to its data access and sharing obligations.
The law also applies to providers of related services — meaning digital services that are connected to a physical product and without which the product cannot perform one or more of its functions. A companion app for a smart device, a cloud dashboard for industrial sensors, or a software platform that processes device-generated data all qualify as related services. Providers of these services, whether or not they are the device manufacturer, are subject to the Act.
Cloud service providers and data processing services used by EU-based customers are subject to the switching and interoperability provisions of the Act, which impose meaningful operational and contractual obligations. Additionally, any business that enters into data-sharing contracts with EU counterparts must ensure those contracts do not include terms that the Act deems unfair or abusive.
For non-EU companies, one significant requirement is the obligation to designate an EU legal representative if you manufacture connected products placed on the EU market but have no EU establishment. This representative acts as a point of contact for national competent authorities and can be held accountable for compliance failures. US companies that have been selling connected products into Europe without giving this much thought may find themselves needing to establish a more formal EU presence.
Connected Products and the Right to Data Access
The heart of the EU Data Act is the data access right established in Chapter II. This chapter creates a legal entitlement for users of connected products and related services to access the data generated by their use of those products, and to share that data with third parties of their choosing.
The access right applies to data generated during use — meaning the operational, behavioral, and performance data created as a result of how a user interacts with or operates a connected product. This does not override GDPR, which continues to govern personal data within that universe, but it does create a new layer of rights specifically around the data generated by the product itself.
As a manufacturer or service provider, you must make that data accessible to the user easily, securely, and in a machine-readable format, either directly from the device or through an online service. If the user instructs you to share the data with a third party — a competing service provider, a business partner, a maintenance company — you are generally obligated to do so. You cannot use technical barriers, contractual restrictions, or design choices to prevent that sharing, and you cannot use the data you receive in ways that would unfairly compete against the user or the third party.
There is a trade secret protection built into the law: a data holder can refuse to share data if doing so would cause serious economic harm through the disclosure of trade secrets. However, this exception is not a blanket right of refusal. You must demonstrate the genuine risk, and national authorities and courts can review such claims. The law also establishes a framework for trade secret protection agreements that allow data sharing to proceed with appropriate confidentiality safeguards in place.
For US companies, the practical implication is significant. If you design or manufacture connected products for the European market, you need to build data access and portability into the product architecture from the ground up. Retrofitting these capabilities into existing products can be technically complex and expensive. New product lines destined for EU sale should be designed with data access portability as a core requirement, not an afterthought.
Business-to-Business Data Sharing
Chapter III of the EU Data Act addresses the voluntary sharing of data between businesses, and it introduces an important safeguard against unfair terms in data-sharing contracts. Where a data holder agrees to make data available to a data recipient — for instance, a manufacturer sharing device data with a customer’s analytics platform — the contractual terms governing that sharing must not be abusive.
The regulation defines a set of contract terms that are presumptively unfair when used in data-sharing agreements with small and medium-sized enterprises. These include terms that grant the data holder the right to unilaterally determine whether data is accessible, terms that limit the data recipient’s liability in ways that are disproportionate, and terms that prevent the data recipient from using the data to develop competing products or services. The law gives national courts and authorities the power to invalidate or modify such terms.
The pricing rules for data access are governed by the FRAND standard — Fair, Reasonable, and Non-Discriminatory. If you are a data holder providing access to data, the compensation you charge must be reasonable and must not discriminate between similarly situated recipients. This standard is familiar from the intellectual property licensing context, but applying it to data creates new challenges around valuation, documentation, and consistency that businesses need to manage carefully.
Business-to-Government Data Sharing
Chapter V of the EU Data Act creates a mechanism for government bodies to request data from private companies in exceptional circumstances. This is distinct from law enforcement data requests under other legal frameworks — the Data Act’s B2G mechanism is intended for situations like public emergencies, natural disasters, or circumstances where private data is needed to support essential public functions that cannot be served through other means.
A public sector body in an EU member state can request that a data holder provide specific data when there is a legitimate need that is proportionate, limited in scope, and subject to safeguards including confidentiality protections and restrictions on secondary use. The data holder may be entitled to compensation, and the request must meet defined criteria that are subject to judicial review. For most US businesses, this chapter is less immediately pressing than the connected product and cloud switching provisions, but companies with significant EU data assets — particularly in regulated sectors — should understand the framework and have internal procedures for evaluating and responding to such requests.
Cloud Switching and Interoperability
One of the most operationally significant aspects of the EU Data Act for technology companies is the cloud switching and interoperability framework set out in Chapters VI and VII. These provisions are aimed at reducing vendor lock-in in the cloud market and ensuring that EU customers can move their data and workloads between cloud providers without unreasonable friction or cost.
Under the Act, cloud service providers must ensure that customers can switch to a competing provider or to an on-premises solution without losing access to their data or being impeded by technical barriers. Switching fees — charges imposed on customers who want to retrieve their data and move it elsewhere — must be phased out entirely by January 12, 2027. After that date, any switching fees are unlawful.
Beyond pricing, cloud providers must provide functional equivalence during the switching process, meaning the customer’s data and service configurations must be transferred in a way that allows them to resume operations with the new provider without material degradation. Providers must also make available interfaces and documentation sufficient to enable interoperability with other services, and they must cooperate with the development of open interoperability standards.
For US cloud service providers with European customers, these provisions require a close look at existing customer agreements, pricing structures, and technical export capabilities. Standard contracts that impose exit fees or technical barriers to data export will need to be updated to comply. The compliance window is not long, and retrofitting switching infrastructure into existing platforms takes engineering resources and time.
Smart Contracts and Automated Data Sharing
Article 36 of the EU Data Act introduces requirements for smart contracts used in data-sharing arrangements. A smart contract, in this context, is any automated program that executes data-sharing obligations based on predefined conditions — typically deployed on a distributed ledger or blockchain infrastructure. The Act does not ban or restrict smart contracts, but it does require that smart contracts used for data sharing be designed to meet certain safety standards.
Specifically, smart contracts used in the context of the Data Act must include mechanisms that allow parties to terminate or interrupt execution, must be resistant to modification by unauthorized parties, and must not use data in ways that go beyond what was agreed. There are also requirements around auditability and transparency so that the parties can verify what the smart contract is doing with their data. For companies exploring blockchain-based data sharing in connection with EU operations or EU-based counterparts, these requirements will need to be incorporated into smart contract design and documentation from the outset.
International Transfers of Non-Personal Data
Chapter IX of the EU Data Act addresses transfers of non-personal data to third countries — that is, countries outside the EU. This is distinct from GDPR, which regulates international transfers of personal data. The Data Act’s transfer provisions apply to non-personal data held by cloud providers and other data processing services, and they create a framework for preventing transfers that would conflict with EU law or result in foreign government access that is disproportionate or lacks due process protections.
Cloud and data processing providers must take technical, legal, and organizational measures to prevent unlawful transfers of non-personal data to third countries. If a foreign government or authority issues an order requiring the disclosure of non-personal data held in the EU, the provider must challenge that order if it conflicts with EU law or with the rights of the data owner. For US companies providing cloud or data processing services to EU customers, this provision creates compliance obligations around how you respond to US government data requests affecting data held in your EU infrastructure. Legal counsel familiar with both US and EU law will be essential for navigating these competing obligations.
How the EU Data Act Relates to GDPR
Many US businesses are already managing GDPR compliance and naturally want to understand how the EU Data Act fits into or overlaps with that framework. The short answer is that GDPR and the Data Act operate in parallel and address different problems — they are complementary rather than redundant, but they intersect in ways that require careful management.
GDPR governs the processing of personal data — information that identifies or is identifiable to a natural person. It establishes legal bases for processing, data subject rights, data breach notification obligations, and much more. The EU Data Act, by contrast, is primarily focused on non-personal data generated by connected products and services, and on the structural rules around data access, sharing, and portability across the economy.
In practice, the data generated by connected products and services is often a mix of personal and non-personal data. A smart device might generate telemetry data that is entirely about machine performance and qualifies as non-personal, but it might also generate location data or usage patterns that constitute personal data under GDPR. The EU Data Act explicitly states that where data subject rights under GDPR apply to personal data, those rights take precedence. Data holders cannot invoke the Data Act’s access obligations to share personal data in ways that would violate GDPR.
The practical result is that any data access system you build to comply with the EU Data Act must have a layer that identifies whether the data being accessed is personal or non-personal, and routes personal data through your GDPR compliance infrastructure. This is not a simple technical exercise for most organizations, particularly those that have not previously invested in data classification and tagging at scale. Throughout this section, the pages on GDPR and Data Act interaction explore this overlap in practical depth.
Key Timeline and Compliance Dates
The EU Data Act was published in the Official Journal of the European Union on December 22, 2023, entered into force on January 11, 2024, and became fully applicable on September 12, 2025. This 20-month implementation period was intended to give businesses time to prepare, but many companies — particularly those that are not deeply embedded in EU regulatory compliance processes — may still be catching up.
The cloud switching fee phase-out has a separate deadline: switching fees must be eliminated entirely by January 12, 2027. Until that date, they can be charged at reduced rates under specific conditions, but the trajectory is clearly toward elimination. New connected products placed on the EU market after September 2025 must comply with the data access and portability requirements from day one. Existing products that were already on the market before that date benefit from a transition period, but manufacturers should not assume that older product lines are permanently exempt — the law encourages compliance across the product portfolio.
Enforcement and Penalties
Enforcement of the EU Data Act is handled by competent national authorities designated by each EU member state, with coordination at the EU level. The penalties for non-compliance are substantial: fines of up to €20 million or up to 4% of total worldwide annual turnover for the preceding year, whichever is higher. For cloud providers and data holders who violate the international transfer provisions, the maximum fine rises to up to 6% of worldwide annual turnover.
These penalty levels are deliberately aligned with GDPR enforcement to signal the seriousness with which EU authorities view data rights. If your company generates significant revenues from EU-connected operations, the potential exposure from a material compliance failure is very large. Regulators have signaled that they intend to enforce the Data Act actively, and early enforcement actions are likely to target high-profile sectors — connected consumer devices, cloud infrastructure, and industrial IoT — where the economic stakes are highest and the market visibility is greatest.
Beyond financial penalties, national authorities can order injunctive relief — requiring a non-compliant company to cease certain practices, modify its products or services, or implement specific technical or contractual changes. For companies with significant EU market positions, reputational consequences and operational disruptions from enforcement action can be just as damaging as the financial penalties themselves.
What US Businesses Should Do Now
The EU Data Act has been fully applicable since September 2025, meaning the time for monitoring and preparation has passed — this is now a live compliance obligation. US businesses with EU market exposure should be working through several key workstreams if they have not already done so.
The first step is a scope assessment: understanding which of your products, services, and operations fall within the regulation’s reach. This means reviewing your connected product portfolio, your cloud and data services offerings, your B2B data-sharing agreements with European counterparts, and your data processing infrastructure. If you have not done this mapping exercise yet, it is the logical starting point for everything else.
The second step is a contract review. Existing data-sharing agreements, cloud services agreements, and related service terms need to be evaluated against the Data Act’s requirements. Terms that restrict data access rights, impose unjustified switching fees, or include abusive B2B provisions need to be revised. New contracts need to be drafted with the Data Act framework built in from the outset.
The third step is product and technical compliance. If you manufacture connected products or provide related services, you need to assess whether your data access and portability infrastructure meets the regulation’s requirements. This may involve engineering changes to existing products, new documentation requirements, and the establishment of secure data-sharing interfaces. If you are a cloud provider, your switching and interoperability capabilities need to be assessed and updated where necessary.
The fourth step is governance and legal representative designation. Non-EU manufacturers of connected products that lack an EU establishment need to designate a legal representative. Governance processes for handling data access requests, B2G requests, and smart contract deployments need to be established and documented. Throughout all of this, coordination between your legal, technical, commercial, and product teams is essential — the EU Data Act is not a compliance checkbox that your legal department can address in isolation.
Exploring the EU Data Act in Depth
The pages in this section go deeper on each major aspect of the EU Data Act, organized into clusters that align with the regulation’s core chapters and compliance challenges. Whether you are approaching this law as a connected product manufacturer, a cloud service provider, or a legal professional advising US clients with EU exposure, the individual topic pages provide the granular analysis needed to understand your obligations and structure your compliance program.
Topics covered include the scope and territorial reach of the regulation, the technical requirements for data access in connected products, the rules governing B2B and B2G data sharing, the cloud switching and interoperability framework, the interaction between the Data Act and GDPR, enforcement and penalties across EU jurisdictions, and the contractual tools for managing data-sharing relationships under the new legal framework. Each page is written for US business owners and legal professionals who need clarity on how this regulation affects real-world operations and transactions.
