The most frequently asked question by exporters beginning the preparation of a Digital Product Passport (DPP) is: Will all the information in the passport be publicly accessible? Will your prescription, supplier names, or cost structure be revealed to your competitors? This article explains what the EN 18239:2026 standard, which addresses access rights, information system security, and trade confidentiality in DPPs, expects from you and which decisions are up to you. This article is part of the DPP Standards Guide series.

Official status of the standard
  • EN 18239:2026 (access rights, information system security and trade confidentiality) was published in September 2026. As of the end of October 2026, there is no reference to it in the Official Journal of the EU; therefore, it does not yet provide a presumption of conformity.
Source: CEN/CENELEC publication information and the Official Journal of the European Union (EUR-Lex), checked 28 October 2026.
Service note: AES Innovation carries out the EU compliance work described on this page (PPWR, digital product passport, CBAM, etc.) in collaboration with expert solution partners; it does not provide these services directly. These activities are outside the scope of our accreditation (AB-0631-M).

What does the standard regulate, and what does it not regulate?

EN 18239, published in September 2026, is one of eight standards prepared for DPP (EN 18239, clause 0.1). Its subject matter is grouped under three headings: managing who has access to DPP data and with what rights, the security of information systems hosting this data, and managing access to confidential information of economic operators (EOs; companies in the market such as manufacturers, importers, and distributors) (clause 1; clause 4.2 for the definition of EO). Identity management, roles and responsibilities, and the transfer of rights and data between companies are also within this framework (clause 0.2).

The standard does not provide a list of which data elements are public and which are restricted; it leaves the content of DPP and access rights to product group-specific regulations (clauses 0.1, 0.2, 5.2(6) and 5.2(7)). It also does not choose a specific authentication technology or encryption method. The only standard it normatively refers to is EN 18219, which regulates unique identifiers (clause 2); for details see... to our singular descriptive text You can take a look.

Proving the origin of the data and whether it has been subsequently altered (signature, certificate, data change trace) is primarily the subject of the sister standard EN 18246; In our EN 18246 document We are addressing it.

Two layers of access: public data and controlled data.

The standard's fundamental distinction is simple: DPP data is either publicly available or controlled. Controlled DPP data is information whose reading or modification depends on the user's access rights (clause 3.1). Publicly available data, on the other hand, is information that any actor can only read without authentication (clause 6.2).

Therefore, the assumption that "all data in the DPP will be publicly available" is incorrect. The reverse is also not true: you cannot hide information in the public layer behind a login screen (clause 6.1).

Three boundaries in access: authentication, location, profiling.

  • Authentication cannot be required for publicly available data: Membership, login or account creation cannot be required to access this data (clauses 5.2(2) and 6.1). The note added to this rule by the standard states that preventing discrimination based on geographical location is one of the reasons for the rule.
  • Blocking cannot be based solely on location: Even controlled access to data cannot be blocked solely on the grounds of the country or jurisdiction in which the actor is located (Article 5.2(3)). In our reading, this means that being outside the EU alone cannot be a reason for blocking; a manufacturer in Türkiye and a repairer in another country both benefit from this rule.
  • Creating user profiles is generally prohibited: measures must be in place to prevent the creation of profiles in the system. The only exception is when the user can only access a particular service with authentication, i.e., when authentication is truly mandatory for that service (clause 5.2(24)).

Our assessment: The idea of using a publicly accessible DPP page as a channel for collecting customer data is incompatible with these points.

Who sees what? Actors and roles.

The standard lists the main actors involved with DPP in four groups (clause 4.2):

  • Economic operators include: manufacturers, authorized representatives, importers, distributors, dealers, and order fulfillment service providers.
  • Other value chain actors include: consumers, professional repairers, independent operators (such as refurbishers, spare parts and technical information providers), recyclers, and the market surveillance authority.
  • Customs authorities.
  • Service providers: These include the primary and backup DPP service providers authorized by EO, the product launcher, and hosting the DPP.

The standard acknowledges that other actors may emerge who are not on the list (clause 4.2).

“The ”public” is not defined as a separate actor; everyone, including the consumer, reads the public layer without authentication (clause 6.2). But exactly which data element will the recycler or repairer see? The standard does not say. The roles that grant access to regulated DPP data are determined by the relevant legal regulation for each product group (clause 5.2(7)). What the standard introduces is a mechanism: Access to controlled data is role-based, requires authentication, and different roles can perform different operations on different datasets (clause 6.2).

WhoWhat does he see?Rest
Everyone (including consumers)Publicly available data; read-only, no authentication required.Article 5.2(2), 6.2
Market surveillance and customs authoritiesControlled data; authenticated, within the scope of the relevant regulation's role.Articles 4.2, 5.2(7), 6.2
Repairers, recyclers, independent operatorsPublicly available data; in controlled data, only the elements that regulation has brought to this role.Articles 4.2, 5.2(7)
Roles you define that are not included in the regulation (e.g., additional authorization for a dealer or authorized service center)Additional privileges you will recognizeArticle 5.2(7), 5.2(9)

The system should allow for the delegation of access roles to another actor; the delegator is responsible for fulfilling the legal obligations required by that role (clause 5.2(18)). The delegator's authority should be based not only on their own role but also on the role of the delegator and the soundness and reliability of the delegation (clause 5.2(20)). In the introduction, the standard gives the addition of information about a repair performed by a professional repairman to the DPP as an example of intercompany transfer of responsibility, rights and data (clause 0.2).

A note for manufacturers outside the EU: The definition of an authorized representative in the standard includes being established in the market where the regulation applies (in the EU for exports to the EU) and having received a legally binding authorization from the manufacturer (clause 4.2). We recommend that you plan out the rights of this role over the DPP from the outset.

Business privacy: What can you restrict and how?

Prescription, supplier name, cost: The standard does not mention any of this information by name. Whether information will be included in the DPP and at what level it will be placed is a matter of product group regulation (clauses 0.1, 5.2(6) and 5.2(7)); data requirements specific to your sector. textile, steel And battery You can find this information on our pages. The tools provided by EN 18239 are as follows:

  • Authorization at the data element level: Access rights should be defined and enforceable at the level of individual data elements, not on a document or page basis (clauses 5.2(10) and 5.2(23)). In the same passport, some fields may be open to everyone, while others may be open only to certain roles.
  • Role assignment: You can assign roles and rights to authorized actors (notified actors) who need access to your controlled data via their unique identifiers; these rights must be product group-specific and comply with the relevant regulation (clause 5.2(6)). The standard defines an authorized actor as a person or entity authorized by an accreditation body or authority and playing a role in the DPP lifecycle (clause 3.6). This concept should not be confused with a notified body.
  • Additional privilege: You may grant additional access to your dealer or authorized service center beyond what the regulation requires, for example, and you may choose the authentication method for these additional roles yourself (clauses 5.2(7) and 5.2(9)).
  • Limits against bulk data scraping: Access to DPP services must be restricted in a way that prevents attacks and unauthorized bulk data scraping (clause 5.2(11)). Access rate limiting may also be imposed if there is a defined risk or legal requirement (clause 5.2(15)).

It is also necessary to know the limits. The standard only allows you to grant additional privileges on top of the roles defined by the regulation and requires that the rights you assign comply with the relevant regulation (Articles 5.2(6) and 5.2(7)). Therefore, withholding data that the regulation has opened up for a role from that role on the grounds of "trade secret" is incompatible with this framework. Speed limiting can also only be applied if legal information obligations are not affected (Article 5.2(15)).

The standard doesn't explicitly state this; however, as a general design principle, it's simpler and safer to not include sensitive commercial information in the DPP at all—which regulation doesn't require—than to protect it with subsequent access layers.

Expectations on the security side.

Authentication and authorization

  • Each actor must have a global unique operator identifier of the type defined in EN 18219 (clause 5.2(1)) and this identifier must be presented during the authentication process (clause 5.2(8)).
  • Controlled access to data should only be granted after authentication and authorization. The principle of least privilege, i.e., everyone should be given only as much right as is necessary for their work, is mandatory (Article 5.2(22)).
  • Operations such as creating, modifying and accessing controlled data must be carried out by means of mechanisms that prevent the person performing them from subsequently refuting it, i.e., by ensuring non-repudiation (Article 5.2(5)).
  • Authentication should be applied not only to actors but also to system components (e.g., in machine-to-machine connections) where required (clause 6.1).
  • Multifactor authentication (MFA): Informative Annex A lists 11 assumptions on which authentication is based when managing controlled data; the third assumption is authentication with at least two different factors (Annex A). Notes to Clauses 5.2(13) and 5.2(22) refer to this annex for good practice. However, what the standard requires is that authentication be carried out in accordance with the relevant legal framework; the standard alone does not require MFA.

Logging and rights management

  • Roles, rights and every access and change to controlled data must be tracked and made subject to audit. This log itself must also be protected: it must be prevented from being altered, fabricated or deleted, and it must be demonstrable when it is intact (clause 5.2(16)).
  • When roles change or an actor's authority expires, how rights are granted, revoked or modified must be linked to a clear and documented process (Article 5.2(17)). There must be a mechanism for immediate modification (e.g., cancellation) of rights in case of breach or inappropriateness (Article 5.2(19)) and an access revocation policy must be established for the DPP system and its services (Article 6.3).

Resilience and service providers

Measures must be identified and implemented to ensure the reliability and resilience of information systems carrying critical DPP data; this should also include an evaluation of the cybersecurity practices of your suppliers and service providers. Including these risk management measures directly in supplier and service provider contracts is only a recommendation (clause 6.5.2). For business continuity, EN ISO 22301 and ISO/IEC 27031 (clause 6.4.2), redundant systems, and resilience to denial-of-service (DoS) attacks (clause 6.5.4) are recommended. The standard does not specify a timeframe or rate for service availability; this is left to implementation discretion (clause 6.5.1).

ISO/IEC 27001 is mentioned at the recommendation and option level, not as a normative reference (clause 2, 5.2(21) and 6.5.5). Therefore, there is no certification requirement. An existing information security management system (ISMS) will make your work easier; however, DPP-specific issues such as authorization and profiling prohibition at the data element level should be addressed separately (non-standard general assessment).

No reference to the Official Gazette: Why you should consider it now.

EN 18239 was published in September 2026; as of the end of October 2026, there is no reference to it in the Official Journal of the EU, therefore the presumption of conformity has not yet arisen. Even when referenced according to the standard's current Annex ZA, the scope remains narrow: the mapping table only links clause 4.2, which lists the actors, with ESPR (EU) 2024/1781 Article 11(a) and only in terms of organizational interoperability in end-to-end communication and data transfer (Annex ZA, Table ZA.1). Access rights, logging, and security clauses are not included in this table; therefore, it would not be correct to say, "If I apply EN 18239, the presumption of conformity with the ESPR's confidentiality and security obligations arises.".

Nevertheless, there are strong reasons to consider the standard starting today:

  • The deadline for the standard to be adopted as a national standard is March 2027, and Türkiye's national standards body is among the organizations responsible for implementing the standard (EN 18239, European preamble).
  • Role, authority, and log structure are the fundamental architecture of a DPP system; adding them later is more expensive than establishing it from scratch (non-standard general assessment).
  • The standard provides a concrete, DPP-specific framework for security questions to ask when selecting a DPP service provider and drafting its contract (clauses 5.2 and 6.5.2).

Decisions you need to make as a producer

  • Will you host the DPP yourself, or will you outsource it to a main DPP service provider; and which service provider will maintain the backup copy (see clause 4.2; for backup details)? our data storage article)?
  • Beyond the roles mandated by the regulation, what additional roles and data elements will you grant access to (clauses 5.2(7) and 5.2(9))?
  • Which authentication method will you choose for additional roles; what does the relevant regulation require for regulated roles (clauses 5.2(9) and 5.2(13))?
  • How will you name the terms of the right of access at the data element level; will you use a controlled dictionary such as the EU Vocabularies of the EU Broadcasting Office (article 5.2(10))?
  • How will you set limits against data scraping in a way that does not disrupt legal information obligations and access by authorities (clauses 5.2(11) and 5.2(15))?
  • Who will be responsible for the delegation of authority and the urgent cancellation processes and how will they be put in writing (Articles 5.2(17) to 5.2(19) and 6.3)?
  • Will you establish an ISMS based on ISO/IEC 27001, or will you proceed with controls at the proposal level (clauses 5.2(21) and 6.5.5)?
  • What cybersecurity clauses will you include in the service provider agreement (clause 6.5.2)?

First steps for preparation

  • Follow the guidelines prepared for your product group; they will specify which role has access to which data.
  • Remove any information that might end up in the DPP and label each item as “public,” “controlled,” or “outside of the DPP.”.
  • List your specific roles, such as dealer, authorized service center, and authorized representative, and the data elements each should see.
  • Plan how you will obtain your global unique operator identifier.
  • Ask prospective DPP service providers: Do they offer data element-level authorization, immutable access logs, MFA, emergency cancellation, and backup hosting? Are there mandatory logins on the public page, tracking, or location-based blocking?
  • Compare your current information security practices to the points in this article and create a list of missing elements.
  • Document the access revocation policy and rights management process in writing.

Information Note

This content is for informational purposes only and does not replace the standard text; in practice, the current and complete text of the standard should be used. AES is not an approved or certification body; it does not issue, verify, or certify Digital Product Passport documents, and does not offer any passport software or Registration System services.

AES's TÜRKAK accreditation covers only the periodic inspection of electrical installations (AB-0631-M). The above information does not constitute a binding legal or technical opinion; each specific case should be evaluated within its own context.

Related Services and Content

Frequently Asked Questions

Does the consumer need to open an account to view the DPP (Digital Product List)?

No. Publicly available DPP data can be read without authentication; no membership or login requirements can be imposed (EN 18239, clauses 5.2(2) and 6.1).

Can I keep my prescription and supplier information confidential?

The standard does not provide a list of information that can be hidden. Controlled data and which role has access to it are determined by the product group regulation; access rights are defined at the data element level (clauses 5.2(6), 5.2(7) and 5.2(10)). You cannot hide data from a role that the regulation opens up to that role.

How do they access my market surveillance and customs data?

With role-based and authenticated access. Which data these roles will cover is defined by the relevant legal regulation (Articles 4.2, 5.2(7) and 6.2).

Can I grant additional access to my dealer or authorized service center?

Yes. The economic operator may grant additional privileges beyond what is provided for in the regulation and may choose its own authentication method for these additional roles (Articles 5.2(7) and 5.2(9)).

Can I block access requests from outside the EU?

Not solely on the grounds of location. Controlled access to data cannot be blocked simply because of the country or jurisdiction of the actor (Article 5.2(3)). Restrictions against attacks and mass data scraping are possible (Article 5.2(11)).

Is ISO/IEC 27001 certification required?

No. ISO/IEC 27001 is mentioned only at the level of suggestion and option, not as a normative reference (clause 2, 5.2(21) and 6.5.5).

If I apply EN 18239, will I benefit from the presumption of conformity?

Not currently. EN 18239 was published in September 2026; as of the end of October 2026, there is no reference to it in the Official Journal of the EU, therefore the presumption of conformity has not yet arisen. Even if a reference were made, the current Annex ZA mapping only links Article 4.2, which lists the actors, to ESPR Article 11(a); the articles on access rights and security are not included in this mapping (Annex ZA, Table ZA.1).