Portability and continuity

No lock-in · ESPR Art. 11

A QR code printed on a product cannot be un-printed. That is why the most important questions for any DPP provider are: what happens to the passports when a contract ends, when you switch providers, and if the provider itself disappears. Here are our answers, in black and white.

Passports outlive the contract

Ending the subscription ends platform access — editing, issuing new passports, support. The published passports, however, stay online at their public addresses. Our policy is not to take published passports down: the QR codes on your products keep working.

Export at any time

While the contract is active, all data can be exported at any time in open, machine-readable formats (JSON-LD / Schema.org). After termination, the data remains exportable for at least 45 more days as a full archive — structured data and attached documents.

If the operator ceases activity

ESPR (Regulation (EU) 2024/1781) requires the passport to remain available even through the operator's insolvency, liquidation or cessation of activity (Art. 11), and Art. 10 provides for a backup copy through a DPP service provider. The mechanism is simple: the backup becomes the original, and the customer arranges a new backup. Our architecture makes exactly this easy — published passports are static pages on a CDN that keep being served independently of the administrative system, and the open formats make moving to another provider a technical exercise, not a negotiation.

Scenario

Published passports

Your data

Subscription ends

Stay online — the QR codes keep working

Exportable for at least 45 days after termination, as a full archive

Switching providers

Identifiers follow GS1 Digital Link and do not depend on us

Full JSON-LD export; we demonstrate the transfer in practice

Operator ceases activity

Static pages keep being served from the CDN

The backup copy becomes the original — the ESPR Art. 10 mechanism

One clarification: the specific backup obligation takes effect with the delegated act for each product group — we track every change and reflect it publicly. For the systems behind the platform, see the “Subprocessors and infrastructure” page.

Last updated: 2 September 2026.

What buyers ask before signing

Continuity questions

They stay online. Ending the subscription ends platform access — editing, issuing new passports, support — but published passports are not taken down and the QR codes printed on your products keep resolving. Our policy is not to remove published passports, because a QR code on a physical product cannot be un-printed.

At least 45 days, as a full archive: structured data plus attached documents, in JSON-LD and Schema.org. While the contract is active you can export at any time, as often as you like. There is no separate charge and no request form.

No. Identifiers follow GS1 Digital Link and do not depend on us, so the codes already printed keep identifying the same products with a different provider behind them. The export is a full JSON-LD file rather than a proprietary dump, which makes a migration a technical exercise instead of a negotiation. Book a call and we will demonstrate the export and the transfer on a real demo passport.

The ESPR anticipates exactly this. Article 11 of Regulation (EU) 2024/1781 requires the passport to remain available through the operator's insolvency, liquidation or cessation of activity, and Article 10 provides for a backup copy held by a DPP service provider: the backup becomes the original and the customer arranges a new backup. Our architecture is built for that outcome — published passports are static pages served from a CDN, independent of the administrative system. Note that the specific backup obligation takes effect with the delegated act for each product group.

The WIARA team demonstrates passport export and transfer

Want to see the export live?

Book a call — we create a demo passport in front of you and show the full JSON-LD export and the transfer.

Last verified