Customer-to-bank access demo

Send the encrypted KYC package to the customer and the unlock link to the bank or app.

Create fake KYC data on this device. SovereignKYC encrypts it locally, stores only ciphertext, and issues a one-time unlock link. The customer can inspect the encrypted package. The bank, fintech, or social app can decrypt once only when it receives the unlock link.

Start Demo See The Model

Use fake data only. This sandbox demonstrates custody separation. It is not a production KYC or compliance system.

Creator flow

Create the KYC package

The customer creates fake KYC data. The browser encrypts the payload before delivery.

Fake customer data Full name Date of birth Address National ID number Document type I confirm this is fake demo data.

Cross-device delivery

Customer / you Encrypted package link Destination type Destination

Bank / app One-time unlock key link Destination type Destination

Live run

Watch the custody model

Encrypt KYC locally
Create receipt without PII
Create one-time unlock grant
Send customer and bank/app links

Waiting for demo submit.

What this proves

Storage is not control. Access is control.

PII is encrypted before delivery

The customer receives a package that can be stored or routed, but it remains ciphertext.

Unlock authority is separate

The bank or app receives a one-time unlock link. Without that link, the package-only view cannot decrypt.

Access is one-time

The unlock link redeems once. Replay attempts are rejected after the key is consumed.