60/100

Moderate evidence

ProblemPublished recordCrimeProblem Space

Trial of live facial recognition in London stations leads to a false positive and no arrests

Truvace record
TRV-2026-1213raw data (JSON)
Version
v3Revised
First published
Evidence type
Investigative reporting
Sources
1 sourceJournalism
sha256
b2e33eafdaab…check it

A six-month trial of live facial recognition (LFR) technology in London’s railway stations that cost more than £320,000 and almost 100 hours of police officers’ time led to one false match against a watchlist of suspects and no arrests. More than half a million faces were scanned between February and July this year in some of the capital’s busiest transport hubs during the British Transport Police (BTP) trial of the surveillance technology, which aimed to help catch offenders and people breaching court orders. A…

The problem

British Transport Police's six-month facial recognition trial in London stations cost £320,786 and scanned over half a million faces, yet produced one false match and no arrests.

What this doesn’t fix

Effectiveness depends on multiple operational variables and proportionality requirements that were not shown to align in the initial trial.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-09-29

Cite this record

v3

Truvace Impact Record TRV-2026-1213, v3: “Trial of live facial recognition in London stations leads to a false positive and no arrests.” Truvace, 2026-11-05. /record/TRV-2026-1213 (accessed on the day you copy it). sha256 b2e33eafdaab48b2…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3b2e33eafdaab…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv245a06720310d…

    Editorial pass: gain/problem restated as concrete outcomes.

  3. Publishedv14e68c690c400…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1213 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.