🧾
Seal locally (no uploads)
Drop a PDF and we add a discreet QR badge. Hashing (SHA-256) and sealing happen in your browser—nothing is sent to our servers.
What you can do
🔏
Register the credential
We register only the file hash, issuance ID and issuer DID. No document copies are stored.
🔍
Verify anywhere
Scan the QR or open /v/<id>. The verifier recomputes the hash locally and compares it to the registry.
🏷️
Tenants & credits
Multi-tenant, credit-based flow. Issue when you’re ready—no background uploads, ever.
How it works
- 1
Seal on your device
You open the PDF locally. We add a QR badge and compute the SHA-256 in the browser. No upload takes place.
- 2
Register hash + signature
We register only the hash, issuance ID and issuer DID/signature. The original file never leaves your device.
- 3
Verify with the sealed copy
Recipients scan the QR or open the public page and (optionally) load the sealed PDF. The check runs locally and matches the registry entry.
Privacy-first flow
Issuer (your device)
- • Open/drag PDF locally
- • Seal + QR badge
- • Compute SHA-256 in browser
Credential registry
- • ID / CID
- • SHA-256 hash
- • Issuer DID + signature
- • Status (active / revoked)
Verifier (recipient device)
- • Scan QR / open
/v/<id> - • Recompute hash locally
- • Compare to registry → authenticity
developed by gecorp