When does this apply?
The regulation entered into force on 11 January 2024 and has applied since 12 September 2025. For connected products placed on the market from 12 September 2026, a design requirement also applies: the product must be built so that the data is accessible to the user by default and with ease. The provisions on switching charges for cloud services follow their own timeline, under which those charges are phased out gradually.
What exactly counts as "data the product generates"?
Raw data and what follows directly from it: measured values, states, events, usage data. What falls outside is information that results from substantial investment in processing and analysis. That line is not drawn sharply, and there will be debate about it in the coming years. For your design, it mainly means you want to keep the two separate, so you can open up one layer without pulling your system apart.
Can we charge for access?
For the user requesting their own product data, access must not be made unnecessarily difficult and there are restrictions on what you may charge. When making data available to a third party at the user's request, different rules apply, including the possibility of reasonable compensation, with a lighter regime for small businesses. This is above all a question for your lawyer; we make sure your system can do both.
What happens to our trade secrets?
They remain protected. The regulation expressly provides a mechanism that lets you attach measures to the sharing of data containing trade secrets and, in exceptional cases, refuse to share it. What does not work is declaring everything a trade secret to avoid the obligation. In practice, separating raw from derived data largely solves this: your secret lies in your analysis, not in the measured value.
Do we have to provide this in real time?
Where the product generates the data continuously or almost continuously and this is technically feasible, immediate availability is the obvious choice. For many applications, periodic delivery is enough. What matters most is that access is simple, secure and in a common format, with no one on your side having to step in. We design the integration so you can adjust the rhythm later without rebuilding.
How long do we have to keep data available?
That can't be captured in a single retention period. It depends on the nature of the product, on what you agree contractually and on other retention obligations that apply to you. What we do is substantiate and document that choice rather than guess at it, and set up the retention policy so that it differs per type of data. That saves on storage costs and makes it easier to explain.
We are a recipient, not a supplier. Is this useful to us?
Absolutely. As a recipient you gain rights: access to the data from the equipment you use, and the ability to have another party work with it. That opens up maintenance contracts that were previously locked in and makes comparison possible. On that side, we help with retrieving that data and making it usable, and with the question of what you need to put in your contracts to actually receive it.
How does this relate to the GDPR?
They apply side by side. If the product data concerns an identifiable person, the GDPR applies in full and you need a legal basis for it; the Data Act does not loosen that. In practice, most machine data is not personal, but with vehicles, wearables and equipment in a home that is different. We flag this in the workshop so that your legal counsel knows what to look at.
What does this mean for our architecture?
Three things. Data must live somewhere it can be accessed without anyone having to go into your system; that means an integration, not database access. There must be a permissions layer around it, because giving access to the user is not the same as giving access to everyone. And there must be logging, so that access can be audited. These three are manageable work if you include them in the design, and a rebuild if you have to add them later.
What belongs in an exit arrangement?
The format in which data is handed over, within what time, under what conditions, and how long you keep supplying after termination so that the transition can be completed. That last point is the one most often missing and the one that gives the most peace of mind. Add to this that the customer may test the export format in advance – that is the difference between an arrangement that works and one that only exists on paper.
Will this cost us our customers?
That is the fear, and it is rarely the outcome. Customers mainly leave when they feel they cannot leave. In procurement processes, a demonstrably working exit arrangement is now a plus point, not a risk. What you do need to think about is which part of your service relied on exclusive access – that part becomes vulnerable, and that is a strategic question better raised now than later.