Your information.
Your choices.

01 / Scope

Who we are

KAB PAY is operated by DoctorNow Holdings Inc (“we”, “us”, or “our”). This policy applies to the KAB PAY website at kabpayment.com, the KAB PAY web and mobile apps, and our related payment and support services.

KAB PAY and KABCARE share an operator and support contact. This policy describes KAB PAY’s payment service; it does not describe KABCARE’s healthcare records or services.

You can contact us without signing in: +233 24 257 3008, WhatsApp, or our support page.

02 / Collection

Information we collect

• Account details: your name, username, email address, phone number, account identifiers, account type, and profile changes.
• Sign-in and security information: password and payment-PIN verification records, verification-code requests, session identifiers, and registered passkey identifiers and public keys. Passwords and payment PINs are stored as salted hashes rather than readable values in the account database.
• Wallet and payment information: balances, amounts, currencies, payer and recipient details, mobile money numbers and networks, bank details you supply for withdrawals, payment references, notes, status, and transaction history.
• Requests and vendor activity: payment links, request codes, QR-code contents, vendor settings, terminal charges, and confirmation records.
• Face-enrollment information: when you choose face payments, live camera footage and reference images used for verification, face templates, enrollment identifiers, and verification results. See Face data and consent.
• Technical and support information: browser or app information, network and service logs, error details, and messages or screenshots you choose to send us.

Payment details entered into a payment provider’s checkout are also handled by that provider. KAB PAY receives information needed to verify and record the transaction. Do not send full card details, passwords, one-time codes, or payment PINs to support.

03 / Purpose

How we use information

We use information to create and maintain accounts, authenticate users, operate wallets, process or verify payments, share payment requests, support vendor transactions, and show balances and payment history.

We also use it to send verification and service messages, respond to support requests, investigate errors and suspected misuse, maintain the service, and meet applicable recordkeeping or legal obligations. Setup status helps us remind you to finish face enrollment and your payment PIN.

04 / Face data & consent

Your face profile is optional.

Face enrollment starts only when you choose it, accept the enrollment consent, and allow camera access. You can use other available payment methods without enrolling your face.

A live scan is sent to Amazon Rekognition, an Amazon Web Services (AWS) service. It checks whether a person is present, produces a verification result and reference image, and creates a mathematical face template associated with your KAB PAY account. Later scans can be compared with enrolled templates to identify your account at a vendor terminal.

Your face is used for identification. A vendor payment also requires your payment PIN and the applicable payment checks; recognizing your face alone does not complete a charge.

We store enrollment status and identifiers in our account system, while face templates are stored in our AWS Rekognition collection. The current integration does not save a separate camera-video archive or audit-image gallery in KAB PAY’s application storage. This does not mean that all data is deleted when a scan ends: stored face templates and enrollment records remain until removed.

AWS processes submitted images and video under its own service terms. Those terms permit certain storage and use for service improvement unless an applicable opt-out is in place. More information is available in AWS’s Rekognition privacy information and AWS service terms.

You may leave a scan using Back or Finish later. Revoking camera permission stops future camera access but does not erase an existing face profile. To withdraw enrollment consent and request removal of your stored face profile, contact support. You can also request deletion of your account.

Face-payment enrollment is separate from passkey sign-in. A device or password manager may use its own biometric check for a passkey; KAB PAY receives the authentication result and public-key information, not that device’s biometric template.

05 / Sharing

Who receives information

• Payment providers: Paystack and the banks or mobile money providers involved in your chosen transaction receive the information needed to process, verify, reconcile, or investigate it. Their own privacy terms also apply; see Paystack’s terms and privacy information.
• Hosting, verification, and messaging providers: AWS helps host and operate KAB PAY, store account records, send verification emails, and provide face verification and matching.
• Other users and vendors: relevant account and transaction details are shown when finding a recipient, receiving a payment, or completing a vendor transaction. A shared payment link, code, or QR code can reveal its recipient, amount, currency, and note to someone who receives it. Share these only with intended recipients.
• Support channels: when you contact us through WhatsApp, SMS, email, or telephone, that communications provider also processes the message or call under its terms.
• Required disclosures: we may disclose relevant information when required by law, a binding legal request, or to investigate misuse and protect users and the service.

The public website does not include advertising trackers. KAB PAY does not provide an advertising marketplace for your payment or face-enrollment data.

06 / Storage & security

Where information is handled

KAB PAY’s current backend uses AWS infrastructure in the United States. Payment and communications providers may process information in other countries. Their processing locations and protections are governed by their applicable terms and data-protection obligations.

We use HTTPS, account authentication, and service access controls to help protect information. No online service can guarantee absolute security. Protect your device and credentials, and contact support if you suspect unauthorized access.

The web app uses browser storage to remember session and account state. Signing out or clearing site data removes locally stored access information; it does not delete server-side account or transaction records. Payment providers may use their own cookies or storage during checkout.

07 / Retention & deletion

Keeping and deleting information

We retain account, payment, support, and security records while needed to provide the service, resolve outstanding transactions or disputes, investigate misuse, and meet applicable recordkeeping obligations. Retention depends on the record and the purpose; an expired login or scan session is not the same as deletion of its related records.

To initiate account deletion, open Account settings → Delete account and confirm your current password. This disables your account and starts a deletion request; permanent removal is handled separately. You may also request help through support without signing in.

Support verifies requests and arranges removal of personal information that does not need to be retained. Contact support to confirm the status and expected completion of your request.

Payment, dispute, audit, or legal records may need to be retained after account deletion. Where retention is required, we limit continued use to that purpose. Backups and providers’ records may have separate retention requirements. Clearing History in the app does not erase server-side transaction records.

Face templates are kept to support your enrollment until the face profile or account is removed. Tell support specifically if you want your face profile removed while keeping your account.

08 / Your choices

Manage your information

You can update your profile, change your password or payment PIN, manage available sign-in options, and request account deletion in Account settings. Camera and other device permissions can be changed in your device or browser settings. Disabling a permission can prevent its related feature from working.

Contact support to request access, correction, a copy, or deletion of personal information, to withdraw face-enrollment consent, or to raise a privacy concern. We may need to verify your identity before acting. Applicable rights and any permitted retention depend on the law governing your request.

KAB PAY is not directed at children. If you believe a child has provided information without appropriate authorization, contact us so we can review it.

09 / Contact & changes

Talk to us about privacy

DoctorNow Holdings Inc · KAB PAY
Phone: 024 257 3008 (+233 24 257 3008)
WhatsApp: Message KAB PAY support
Support: kabpayment.com/support/

We may update this policy when the service or its data practices change. The current policy and its last-updated date will remain available at this URL.