Author: Maciej Ramus, CMO and co-founder of JSON Crew.
A rental company has forty of your excavators. Its boss calls you: “I want the data from the machines: operating hours, faults, fuel consumption. I’ll give it to a service company in our town, because it’s closer than your service team.” A few years ago you could have replied that the data from your machines belongs to you. Today, in the European Union, that answer is against the law.
Since 12 September 2025, the EU regulation on data has applied, known in English as the Data Act (Regulation (EU) 2023/2854). On 12 September 2026 a further obligation took effect, one that reaches into the design itself: every new device model must be designed so that the user has access to its data. This article is for manufacturers of machines and devices: what exactly you must make available, to whom, from when, who is exempt and how to build it so you don’t end up exporting files by hand for every customer.
In short:
- The Data Act (Regulation (EU) 2023/2854) gives the user of a machine or device the right to the data it generates. It has applied since 12 September 2025, and from 12 September 2026 every new model must have access to this data designed in from the start.
- Before the sale, the manufacturer must tell the customer what data the device collects and how to retrieve it, and then provide it free of charge, in a machine-readable format, including to a company the customer nominates, such as an independent service provider.
- It works both ways: the manufacturer may use non-personal data from the customer’s device only on the basis of a contract with that customer. If your service, warranty or predictive maintenance relies on this data, check your contracts.
What is the Data Act and why does it affect machine manufacturers?
The Data Act is an EU regulation that sets out who may use the data generated by connected devices. It applies directly, just like the GDPR: you don’t need to wait for a Polish act to apply its provisions.
The starting point is simple. The EU legislator noticed that a manufacturer who controls the design of a device in practice decides who sees its data, even though it has no special right to that data. The customer bought the machine, works with it, pays for fuel and inspections, yet only the manufacturer sees the data from that work. The Data Act reverses this: whoever uses the device must also get the data from its use.
For a manufacturer, this means three groups of obligations. The first is design: access to data must be planned into the product. The second is information: before the sale, the customer must know what data the device generates and how to retrieve it. The third is providing data: at the user’s request, to the user or to a company they nominate.
Is your device a “connected product”?
The Act refers to a connected product (Art. 2(5)). This is an item that obtains or generates data about its use or environment and can communicate that data: over a network, through a physical connection or from on-device storage. Its primary function must not be storing or processing data on behalf of someone else, which is why servers and network drives don’t count.
In practice, this covers almost every modern machine and device with electronics: an excavator with telematics, a heat pump with an app, a boiler with a WiFi module, a packaging line with a control panel, a forklift, an e-bike. Important: a service port on its own also counts. If your service technician downloads data by cable from a socket on the controller, the device can communicate data, even without internet access.
Out of scope is a device whose design does not provide for data leaving the controller at all. The Act also does not require you to generate new data or store more than the design provides for. According to the recitals of the regulation, it also does not cover information derived from the data, such as the output of your algorithm that predicts failures from sensor readings. Raw readings yes, your analysis no.
Check your model with four questions.
With the default settings (data over the internet, medium-sized or large manufacturer, model already on sale, you as the manufacturer), 3 of the 4 obligations apply to you. Switch the model to a new one placed on the market after 12 September 2026 and a fourth is added: access designed into the device.
What exactly you must make available from 12 September 2026
Art. 3(1) states that a connected product and its related service must be designed so that product data and related service data, together with the metadata needed to interpret them, are accessible to the user:
- by default, meaning without filling in requests or waiting for the manufacturer’s approval,
- easily and securely,
- free,
- in a comprehensive, structured, commonly used and machine-readable format, for example CSV or JSON, not a screenshot or a PDF,
- directly from the device, where relevant and technically feasible.
Product data is everything the device generates during operation: sensor readings, operating hours, cycle counters, error codes, operating states, energy consumption. A related service is software without which the device could not perform one of its functions, or which controls it remotely, usually your app or portal. Its data includes, for example, the history of settings the customer has changed in the app.
Without metadata, raw data means nothing. A column labelled “T3” with the value 412 is a puzzle for the customer. A description saying that T3 is hydraulic oil temperature in tenths of a degree, sampled every 10 seconds, turns it into information. You must make this description available too.
An important clarification from practice: in its answers to frequently asked questions, the European Commission stresses that the Act does not impose a single design approach. You can choose whether the data is available in an app, through an API, from a port on the device or from a customer portal. What counts is the result: access that is by default, easy and free of charge.
What you must tell the customer before they sign the contract
This obligation (Art. 3(2)) rests on whoever sells, rents or leases the device. That may be the manufacturer, but also a dealer or a rental company. Before the contract is concluded, the customer must receive at least:
- the type, format and estimated volume of data the device is capable of generating,
- whether the data is generated continuously and in real time,
- whether the data is stored on the device or on a remote server, and for how long,
- a description of how the customer can access or delete it, including the technical means, terms of use and quality of service.
For a related service (an app or portal) the list is longer (Art. 3(3)). It adds, among other things: whether the prospective data holder intends to use the data itself and for what purpose, who the data holder is and how to contact them, how to request that the data be shared with another company, the right to lodge a complaint with the competent authority, whether the data contains trade secrets and whose, and how long the contract lasts and how to terminate it.
The recitals of the regulation themselves suggest the simplest approach: a stable web address with a description of the data, handed out as a link or QR code on the product sheet and in the offer. One page per model, in the local language, maintained together with the technical documentation. If a software update changes the scope of data, the information must change as well. That is another reason for OTA updates and data documentation to live in a single process.
What about devices you have already sold?
This is where many manufacturers get it wrong. The design obligation in Art. 3(1) is not retroactive: you don’t have to rework machines already in use at customers’ sites. But Art. 4 has applied since 12 September 2025 and covers all devices you actually hold data from.
If the user cannot retrieve the data themselves, the data holder must provide it on a simple request submitted electronically: without undue delay, of the same quality as is available to the data holder, free of charge, in a machine-readable format and, where relevant and feasible, continuously and in real time. This concerns readily available data, meaning data you already collect or can obtain without disproportionate effort.
A few details that are easy to overlook:
- You must not make it difficult. A form hidden five levels deep in the menu, or a “download data” button in the same colour as the background, counts as prohibited obstruction under Art. 4(4).
- You must not demand unnecessary information when checking whether the request comes from an authorised person, nor keep access logs longer than necessary (Art. 4(5)).
- Personal data may be provided to someone who is not the person it concerns only if you have a legal basis for this under the GDPR. Example: data from a tractor may show when and where a particular operator worked.
Work out what it costs to handle such requests manually.
With the default settings (2,000 devices, 5% of users requesting data, 2 hours per request), that is 200 hours a year, or one eighth of a full-time job. Move the number of devices to 8,000 and the request rate to 15%: you get 2,400 hours and one and a half full-time jobs doing nothing else. The request rate will grow as independent service providers and fleet management companies start requesting this data on behalf of customers.
Your customer can share your data with another company
Art. 5 goes a step further. At the user’s request, the data holder must make the same data available to a third party the user nominates: an independent service provider, a leasing company, a fleet management software vendor, an insurer. On the same terms as for the user, meaning of the same quality and in a machine-readable format.
There is one exception, for the largest online platforms designated as gatekeepers: they cannot be recipients of such data. The third party also cannot use the data to develop a competing device.
You may charge a fee for making data available to a third party, but it must be reasonable and non-discriminatory (Art. 9). Where the recipient is a micro, small or medium-sized enterprise, the fee must not exceed the costs of making the data available.
For many manufacturers this is the hardest point, because it affects the business model. If you earn money from inspections and parts, and until now only your service team saw the machine data, a local competitor can now see it too. The answer is not to block the data, because that is against the law, but to offer a better service: one that reacts faster on the basis of the same data. I write about this in my article on predictive maintenance.
Your own use of the data requires a contract
Even people who have read carefully about data sharing miss this point. Art. 4(13) states that the data holder may use readily available non-personal data only on the basis of a contract with the user. It also may not use it to derive insights into the customer’s economic situation, assets or production methods in a way that would undermine their market position. And it may not make non-personal data available to other companies beyond what is needed to perform the contract with the user (Art. 4(14)).
In practice: if data from your customers’ machines feeds your research, a new model, quality analysis or predictive maintenance, you need clauses in the sales contract, the app terms or the service agreement that permit this and state the purpose. A general sentence in terms written years ago may not be enough. On top of that comes Art. 13 on unfair contractual terms between businesses: a term imposed unilaterally that grossly deviates from good commercial practice is not binding on the other party.
Trade secrets: protection yes, excuse no
Manufacturers most often ask: “What if the data reveals how my control algorithm works?” The Act provides protection, but it requires work in advance (Art. 4(6) to (8)):
- First, you identify which data are trade secrets yourself, including in the metadata.
- Then you agree protective measures with the user: a confidentiality agreement, model contractual terms, restricted access, technical standards.
- If the user does not want such measures or does not comply with them, you may withhold those specific data. The decision must be justified in writing and notified to the competent authority.
- Refusal despite agreed measures is possible only in exceptional circumstances, when you demonstrate that serious economic damage is highly likely. Also in writing, also notified to the authority.
Takeaway for the engineering department: in the design, separate data that are raw readings from parameters that reveal know-how. It is easier to defend the confidentiality of one calibration table than of an entire data stream.
Who the Data Act does not apply to
Art. 7 exempts micro and small enterprises from Chapter II, meaning from all the obligations described above, but on two conditions. The company must not have a partner or linked enterprise that is not a micro or small enterprise, so a subsidiary of a large group is not exempt. And it must not design or manufacture the device as a subcontractor.
A medium-sized enterprise has a transitional exemption: for one year from the moment it became medium-sized, and for each new model for one year from placing it on the market. The exemption covers the data sharing obligations, not the ban on unfair terms. A contractual term that takes away the user’s rights under Chapter II is not binding on them anyway.
How to build it so you don’t end up exporting files by hand
Our projects for device manufacturers point to one simple rule: data access for the customer is a product feature, not a task for the support team. We build it in the same places where the app or service portal already exists:
- User account and device assignment. Everyone with a right to the data sees their own devices. The recitals of the regulation explicitly mention co-ownership and rental: if both the owner and a rental company use an excavator, each should have access to the data they generated.
- Change of owner. Machines end up on the second-hand market. You need a way for the previous owner to lose access, the new owner to gain it, and the account to be deleted together with its data.
- Export and API. A “download data” button with a choice of period, a CSV or JSON file, a description of the columns. For larger customers and third parties: an API with an access key and, where it makes sense, a real-time stream.
- Consents for sharing with third parties. The user nominates the recipient, sets the scope and duration, and can withdraw consent. You keep a record of what was shared and with whom.
- Data dictionary. A single description of the variables, versioned together with the device software. From it you generate the metadata in the export and the pre-contractual information page.
- Trade secret flags. Fields that are trade secrets, flagged in the dictionary and excluded from the default export, with a separate path once a confidentiality agreement is signed.
If your devices already have telematics, most of this list is an extension of your existing portal, not a new system. If they don’t, start by asking whether a standard IoT platform will give you this level of control over the data. I write about this in my article on custom IoT applications.
Who enforces the Data Act in Poland and what are the penalties for infringements
The regulation leaves it to the Member States to designate the competent authority and set penalties that must be effective, proportionate and dissuasive (Art. 40). In Poland, in October 2026, the government adopted a draft act implementing the Data Act, prepared by the Ministry of Digital Affairs. Under the draft, the competent authority will be the President of UKE (Poland’s Office of Electronic Communications): it handles complaints, conducts proceedings and imposes fines, and before imposing a fine it must call on the company to remedy the infringement. At that time the act had not yet gone through the Sejm, so check the final level of fines in the version that is adopted.
Two things, however, are already certain. First, the regulation applies directly, so the absence of a Polish act does not release you from your obligations. Customers can enforce their rights in court. Second, manufacturers selling across the EU market are subject to supervision in other countries. In Germany, the authority is the Federal Network Agency (Bundesnetzagentur).
The Data Act and the Cyber Resilience Act: two deadlines in September 2026
September 2026 was a double milestone for device manufacturers. On 11 September, the obligation to report actively exploited vulnerabilities and severe incidents under the EU cyber resilience regulation (Cyber Resilience Act, Regulation (EU) 2024/2847) began to apply: an early warning within 24 hours and a notification within 72 hours. One day later, on 12 September, came the Data Act obligation to design access to data. The main requirements of the Cyber Resilience Act will follow on 11 December 2027.
These rules complement each other. The Data Act tells you to open up the data, the Cyber Resilience Act tells you to do it securely. A portal with data export and an API is a new attack surface, so design them together: authentication, permissions, encryption, an access log and secure updates.
Five questions for your design engineer, lawyer and head of service
- What data does each of our models generate and where is it stored? If nobody has this list, that is the first task, because without it you cannot write the pre-contractual information.
- Can the customer retrieve their data themselves today, without emailing us? If not, what is our process for Art. 4 requests and how many did we receive last year?
- Do our contracts and app terms allow us to use non-personal data from customers’ devices, and for what purposes?
- Which data are our trade secrets, and can we technically separate them from the rest?
- Which model are we placing on the market next, and does its design already include data access for the user?
This article describes the rules in simplified form, from the perspective of a company that builds apps and portals for device manufacturers. It is not legal advice. Check the details for your product with a lawyer.
Frequently Asked Questions
What is the Data Act?
The Data Act, “akt w sprawie danych” in Polish, is Regulation (EU) 2023/2854. It sets out who may use the data generated by connected devices and their related services. It has applied directly in all EU countries since 12 September 2025.
From when must a manufacturer design devices with data access?
The obligation in Art. 3(1) applies to connected products and related services placed on the market after 12 September 2026. Models already on sale do not need to be redesigned, but data the manufacturer already collects must be provided to the user at their request.
Does the Data Act apply to small companies?
Micro and small enterprises are exempt from the data sharing obligations in Chapter II, provided they have no partner or linked enterprise that is not a micro or small enterprise, and they do not design or manufacture the device as a subcontractor. A medium-sized enterprise is exempt for one year from obtaining that status.
Do I have to make data available free of charge?
To the user, yes: access must be free of charge. For making data available to another company nominated by the user, the data holder may charge a reasonable, non-discriminatory fee, and from micro, small and medium-sized enterprises only cost recovery.
Can a customer share data from my machine with a competitor?
They can share it with, for example, an independent service provider. However, the data cannot be used to develop a competing device or to derive insights into the manufacturer’s economic situation and production methods. Trade secrets are protected by agreed measures, and refusal is possible only in exceptional, well-justified cases.
Who enforces the Data Act in Poland and what are the penalties?
Under the draft act adopted by the government in October 2026, supervision will be taken on by the President of UKE, who will handle complaints and impose fines. At that time the act had not yet gone through the Sejm, so check the level of fines in the version that is adopted. The regulation itself applies regardless of the Polish act.
Next step: turn the obligation into an advantage
The data you must hand over to the customer passes through your system anyway. The same portal that meets the Data Act can show the customer the state of their fleet, send inspection reminders and suggest parts before something breaks. How to use device data in service is covered in article on predictive maintenance. More on how we build apps and platforms for device manufacturers: IoT applications.
How to Cite This Article: Maciej Ramus, “The Data Act and your devices: what machine manufacturers must make available to customers from September 2026”, JSON Crew, jsoncrew.com, 2026.
Maciej Ramus, CMO, JSON Crew
