The questions people actually ask.

A small proportion of any population has fingerprints that scan poorly — manual labour, age, certain skin conditions, injury. Biolog captures multiple fingers at enrolment and supports alternative modalities, and every deployment includes a defined exception process with supervisory authorisation and a full log entry. What we do not do is leave the operator to improvise, because an undefined exception process becomes an unmonitored bypass.

Biolog works from mathematical templates derived from the sample, which cannot be reversed into a usable image. The precise answer for your deployment, including anything retained for any purpose, is set out in the data handling statement issued with it — see the Security & compliance page.

Verification devices hold a synchronised local subset of the register and continue working offline, queuing transactions for sync when connectivity returns. An examination does not stop because a mast is down.

They can hand over the plastic, but the card is a pointer to a biometric record. Where verification is biometric, the friend fails. Where a deployment uses card-only verification at a low-risk point, that is a choice made knowingly during configuration, not a gap.

This is the single number that determines whether you can enrol your population in the window available, so we measure it on your hardware, with your data fields, during the pilot phase — and we plan the enrolment schedule around the measured figure rather than a quoted one.

Not necessarily. Existing biographic data can be pre-loaded so that enrolment captures only the biometric. Existing card estates can sometimes be re-encoded rather than replaced. Send us what you have and we will assess it.

Biolog is built to support an institution’s obligations under the Nigeria Data Protection Act 2023 — consent capture, purpose limitation, configurable retention, subject rights handling and an audit trail. Compliance is a shared responsibility: we provide the mechanisms, the institution holds the lawful basis and the controller obligations.

Usually. Biolog integrates natively with the BTS product family and connects to third-party systems through its API. Tell us what you run and we will tell you plainly what integrates, what needs building, and what does not.

Pricing depends on population size, number of verification points, hardware requirement and whether cards are produced. We issue a costed schedule after a discovery conversation. We do not publish a price list, because a number without those variables would be a guess.

It depends almost entirely on how quickly you can move your population through enrolment, which depends on stations, staffing and communication rather than on us. We quote a range against your figures during discovery. See Deployment & support.