Choosing a backup service for your passports

What should you ask a back-up provider? Whether it keeps every version for the whole passport lifetime, keeps your access rules, can return the version current at a given time, stores the mandatory documents, takes your changes through EN 18222, and can prove what it holds. Each question below rests on EN 18221 4.2 to 4.5 or on ESPR.

Use the questions with any provider. Under each one is why it matters and how dpp-backup.com answers it.

1. Does it keep every version, for the whole lifetime?

Why: EN 18221 4.2 asks the back-up provider to keep every archived version during the passport lifetime, and 4.3 asks for the newest version and every required historical version. ESPR Article 9(2)(i) sets the lifetime at no less than the expected lifetime of the product.

dpp-backup.com: every version is stored whole and never changed, and nothing is deleted through the interface for platforms.

2. Can it give you the version that was current at a given time?

Why: under EN 18221 4.2, authenticated and authorised actors can get the archived version that was current at a given moment. EN 18222 4.4 has the call for it, ReadDPPVersionByIdAndDate.

dpp-backup.com: yes, in the portal and through ReadDPPVersionByIdAndDate.

3. Does it keep your access rules?

Why: EN 18221 4.2 and 4.3 ask that archived versions and the back-up copy are restricted in the same way as the original passport. ESPR Article 11(f) restricts who may change the data.

dpp-backup.com: your platform sends, with each version, the list of data elements that are not public, and those are never shown to the public from the copy. Without the list we show no product data from that version publicly rather than guess, so make sure your platform sends it.

4. Who can read the copy, and when?

Why: under EN 18221 4.3, specifically authorised users can read the copy during the lifetime, and it becomes generally accessible once the economic operator is no longer active on the market. ESPR Article 11(e) asks the passport to stay available after an insolvency, a liquidation or the end of activity in the EU.

dpp-backup.com: public reading opens for a domain when that domain is pointed at the copy. The same addresses then answer.

5. Does it hold the mandatory documents?

Why: under EN 18221 4.4, the back-up provider is responsible for storing and making accessible the mandatory documents in the passport.

dpp-backup.com: it holds the files your platform uploads with the passport.

6. How do your changes reach it?

Why: EN 18221 4.5 asks that the passport and every change reach the back-up provider often enough to keep data loss small, through EN 18222 or another secure mechanism you agree on, over a protocol as in EN 18216.

dpp-backup.com: through the EN 18222 calls CreateDPP and UpdateDPPById, over HTTPS. Your platform sends each change as it happens.

7. Does it offer the read calls of EN 18222?

Why: EN 18222 4.1 asks a back-up provider to offer ReadDPPById, ReadDPPByProductId and ReadDPPIdsByProductIds.

dpp-backup.com: all three, and ReadDPPVersionByIdAndDate.

8. Can it prove what it holds?

Why: ESPR Article 11(g) asks that data authentication, reliability and integrity are ensured, and EN 18221 4.2 asks for the integrity and originality of archived versions.

dpp-backup.com: a SHA-256 hash of every version and a receipt signed with Ed25519, which anyone can check against the published key.

9. What may it do with your data?

Why: under ESPR Article 11, a service provider shall not sell, reuse or process the data beyond what its storing or processing services need, unless you agree to it. For batteries, Battery Regulation Article 78(d) says the same.

dpp-backup.com: uses the data only to store it and make it available.

10. What does it promise that you cannot check?

Why: a promise you cannot check is not proof. Ask for receipts, a public key and clear limits.

dpp-backup.com: it publishes no uptime figure and no recovery point objective until they are measured. It keeps only published passports, never drafts.

The checklist

  • Every version kept for the passport lifetime (EN 18221 4.2, 4.3)
  • The version current at a given time can be read (EN 18221 4.2, EN 18222 4.4)
  • The same access rules as the original (EN 18221 4.2, 4.3)
  • General access once the operator is no longer active (EN 18221 4.3, ESPR Article 11(e))
  • Mandatory documents held (EN 18221 4.4)
  • Changes received through EN 18222 or another agreed secure way (EN 18221 4.5)
  • The read calls of EN 18222 4.1
  • Proof of integrity for every version (ESPR Article 11(g))
  • Data used only for the service (ESPR Article 11; Battery Regulation Article 78(d))

EN 18221 · EN 18222 · ESPR Article 10(4)

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.