Prove say dem got am, no be only say you sent am
Record wey says “sent” na just one step. History shows who e went to, when e arrived and when dem opened am, so you fit answer delivery questions from events.
Every delivery records who e reached, when e arrived and opened, and signature, answer or consent wey followed. Read one item history or export records for audit or wider review.
Example to explain am
Record wey says “sent” na just one step. History shows who e went to, when e arrived and when dem opened am, so you fit answer delivery questions from events.
Every approval, signature, reply and returned file gets recorded as e happens, no be later from memory. Na this makes am evidence, no be just summary, ready when regulator asks.
When last person finishes, file gets sealed. Court, regulator or other side lawyer fit check copy against document, without account or asking you or us for anything.
Spreadsheet carries your own reference for every person, so each row matches your customer record without another matching exercise.
As each thing happens, no be when person asks later.
Added to ledger. Nothing gets rewritten, even corrections.
Sealed copy of one item, or CSV of answers, consent register or codes.
Twelve, with different meanings: accepted but not sent; sealed waiting for person without Keepable; delivered; read; approved, rejected, signed, acknowledged, granted, declined or submitted; plus expired and undeliverable with reason. Wrong NIN and customer wey said no no be same event; we no call both “failed”.
Entries only get added, never rewritten. Correction na new entry wey says wetin changed, no be silent change. Order of events na fact inside record, no need trust anybody, even us.
Three CSV files: form answers with one row per person, consent register for data protection officer, and claim codes with state. All begin with person and your own reference, so files for same audience fit join together.
No. Link gets signed, lasts short time and na new one every request. E no carry identity, so anybody with am fit read till e expires. File carries other people identity data. Fetch am through your server and give auditor the file itself.
Yes, and exports get recorded too. Both need deliberately granted permission, and ledger records who did am. Permission must cover bulk access too.
Nothing; only file wey dem already get. Their browser computes fingerprint and checks whether na sealed document. No account or Workspace access needed. Public verifier still needs Keepable published trust material, as recipient seal page explains.
No. This na record of correspondence you sent and responses. Service case follows one submitted request till outcome. Evidence case brings relevant records together for complaint, dispute, audit or investigation.
Record covers this interaction: wetin you sent, who got am, when dem opened am and wetin followed. E no prove all underlying statements true or replace specialist case-management system. E gives history of wetin happened for Keepable, with who did am.