Data Processing

Last updated: 5 November 2026

In short

When a lender uses AfriScore, the lender decides what borrower data to send and why. AfriScore processes it only on the lender’s instructions, under a written data processing agreement. This page summarises our standard approach; the signed agreement governs.

01

About this page

This page explains how AfriScore handles personal data on behalf of lenders that use the AfriScore API or run a pilot. It summarises our standard data processing agreement. How we handle data from visitors to this website is covered in the Privacy Policy.

02

Roles

The lender is the controller of its borrowers’ data: it decides what to send and why. AfriScore is the processor: it processes that data only to deliver the service the lender has asked for. For website visitors, AfriScore is the controller.

03

What we process

Inputs: behavioural and numerical fields such as mobile money activity, utility payments, airtime patterns, device metadata and prior lending indicators. Outputs: a credit score, a risk tier, a probability of default and, on request, the factors behind them. We ask lenders to identify borrowers with a reference they control, not with names or national ID numbers.

04

Instructions and purpose limits

We process borrower data only on the lender’s documented instructions: to return scores and explanations and, during a pilot, to calibrate the engine on that lender’s own outcomes. Any other use requires the lender’s written agreement. We do not sell borrower data.

05

Where the data lives

You choose the deployment. With the hosted API, each request is processed by AfriScore’s scoring service. With an on-premise deployment, the engine runs with Docker inside the lender’s environment, so borrower data does not have to leave the lender’s network. The location of hosted processing is stated in the agreement.

06

Security

Requests are sent over encrypted connections, access to systems and data is limited to people who need it, and on-premise deployments let the lender apply its own network and access controls. The lender’s security team can review the integration and deployment before real applications flow.

07

Sub-processors

We use a limited number of service providers to run the scoring service. The list of sub-processors that apply to a lender is provided with the data processing agreement, and we tell the lender before adding or replacing one.

08

Retention and deletion

Retention periods are set in the agreement and kept as short as the service allows. When the agreement ends, or when the lender instructs us, we delete or return the data it sent us, unless the law requires us to keep it.

09

Rights of borrowers

Because the lender is the controller, borrowers exercise their rights, such as access, correction and deletion, with the lender. We assist the lender in responding, and every score can be explained with the factors that drove it.

10

Incidents and audits

If we become aware of a security incident affecting a lender’s data, we notify the lender without undue delay and help it respond. We provide the information a lender reasonably needs to verify our compliance and support audits as agreed in the contract.

11

Contact

For data processing questions or to request our standard agreement: privacy@afriscore.africa.