EN 18221: storage, archiving and persistence
What does EN 18221 ask of a back-up provider? To keep the newest version and every required historical version of the passport for its whole lifetime, with the same access rules as the original (4.2, 4.3). To store and make accessible the mandatory documents (4.4). And to receive every change often enough to keep data loss small, through EN 18222 or another agreed secure way (4.5).
EN 18221:2026, Digital product passport – Data storage, archiving, and data persistence, is one of the European standards written for ESPR passports. It is sold by the national standards bodies. This page sums up its requirements in our own words and gives the clause numbers. It does not reproduce the text of the standard.
Commission Implementing Decision (EU) 2026/1736 of 14 July 2026 cites EN 18221:2026 in the Official Journal as a harmonised standard under ESPR, together with EN 18216, EN 18219, EN 18220, EN 18222 and EN 18223. EN 18239 and EN 18246 are not cited.
Two roles
- Main digital product passport service provider (3.3.1): hosts the passport on behalf of the economic operator, if the operator does not host it itself.
- Back-up digital product passport service provider (3.3.2): hosts the back-up copy of the passport.
The digital product passport lifetime (3.4) is the period during which the passport is required by regulation to be available to anyone with a right to access its data. Clause 4.1 says its storage requirements apply to both main and back-up providers.
4.2 Archiving: every version, for the whole lifetime
The back-up provider keeps the archived versions, and so does the creator of the passport or its main provider.
- Archiving starts with the first change of the passport. All changes are archived, unless product rules exempt them (for example real-time sensor data).
- All archived versions are kept during the passport lifetime.
- Archived versions have the same access restrictions as the current passport.
- Authenticated and authorised actors can get the archived version that was current at a given moment.
- The integrity and originality of the archived versions are ensured, following EN 18246.
4.3 Persistence: the copy outlives the operator
Once the economic operator is no longer active on the market, the passport is generally accessible from the back-up provider.
- The back-up provider keeps the newest version and every historical version that is required.
- The attributes of the back-up copy have the same access restrictions as in the original passport.
- During the lifetime, the passport is available from the back-up provider to specifically authorised users.
4.4 Attached documents
When the passport includes digital documents, directly or by reference, they must be accessible through the passport for its lifetime. The back-up provider is responsible for storing and making accessible the mandatory documents included in the passport.
4.5 Replication to the back-up provider
- The passport and all its changes are replicated to the back-up provider, as 4.3 requires.
- After a change, replication happens often enough to keep data loss small. The standard gives a maximum recovery point objective as one example. Product rules may set the frequency.
- Replication can use the standard life cycle interface of EN 18222, or another secure mechanism both sides agree on.
- It takes place over a data exchange protocol in accordance with EN 18216.
The link to ESPR
Annex ZA of EN 18221 links clauses 4.3 and 4.5 to ESPR Article 10(4). The link covers the technical side of the backup only, not whether a backup exists: having one stays the economic operator's duty. Annex ZA also links 4.5 to Article 11(c).
How dpp-backup.com meets each clause
| Clause | dpp-backup.com |
|---|---|
| 4.2 | Every version your platform sends is stored whole and never changed. The version current on a given date can be read, in the portal and through ReadDPPVersionByIdAndDate. Each version has a SHA-256 hash and a signed receipt. |
| 4.3 | Keeps every version it receives. Data elements your platform lists as not public stay hidden from the public. A version sent without that list shows no product data publicly, rather than a guess. Public reading opens for a domain when that domain is pointed at the copy. |
| 4.4 | Holds the files your platform uploads with the passport. |
| 4.5 | Takes in the passport and every change through EN 18222, over HTTPS. Your platform sends each change as it happens. No recovery point objective is published, because it depends on when your platform sends. |
Keep a back-up copy of your passports
Create an organisation with your company email. Once it is approved, you connect the platform that holds your passports.
A company email address is required. Our staff review new organisations on working days. The portal is in English.