09 / Maka ụlọ ọrụ

See every step.Export the record.

Each delivery records who it reached, when it arrived, when it was opened and any signature, answer or consent decision that followed. Read one item's history, or export a set of records for an audit or wider review.

Proof of delivery · open times · signed copies · consent records · audit exports

N'ime ngwa

History of one letter

Loan offer letter · to a verified recipient

Sealed

  • Delivered12 Jun, 09:14
  • Opened12 Jun, 18:02
  • Signed13 Jun, 08:41 · confirmed with a passkey
  • Sealedthe signed copy, checkable by anyone

  1. Show

    You can prove they got it, not just that you sent it

    A log line reading "sent" is only one step. The record shows who it went to, when it landed and when they opened it, so delivery questions can be answered from the event history.

  2. Trace

    You see every step, in the order it happened

    Each approval, signature, reply and returned file is written down at the moment it happens rather than assembled afterwards from what people remember. That is what makes it evidence instead of a summary, and it is the difference between answering a regulator and preparing for one.

  3. Seal

    You hand over a copy that proves itself

    When the last person is done, the file is sealed. A court, a regulator or the other side's lawyer can check that copy against the document itself, without asking you for anything, without asking us for anything, and without an account.

  4. Export

    You can give an auditor a ready file

    The spreadsheet already carries your own reference for every person in it, so each entry maps back to the customer record you hold without a separate matching exercise.

1,369

organisations investigated in a single sweep. 795 of them were banks and fintechs.

NDPC · August 2025

Written when
As each thing happens, not on the day somebody asks about it.
Kept how
Appended to a ledger. Nothing in it is ever rewritten, including a correction.
Handed over as
A sealed copy of any one item, or a CSV of the answers, the consent register, or the codes.

Nkọwa zuru ezu

What states can one recipient be in?
Twelve, and they say different things on purpose. Accepted but not sent yet. Sealed and waiting for somebody with no Keepable yet. Delivered. Read. Then whatever they did: approved, rejected, signed, acknowledged, granted, declined, submitted. Plus expired, and undeliverable with the reason attached. A mistyped NIN and a customer who said no are not the same event, and nothing here collapses them into "failed".
What does "cannot be edited" mean in practice?
Entries are appended and never rewritten, so a correction is a new entry that says what was corrected rather than a value that quietly changed. The order of events is therefore a fact about the record rather than something anybody has to take on trust, including us.
What exactly can I export?
Three files, each a CSV: the form answers, one row per respondent; the consent register a data protection officer keeps; and the claim codes with their state. All three lead with the same two columns, the person and then your own reference for them, so two of them downloaded for the same audience join to each other.
Is a download link something I can email to an auditor?
No, and the product will not help you do it. The link is signed, short-lived, minted fresh each time you ask, and carries no identity, so whoever holds it is the reader until it expires. One of these files is a spreadsheet of other people's identity data. Fetch it from your own server and hand the auditor the file.
If somebody looks at a masked answer in the clear, is that recorded?
Yes, and so is exporting a set of them, which is the same act in bulk. Both need a right somebody granted deliberately, and both are written to the ledger with the person who did it. A gate that only covers the slow route is decoration.
What does a third party need from me to check a sealed copy?
Nothing. They need the file, which they already have. Their own browser computes its fingerprint and asks whether that is the document that was sealed. They do not need an account or access to your Workspace. The public verifier still depends on Keepable publishing the relevant trust material, as explained on the recipient seal page.
Is this the same as a service case or an evidence case?
No. This page describes the record of correspondence you sent and the response it received. A service case follows one submitted request to its outcome. An evidence case is a separate matter that brings relevant records together for a complaint, dispute, audit or investigation.

Oke ya

The record covers what happened in this interaction: what you sent, who it reached, when they opened it and what they did next. It does not prove that every underlying statement is true or replace a specialist case-management system. It gives you the attributable history of what happened in Keepable.

Malite ebe a

Try it out

Maka ndị mmepe: Exports reference.