Must I make commercially sensitive data about my aluminium public?
Not everything in the digital product passport is public
No, not automatically. The ESPR makes a distinction between information that is visible to everyone via the digital product passport and information that is intended only for specific parties, such as supervisory authorities or other actors in the supply chain. The fact that a piece of data is in the passport does not automatically mean it is public. For aluminium semi-finished products, this often concerns sensitive data such as the precise alloy composition, details about the production process or the identity of specific suppliers. The regulation takes into account that this type of information has business value, and therefore creates a distinction between what is publicly visible and what remains of limited access.
Who this applies to and what it does not
This applies to data that is specifically collected and provided for the digital product passport: technical characteristics, origin, processing history and the like. So it concerns the information that ultimately is attached to the product via the QR code. It does not apply to business confidential information that is separate from the passport, such as financial data, internal cost prices or customer lists — these are governed by ordinary rules on trade secrets, and these do not change with the arrival of the digital product passport. There is also a difference between what a manufacturer or importer must internally record and provide, and what ultimately comes back as a publicly visible field in the passport itself. This distinction is made concrete in the delegated act per product category, and this does not yet exist for aluminium.
No fixed date for this rule yet
There is no firm date yet. The ESPR itself is already in force, but which data for aluminium semi-finished products must exactly be in the passport, and which of these is publicly accessible versus limited to certain parties, is laid down in a product-specific delegated act. According to the European Commission's work plan for 2025-2030, this delegated act for aluminium is expected around 2027. Until this delegated act is published, there is no concrete obligation for aluminium to enter data in a passport, let alone to make it public. As soon as the text is published, the exact date and the content of the information requirements will appear here.
How to approach this in practice
The first step is to make an overview of which data about the aluminium product is already being shared, with whom, and on what basis — think of certificates, material declarations or data that is already being provided for other regulations. This overview can later be used to determine what will probably end up in the passport and what will not. The second step is to wait for the publication of the delegated act for aluminium: only then will it state which fields are mandatory and which of these become publicly visible. The third step, for those who have a passport compiled via alupas.eu: data provided for the passport does not need to be separately marked as "confidential" before the regulation itself makes this distinction — the platform processes the submission according to the access levels prescribed by the regulation once these are established. If you are already in doubt whether a specific piece of data is commercially sensitive, it is advisable to state that clearly upon submission, so that this can be taken into account when compiling the passport.
The basis: Article 10 and Article 38 ESPR
Article 10 of the ESPR (Regulation (EU) 2024/1781) sets out the general requirements for the digital product passport, including the way in which information is made accessible to different types of users — from consumer to competent authority. It follows from this that not every piece of data in the passport needs to be equally visible to everyone; which data are accessible to whom will be determined further for each product group. Article 38 regulates the obligations of actors in the supply chain, such as manufacturers and importers, to provide correct and complete information to whoever compiles the passport. This is a submission within the chain, aimed at correctly building the passport — not automatic disclosure to the outside world. The distinction between "submitting for the passport" and "making public via the passport" is thus already present in the regulation itself, and will be worked out further once the product-specific implementation is available.
If you wish to prepare now, it is best to keep a list of which data on the aluminium product are available internally and which of these are considered sensitive, so that this list is ready once the delegated act for aluminium is published. For specific questions about a particular submission, you can contact alupas.eu, and for the formal text the official publication by the European Commission remains the source to follow.
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 on EUR-Lex. We refer per statement; you do not have to take our word for it.
What you must concretely do
What is expected of you
Provide data that complete the passport
Article 10 of the ESPR (Regulation (EU) 2024/1781) describes what kind of information a digital product passport contains: data on materials, composition, origin and environmental characteristics of the product. For a company with 10 to 100 employees, this means in practice that alloy data, surface treatment and origin of raw material must be supplied to whoever compiles the passport. Which data exactly are expected is described on what data are included in the aluminium product passport? That is the starting point: first it is clear what must be in it, only then is the question relevant what of that is sensitive.
Provide data to other actors in the chain
Article 38 of the ESPR covers the obligations of actors in the supply chain: manufacturers, importers and other links exchange information with each other that is necessary to comply with the regulation. For a foundry or profile company, this means that a supplier or customer can request data that is necessary for their own passport or file. This is a different flow than the data that appear in the public passport — a distinction that in practice often gets mixed up.
Distinguish between what becomes visible and what does not
Not every data stream within the product passport is visible to everyone. Who may see which data depends on the role of that party — regulator, customer, recycler or consumer. That distinction is described on who may view which data from the product passport? For a company this is exactly the point where the question about commercially sensitive information lands: not "must this data exist in the passport", but "who gets to see this data".
Keep the technical file and the passport side by side
A technical file often contains more and more detailed information than what ends up in the passport. The passport is an extract with a public or semi-public character; the file behind it can contain process parameters, supplier data and internal specifications that are not intended for the passport. The difference between those two is explained on what is the difference between my technical file and the digital product passport That distinction is the core of how sensitive data is handled: not everything you know needs to be in the passport.
Where things go wrong in practice
A production company supplies the complete recipe of an alloy instead of the EN-AW designation and the characteristics that the passport requests. The designation and composition as expected in the passport are described on how do I record the alloy and the EN-AW designation? — a precise recipe with exact proportions of alloying elements is generally not what is requested there.
A supplier refuses any data exchange out of fear that competition-sensitive information will reach a customer, and therefore supplies too little to make that customer's passport complete. This often arises from unclear understanding of what article 38 requires: sharing data within the chain is not the same as making that data public.
A company sends internal reports or certificates in full formwhile only a result value or a reference to the measurement method is needed. The question which measurement method underlies the passport is different from the question which underlying test report becomes visible; see according to which method should I measure the values for the passport?
Origin data of scrap or residual streams are passed on completely with supplier namewhile for the share of recycled material a demonstrated percentage is relevant, not the identity of every supplying party. How that share is demonstrated is on how do I demonstrate the proportion of recycled aluminium?
Repair and residual material information is supplied with internal process detailswhile the question of whether this type of information belongs in the passport is separate from the question of how detailed that is; see must I include information about repair and restoration of aluminium in the passport
What you can document now
- An overview of which data are internally available versus which of those actually end up in the passport — with a reference to the distinction between file and passport.
- An internal agreement on who within the company decides which information is shared towards a supply chain partner based on Article 38, and which information goes to the passport itself.
- A template for data exchange with suppliers and customers, with a fixed format that specifies which data item is requested and in what form (result, not underlying source data).
- An overview of roles and access levels, aligned with who may view which data, so that sensitive information is not shared more broadly than necessary as a matter of course.
- A fixed procedure for submitting measurement results and origin percentages, so that the same level of detail is shared each time instead of reassessing what is and is not possible with each request.
- An overview of the language in which data are provided and published, relevant when internal documentation is drawn up in a different language than what the passport requires; see in which language must the data in the product passport be presented
This is not legal advice. This page provides general information on the legislation that this platform covers. We do not know your situation. If 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 not right? Let us know — corrections are prioritised.