NON-INTRUSIVE — no impact on National Telecommunications infrastructure·Respects data privacy — metadata only, never message content·Real-time operation, all access authorised and audited

Northern Nigeria Command Centre

A Northern Nigeria Security Trust Fund system · state-level indicators across the 19 northern states and the authorised case workflow

Demonstration data. All counts, cases, device references and locations on this page are fictional. No real phone can be located from this dashboard.
Agreed use policy. Following discussion with the Fund's team: this platform is to be used only for legitimate cases carrying a valid, recorded approval. Against the recent proliferation of arms into the wrong hands across the north — fuelling kidnapping, murder and terrorism — the authorised case workflow now flags, in red, any subject whose movement history includes a known high-risk forest or ungoverned-space corridor (see Location & movement, under Subject lookup) — documented examples include Sambisa in Borno, Rugu/Dajin Rugu across Katsina, Zamfara and Kaduna, Dansadau in Zamfara, Kamuku in Kaduna, Alawa in Niger, the Kainji Lake forests in Niger and Kwara, and Falgore in Kano. These corridors ordinarily carry very few residents or legitimate daily users, so a device detected there stands out against the sparse background activity; the platform weighs that low-population context alongside the corridor itself, and seeks the most precise, lawfully obtainable fix for exact location and apprehension.

Northern Nigeria at a glance

Live visibility at state level, local government level, and combined across all 19 states.

LIVE —

Figures refresh automatically for this demonstration — a simulated feed, not a live operator connection. Production figures would refresh the same way from the operator gateway.

Real-time analysis

Live intelligence, updating automatically.

—

Live analysis feed

LIVE

By state

Real-time analysis is computed on the live (simulated) feed. A state command sees only its own state; NNSTF Head Office (Central Command & Control) sees the combined picture across all 19 states, including cross-state escalations. Illustration on fictional data only.

Northern Nigeria by zone and state

Pick a zone or a state capital to see aggregate counts for the selected window.

Synthetic sample
Map loads when onlineThe counts on the right work without a connection.

A marker shows a state capital for reference, never a phone position.

Counts represent devices observed in a sample window, not unique people. Values below 20 are suppressed. No device trail, live location, identity or operator feed is connected. Map tiles load from OpenStreetMap when online.

Area activity

Active cellularData onlyForeign roamingSatellite

Tap a column to sort, or a state name to focus the whole dashboard on it. All rows contain illustrative figures, not operator data. Counts below 20 are suppressed. Data-only and roaming are subsets of cellular activity and can overlap; satellite is a separate category. Do not sum these columns.

Review queue

Open a case to see where it sits in the approval chain.

Sample cases
Approval boundaryLocation and device-status requests require two different reviewers. This preview cannot submit, approve or dispatch requests.

How an authorised agency locates a number of interest

Step through one fictional case, from the request to the audited result.

Illustration · fictional case

    This walk-through uses a fictional number, case and operator response. A number can only be located inside an approved case, by one operator, for a limited time. The answer is the approximate network area the SIM was last seen in, not a GPS position. A movement history over a period is a separate, higher request — returned only under a judicial warrant (see Subject lookup). The legal authority needed for each request is set by the governing law and should be confirmed with counsel before go-live.

    Subject lookup (authorised session)

    Open a single number of interest under a recorded authorisation. All figures are fictional.

    Illustration · fictional case

    Searches existing, already-authorised case records only — no limit on the number of searches per session. This does not open a new lookup on an arbitrary number; opening a case still requires the authorisation form below.

    No active sessionComplete the authorisation record to open a subject view.

    Audit trail

    No access recorded yet. Opening a session writes the first entry.

    Every lookup is time-bound and written to the audit trail. In production this writes to the central, tamper-evident log reviewable by the Trust Fund and the regulator. Compliant with the Nigeria Data Protection Act 2023; all data processed and hosted within Nigeria.

    Monthly case results

    Cases by the month they were submitted.

    cases submitted

    Status reflects each case’s current stage. These are case counts, not unique mobile users.

    Operator lanes

    Selected per case. Responses stay in a separate signed sandbox.

    Satellite counts require a separate provider interface. No live operator or satellite connection is active.

    Four system modules

    How the platform is organised, and what this preview covers.

    Traffic records

    Aggregate fictional activity is displayed. Network-wide call, SMS, data and transaction records are not ingested.

    Production interface pending
    Subscriber identities

    The case workflow uses demo references. There is no national identity or subscriber database in this preview.

    Production interface pending
    Device registry

    Demo IMEI references and a fictional multiple-SIM indicator are represented in the software prototype.

    Synthetic workflow
    Investigation front office

    Case submission, two-person review, operator sandbox response and audit are demonstrated.

    Synthetic workflow

    Contact graphs, broad traffic collection and deep packet inspection are not part of this preview. A subject’s movement history is demonstrated under Subject lookup and is returned only under a judicial warrant.

    Lawful boundary — what the platform will not do

    The limits are built into the design, not left to policy. They keep the Command Centre inside Nigerian law and protect the agency as much as the subject.

    By design
    No message content

    Conversations on WhatsApp, Signal, Telegram or any encrypted app are never read. End-to-end encryption means even the operator cannot hand this over.

    Not provided
    No installed-app list

    The platform does not enumerate the applications on a subject’s handset. That inventory lives on the device and is not visible to the network from a phone number.

    Not provided
    No device access

    No software is placed on any phone; no keystrokes, files, camera or microphone are captured. Endpoint intrusion is outside lawful interception.

    Not provided
    No mass collection

    No bulk traffic capture and no deep packet inspection. A number is examined only inside one approved case, through one operator, for a limited time.

    Not provided

    Each of these capabilities would require compromising a device or breaking encryption. They are neither built into nor technically reachable from this platform. What the Command Centre provides instead is lawful communications metadata — who and when, and an approximate network area — obtained from the operators under the governing law.

    Access control

    Every lookup is authorised and audited

    A number of interest can only be examined once an authorisation record is complete and two independent reviewers have approved the case.

    Authorisation
    Required before any access
    Recorded
    Officer, approving authority, legal basis, reference, purpose, expiry
    Reviewers
    Two, independent, per case
    Validity
    Time-bound; access ends at expiry
    Audit
    Every access logged and reviewable
    Location result
    Approximate area for a single location; movement history and live, continuous monitoring only under a judicial warrant
    State-command scope
    A state-command login sees and searches only its own state; a number opened there is not visible to other states
    NIN verification
    Checks identity against NIMC via Lawful Access; returns a masked reference and a match result only — the full NIN is never shown, stored or exported
    Safeguard: The full request-to-result workflow is demonstrated under “Review queue” and “Locate a number” above. The legal authority required for each request is set by the governing law and should be confirmed with counsel before go-live.

    Compliant with the Nigeria Data Protection Act 2023. All data is processed and hosted within Nigeria.

    Integration

    For the technical team: three ways to feed this dashboard with one JSON payload, and the regulator gateway (NCC) that live case work connects through.

    1 · Try a payload

    Load a JSON file from your computer to see your own figures immediately. Nothing leaves this browser.

    2 · Connect an endpoint

    Set dataSource: 'api' and api.url in the CONFIG block at the top of the script. The page fetches the payload and can refresh on a timer.

    3 · Embed in a portal

    Frame the page with ?embed=1 and push data or filters with postMessage, or call CommandCentre.setData() directly.

    Regulator gateway — Nigeria Communications Commission (NCC)

    The sanctioned route to operator records. Live case work (location, CDR summaries, NIN–SIM linkage, lawful monitoring) connects to operators through the NCC gateway under the Commission's lawful-access framework — not by any direct link to a carrier.

    Not connected
    NCC lawful-access gatewayAwaiting authorisation
    MTN · Airtel · Glo · 9mobile (via NCC)Reached through the gateway
    NIMC National Identity DatabaseSeparate Lawful Access channel

    Demonstration only — no live NCC or operator connection is active. In production this exchanges signed credentials with the NCC gateway; the Commission authorises the connection, and every request through it is logged on both sides.

    Payload contract (abridged sample)
    
          
    Endpoint configuration
    
          
    Embed and messaging
    
          

    Apply the suppression threshold on the server as well: send null for any count that must not be disclosed and the dashboard will show it as suppressed. Shareable views: ?area=Kano&window=previous&month=2026-08&place=kano. Show selected sections only: ?embed=1&only=overview,area-activity.

    How to read this dashboard

    1. Counts are devices, not people. One person may carry several devices or SIMs.
    2. Small numbers are hidden. Any count below 20 shows as “Suppressed” to protect individuals.
    3. Do not add the columns together. Data-only and roaming are subsets of active cellular; satellite is separate.
    4. Map markers are town centres. They never show where a phone is.
    5. A number is located only inside an approved case. A single location is an approximate network area, never a GPS pinpoint. A movement history over time is available only under a judicial warrant.
    6. Every case needs two different reviewers before any operator request, and each step is audited.