KeepableYou fit tell who sent am
Before bank, court, employer or agency sends anything, we check am against company register and responsible person approves Keepable account. Item shows verified organisation wey sent am, no be only display name for message.
Know who send am. Know say e stay complete.
When verified organisation sends item through Keepable, we seal am as e arrives. Check who sent am and whether file changed. Anybody wey you give copy fit do same check without account.
Example to explain am
Statement of account · May 2026
Northbridge Bank
- Sender verified
- Checked against CAC before first letter
- Sent
- 2 June 2026, 09:14 WAT
- Fingerprint
- 4f9a 71c0 e8d2 5b13
- No change since
- The time dem sent am
Anybody fit check this file without account.
Check one nowWetin you fit do with am
E stays document, no be screenshot
Na original arrives, no be picture or link wey expires. E stays for Keepable when you change device, and seal lets you later check say na same file.
Give another person copy wey dem fit check
Landlord, embassy, new employer or court fit check copy without account. Their browser shows whether na file wey dem sent and whether e changed.
Seal comes from file itself, so check follows the copy.
Wetin gets sealed
Exact document bytes as dem be when sender sent am.
Wetin check proves
Say file for your hand na exact file wey dem sent, no be another version.
Where e happens
For your browser. File no leave your phone, and no login needed.
Questions and answers
Wetin this fingerprint really be?
Na SHA-256 digest: standard calculation turns whole file into one 64-character value. Change one letter or one scan pixel and result go completely different. No be summary, and you cannot recover file content from am.
If file no leave my phone, wetin check sends?
Signed proof gets checked for your device first. After e passes, browser fit send only file SHA-256 fingerprint to find optional record details. Document, name and content stay for your device.
Which proof follows document?
Keepable document signature, certificate chain and signed snapshot of sender organisation and send time. Verifier reads dem from PDF. No receipt code to find or type.
Seal proves who sent am, or only say e no change?
Keepable signs PDF and historical sender snapshot together. Verifier checks signature, exact bytes and recorded time we accept sender send action. E proves wetin Keepable sealed for named sender; e no claim say sender use separate signing key.
What if sender or Keepable closes business?
Keep PDF and audit export with records. Signature and sender snapshot remain for file, but public verifier needs our currently published private-root and authorised-signer list. We no promise browser checks after certificate expires or service closes.
I fit check my own upload the same way?
Yes, result go say na your own. Your uploads get sealed too, so you fit prove no change since you put am here. No sender name because no sender. See your own documents page.
The limit
Seal proves say document no change since dem sent am, and e comes from named organisation. E no prove say content true. If bank sends wrong balance, seal proves bank sent that statement; balance still na matter between you and bank.
Make room for wetin matter.
Items sent through Keepable arrive sealed. Your own files get marked as your own.