How you can trust the copy
Every version is kept as it was received. Its content is hashed with SHA-256, and dpp-backup.com signs a receipt for it with Ed25519. The public key is published, so anyone can check a receipt.
Receipts and the public key
For each stored version, dpp-backup.com issues a receipt: the passport, the version number, the SHA-256 hash of the content, the sender and the time it was received. The receipt is signed with the service's own Ed25519 key.
The public key is at /.well-known/backup-receipt-key. A receipt proves that a version was delivered and held. It does not carry the passport itself.
Verify a receipt · The receipt format
- Passport
5b1d3a8e-0c3f-4a8e-9a77-2f1f3c9b7e01- Version
3- Content hash (SHA-256)
5ef66f44fdc06ae36600e5034d550dd9fd3fa77f223f4e6cd292607cba1d1c42- Received at
2026-11-20T09:14:02.318Z- Sender
conn-d7e4ebf8-eac6-48b7-b79f-27487a59d7a0- Receipt id
bb0fed2c-d3b6-4864-803d-bfa4a373d142- Key id
e1e440dafc6d9fc4
Integrity
The database computes a SHA-256 hash over the content of every version, the same way for every version. The same hash is in the receipt, and it is shown with the version when the version is read from the copy. ESPR Article 11(g) asks that data authentication, reliability and integrity are ensured.
Versions kept as received
- Every version is stored whole and is never changed afterwards.
- Nothing is deleted through the interface for platforms. A delete call is refused.
- The time of a version is the time it was stored. A sender cannot place a version in the past.
- Only published passports are taken in. Drafts are refused.
Access rules
- EN 18221 4.3: the copy keeps the access restrictions of the original passport. Specifically authorised users can read it while your passport is live; general access opens once the economic operator has left the market.
- To do that, the copy needs to know which data elements are not public. Your platform sends that list with each version, and those data elements 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.
- Public reading is opened for one domain at a time, when that domain is pointed at the copy.
- In the portal, each person has a role: owner, admin, operator or auditor. The auditor role can read but not change.
- Answering for a domain from the copy needs two people: one asks, another approves.
Who can send and sign in
- A platform sends with a credential made for one connection. The credential is shown once. dpp-backup.com keeps only a SHA-256 hash of it.
- Ownership of a domain is proven with a DNS TXT record that dpp-backup.com looks up itself.
- Signing in to the portal needs a company email address. Our staff approve every new organisation.
- An audit log records sign-ins and changes in each organisation, and calls that were refused.
Data used only for the service
dpp-backup.com uses passport data to store it and make it available, and for nothing else. ESPR Article 11 says a digital product passport service provider shall not sell, reuse or process the data beyond what is necessary for its storing or processing services, unless specifically agreed with the economic operator. For batteries, Battery Regulation Article 78(d) says the same of operators that store the data on behalf of the economic operator.
What this page does not claim
- No figure for uptime and no recovery point objective. They are not published until they are measured.
- Reading a version as it was on a date reads a stored version. It does not put any system back to an earlier state.
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.