Backup copies for digital product passports

The Ecodesign Regulation requires a backup copy of the product passport held by an independent third party. I also offer it for passports from other manufacturers and platforms.

Also for other manufacturers and platforms

Regulation (EU) 2024/1781 (ESPR) requires in Article 10(4) that a backup copy of the product passport be available through an independent third-party service provider when the product is placed on the market. The backup must therefore not sit where the passport itself sits. This applies to every product that needs a passport under the ESPR, i.e. as soon as a delegated act requires the passport for its product group. No backup copy is provided for batteries: there is no delegated act under the ESPR for them, and the Battery Regulation only requires that the passport remains available (Art. 78(e)). A voluntary custody arrangement can still make sense, because a battery passport accompanies the battery for ten to twenty years.

What this is good for only shows once a manufacturer leaves the market. General access to the passport then becomes available (EN 18221, clause 4.3). A product passport should outlive the company that issued it.

I offer this because these data are, to my mind, the part of the circular economy that disappears most easily. A company files for insolvency, the server is switched off, and with it go the details on material, repair and recovery.

Stored verbatim

Passports are stored as they arrive and returned unchanged. They are never translated into someone else's data model.

Append-only

A stored version is never altered and never deleted. A correction is a new version; the old one stays retrievable.

Verifiable

Every file carries a SHA-256 checksum. That a version is unchanged can be recomputed with ordinary tools.

Readable without me

The archive is ordinary files with an explanation alongside. Readable without this service and without me.

Competitors included: if your passports live on another platform, the backup can still sit here. The regulation demands independence anyway. Conversely, I am never both main and backup provider for the same customer. For the customers of my own platform I engage a third provider.

Technical integration

For developers and platform operators

Integration is via the lifecycle API under EN 18222:2026, clause 8.2, over HTTPS under EN 18216. Access only with proof from a custody agreement.

For attached documents under EN 18221 clause 4.4, such as test reports and declarations of conformity, EN 18222 provides no method. This service offers three of its own for this; the file’s checksum is part of the path, so its integrity can be confirmed as soon as it is received.

Large documents bypass the interface and go directly into storage: the service issues a short-lived signed address and recalculates the checksum as soon as the file is there. How long documents are retained is governed by the contract.

The address of the backup service also returns JSON when it is called without a browser.

The service takes in passports with the first custody agreement. Get in touch if you need a backup copy, or are still working out who should hold it.