A safety map is only worth what its data is worth. Transparency matters. This page explains exactly how SafePass builds its safety map, where information comes from, how reports are verified, and how every marker earns its level of confidence.
Where we publish a figure, we publish where it comes from and the date we last confirmed it. Where data is not yet available, we say so rather than estimate or speculate.
5Verification levels every safety marker is classified intoVerifiedSafePass incident-verification model: Unverified, Partially Confirmed, Verified, Disputed, Rejected. Last reviewed 5+Independent user confirmations that promote a report to VerifiedVerifiedSafePass verification weighting rules: a report reaches Verified at 5 or more user confirmations, or on admin approval. Last reviewed
Building the map: a three-layer strategy
Layer 1
Analyst curation, before launch
Before a single public journey is monitored, SafePass analysts curate the map using publicly available security information and verified institutional sources. An empty map is not a neutral starting point for a safety product. It is a misleading one, so the map is built first.
Every curated marker carries its coordinates, a category, a description, a severity level, and the source it came from. The source travels with the marker; it is not discarded once the pin is placed.
Areas with repeated publicly reported kidnapping incidents
Known official police, military, and FRSC checkpoints, where publicly verifiable
High-risk zones with repeated incident history
Layer 2
Crowdsourcing, from day one onward
From launch, the map is extended by the people using it. Travellers can report incidents they personally observe during monitored journeys, and SafePass administrators add markers for new intelligence, partner-supplied reports, and emerging threats.
Each report records its GPS coordinates, category, timestamp, description, and who filed it. Travellers can also act on markers others have placed: confirming one, flagging it as no longer there, reclassifying a checkpoint, or escalating something that looks wrong.
Reports cover kidnapping, armed robbery, accidents, roadblocks, police checkpoints, fake checkpoints, bad road, vehicle breakdowns, and suspicious activity
Administrators add markers for verified partner reports and emerging threats
Existing markers can be confirmed, disputed, reclassified, or escalated by travellers who pass them
Layer 3
Confidence scoring
Not every marker carries the same weight. A single unconfirmed report and an admin-approved one are both useful, but they are not the same claim, and the map does not present them as though they were.
Each marker is classified into one of five confidence levels, and its level is visible wherever it appears, in the app and here. Colour is never the only indicator of confidence, so the classification is legible regardless of how you see colour.
A report becomes Verified on admin approval, or once five or more travellers independently confirm it
Conflicting reports are marked Disputed and routed to a human for review rather than silently resolved
Reports an administrator rejects as false or malicious are removed from the map entirely
How much a single report counts
Every marker on the SafePass map carries one of these five classifications. Each pairs a colour with an icon and a written label, so the classification never depends on colour alone.
Unverified
Reported by one traveller but not yet independently confirmed. Displayed with a caution indicator so it informs without being mistaken for a confirmed fact.
Partially Confirmed
Between two and four independent traveller confirmations, or an administrator has verified it.
Verified
Confirmed by SafePass administrators, or independently corroborated by five or more travellers. Shown prominently, because this is the confidence level the map most trusts.
Disputed
Reports conflict. Some travellers confirm it, others say it is not there. Flagged for administrator review rather than resolved automatically.
Rejected
Determined to be false, duplicated, malicious, or otherwise unreliable after review. Hidden from the public map, which is why you will never see this confidence level on a live marker.
How quickly information changes
Safety conditions can change rapidly. While SafePass works to keep information current through traveller reports, administrator review, and trusted public sources, users should always remain alert and exercise personal judgement.
Markers may be updated, downgraded, or removed whenever new evidence becomes available.
Where the information comes from
SafePass draws on a mix of public, institutional, and in-house sources.
Nigerian Police Force public statements
FRSC advisories
NEMA
Publicly reported news
Verified partner organisations
SafePass Monitoring Centre
Traveller reports
Emergency service information
Community intelligence
This page is reviewed at least quarterly against SafePass product records. Every figure above shows the date it was last confirmed. Where a figure cannot be confirmed as current, we remove it rather than leave it published.
