Continuity

What happens to
your passports if
something goes
wrong

A Digital Product Passport is a legal commitment that outlives the sale, the subscription, and potentially the company that published it. Any vendor who has not thought about this has not thought about the problem. Our hosting platform is in development; this page describes how it is being designed.

Four scenarios

  • You stop paying

    Export, transfer, or archive tier. Passports keep resolving.

  • You leave for a competitor

    Full export: passport data, version history, audit trail, in a documented format.

  • You are acquired

    Registered passports can be transferred to another verified economic operator that takes over the obligations.

  • We cease trading

    Independent third-party backup, and an export you already hold. Your passports are not hostage to our balance sheet.

Export your data

When the platform is live, you will be able to download a copy of the personal data it holds about you (profile, memberships, legal acceptances, invitations, and your own activity log) as JSON.

Download my data (JSON)

What you can export

  • Published passport content in JSON-LD
  • Every version, with content hashes
  • The audit trail
  • Registry identifiers
  • Carrier assets, vector and print

Immutability

Why you cannot quietly edit a published passport

Publishing locks the master data into an append-only version. A correction creates a new version rather than overwriting the old one, and versions are hash-chained so that removing or altering one breaks verification of every version after it.

This is deliberate. A passport whose history can be rewritten is not evidence of anything.