A safety map is only worth what its data is worth. This page explains, in public, how SafePass seeds its map before the first journey is ever taken, how it grows from the journeys that follow, and how much weight any single report carries.
Where we publish a figure, we publish where it comes from and the date we last confirmed it. Where we have no figure yet, we say so rather than estimate.
5Verification tiers every safety marker is classified intoVerifiedSafePass incident-verification model — Unverified, Partially Confirmed, Verified, Disputed, Rejected. As of 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. As of ₦2,000Cost of a monitored journeyVerifiedSafePass published pricing — charged per monitored journey, deducted from the wallet. As of ₦2,000Minimum wallet top-upVerifiedSafePass published pricing — minimum wallet funding amount. As of
Building the map: a three-layer strategy
Layer 1
Admin pre-seeding, before launch
Before a single public journey is monitored, the map is populated by hand with safety data that already exists in the public record. An empty map is not a neutral starting point for a safety product — it is a misleading one, so the map is seeded first.
Every seeded 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.
Known kidnapping corridors, drawn from public news archives, security advisories, and police reports
Permanent police, military, and FRSC checkpoints
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 report what they encounter on the road from the SafePass app, 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
Verification weighting
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 tiers, and its tier is visible wherever it appears — in the app and here. Colour is never the only indicator of tier, 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
A single report, not yet corroborated. Shown 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
Administrator-approved, or confirmed by five or more travellers. Shown prominently, because this is the tier the map is most confident in.
Disputed
Reports conflict — some travellers confirm it, others say it is not there. Flagged for administrator review rather than resolved automatically.
Rejected
An administrator has explicitly judged the report false or malicious. Rejected reports are hidden from the map entirely, which is why you will never see this tier on a live marker.
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.
