Nothing reaches the map on one person's word.
A map anyone can post to is a weapon. Everything below exists to make sure that a single report — however sincere, however malicious — cannot change what you see.
The path a report takes
From something seen to something shown
Scroll the diagram sideways →
A report that never gets corroborated never appears. It is not deleted and it is not published — it waits. Roughly nine out of ten anonymous reports are expected to stop there. That is normal, and it is the point.
Citations
A source is checked, not taken on trust
When an incident cites a newspaper, that claim is tested before it counts for anything. These are the ways a citation can be wrong, and what catches each one.
| How a citation can be wrong | What catches it |
|---|---|
| The link was invented | We fetch it. Anything other than a working page fails the citation, and a failed citation counts for nothing. |
| A lookalike web address | Every outlet has a registered domain. A link that is not on it is rejected before it is even stored. |
| A real article about a different incident | The article's publication date has to bracket the incident. An article cannot report something that has not happened. |
| A story recycled from an older attack | The same date check. This is the most common way false claims spread after a kidnapping in Nigeria. |
| Two outlets, one original source | Corroboration counts distinct publishers, not articles. Nigerian outlets republish each other constantly. |
| The outlet later removes the story | We keep a dated record and an archive link, so what we relied on can still be shown. |
Reporters
Trust is earned, and it can be lost
Some reporters are given a code. We do not know who they are — the code is stored as a one-way hash and there is no name attached to it anywhere.
What we track instead is whether a code's past reports turned out to be true. A code whose reports are repeatedly confirmed by independent sources earns priority. A code whose reports stop holding up loses it, automatically, without anyone having to make an accusation about anybody.
Why it works this way
You cannot verify a stranger's intentions, and you cannot verify a friend's either — people are pressured, paid and replaced. So SafeNaija never asks whether someone is trustworthy. It asks whether their reports have been right, which is something that can actually be measured.
A trusted code still cannot publish alone. One person is one witness however reliable they have been, and independence is the one thing confidence cannot substitute for.
Mistakes
When we get it wrong
We will. Any person or organisation can dispute a record by writing to corrections@safenaija.ng. We respond within 24 hours and take down anything we cannot substantiate while we review it.
Every correction and removal is logged publicly with its reason. We would rather be visibly correctable than quietly wrong.