Kehbar — Security

i. The money

We're not a bank. The bank is the bank.

Kehbar is the layer on top of your bank. Payments are processed through licensed banking partners regulated by the Central Bank of Nigeria, not by us. This is the most fundamental thing on this page, and it shapes everything else.

Your money never sits with Kehbar.

Payments are processed through licensed banking partners regulated by the Central Bank of Nigeria. Kehbar holds the agreement and the record, never the money itself. We're software, not a deposit-taking institution.

If Kehbar disappears, your money doesn't go with it.

Your funds live at a bank, under your name, not ours. Kehbar going away is no different from any other piece of software going away. The money is unaffected because it was never with us.

We use the same bank transfer system as ordinary bank transfers.

When you pay through Kehbar, the money moves from your bank to the other party's bank using the established Nigerian banking network. The protections that apply to any local bank transfer apply here too.

We don't store card or banking credentials.

Payments are processed by our banking partners. Card numbers, account passwords, and bank login credentials never sit on Kehbar's systems. We work with the tokens our partners give us, never the underlying credentials.

ii. The account

Sign-up that gets out of the way. Verification that doesn't.

Signing up should be quick. Verification should be thorough. They happen at different moments: you can join Kehbar and look around before you're ready to transact, and the heavier checks wait until they actually matter.

Three sign-in options, all equal.

Email, phone, or Google, whichever you prefer. Whatever you pick, you verify it once at sign-up with a one-time code. We don't ask for the others, and we don't sell you on linking them later.

We don't use transaction PINs.

PINs that protect every individual action become muscle memory, which means they don't actually protect anything. We use device-level verification at the moments that matter, and ask less at the moments that don't.

Identity verification happens once, when it matters.

When you're ready to send or receive real money, you verify your identity with BVN or NIN plus a brief selfie. The verification is held by our banking partner. You don't repeat it for every action.

You can sign out of sessions you don't recognise.

Active sessions are listed in your account settings: device, location, last seen. You can sign any of them out at any time, and the system will sign you out automatically after extended inactivity.

iii. The data

We hold what's necessary. We don't hold what isn't.

Data minimalism is operationally easier, safer for us, and aligned with what's right for the people using Kehbar. We hold the records the product needs to work, and explicitly don't hold the things that aren't necessary.

Encrypted in transit and at rest.

The connection between your device and our servers is encrypted with current industry standards. The records we hold on our infrastructure are encrypted too. Nobody at Kehbar can read your records casually; access is logged and limited.

We don't sell your data. We don't run ads.

Kehbar has no advertising surface and no business model that depends on knowing more about you than the product requires. Your data is used to make Kehbar work for you. That's the entire purpose.

Both sides of an agreement see the same record.

Every agreement has a shared record both parties can see in real time. There's no version where one of you has more information than the other. Symmetry of vision is structural here, not optional.

You can export. You can delete.

Your data is portable: you can take a copy at any time. You can delete your account when you choose to, and deletion is real: records are removed, not soft-archived. We retain only what we're legally required to keep, for the periods we're legally required to keep it.

iv. The disagreement

A witness, not a judge.

This is the conviction the rest of the page rests on. When two people remember an agreement differently, when a payment is contested, when something goes wrong, Kehbar's role is to keep the picture clean, not to decide who's right.

We hold the record. We don't arbitrate.

The record shows what was agreed, what was paid, and when. We don't choose between competing accounts of what should have happened. That conversation is yours to have; we just make sure both sides are looking at the same facts.

Both versions of a difficult moment stay visible.

If two people disagree about whether a payment satisfied an agreement, both their accounts are part of the record. We don't merge them, and we don't favour one over the other.

We escalate to authorities only when legally required.

Records can be requested by a court or by regulators acting within their authority. If that happens, we comply with the law. We don't share records voluntarily, and we'll notify you where we're permitted to.

We can show the record. We can't reverse a bank transfer.

Once a payment leaves your bank, it's a matter for the banks involved and, where relevant, the police. Kehbar can produce a clear record of what happened, but we can't undo a transfer that's already been made. If you believe you've been defrauded, your bank's fraud line and the police are the right first calls.

For security researchers

Responsible disclosure.

If you've found a vulnerability in Kehbar, please write to security@kehbar.com. We'll work with you to confirm, fix, and disclose. We don't run a paid bounty programme yet; credit is offered, or withheld at your preference. We won't pursue legal action against researchers who report in good faith and don't access data they shouldn't.

For everything else

Questions about your account.

For questions about how your data is handled, how to delete your account, or how a specific safety feature works, help@kehbar.com reaches us. If you think your account is being misused, mention that in the subject line and we'll look at it first.

This page is a working document. Security evolves, and so does this page.

Last updated · 8 June 2026