Try a Solidus verification.

Before you upload anything, read the next two paragraphs.

What happens to what you upload

A document you submit to this demo is stored, and it is retained on the same timer as any other capture, a purge window defaulting to 30 days. If the session is recorded, the recording carries a window defaulting to 365 days.

It is not deleted the moment the demo finishes, and any Solidus page that has said otherwise was wrong. what our retention actually is

There is also no request-based deletion. We have no erasure workflow (the purge runs on a timer, not on a request) and the purge job ships defaulting to a dry run, so whether a given deployment is actually deleting on schedule is a deployment fact, not a guarantee.

Our recommendation: use a document you are comfortable having stored, or use one of the test documents rather than your own. That is an unusual thing for a demo page to say. It is the accurate thing.

What the demo actually demonstrates

The pipeline: a document read and authenticated, a live capture and face match, a decision, and a credential issued to a holder.

What it does not demonstrate:

• A consistent configuration. Parts of the pipeline depend on a separate inference service; voice liveness in particular is inactive unless that service is running. So two runs of this demo can exercise different checks. detail
• Anti-spoof capability. Our passive model has not cleared an adversarial review and no accredited laboratory has tested it. A demo that accepts your genuine document tells you nothing about what it does with a fake one. detail
• Anything with legal weight. No Member State recognises it, no regulator accepts it, and no relying party has ever acted on one in production. reliance

What to look at while you use it

• The credential you end up holding. It is vc+sd-jwt: an open format any conformant verifier can read, not a record trapped in our system. That is the actual point of the product. the mechanics
• What a verifier receives when the credential is presented, and what it does not.
• The failure paths. Deliberately fail a step and see what reason you get back. How a system behaves when it says no is more informative than how it behaves when it says yes.