Short version: we never see your ID document. The identity check runs at the trust service provider, not here.
How it actually works
- 1You start the check from swipesign and get handed to the provider: A-Trust, WebID, or whichever national eID you picked.
- 2Everything sensitive happens over there. Your passport or ID card, the video, the document scan, the biometric comparison: all of it stays inside the provider's systems.
- 3The provider tells us the result: whether the check passed, and the verified name that goes on your certificate.
- 4That's it. No images, no document numbers, no video.
What we hold
| Data | Where it lives |
|---|---|
| Passport / ID card images | The provider. Never sent to swipesign. |
| Video or biometric check | The provider. Never sent to swipesign. |
| Verified name | swipesign: it appears on your signature |
| Whether verification passed, and when | swipesign: recorded in the audit trail |
| Your certificate | Issued and held by the provider |
Why it is built this way
Partly because eIDAS requires it: only a qualified provider may run the check. Partly because we'd rather not hold a pile of passport scans. Data we never receive can't leak from us.
It also means the provider is your point of contact for anything about the check itself. If verification fails and you want to know exactly why, they hold the detail. We only know it didn't pass.
Same applies to people signing your documents
Your signers verify with a provider too, and their ID never reaches us or you. You see their verified name and the audit trail, which is what you need to rely on the signature.