Intelligent monitoring, built to be defensible.
We are opening a limited early-adopter programme for Nigerian churches, schools, hotels, retailers, fuel stations, hospitals, commercial and industrial facilities. You get the technology — and, just as importantly, the privacy architecture and the compliance paperwork that lets you answer your board, your congregation, your parents or your regulator when they ask what you have installed.
What this programme is, stated plainly
This is an early-adopter programme, which means we are deliberately working with a small number of Nigerian organisations first, at pilot scale, before opening the offering broadly. Public-sector engagements remain subject to the relevant government reviews and approvals; nothing on this page should be read as announcing an approval that has been granted.
We have also chosen not to display any certification, registration or approval badge that has not actually been issued. Where something is in progress you will see it labelled “Targeted”, “Under review” or “Subject to approval” — on this page and on the data protection page. You should treat any vendor who does otherwise with caution.
Why an early adopter would take this over the alternative
The Nigerian market is not short of cameras. What it is short of is deployments that can survive being questioned — by a board, by a parent body, or by the Nigeria Data Protection Commission.
Privacy-by-design, not privacy-by-promise
The privacy controls are architectural. Retention limits, access scoping and audit logging are enforced by the system, so a busy administrator cannot accidentally opt out of them.
You choose where the data lives
The same system runs in the cloud, in a Nigeria-hosted tenancy, or entirely on your own premises. That decision is yours and it is written into the contract, not left to us.
Built for Nigerian network conditions
Processing at the camera edge means the system keeps working through an unreliable uplink, and it moves far less data over the connection you are paying for.
Evidence you can actually use
Every retrieval is logged against a named user with a stated reason, which is what turns recorded footage into material that stands up in an internal or legal process.
A documented compliance position
You receive the impact assessment, the data-flow diagram, the retention schedule and the consent notices as documents — the paperwork a regulator asks for, prepared up front.
An exit that is not a hostage negotiation
Defined export formats and a written deletion procedure at termination. Leaving is a documented process, not a commercial lever.
Ten settings — and the privacy question each one raises
Every one of these deployments is legitimate and every one carries a different obligation. We have written the obligation next to the use case rather than leaving you to discover it after installation.
Churches
Entry monitoring for large gatherings, crowd-density awareness at peak services, and incident review after the fact.
Places of worship attract heightened sensitivity. Signage at every entrance, a named contact for the congregation, and a documented lawful basis are prerequisites, not extras.
Schools
Perimeter and gate monitoring, visitor management, and verified pick-up of pupils by an authorised guardian.
Processing involves children. Parental consent, a strict retention ceiling, and no processing beyond the stated safeguarding purpose should be treated as mandatory.
Hotels
Lobby and entrance monitoring, guest-safety incident review, and staff access control to back-of-house areas.
Guest expectation of privacy is high. Cameras belong in public circulation areas only — never in rooms, corridors serving rooms, or any area of expected privacy.
Supermarkets
Shrinkage reduction, queue and footfall analytics, and evidence capture for loss-incident investigation.
Analytics that only need a count should run as anonymous counting, not identity matching. Match the technique to the purpose rather than enabling everything.
Fuel Stations
Forecourt safety monitoring, drive-off detection, and after-hours perimeter alerting.
Vehicle-plate capture is personal data when it identifies a person. It needs the same lawful basis and retention discipline as any other identifier.
Hospitals
Entrance and pharmacy-store monitoring, restricted-ward access control, and lone-worker safety in isolated areas.
Health context makes almost everything sensitive. Clinical areas should be excluded by default and any deployment reviewed with the facility's own privacy lead.
Commercial Facilities
Multi-tenant lobby access, contractor and visitor verification, and tenant-scoped incident review.
Where several tenants share a building, it must be documented which organisation is the controller for which camera before anything is switched on.
Industrial Facilities
Restricted-zone access control, PPE-compliance monitoring, and perimeter intrusion detection across large sites.
Workplace monitoring engages employment law as well as data protection. Worker notification and a proportionality assessment belong in the deployment file.
Roads & Traffic Monitoring
Traffic-flow measurement, incident detection, and congestion analytics for road operators.
Traffic analytics rarely need to identify anyone. Anonymous counting and speed measurement should be the default configuration, with identification switched off.
Street Lighting & Smart City
Lighting-fault detection, environmental sensing, and public-space situational awareness for municipal operators.
Public-space monitoring is the highest-scrutiny category of all. Public consultation and a published impact assessment should precede deployment.
Four ways in, from a time-boxed pilot to full data sovereignty
Every package below includes the compliance documentation, not just the hardware. That is the part most quotations leave out and the part that costs you when someone asks a hard question later.
Proof-of-Concept Pilot
A single site that wants evidence before committing.
Fixed-fee pilot. Figure confirmed in writing before any work starts.
- ✓One site, limited camera count, agreed in the scoping call
- ✓Site survey and camera-placement plan
- ✓A written Data Protection Impact Assessment for the pilot scope
- ✓Privacy signage and a consent-notice pack for the site
- ✓Time-boxed pilot period with a defined end date
- ✓Full data deletion at pilot close, with a written deletion certificate
Single-Site Deployment
One church, school, hotel, clinic or filling station going live.
Priced per camera and per site after the survey.
- ✓Everything in the pilot, made permanent
- ✓Installation, commissioning and staff handover training
- ✓Role-based administrator accounts with individual named logins
- ✓Configurable retention schedule with automatic deletion
- ✓Audit trail of every access to recorded material
- ✓Choice of cloud, Nigeria-hosted or on-premises deployment
Multi-Site Programme
Chains, campuses, hotel groups and facility managers.
Volume-based. Per-site rate falls with site count.
- ✓Everything in the single-site deployment, across all locations
- ✓Central administration with per-site access scoping
- ✓Consolidated reporting across the estate
- ✓A named delivery contact and an agreed support response time
- ✓Group-level retention and deletion policy applied consistently
- ✓Assistance preparing your NDPC filings for the estate
On-Premises / Data-Sovereign
Buyers who require that no data leaves their premises or Nigeria.
Quoted against your infrastructure and network assessment.
- ✓Everything in the multi-site programme
- ✓Processing and storage on your own hardware, or a Nigeria-hosted tenancy
- ✓No cross-border transfer of recorded material by default
- ✓Your team holds the encryption keys and the administrator root accounts
- ✓Documented data-flow and architecture pack for your own regulator filings
- ✓Support model designed to work without remote access to live footage
On the absence of a price list. Deployment cost is driven by camera count, site count, cabling and power conditions, network quality and whether you host on your own premises or with us. Publishing a single headline figure would be wrong for almost every buyer who read it, so we quote in writing after a survey instead. Ask us for the survey and you get the number.
The privacy position, in one paragraph
Analysis runs on the camera. In the default configuration no facial image is transmitted off the device and none is retained. What is stored is an event record, held under a retention schedule you set, deleted automatically on expiry, and readable only by named users whose access is logged. You choose whether that data lives on your own premises, in a Nigeria-hosted tenancy, or in a cloud region — and that choice goes in the contract.
Documentation you can take into a meeting
Each of these opens in your browser and prints to PDF. They are written to be handed to a facilities manager, a board, or a legal reviewer without further editing.
NDPA privacy & consent notice template
A ready-to-adapt privacy notice and consent framework for a monitored premises, drafted around the Nigeria Data Protection Act 2023. Includes the entrance signage wording.
Open →Product brochure
The commercial overview: what the system does, where it fits, which sectors it serves, and how an early-adopter engagement runs from survey to go-live.
Open →Technical datasheet
Architecture, processing model, encryption posture, hosting options, retention behaviour and integration surface — with unconfirmed hardware figures marked as such rather than guessed.
Open →Data retention & deletion policy
The default retention schedule, how it is configured per camera, how deletion is executed and evidenced, and what happens to your data when a contract ends.
Open →System architecture diagram
The three trust boundaries — camera edge, your site, and the management plane — with every boundary crossing labelled.
Open →Biometric data-flow diagram
The lifecycle of a single frame from capture to automatic deletion, showing at each stage what exists, where it lives and whether it can identify anyone.
Open →See it running, on your own site
A demonstration is more useful at your premises than in a showroom, because your lighting, your entrance geometry and your network are the variables that actually decide whether this works. Tick the on-site box and we bring the equipment to you.
- →A working system, not a slide deck.
- →A walk-through of exactly what data the deployment would create.
- →The draft privacy notice your site would need at its entrances.
- →A written scope and price, after the survey.
Not ready for a demonstration yet?
Send the question instead. Procurement questions, privacy questions, questions from a board that wants to understand the exposure before anyone commits — all fine, and all answered by a person.