Police Accountability

  • |

    America’s License-Plate Database Has Entered Its ‘LMAO’ Era

    ByHugh Jass

    The filing blinked first. Atlanta’s September 14 audit reported that 99.93% of 115,578 year-to-date Flock searches complied with department policy, a number so reassuring it arrived wearing a tie and carrying a binder. Then the footnote cleared its throat: 79 searches, or 0.07%, still required investigation. Statistically, that is tiny. For the people whose vehicle-location data was searched, “tiny” is not necessarily a synonym for “please stop worrying.”

    This is the institutional fantasy at the heart of automated license-plate readers: install cameras, add a search-reason field, and accountability will emerge like a well-trained office plant. But the technology can record a search without preventing an officer from treating the national road system like personal browser history. The audit trail exists; the question is whether the rules behind it have enough teeth to matter.

    That concern is not theoretical paperwork theater. A USA TODAY records investigation described repeated or improper Flock searches across agencies, with cases leading to arrests, firings, or internal investigations. That does not mean every flagged search was illegal or malicious, and it does not make every department equally culpable. It does mean the system’s clean percentage cannot be allowed to become a ceremonial curtain hiding the people who need to examine the exceptions.

    Meanwhile, reporting from Huntsville described a public-records dispute involving requests for Flock audit logs. That is not proof that records were destroyed, and it is not proof that misconduct occurred. It is, however, a useful reminder that surveillance accountability has two doors: the database must remember what happened, and the public must have a meaningful way to inspect the memory. A locked filing cabinet is not transparency merely because it contains excellent notes.

    So here is my formal finding, entered into Exhibit A with a trembling administrative stamp: Atlanta’s 99.93% may describe broad compliance, but it does not settle whether questionable searches are consequentially investigated or publicly reviewable. A system that remembers every plate while making the public fight for the audit trail is less a safeguard than a surveillance spreadsheet with a locked cabinet. The document has a pulse. Someone should be allowed to check its browser history.

    Sources

  • |

    America Bought a Surveillance Dragnet and Forgot the Employee Handbook

    ByHugh Jass

    The document coughed first: America had purchased a national map of where ordinary people drive, then apparently filed the employee handbook under “please use responsibly.” A Washington Post investigation reported at least 50 officers accused or charged with misusing license-plate-reader systems, including 26 cases involving intimate partners or former partners. The technology can help reconstruct a person’s movements across thousands of communities. The paperwork, meanwhile, appears to have been walking there with a carrier pigeon.

    That is the central administrative failure: the networks expanded faster than the rules explaining who may search them, for what reason, and what happens when the reason is “curiosity with a badge.” The Post described safeguards such as case-number requirements, search justifications, and routine review as optional or inconsistently enforced in many places. An audit log is not accountability if everyone treats it like a guest book at a haunted house.

    Exhibit A arrived from Reynoldsburg, Ohio. WOSU reported that two former officers may have conducted as many as 100 personal searches, including one plate searched 46 times. Those are reported allegations, not a verdict against every officer or every agency using the technology. But the numbers do explain why “the system keeps a record” is not a complete safety plan. A burglar alarm also keeps a record after the window is broken.

    The institutional contradiction is almost too tidy for government: a search can be technologically easy while the justification, review, and consequences remain bureaucratically foggy. Police agencies and vendors helped install a tool capable of tracing ordinary travel before dependable controls became routine. The public received the movement map first and the policy memo later, possibly after someone found it beneath a stack of procurement confetti.

    My mock finding, after an afternoon in the records room, is that the real suspect is not only the officer who found the search button. It is the missing policy that left the button glowing in the dark. The recommended form now includes a checkbox labeled: “Why did this officer look up an ex?” Beneath it: “Please use responsibly.” The filing blinked. Nobody called it accountability.

End of content

End of content