Must I disclose business-sensitive data about my tyres?
Not everything in the passport is public
No, not every piece of data about a tyre needs to be made visible to everyone. The ESPR (Regulation (EU) 2024/1781) is designed so that a digital product passport can contain different types of information, with different target audiences: some data is intended for the end user or the general public, other data is relevant only to a specific party, such as a supervisory authority, a repairer or a recycler. This layered structure provides room to treat data that lies deep in the production process differently from data intended to be widely shared, such as performance characteristics or instructions for use. What specifically must be made public for tyres is not yet determined — this will be specified per product group in a separate regulation that has yet to be published.
What falls under this, and what does not
This question applies to everyone who provides data for the passport: the manufacturer or importer who supplies the source data, and parties further down the chain such as wholesalers and fleet managers who work with the passport. It concerns data that factually relates to the product — composition, performance, origin, maintenance, information about end of life. What does not fall under this: internal business processes, pricing arrangements, customer relations or other information unrelated to the product itself. The ESPR regulates the content of the passport, not the business operations behind it. At this general level, the regulation also does not determine per tyre which specific data is public and which data remains restricted to specific actors — that detail belongs in the delegated act for tyres, which does not yet exist.
When this becomes concrete for tyres
No delegated act has yet been published for tyres that sets out which data must be included in the passport and who has access to it. According to the European Commission's work plan for 2025-2030, that delegated act for tyres is expected in 2027. Until that act is in place, the general framework of the ESPR is established — including the principle that a passport can operate with different access levels — but the product-specific requirements for tyres are still missing. Once the delegated act is published, this page will be updated with details of which data is involved and when the obligation takes effect.
How to proceed now
Anyone already collecting data with a view to a future passport can start by distinguishing between two types of information. On the one hand, data that is clearly intended to be shared, such as material composition insofar as relevant for recycling, performance indicators and safety information. On the other hand, data that lies deeper in the production process, such as precise formulations, supplier relations or production methods. For that second category, it is worthwhile to map out now what is considered commercially sensitive within your own organisation and why, so that this assessment is ready once the delegated act for tyres clarifies which data becomes mandatory and how access to it will be arranged. Tyrepas compiles the passport from the data supplied by the manufacturer or importer; what data this is exactly and how access to that data is structured follows from that forthcoming regulation and not from a choice by the platform itself.
The basis: Articles 10 and 38 ESPR
Article 10 of the ESPR determines what a digital product passport must be able to do: it lays the foundation for the content and accessibility of the data made available via the QR code, and provides room for a setup in which not all information is intended for the same target group. Article 38 regulates the obligations of actors in the supply chain when submitting and making that data available. Both articles together form the general framework; the product-specific details for tyres — which data is mandatory, who may view it, and how any commercially sensitive information is handled within it — are filled in only in the delegated act that is still to be published for tyres.
Anyone already engaged with this issue is well advised to organize their own data in advance in the two categories mentioned above and to consult the text of articles 10 and 38 of the ESPR (via the link below) themselves, so that their own inventory aligns with the terminology used by the regulation. Once the delegated act for tyres is published, this page will be supplemented with the product-specific rules applicable at that time.
What this is based on
- Regulation (EU) 2024/1781 (ESPR), Article 10 (requirements for the digital product passport)
- Regulation (EU) 2024/1781 (ESPR), Article 38 (requirements for actors in the supply chain)
The regulation itself is available on EUR-Lex. We provide references per statement; you do not have to take our word for it.
What you must do concretely
What is expected of you
Distinguish between what is mandatorily public and what is not
The ESPR requires the inclusion of data in the product passport, but not all data contained in it is visible to everyone. Article 10 of the ESPR (Regulation (EU) 2024/1781) distinguishes between information that is accessible to the public and information intended only for specific parties, such as competent authorities or economic operators further down the supply chain. For a company with 10 to 100 employees, this means in practice that not everything in the passport is automatically viewable by a competitor or end user. Which data falls into which category depends on the product category-specific rules for tyres, which still need to be established. An overview of who may view which data is available on the page who may view which data from the product passport.
Obligations of actors in the supply chain
Article 38 of the ESPR (Regulation (EU) 2024/1781) specifies what information actors in the supply chain — including importers and distributors — must provide to each other and to competent authorities. This is a different obligation from the public information in the product passport: it concerns data that must be made available upon request by parties with a legal basis to request it, not data that is freely accessible to anyone with a QR code. For an importer or wholesaler, this means that part of the records on composition, origin or test results must be kept in order internally, without automatically meaning that this data will also appear publicly in the passport.
Determine what is genuinely confidential
The practical question a company faces is not "must this be public" in a general sense, but which specific data category for tyres will fall under which regime. This will be determined on a per product category basis and has not yet been finally established for tyres. A company can already inventory which data on rubber composition, recipe or supplier relations it considers commercially sensitive, so that this inventory is ready once the delegated act establishes the classification. See the page for the data expected to appear in the passport which data will be included in the product passport for tyres.
Where things go wrong in practice
Share everything out of caution. An importer who is uncertain about what must and must not be public sometimes provides more data to the platform that compiles the passport than strictly necessary — including internal recipe details not intended for the public part of the passport. Once published, that is not easily reversed.
Confusion between "in the passport" and "public". Some companies assume that every piece of data supplied for the passport is also visible to everyone via the QR code. This is not necessarily the case; there is a difference between what is recorded and what is made publicly accessible.
Not distinguishing between supply chain partner and end user. A wholesaler that shares data with a fleet manager sometimes treats it the same way as a publication to consumers, whereas the obligations under Article 38 of the ESPR (Regulation (EU) 2024/1781) are specifically directed at actors in the supply chain, with a different legal basis than a public passport.
Unclear agreements with the manufacturer on the origin of data. When an importer passes data from a manufacturer outside the EU to the platform, it is not always established who is responsible if data is subsequently considered too sensitive to be made public. This leads to disputes later, especially when the data has already been published.
Confusion with the tyre label. Because the tyre label already contains longer-existing, partly comparable data, companies sometimes assume that everything stated on the label must also automatically be public in the product passport, or vice versa. The relationship between the two is a point of attention; see how does the tyre label relate to the product passport.
What you can record
- An internal list of which data on rubber composition and formulation are considered commercially sensitive, before submission to the platform. See also which data on rubber composition must I record.
- An agreement with the manufacturer or supplier on which party supplies which part of the data, and who is responsible for its accuracy and confidentiality.
- An overview of which data are expected to become publicly visible and which are intended only for supervisory authorities or chain partners, once the product category-specific rules for tyres are known.
- A procedure for what to do if data has been inadvertently shared too widely, including the question of whether and how this can be adjusted later — see can I adjust data after the product passport has already been published.
- A file containing the underlying test methods and measurement reports, separate from the data intended for publication, so that it is clear what has and has not been submitted for the product passport itself.
This is not legal advice. This page provides general information about the legislation that this platform concerns. We do not know your situation. If you are in doubt about your own case, consult a lawyer or the competent supervisory authority.
Written with AI based on the sources above, checked by a human on 2026-08-22. Is something incorrect? Let us know — corrections are given priority.