TRV-2026-1213Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1213 version: 1 kind: certified reason: Certified into the record timestamp: 2026-09-30T06:54:02.492196Z status: published lens: p_space sector: crime headline: Trial of live facial recognition in London stations leads to a false positive and no arrests dek: 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… gain_title: (none) problem_title: The six-month live facial recognition trial in London stations cost over £320,000 and nearly 100 officer hours yet produced only one incorrect watchlist match and no arrests. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: The six-month live facial recognition trial in London stations cost over £320,000 and nearly 100 officer hours yet produced only one incorrect watchlist match and no arrests. problem_evidence: led to one false match against a watchlist of suspects and no arrests. | equipment hire and police staffing for the 18 deployments across the trial cost £320,786 and led to only one alert on a watchlist quick_read: Between February and July 2026, British Transport Police trialled live facial recognition in London's busiest railway stations, scanning over half a million faces across 18 deployments at a cost of £320,786. Freedom of information data showed the system generated only one watchlist alert, which was a false positive, and resulted in no arrests. The outcome raises questions about proportionality and operational value as police expand the same technology to the Underground, with later claims of three compliance-related alerts. It matters because it tests whether high-cost biometric surveillance delivers public safety benefits while processing sensitive personal data at scale, and uncertainty remains about watchlist composition, location selection, and independent oversight. limitation: Effectiveness depends on multiple operational variables and proportionality requirements that were not shown to align in the initial trial. tag: Evidence-backed problem key_points: British Transport Police ran 18 deployments of live facial recognition in busy London railway stations between February and July, scanning more than half a million faces. | Freedom of information data showed the six-month trial cost £320,786 for equipment hire and police staffing and produced only one watchlist alert. | Police extended the trial for four months to include London Underground stations, later reporting three confirmed alerts related to compliance with prevention orders. rundown: British Transport Police deployed live facial recognition across 18 operations in major London railway stations from February to July, scanning more than half a million faces against suspect watchlists. A freedom of information disclosure obtained by Liberty Investigates showed the trial cost £320,786 and yielded a single alert that was a false positive, with no arrests resulting. Despite the low hit rate, the force extended the trial to Underground stations, citing three later confirmed alerts involving people complying with sexual harm prevention orders, while oversight concerns about proportionality and special category data processing remain. sources: - journalism | The Guardian | https://www.theguardian.com/technology/2026/sep/29/trial-live-facial-recognition-cameras-london-stations-false-positive | 2026-09-29 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 4e68c690c4004d02c866890598290385a35f00813f78ffed9388f08ad119ff8d
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1213 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace