Documented cases
This has already happened.
Some surveillance failures begin when a person breaks the rules. Others begin when a system works exactly as designed. Both create powers that are hard to see, hard to contest, and harder to remove once they’re routine.
Every case below is labelled by what the record actually establishes — a conviction, an official audit, a settlement, a court filing, a pending charge. Where something is disputed or unresolved, it says so. That distinction is the point of the page.
Personal access became personal surveillance
Milwaukee, Wisconsin
CONVICTION Checked August 2026
A Milwaukee police officer used his authorized Flock access 179 times over two months to check the locations of two people for personal reasons, while on duty. Every one of those searches was logged with the same one-word justification: "investigation." The department didn't find it. One of the people being tracked did, by looking up their own plate on a public audit-log site, and reported it. The officer resigned and pleaded guilty.
Josue Ayala, an eight-year veteran assigned to Milwaukee Police District 2, ran 179 searches through the department's Flock system between 26 March and 26 May 2025 - 55 queries against one plate and 124 against another. The two people had previously been in a relationship; Ayala had begun dating one of them.
Milwaukee Police Department policy required a documented reason for every search. According to the criminal complaint, Ayala entered the single word "investigation" every time. Nothing in the system rejected it.
The misuse was not caught by an internal audit. One of the people being tracked looked up her own plate on HaveIBeenFlocked.com - a site built from Flock audit logs obtained through public records requests - saw the query history, and filed a complaint. Only then did detectives review the search history.
Ayala resigned and pleaded guilty to attempted misconduct in public office, a misdemeanour reduced from the original charge. He received a probationary sentence with 180 days of jail held in reserve.
Afterwards, one of the internal affairs detectives assigned to investigate Ayala was himself charged with misusing Flock to track two people. He told investigators his searches were for "training." Those charges are pending and are not a conviction.
Why it matters in Biddeford
This doesn't establish that Biddeford officials would behave the same way. It establishes what authorized access makes possible once the system exists - and that a free-text reason field plus an audit log did not prevent it, or detect it.
Normal operation created a movement record
Norfolk, Virginia
COURT RECORD - APPEAL PENDINGNot a misconduct case Checked August 2026
Records produced in litigation showed Norfolk's cameras captured one resident's vehicle 475 times in about four months. No officer had to misuse anything. No rule had to be broken. The collection was routine - and that is the point.
Lee Schmidt, a retired Navy sailor, and Crystal Arrington sued the City of Norfolk in October 2024 with the Institute for Justice, arguing that a city-wide camera network capturing their daily movements is a warrantless search. Discovery showed Schmidt's vehicle recorded 475 times over roughly four months, and Arrington's 325 times in the same period.
In January 2026 a federal judge in the Eastern District of Virginia granted summary judgment to the City. In a 51-page opinion, Chief Judge Mark Davis found that roughly 175 camera clusters with a 21-day retention window did not amount to tracking "the whole of a person's movements" under Carpenter v. United States.
The court did not say the question was closed. Davis wrote that ALPR surveillance "could become too intrusive" at some point, adding that while a definitive answer is elusive, "at least in Norfolk, Virginia, the answer is: not today."
Schmidt and Arrington appealed. The case is pending before the Fourth Circuit as Schmidt v. City of Norfolk, No. 26-1227.
Why it matters in Biddeford
This is not a misconduct case, and labelling it one would be wrong. It is evidence of what ordinary, lawful operation collects. The question it puts to Biddeford isn't whether the system could be abused - it's whether routine collection at that scale is a trade worth making, and who gets to decide.
What this page is not
These cases don’t prove Biddeford would do the same
They aren’t an accusation against anyone in City government, and nothing here suggests that every department misuses every technology. Presenting exceptional cases as inevitable outcomes would be dishonest, and it isn’t the argument.
What they show is why surveillance authority shouldn’t enter City government as routine equipment procurement. Once the capability exists, what happens next depends on every future user, administrator, policy, contract, vendor and administration — none of whom are in the room when the purchase order is signed.
The public decision belongs before that chain begins.
Still being checked
More cases are coming to this page
Several well-documented cases — a police department that learned from a state auditor that outside agencies had been searching its own cameras, a wrongful arrest built on a false facial-recognition match, a predictive-policing program that turned a teenager into a standing target — are not published here yet.
They will be, once each has been checked against the underlying court filing, government audit or official release rather than against a summary. A page whose entire argument is about evidentiary standards has to meet its own.