Artifact GuideEUData Act Article 3

EU Data Act Pre-Contract Information

Article 3 requires clear information before a user buys, rents, or leases a connected product, and before a related-service contract is concluded.

Use the required information to prepare product data sheets, checkout disclosures, contract schedules, and records of what the user received before contracting.

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

Article 3 of Regulation (EU) 2023/2854 requires clear pre-contract information for and related services. The disclosure duties in Article 3(2) and (3) have applied since 12 September 2025. They are separate from the design duty in Article 3(1), which applies to connected products and related services placed on the market after 12 September 2026. Article 3 does not create a CE-style conformity declaration.

Section 1

When Data Act Article 3 pre-contractual information must be given to the user

For a connected product, the seller, person renting out the product, or lessor must give the Article 3 product-data information before the purchase, rent, or lease contract is concluded.

For a related service, the provider must give the related-service information before the service contract is concluded. The information must be clear and comprehensible. For connected-product information, Recital 24 says the obligation may be fulfilled through a stable URL distributed as a web link or QR code, provided the user can store the information for future reference and reproduce it unchanged.

  • Use one disclosure set for the connected product and a separate disclosure set for each related service that obtains or generates data.
  • Check Article 7 before drafting. Chapter II does not apply to data generated through products manufactured or designed, or related services provided, by a qualifying microenterprise or small enterprise when the partner, linked-enterprise, and subcontracting conditions are also met. If the exclusion applies, record the facts and the resulting Chapter II outcome instead of issuing an Article 3 disclosure by default.
  • For an enterprise that has qualified as medium-sized for less than one year, Article 7 also excludes data from its and related services; connected products it places on the market receive the separate one-year product transition stated in Article 7. Record the date the enterprise became medium-sized and the product placement date.
  • Do not substitute a privacy notice, marketing brochure, warranty statement, or product compliance declaration for the Article 3 data-access information.
  • Keep a dated copy of the disclosure shown before contract conclusion so the business can establish which facts were presented for that product, service, channel, and transaction.
Section 2

Connected product disclosure items the Data Act requires before purchase

The connected-product disclosure should describe the product data the device is capable of generating. A useful version names concrete categories such as sensor readings, operating status, location or movement data, fault codes, environmental readings, user-interface events, battery status, or other product-specific telemetry when those categories apply.

Article 3 also requires information about whether the product can generate data continuously and in real time, whether it stores data on the device or on a remote server, the intended retention period where applicable, and how the user may access, retrieve, or erase the data.

  • List the type, format, and estimated volume of product data.
  • State whether continuous or real-time generation is possible.
  • State whether storage is on-device, remote, or both, and give the intended retention duration where applicable.
  • Describe the access, retrieval, and erasure route, including technical means, terms of use, and quality of service.
  • Name the format users can expect, such as API response, dashboard export, CSV, JSON, or another structured machine-readable format when available.
Section 4

Data holder identity, data use, and third-party sharing under the Data Act

The related-service disclosure must identify the prospective data holder by trading name and geographical address, and identify other data processing parties where applicable. It must also give fast and efficient communication means for contacting the prospective data holder.

The user also needs to know whether the prospective data holder expects to use readily available data itself, for which purposes, whether one or more third parties may use the data for purposes agreed with the user, and how the user can request sharing with a third party or end sharing where applicable.

  • Name the prospective data holder and contact route in the disclosure, not only in legal entity boilerplate elsewhere.
  • State the provider's own intended uses of readily available data in concrete terms, such as maintenance, service operation, diagnostics, product improvement, or another supported purpose.
  • Explain the user request path for sharing data with a third party and for ending that sharing.
  • Flag restrictions that follow from the Data Act itself, including that gatekeepers under the Digital Markets Act are excluded as eligible third parties under Article 5.
  • Where multiple parties provide an integrated product and service, identify which party the user contacts for which dataset.
Section 5

Data categories and boundaries in Data Act disclosures to avoid overclaiming

Article 3 disclosures should be specific enough for the user to understand what they can later access, but they should not promise access to data that is outside the Data Act access regime.

The Commission explainer states that Chapter II covers raw and pre-processed data generated from use of a connected product or related service that is readily available to the data holder, including relevant metadata. Inferred or derived data and protected content are described as out of scope unless another agreement or rule applies.

  • Separate raw and pre-processed data from inferred, derived, enriched, or proprietary analytics outputs.
  • Include metadata needed to interpret and use the data, such as timestamp, unit, source sensor, product identifier, or basic context where applicable.
  • Do not imply that the Data Act creates a new right for the data holder to use non-personal product data; Article 4 links that use to a contract with the user.
  • Where mixed personal and non-personal data is involved, state that personal data handling still depends on applicable data protection law.
  • Where trade secrets are involved, state the existence of trade-secret data and the identity of the trade secret holder where Article 3 requires it.
Section 6

Complaint, trade secret, and contract details the Data Act disclosure must list

The related-service disclosure must tell the user about the right to lodge a complaint alleging an infringement of Chapter II with the competent authority designated under Article 37.

It must also state whether the prospective data holder is the holder of trade secrets in the accessible or generated data. If the prospective data holder is not the trade secret holder, the disclosure must identify the trade secret holder. The same disclosure set must include the duration of the user-data-holder contract and termination arrangements.

  • Include a complaint notice that points to the competent-authority route rather than a generic customer-support promise.
  • Identify trade-secret status and the trade secret holder before the user contracts for the related service.
  • Explain the contract duration and termination route between the user and prospective data holder.
  • Align the complaint, trade-secret, and termination wording across the service terms, data-access terms, and customer help pages.
Section 7

Evidence to keep that Data Act Article 3 disclosures were actually provided

The evidence record should prove what the user saw before contracting and why the data facts were accurate at that time. It should connect customer-facing wording to the product architecture, service logs, API behavior, retention settings, and contracts.

Article 3 specifies the information to provide but does not prescribe this evidence pack. Keeping it is a practical control for release review, sales and ecommerce checks, user disputes, competent-authority questions, and later updates when product data, related-service data, access methods, or retention arrangements change.

  • Keep the exact disclosure version shown for each product, service, SKU, territory, and transaction channel.
  • Keep data-category inventories showing type, format, estimated volume, collection frequency, storage location, retention, and access or erasure route.
  • Keep technical proof for access routes, such as API documentation, export screenshots, data schema examples, quality-of-service terms, and account-request flow evidence.
  • Keep identity and role evidence for the data holder, data processing parties, trade secret holder, and third-party sharing path.
  • Keep release notes or change records showing when new data fields, firmware changes, service updates, retention changes, or third-party sharing changes required disclosure review.
Recommended next step

Review your Data Act Article 3 disclosure pack

Check whether product pages, order flows, related-service terms, data-access documentation, and evidence records all describe the same generated data, access route, retention, data holder, third-party sharing path, and complaint route.

Primary sources

References and citations

eur-lex.europa.eu8 citations
Referenced sections
  • Primary legal source for Article 3 pre-contract information, including data categories, access methods, data holder identity, complaint notices, trade secrets, contract details, Article 7 scope limits, and Article 50 application dates.
  • Articles 3, 7, and 50 set the pre-contract information duties, qualifying enterprise exclusions and transition, and application dates; the Article 3(1) design duty has a later product-market date.
  • Article 3(2) lists the minimum information for connected products, including data type, format, volume, real-time generation, storage, retention, and access or erasure methods.
Show 5 more
  • Article 3(3) lists the minimum information a related-service provider must give before contract conclusion.
  • Article 3(3) requires identity and contact information for the prospective data holder, disclosure of intended data use, and information on third-party sharing requests.
  • Recitals and Articles 3 and 4 distinguish accessible product and related-service data, relevant metadata, contractual use of non-personal data, personal-data limits, and trade-secret disclosures.
  • Article 3(3) requires complaint, trade-secret, contract-duration, and termination information before a related-service contract is concluded.
  • Article 3 defines the disclosure facts that this recommended evidence record should support for products and related services; it does not prescribe the record format.
digital-strategy.ec.europa.eu6 citations
Referenced sections
  • Official Commission explainer used for practical context on connected products, related services, raw and pre-processed data, user and data-holder roles, third-party sharing, and complaints.
  • Explains that Chapter II gives users of connected products and related services control over data generated through their use.
  • Gives practical examples of related services and distinguishes them from the connected product itself.
Show 3 more
  • Explains typical user, data holder, and third-party roles for connected products and related services.
  • Explains the practical scope of Chapter II data and the exclusion of inferred or derived data and content.
  • Supports evidence for practical access mechanisms, data holder roles, and user requests.
ec.europa.eu3 citations
Referenced sections
  • Official Commission FAQ used for enforcement and complaint-route context and for Chapter II interpretation points such as raw and pre-processed data.
  • Supports the link between Chapter II data access and raw or pre-processed data, including relevant metadata.
  • Explains that complaints should be directed to the relevant competent authority or data coordinator in the Member State.
Show all related guides (61)

Data Act Trade Secrets and Protection Measures

Data Act guide for protecting trade secrets during access and sharing: classification, safeguards, refusal thresholds, notices, evidence records, and reviews.

Data Act Unfair Contractual Terms | Article 13 B2B Contract Review

Review B2B data-sharing clauses under EU Data Act Article 13: unilateral terms, always unfair examples, presumed unfair terms, model clauses, evidence, and remediation.

Data Act Vehicle Data Guidance

Commission-cited guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries.

Data Act vs GDPR: connected-product data access

Compare EU Data Act connected-product access duties with GDPR personal-data rules: scope, roles, lawful basis, data subject rights, third-party sharing, trade secrets, and conflicts.

EU Data Act Applicability Test

Check whether a product, related service, data holder, cloud service, data-space role, smart contract, or B2G request is in scope of the EU Data Act.

EU Data Act 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.