Article 3 of the EU Data Act requires manufacturers to design connected products and related services so that the data they generate is accessible to the user by default, easily, securely and without charge. In practice this means deciding early which data is exposed, in what format, and how access is delivered, before the product ships.
Key takeaways
- Article 3 of the Data Act requires that data generated by connected products and related services is accessible to the user by default.
- Access must be easy, secure, without charge and provided in a structured, commonly used, machine-readable format.
- Design decisions about sensors, storage and interfaces made early determine how hard compliance becomes later.
- Information about the data a product generates must be given to the user before the contract is concluded.
What does Data Act Article 3 require from product design?
Article 3 requires that connected products and related services are designed and manufactured so that the data generated by their use is accessible to the user by default. The provision also defines the quality of that access: the data should be easily and securely accessible without charge, in a comprehensive, structured, commonly used and machine-readable format, and directly accessible where that is relevant and technically feasible.
The obligation also reaches the information a buyer receives before signing a contract. The user must be told what data the product can generate, including its nature, volume and collection frequency, and how that data can be accessed. This makes Article 3 a design requirement rather than only a documentation task, because a product that cannot expose its data cannot accurately describe it either.
The Regulation is Regulation (EU) 2023/2854, and the authoritative wording of Article 3, along with the provisions that set when the obligations apply, is available in the official Data Act text on EUR-Lex. This article is general information and not legal or tax advice. Read the application provisions in the official text before planning a release date, because they depend on when a product is placed on the market.
Which products and services fall under Article 3?
Article 3 covers connected products and related services whose use generates data, and the definitions in Article 2 of the official text decide whether a specific device is in scope. Teams should read those definitions against their actual product rather than relying on a general summary, as the Data Act on EUR-Lex sets out the exact terms.
In engineering terms, a connected product is an item that obtains, generates or collects data about its use or environment and can make that data available through an electronic communications service, a physical connection or on-device access. Related services are digital services connected to the product, such as an app or a cloud service, that affect the product's functions.
Grey areas are common. A sensor module inside a machine, a gateway that aggregates readings from several devices and a cloud dashboard can all be parts of the same system. Teams should map which component creates the data and which component holds the user relationship, because that mapping determines where access has to be provided.
How do you design a product so data is accessible by default?
Start with a data inventory, then decide for each data stream who needs it and through which interface it will be exposed. The design choices that follow are easier to make when every stream has a named purpose and owner.
A practical design sequence has six steps.
- Inventory the data. List sensor readings, event logs, error codes, configuration states and usage counters, and note how often each one is written.
- Classify each stream. Mark which streams contain personal data, since those also fall under the GDPR on EUR-Lex and need a lawful basis and data minimisation before they are exposed.
- Choose the access path. Options include an on-device export, a local interface on the network and a cloud endpoint. Each has different security and dependency consequences, covered in the next section.
- Define the format. Publish a versioned schema and data dictionary, using a structured, machine-readable format such as JSON or CSV with documented field meanings.
- Build authorisation. Confirm that the user, and any third party the user authorises, receives their own data and nothing beyond it.
- Write the pre-contract information. Produce a description of data types, volume, frequency and access routes that sales and documentation teams can reuse.
Where do these designs fail?
Most failures come from unclear data ownership, undocumented formats and access that depends on a service the manufacturer can switch off. Each failure has a clear mechanism, which makes it possible to design against it.
Format drift across firmware versions
A field renamed in a firmware update breaks every downstream integration built on the old schema. The failure is silent until a customer's dashboard shows empty values. Versioned schemas and automated tests against sample exports reduce that risk, though they add release effort.
Openness against security
A local interface that is easy to reach is also easy to attack. Access tokens should be scoped, expire and be revocable, and the export should be rate-limited. Stronger controls make integration harder for legitimate users, so the trade-off should be decided per data stream rather than once for the whole product.
Cloud dependency
A cloud-only export works well while the vendor runs the service. If the service is withdrawn, users lose access to historical data. Keeping a local export path, even a basic one, keeps the obligation meaningful for the life of the product.
| Criterion | On-device export | Local network interface | Vendor cloud endpoint |
|---|---|---|---|
| Works without the vendor service | Yes | Yes | No |
| Size of the security surface | Narrower | Moderate | Broader, shared infrastructure |
| Build effort | Low to moderate | Moderate | Moderate to high |
| Depends on continued vendor operation | No | No | Yes |
No single option satisfies every case, so many designs combine a local path for the user with a cloud path for authorised services.
Hypothetical examples
Here are two hypothetical scenarios:
A manufacturer of industrial pumps logs only alarm codes, written in a proprietary binary format that only its own service tool can read. Under an Article 3 review, the team would publish a documented export of operating states and alarm history, described in a versioned data dictionary, and expose it through a local interface that the operator controls.
A maker of connected kitchen appliances sends usage data only to its own app. The design question is whether a user can request the same stream for a second authorised service, and whether that request runs through a scoped token rather than a shared account login. The answer changes the architecture, not just the documentation.
How should a product team start?
Start with the data inventory and an access review before the hardware design is frozen, because late changes are the most expensive. Teams that already maintain APIs can reuse much of the same discipline for the export layer.
Rui Codex offers technical implementation support for system integrations and for custom software development, so engineering teams planning an export layer can bring in outside help for the build. Decisions about legal obligations remain with the manufacturer and its counsel. For the security side of cloud and data work, the security and GDPR engineering guides cover related practice.
- A complete list of data streams with their owners and update frequencies.
- A documented decision for each stream on whether it contains personal data.
- A chosen access path with a stated reason and a documented fallback.
- A versioned schema with test exports checked on every firmware release.
- Pre-contract information reviewed by the team responsible for sales documentation.
Frequently Asked Questions
Does Article 3 apply to every connected device?
No, Article 3 applies only to connected products and related services within the scope defined in the Regulation, so a team should check the definitions before assuming the obligation applies. Products that generate no data through their use, or that fall outside the definitions, are not covered by this obligation. Scope questions are best settled by reading Article 2 of the official text and, where needed, by taking legal advice.
Does the user have to get the data without charge?
Yes, Article 3 requires that the data be accessible to the user without charge, so a product design should not place basic data export behind a fee. Designers should check the official wording of the provision for the exact conditions. Charging for additional, separately defined services is a different question from charging for the user's own access to generated data.
What is the difference between accessible by default and directly accessible?
Accessible by default means the product is designed so users can obtain their data without special configuration or a request. Directly accessible is a narrower requirement that applies where relevant and technically feasible, and it means the user can reach the data from the device itself. Both requirements should be considered at the design stage rather than added later.
Do I need to tell customers what data is generated before they buy?
Yes, the Regulation requires pre-contract information on the nature, volume and collection frequency of the data, and on how it can be accessed. Put this information in the sales documentation and product information so it is available before the contract is concluded. Reviewing it whenever the firmware changes keeps it accurate.
How does the GDPR interact with Article 3?
Where the data includes personal data, the GDPR on EUR-Lex applies alongside the Data Act, so access must respect the lawful basis, data minimisation and the rights of other people in the data. Engineers should design the export with filtering and authorisation controls from the start rather than adding them after launch.
Conclusion
Article 3 turns data access into a product requirement, and the cheapest time to meet it is during design. Teams that inventory their data, choose access paths deliberately and version their schemas avoid the silent failures that come from retrofitting exports onto finished hardware. The trade-offs between openness, security and vendor dependency should be decided per data stream and recorded, so the reasoning survives staff changes. If you are planning a connected product or an export layer and want an engineering review of the access design, request a project consultation or email info@ruicodex.com to discuss your project.
Sources
- Regulation (EU) 2023/2854 on harmonised rules on fair access to and use of data (Data Act) - EUR-Lex, Publications Office of the European Union
- Regulation (EU) 2016/679 (General Data Protection Regulation) - EUR-Lex, Publications Office of the European Union