NeuroSign: sign with a face, verify without us
One story: a bank officer sends a loan agreement, the borrower signs on a phone, anyone verifies the result offline.
1 Sender
Upload, add signer, policy picks the check, place the field, send. 4 steps.
2 Signer (phone)
Review, verify and sign in one step, evidence file. 2 screens to a signature, then the result.
3 Verify offline
Drop a signed file, get five checks. Try the two tampered samples.
4 Audit certificate
One readable record: identity check, integrity, time, log position.
Signer path next to the market
Rows without a tag are estimates from public documentation and help pages (research files 02 and 03). The row tagged Measured comes from one live run on 08.10.2026, one account, not an average. The NeuroSign row is counted live in this prototype.
| Product | Screens / clicks to a signature | Identity check |
|---|---|---|
| DocuSign | about 7 clicks without identity check | separate step; on desktop a second device and a code typed back |
| Adobe Acrobat Sign / Dropbox Sign | 5 to 6 clicks | separate or paid add-on |
| PandaDoc | 4 to 5 clicks | plus 4 screens when ID check is on |
| OneSpan Sign | about 6 screens before signing | separate step, then "Continue to signing" |
| Aadhaar eSign (typical platform) | 4 to 5 screens | 2 domain changes, 3 OTP per hour limit |
| Zoho Sign (self-sign, measured 08.10.2026) Measured, 1 live run | 4 screens, 8-9 clicks plus a drag and a typed signature (6-7 clicks after the first signature). The remote-signer path (link from an email) was not measured. | none in the self-sign path; identity is the account login; evidence is email, IP and time |
| NeuroSign prototype | 2 screens and 2 taps until the signature is recorded; the 3rd screen only shows the result | same step as signing, no code, no second device, no domain change |
How to read the tags
- 1 DocumentUpload
- 2 SignerWho signs
- 3 Check and fieldPolicy and place
- 4 SendReview
Step 1 of 4: Upload the document
Loaded document
- Name
- Size
- SHA-256
This hash is shown to the signer and written to the evidence record.
- 1 DocumentDone
- 2 SignerWho signs
- 3 Check and fieldPolicy and place
- 4 SendReview
Step 2 of 4: Add the signer
- 1 DocumentDone
- 2 SignerDone
- 3 Check and fieldPolicy and place
- 4 SendReview
Step 3 of 4: Identity check and signature field
Click the page to move the signature field.
- 1 DocumentDone
- 2 SignerDone
- 3 Check and fieldDone
- 4 SendReview
Step 4 of 4: Review and send
- Document
- Class
- SHA-256
- Signer
- Identity check
- Link valid for
- 72 hours, one active session at a time
- Storage
- Planned: encrypted at the bank (X-Wing + AES-256-GCM), kept 7 years (demo value, set by bank policy). Not happening in this prototype.
Sent. Waiting for the signer.
- Created
- Waiting for signer 1
- Signed
Signer link (one-time session, expires in 72 hours):
https://sign.demobank.example/s/7Qm2x9...kd3
Email and SMS delivery are not part of the demo.
Verify a signed document
Works without our server and without a network. Everything below runs in this page, which makes no network request and uses system fonts.
Tip: on the signer's last screen, download the evidence file and the signed sample document, drop both here, then change one character in the sample document and drop it again.