Your passport data is not the provider’s asset. EU law says so, in so many words. When you hand your Digital Product Passport to a service provider — to host it, back it up and make it available to the people entitled to see it — the ESPR, Regulation (EU) 2024/1781, draws a hard line around what that provider may do with the data, and what it may never do.

Who a DPP service provider is

Article 2(32) defines a digital product passport service provider as a natural or legal person that is an independent third party, authorised by the economic operator which places the product on the market or puts it into service, and that processes the passport data for the purpose of making them available to actors with a right to access them. Independent, authorised, and mandated to availability: a custodian of access, not an owner of the record.

The back-up duty: why a provider is not optional

Article 10(4) is one sentence with large consequences: the operator, when placing the product on the market, shall make available a back-up copy of the digital product passport through a digital product passport service provider. Manufacturers must ensure the passport is available including that back-up — the most up-to-date version — under Article 27(1)(c); importers must check the same under Article 29(2)(c). Recital 38 gives the reason: access must hold including after an insolvency, a liquidation or a cessation of activity. Every operator with a passport duty needs a provider — the only choice is which, and on what terms.

What the provider may do

Article 11(c) allows the passport to be stored by the economic operator responsible for its creation or by digital product passport service providers. Within that mandate, the provider runs the passport as designed:

  • Interoperability: fully interoperable with other passports (Article 11(a));
  • Access by role: customers, supply-chain actors, repairers, recyclers, market surveillance and customs authorities get free-of-charge, easy access according to their access rights (Article 11(b));
  • Controlled change: rights to introduce, modify or update data are restricted to the actors and data the delegated act specifies (Article 11(f));
  • Integrity and security: authentication, reliability and integrity ensured, with a high level of security and privacy and fraud avoided (Article 11(g) and (h)).

Under Article 10(1)(d), passport data must rest on open standards and stay transferable without vendor lock-in.

What the provider may not do

Article 11 — the ban, in the Regulation’s own terms

  • No selling: a provider that stores or otherwise processes passport data shall not sell that data;
  • No re-use: it shall not re-use the data for its own purposes;
  • No extra processing: no processing, in whole or in part, beyond what is necessary for the storing or processing services;
  • One exception only: broader processing only if specifically agreed with the economic operator — agreement, not a buried clause, is the test.

Customer personal data, too, must not be stored in the passport without explicit consent under Article 6 of the GDPR (Article 10(1)(e)).

Built to outlive the company

Article 11(e) requires the passport to remain available for the period specified in the delegated act, including after an insolvency, a liquidation or a cessation of activity in the Union of the operator responsible for its creation. Article 9(2)(i) adds that this period must correspond to at least the expected lifetime of the product. A new passport for the same product — after repair, repurposing or remanufacturing — must be linked to the original (Article 11(d)).

What is not fixed yet

One part of the regime is still open. Under Article 11’s third paragraph, the Commission is empowered to adopt delegated acts setting the requirements to become a provider and, where appropriate, a certification scheme; Recital 40 floats an impact assessment on it. Until those acts land, there is no EU certification of DPP providers in force: a provider claiming one today is claiming something the law has not yet created. What exists is the Regulation — and contracts should be written to it.

Choosing a provider: six checks

  • The Article 11 ban, in the contract: no sale, no re-use, no processing beyond the service; broader use only under a specific, separate agreement;
  • A live back-up: the provider’s copy is the most up-to-date version (Articles 10(4) and 27(1)(c)), not a periodic snapshot;
  • Open standards, real exit: full export in interoperable formats — test the exit before you need it;
  • Access and change control: tiered access by role, restricted rights to introduce, modify or update data (Article 11(b) and (f));
  • Survival on both sides: availability if the operator ceases activity — and a clause for the provider ceasing too;
  • Privacy by design: no customer personal data without explicit consent; security and integrity matching Article 11(g) and (h).

How Ledger Consortium helps

Ledger Consortium is built to Article 11’s terms: we aggregate the product data held by you and your suppliers, anchor each passport record on a governed blockchain — timestamped and tamper-evident — and make it available by role, with a back-up built to outlive reorganisations. Your data is not sold, re-used or mined: it runs your passports, and nothing else. Anchoring proves a record existed and has not been altered; it does not certify that the data a client supplied was true — accuracy remains the operator’s responsibility. Costs are predictable, there is no token and no crypto exposure, and the platform is GDPR- and eIDAS-aligned. In Italy, the Ledger DPP is distributed by Il Sole 24 Ore (Valore24), whose channel onboards dozens of companies per month. See a working passport in our live demo, browse News, and read Aluminium: Light Metal, Heavy Data.