Facial recognition in policing

Lesson 1 of 5 in Biometric Surveillance, Law Enforcement AI, and Protecting Children.

On a January afternoon in 2020, Detroit police arrested Robert Williams on his front lawn, in front of his wife and two daughters, for a watch-store theft he did not commit. The evidence: a grainy surveillance still run through a facial recognition system, which returned his expired driver’s-licence photo as a candidate match. A detective put that photo in a six-pack lineup; a security contractor who had never seen the thief in person picked it. Williams spent thirty hours in custody. He is the first publicly documented wrongful arrest driven by facial recognition — and every documented case since (Porcha Woodruff, eight months pregnant, arrested for carjacking; Nijeer Parks in New Jersey; more in Detroit, New Orleans, Texas) shares two features: the technology erred, and the humans around it treated a candidate match as an identification.

Understand the mechanics and the failure pattern becomes predictable. A face recognition search takes a probe image, computes a numeric faceprint, and ranks a gallery (mugshots, licence photos, scraped web images) by similarity. The output is a ranked list of candidates, each above some adjustable threshold — never a verified identity. NIST’s FRVT testing shows the best algorithms are extraordinarily accurate on clean photos, and dramatically less so on the low-quality probes real investigations use — with error rates that differ by demographic group, the pattern the Gender Shades study first made public.

How a face search becomes an arrest — and where it should have stopped

  1. Probe image from CCTV

    Often low-resolution, off-angle, poorly lit — exactly the conditions where accuracy collapses.

  2. Algorithm ranks gallery candidates

    Returns a ranked list above a similarity threshold. The threshold is a policy choice, not a fact of nature.

  3. Analyst reviews candidates

    Best practice: treat any selection as an investigative lead only, documented as such.

  4. Is the match corroborated by independent evidence?
  5. Traditional investigation continues

    Alibi checks, phone records, witness interviews — the match is a lead, not proof.

  6. Lineup seeded with the match photo → arrest

    The wrongful-arrest pattern: the only “corroboration” is a witness picking the same photo the algorithm chose. Detroit’s 2024 Williams settlement now bans exactly this.

Key terms: facial recognition, remote biometric identification, biometric data, false positive, automation bias

Regulatory responses split into three families. US cities went first with outright bans on government use — San Francisco in May 2019, then Boston, Oakland, and roughly two dozen others; Portland, Oregon went furthest, banning private use in places of public accommodation. Some jurisdictions later reversed or softened (Virginia banned in 2021, re-authorised with safeguards in 2022; New Orleans reinstated use in 2022), so treat any list of bans as a snapshot.

States legislate procedure rather than prohibition: Washington’s 2020 law requires warrants for ongoing surveillance; Maryland and others now require training, disclosure to defendants, and bar FRT matches as the sole basis for arrest — the exact rule Detroit adopted in the Williams settlement.

The EU chose a third path: risk-tier the practice, not the technology. That is the subject of the next section — and the reason your prerequisite module matters here.

The EU AI Act slices police facial recognition along two axes: real-time versus retrospective, and publicly accessible spaces versus everywhere else. You met the full Article 5 text in the prohibited-practices module; here is the operational logic.

Real-time remote biometric identification (RBI) in publicly accessible spaces for law enforcement is prohibited — Article 5(1)(h) — subject to three narrow exceptions: targeted searches for victims of abduction, trafficking, or sexual exploitation and for missing persons; prevention of a specific, substantial, and imminent threat to life or a genuine, foreseeable terrorist threat; and locating suspects of listed serious offences punishable by at least four years. Even inside an exception, use requires prior authorisation by a judicial or independent administrative authority, a fundamental-rights impact assessment, registration, and a national law that opts the member state in.

Retrospective (post) RBI is not prohibited — it is high-risk under Annex III, with an extra deployer safeguard: Article 26(10) requires judicial or administrative authorisation, sought within 48 hours where the search is not tied to a specific ongoing investigation. The lesson for practitioners: in the EU the question is never “is facial recognition legal?” but “which practice, in which space, in which time-mode, under whose authorisation?

Police facial recognition — three regulatory families compared
FamilyApproachInstrumentWhereWeakness

City/state bans

Prohibit government (sometimes private) use outright

Local ordinance or state statute

San Francisco (first, 2019), Boston, Portland (incl. private use); ~two dozen US cities

Reversible by the next council vote — Virginia and New Orleans both walked bans back

Procedural regulation

Permit with warrants, training, disclosure, and a ban on FRT as sole basis for arrest

State statute or litigation settlement

Washington (2020), Maryland, Detroit (Williams settlement, 2024)

Depends on compliance culture inside agencies; audits are rare

EU risk-tier model

Prohibit real-time public-space law-enforcement RBI (narrow, authorised exceptions); classify retrospective RBI as high-risk with 48-hour authorisation

AI Act Art 5(1)(h), Art 5(3), Annex III, Art 26(10)

All 27 member states (opt-in national laws required for the exceptions)

Member-state opt-ins and broad “serious crime” lists could normalise the exceptions

Interactive checkpoint quiz (2 questions) — open this page in a browser to take it.