Business@OptimusCyberX.ai+[00] [0000] [0000] AI-powered cybersecurity for small and mid-sized businesses · Building with AI? Visit Optimus AI →
Optimus CyberX, Cybersecurity Simplified
Get a free security assessment
Menu
EU data access and cloud switching law

The EU Data Act, what it means for your products and cloud services

See who gets access to connected-product data, what fair data-sharing contracts look like, and what cloud providers must offer when customers switch.

11 Jan 2024entered into force
12 Sep 2025applicable from
12 Sep 2026product design duty (Art. 3(1)) starts for new products
12 Jan 2027switching charges end

Official sources

Use these official places to read the regulation, the FAQ and the Commission guidance.

Official website

The European Commission page for the Data Act links to the regulation text, FAQs, model contract terms and the legal helpdesk.

Visit digital-strategy.ec.europa.eu ↗

Get the document

The regulation is published free in the Official Journal and on EUR-Lex. The Commission also publishes FAQs, draft model contractual terms and standard contractual clauses for cloud contracts.

Open the official page ↗

Works alongside

GDPR still governs any personal data covered by the Act. NIS2 and the Cyber Resilience Act cover the security side of connected products and services.

Browse all frameworks →

What EU Data Act is

The Data Act gives users of connected products, such as cars, machines and smart devices, a right to access and share the data those products generate. Makers and data holders must make it easy, usually free of charge, in a structured and machine-readable format.

It also bans unfair data contract terms between businesses, lets public bodies request data in exceptional need, and makes it easier to switch cloud providers by setting contract terms, a maximum notice period and an end to switching charges.

History

How EU Data Act got to where it is today

The milestones that changed what organisations have to do.

2020

European data strategy

The Commission's 2020 strategy for data focuses on putting people first in developing technology, and is the background to the Data Act.

2023

Regulation adopted

Regulation (EU) 2023/2854 is signed on 13 December 2023.

2024

Entered into force

The Data Act enters into force on 11 January 2024. Reduced, cost-limited switching charges are allowed from that date until 12 January 2027.

2025Current

Applies from 12 September

The Data Act applies from 12 September 2025. The unfair terms chapter applies to contracts concluded after that date.

2026

New products must be accessible by design

The product design duty in Article 3(1) applies to connected products and related services placed on the market after 12 September 2026. From 12 January 2027, providers may charge nothing for switching.

Dates are for orientation. The official website holds the authoritative record.

Do you need it?

If any of these sound familiar, probably yes.

1

You make or sell connected products, or provide services related to them, in the EU.

2

You hold data from connected products and receive requests from users or third parties.

3

You offer cloud, SaaS or other data processing services to EU customers.

4

You sign data-sharing contracts with other businesses and want terms that stand up.

What it asks of you

The requirements fall into six areas. The requirements-in-depth page walks through the chapters and articles.

01

User access to product data

Users can get the data their connected products and services generate, easily and free of charge.

02

Sharing with third parties

At a user's request, data holders pass data to a third party on fair terms.

03

Fair contract terms

Unilaterally imposed unfair data terms between businesses are not binding.

04

Data for public bodies

Data holders respond to duly reasoned public sector requests in exceptional need.

05

Cloud switching

Contracts, notice periods, assistance, data export and no switching charges after 12 January 2027.

06

International access and interoperability

Safeguards against unlawful foreign government access, plus interoperability duties.

The 5 chapter groups, 10 article groups and 32 obligations

Open any chapter to see what the Data Act asks of makers, data holders and cloud providers, and the records to keep.

10 article groups · 32 obligations

ch2Chapter II: Connected product dataAccess to product data for users and their chosen third parties.3 article groups · 8 obligations
art3Design and information duties (Art. 3)Build products so users can get their data, and tell them before they buy.3 obligations
  1. Art. 3(1)

    Design and make connected products, and design and provide related services, so product data and related service data, with the metadata needed to use it, are by default easily, securely, free of charge, structured, machine-readable and, where relevant and feasible, directly accessible to the user.

    What you do

    • Add a data export function to the product or service
    • Document the data format and metadata
  2. Art. 3(2)

    Before a purchase, rent or lease of a connected product, tell the user the type, format and estimated volume of data the product can generate, whether it is continuous and real-time, whether it is stored on the device or a remote server and for how long, and how to access, retrieve or erase it.

    What you do

    • Add a data information sheet to the sales process
    • Keep it up to date for each model
  3. Art. 3(3)

    Before a related service contract, give the user information on the nature, volume and collection frequency of data, how to access it, storage and retention, whether you will use the data and for what purposes, whether third parties may use it and who the data holder is.

    What you do

    • Include the information in the service terms
    • Offer a plain-language summary

Evidence to keep

  • Product data inventory
  • Pre-contract information sheets
  • Design requirements for data access
art4User access to data (Art. 4)Give users their data on a simple request when they cannot get it directly.2 obligations
  1. Art. 4(1)

    Where the user cannot access data directly, make readily available data and its metadata accessible without undue delay, of the same quality as you have, easily, securely, free of charge, in a structured machine-readable format and, where relevant, continuously and in real time, on a simple electronic request.

    What you do

    • Provide an online request form and an API or export
    • Set an internal response time target
  2. Art. 4(2)

    Users and data holders may restrict or prohibit access, use or sharing of data by contract only if it could undermine product security requirements in law and seriously harm the health, safety or security of people, and a refusal must be notified to the competent authority.

    What you do

    • Document the security reason for any restriction
    • Notify the authority when you refuse on this ground

Evidence to keep

  • Access request procedure
  • Request log and response times
  • Security restriction decisions
art56Sharing with third parties (Arts. 5 and 6)At the user's request, data holders pass data to a chosen third party, who must use it only as agreed.3 obligations
  1. Art. 5(1)

    On a user's request, make readily available data and metadata available to a third party without undue delay, at the same quality, easily, securely, free of charge to the user, in a structured machine-readable format, under the terms of Articles 8 and 9.

    What you do

    • Verify the user's request and the third party's identity
    • Share through a secure API or transfer
  2. Art. 6(1)

    A third party receiving data processes it only for the purposes and conditions agreed with the user, subject to data protection law, and erases it when no longer needed for the agreed purpose.

    What you do

    • Put purpose limits and deletion in the agreement
    • Audit use by recipients
  3. Art. 6(2)

    A third party must not make it unduly difficult for the user to exercise choices, including by manipulating or deceiving the user, and must not use the data for profiling unless necessary to provide the requested service.

    What you do

    • Use neutral consent screens
    • Ban profiling uses in the agreement

Evidence to keep

  • Third-party sharing requests and approvals
  • Sharing agreements
  • Third-party use restrictions
ch34Chapters III and IV: Terms and fairnessFair terms for sharing data between businesses.2 article groups · 5 obligations
art89Conditions for making data available (Arts. 8 and 9)Fair, reasonable and non-discriminatory terms for business-to-business data sharing.3 obligations
  1. Art. 8(1)-(2)

    When you must make data available to another business, agree the arrangements on fair, reasonable and non-discriminatory terms, transparently, and know that a term that is unfair or that cuts back the user's Chapter II rights is not binding.

    What you do

    • Publish standard terms for data recipients
    • Review terms against the unfair terms list
  2. Art. 8(3)

    Do not discriminate between comparable categories of data recipients, including your own partner or linked enterprises.

    What you do

    • Apply the same terms and pricing rules to like recipients
    • Record the reason for any difference
  3. Art. 9(1)-(2)

    Compensation agreed between a data holder and a data recipient must be non-discriminatory and reasonable and may include a margin, taking into account costs of making the data available and investments in producing it.

    What you do

    • Document how the charge is built from costs
    • Keep the calculation for audit

Evidence to keep

  • Standard data sharing terms
  • Compensation calculation basis
  • Records of any refusal or dispute
art13Unfair contract terms (Art. 13)Terms about data access and use that one business imposes on another can be unenforceable.2 obligations
  1. Art. 13(1)-(3)

    A data access or use term unilaterally imposed on another enterprise is not binding if it is unfair, meaning it grossly deviates from good commercial practice, contrary to good faith and fair dealing.

    What you do

    • Review standard terms for one-sided data clauses
    • Keep records showing terms were negotiated
  2. Art. 13(4)

    Treat as unfair terms that, for example, exclude or limit liability for intentional acts or gross negligence of the party that imposed the term, or exclude the other party's remedies.

    What you do

    • Remove liability exclusions that fall within the unfair list
    • Have legal review any new data clause

Evidence to keep

  • Contract term review checklist
  • Negotiation records
  • Standard clause library
ch5Chapter V: Data for public bodiesRequests in exceptional need.1 article group · 4 obligations
art1422Data for public bodies in exceptional need (Arts. 14 to 22)Respond to reasoned public sector data requests.4 obligations
  1. Art. 14-15

    Make data available on a duly reasoned request from a public sector body, the Commission, the European Central Bank or a Union body that shows an exceptional need, limited in time and scope, such as responding to a public emergency.

    What you do

    • Name a contact for public body requests
    • Check each request against the exceptional need conditions
  2. Art. 17

    Check that a request specifies the data, shows the exceptional need, explains the purpose, intended use and duration, the planned erasure, why you were chosen and who the data will be shared with.

    What you do

    • Use a checklist to validate incoming requests
    • Ask for missing information in writing
  3. Art. 18

    Make the data available without undue delay, and if you decline or seek changes to a request, say so promptly and within five working days where the data is needed to respond to a public emergency.

    What you do

    • Set a five working day response step
    • Record reasons for any refusal
  4. Art. 20

    Provide data needed for a public emergency free of charge unless you are a micro or small enterprise, and know you are entitled to fair compensation in other cases.

    What you do

    • Record whether the emergency exception applies
    • Keep cost records for compensation claims

Evidence to keep

  • Public sector request register
  • Decision and response records
  • Compensation records
ch6Chapter VI: Switching between data processing servicesContracts, charges and technical help for switching cloud providers.2 article groups · 9 obligations
art23-26Switching contracts and information (Arts. 23 to 27)Remove barriers to switching and say clearly how it works.5 obligations
  1. Art. 23

    Take the measures in Articles 25, 26, 27, 29 and 30 so customers can switch to another provider, to on-premises infrastructure, or use several providers at once, and remove commercial, technical, contractual and organisational obstacles.

    What you do

    • List current obstacles to exit and plan their removal
    • Allow porting after free-tier use
  2. Art. 25(1)

    Set the customer's switching rights and the provider's obligations out in a written contract that the customer can store and reproduce before signing.

    What you do

    • Provide the contract in a downloadable form
    • Include a switching schedule
  3. Art. 25(2)(a)-(d)

    Include clauses allowing switching or porting of all exportable data without undue delay and within a mandatory maximum transition period of 30 calendar days, with assistance and continuity during it, a maximum notice period of two months and support for the customer's exit strategy.

    What you do

    • Write the notice period and 30 day transition into the contract
    • Define the assistance the provider will give
  4. Art. 25(2)(e)-(i)

    List exhaustively the categories of exportable data and digital assets, any provider-internal data exempt from export for trade secret reasons, a data retrieval period of at least 30 days, full erasure after that and the switching charges allowed.

    What you do

    • Publish the list of exportable data
    • Delete customer data after the retrieval period and confirm it
  5. Art. 26-27

    Give customers information on available switching and porting procedures, methods and formats and known limits, and cooperate in good faith, including destination providers, to make switching work.

    What you do

    • Publish a switching guide
    • Name a switching contact

Evidence to keep

  • Switching procedure and exit plan
  • Contract terms on notice, transition and retrieval
  • Information published to customers
art29-31Charges and technical aspects (Arts. 28 to 31)No switching charges after 12 January 2027, transparency and technical help.4 obligations
  1. Art. 28

    Publish and keep up to date the jurisdiction that governs your ICT infrastructure for each service and a general description of measures to prevent unlawful international government access, and list those web pages in contracts.

    What you do

    • Add a transparency page per service
    • Reference the page in the contract
  2. Art. 29(1)-(3)

    Charge nothing for the switching process from 12 January 2027, and until then charge no more than the costs directly linked to switching.

    What you do

    • Remove switching and egress fees tied to switching by 12 January 2027
    • Cap interim fees at cost
  3. Art. 29(4)-(6)

    Give prospective customers clear information on standard fees, early termination penalties and any reduced switching charges before contract, flag services where switching is highly complex or costly, and publish this on a dedicated web page.

    What you do

    • Publish the price and penalty summary
    • Flag complex services openly
  4. Art. 30

    Providers of infrastructure-type services (such as servers, networks and virtual resources) take all reasonable measures to help the customer reach functional equivalence on the new service after switching.

    What you do

    • Publish open interfaces and export tooling
    • Offer migration support documentation

Evidence to keep

  • Charging policy
  • Website transparency pages
  • Technical switching documentation
ch78Chapters VII to X: International access, interoperability and enforcementSafeguards, standards and supervision.2 article groups · 6 obligations
art32-36International access and interoperability (Arts. 32 to 36)Safeguards for non-personal data and common interoperability expectations.4 obligations
  1. Art. 32(1)-(2)

    Take adequate technical, organisational and legal measures to prevent international or third-country government access to, or transfer of, non-personal data held in the Union where that would conflict with EU or national law, and recognise a third-country order only if it rests on an international agreement.

    What you do

    • Assess exposure to third-country access requests
    • Add contractual and technical safeguards such as encryption with customer-held keys
  2. Art. 33(1)

    Participants in data spaces that offer data or data services meet the essential interoperability requirements, starting with describing dataset content, licences, collection methods, quality and uncertainty in a machine-readable form.

    What you do

    • Publish dataset descriptions in a machine-readable format
    • Record licence and quality metadata
  3. Art. 34

    Support interoperability for customers who use data processing services in parallel by applying the main switching duties, and charge data egress fees for that parallel use only to pass on the costs actually incurred.

    What you do

    • Apply the cost pass-through rule to parallel-use egress charges
    • Keep cost records behind egress fees
  4. Art. 36(1)

    Vendors and deployers of smart contracts used to execute data sharing agreements make sure they meet essential requirements such as robustness and access control and safe termination and interruption.

    What you do

    • Review smart contract designs against the listed requirements
    • Add a safe stop function

Evidence to keep

  • International access safeguard assessment
  • Interoperability descriptions
  • Smart contract design records
art37-43Enforcement and related rules (Arts. 37 to 43)Authorities, penalties and the database right.2 obligations
  1. Art. 37-40

    Know that each Member State designates competent authorities (and a data coordinator where there is more than one), that users and others can lodge complaints, and that Member States set effective, proportionate and dissuasive penalties.

    What you do

    • Identify the competent authority in each Member State you serve
    • Keep complaint handling logs
  2. Art. 43

    Do not rely on the database sui generis right to block access to data generated by a connected product or related service that falls within scope, especially for Articles 4 and 5.

    What you do

    • Review database rights claims on product data
    • Update licences accordingly

Evidence to keep

  • Regulatory contact list
  • Complaint handling records

Outcomes and implementation examples are from Regulation (EU) 2023/2854 on harmonised rules on fair access to and use of data (Data Act), published by NIST. Descriptions of what to do and the evidence lists are our own plain-English guidance. Check the official source for the authoritative text.

Your path to getting started

Five steps from first look to ready. Effort depends on your size and starting point.

  1. 1

    Map your data

    List the connected products, related services and data you generate, store and share.

  2. 2

    Set up access routes

    Provide direct access or a simple request process with machine-readable exports.

  3. 3

    Update contracts

    Add the required pre-contract information, fair data terms and, for cloud, the switching terms.

  4. 4

    Handle third-party and public requests

    Define how you verify, decide, respond and record each request.

  5. 5

    Prepare to switch

    Cloud providers set export tools, notice periods, retrieval periods and charging policy.

How Optimus GRC helps

Each area maps to a part of the platform, so the work and the evidence sit together.

What it asksWhat you do in Optimus GRC
User access to product dataData access requests and responses
Sharing with third partiesThird-party sharing agreements and logs
Fair contract termsContract term reviews and negotiation records
Data for public bodiesRequest log and decisions
Cloud switchingSwitching contract terms and customer requests
International access and interoperabilityTransparency pages and safeguard records

Free EU Data Act readiness checklist

A one-page PDF you can print or share with your team. No sign-up needed.

Download the checklist (PDF)
  • Connected product data inventory
  • User data access request procedure
  • Data sharing agreement checklist
  • Cloud switching terms checklist

Share or cite this page

Writing about EU Data Act? You are welcome to link to this guide. Copy the link below.

<a href="/frameworks/eu-data-act/">EU Data Act explained in plain English - Optimus CyberX</a>

Common questions

When does the Data Act apply?

It entered into force on 11 January 2024 and applies from 12 September 2025. The design duty in Article 3(1) covers connected products and related services placed on the market after 12 September 2026, and switching charges must be zero from 12 January 2027.

Does it apply to personal data?

Yes, but it does not replace data protection law. Where personal data is involved the GDPR still applies, including the rights of data subjects.

What does a cloud provider have to do for switching?

Put a written contract in place that allows switching or exporting data without undue delay, with a maximum notice period of two months, a transition period of up to 30 days, a retrieval period of at least 30 days, full erasure afterwards and a clear list of exportable data.

Who enforces it?

Each Member State designates one or more competent authorities, with a data coordinator where there is more than one, and sets its own penalties that must be effective, proportionate and dissuasive.

Related frameworks

See how ready you are for EU Data Act

Answer questions across every area. We email you a report showing where you comply and where you do not.

Run your free assessment