A Menasha police officer wanted to know where his ex-girlfriend was. So he sat at home in Appleton, off duty, logged into his department’s account on a camera network, and searched for her cars. He did it more than once. In the box where the system asks why you are running the search, he typed that he was doing welfare checks.
He was convicted, and in August 2026 a judge sent him to jail for six months plus probation, declining to follow the lighter sentence the prosecutor and his own lawyer had jointly recommended. He was taken into custody in the courtroom. His attorney has since moved for bond pending appeal.
The technology he used is called Flock, and there is a good chance it is photographing your car several times a week.
This post is long because the subject deserves it. If you are reading it because you have been charged with something and a license plate reader is in your case, skip to what a defense lawyer actually does with this.
What a Flock camera actually is, and what it records
An automated license plate reader, or ALPR, is a camera plus software. It photographs every vehicle that passes, reads the plate, and writes a record: plate number, timestamp, location, and an image.
Flock Safety is the largest vendor selling these to American police departments and, increasingly, to homeowners associations, business parks and private communities. The cameras are small, solar-powered, and mounted on poles at intersections and neighborhood entrances. Most people do not notice them, and there is no requirement anywhere in Wisconsin that they be marked.
Three things about how the system works matter more than the cameras themselves.
It does not only read plates. The software builds what the industry calls a vehicle fingerprint: make, body type, color, roof rack, bumper sticker, dent, the ladder on top. That means a search can find a vehicle whose plate was never captured cleanly, and it means covering or changing a plate does not make a car invisible to the network.
One search hits the whole network, not one camera. This is the part that does the real work and the part people consistently underestimate. Agencies that buy Flock can generally opt into sharing with other agencies on the platform. A single query from a single terminal can run against cameras owned by hundreds of other departments across many states. In the Menasha case, the allegation was that the officer’s searches reached thousands of cameras covering large geographic areas, from his living room.
The records persist. Retention is set by policy and contract rather than by any Wisconsin statute we could locate. A common default is on the order of 30 days, but the number is a setting, not a law, and it can be changed by the people who own the setting.
Put those together and you get something that is not really a camera at all. It is a searchable, retrospective, nationwide map of where cars have been.
The part nobody mentions: not all of these cameras belong to the police
Flock does not only sell to police departments. It sells to homeowners associations, apartment complexes, business parks, self-storage facilities and private security firms. Those customers can, and frequently do, elect to share their camera feeds with local law enforcement.
This creates a legal wrinkle that matters enormously and gets almost no coverage. The Fourth Amendment restrains the government. It does not restrain your neighborhood association. When a private HOA camera photographs your car and the HOA hands the footage to police, the constitutional analysis is not the same as when the police camera photographs your car, and in many circumstances a search argument that would work against the second is unavailable against the first.
So one of the first questions in any case involving a plate-reader hit is a factual one, not a legal one: who owns that camera? A pole at a city intersection and a pole at the entrance to a private subdivision look identical from the road and are treated very differently in a suppression brief. The answer is in the contract and the camera registry, both of which are obtainable.
The Menasha case, and why the boring detail is the important one
The facts as described in the reporting and the criminal complaint: the officer used his department credentials while off duty, from his home in a different city, to run searches for vehicles belonging to his ex-girlfriend in October 2025. He told investigators afterward that desperation and poor judgment played a part and that he knew the searches were wrong.
Two details deserve more attention than they usually get.
He was caught because the system logs searches. Flock keeps an audit trail: who searched, when, for what, and what reason they typed. That audit trail is why there was a prosecutable case at all. It is also, as we will get to, the single most useful document in a defense file when ALPR evidence shows up in a criminal case.
He was not stopped because the system asked him to justify himself. The reason field is a free-text box. He typed “welfare” and the search ran. Nothing in the software required a supervisor to approve it, a case number to attach to it, or a judge to have signed anything. The control was a text box, and the text box did what text boxes do.
That is the structural problem in one sentence. The audit log is excellent at telling you afterward what happened. It does nothing at all to stop it while it is happening.
This is not one bad officer
If the Menasha case were isolated, it would be a personnel story. It is not. Reporting over the last several years has documented a consistent pattern of ALPR networks being queried for reasons that have nothing to do with the case the searching officer was assigned:
- officers running plates on former partners, current partners, and people they were personally interested in
- searches run on behalf of other agencies for immigration enforcement in states whose own laws restrict local police from assisting with it
- at least one widely reported instance of a search across a large multi-state camera network in connection with a woman who had ended a pregnancy
- audits in several states finding large numbers of queries with reason fields that were blank, generic, or plainly pretextual
We are describing these as press accounts, because that is what they are. They are not judicial findings, and this firm has not litigated them. What they establish is not that any particular officer broke a particular law. It is that the reason field is doing the work everywhere, and the reason field is a text box everywhere.
The public reaction has been real. City councils in a number of communities have voted down or cancelled Flock contracts after residents showed up to meetings with printouts of their own vehicles’ movements. Some agencies have withdrawn from the national sharing network while keeping their local cameras. Others have added warrant requirements by policy. None of that is Wisconsin law yet.
Is any of this constitutional? The honest answer
Here is where a lot of writing on this subject overpromises, so we will be careful.
There is no United States Supreme Court decision holding that ALPR network searches are a Fourth Amendment search. Anyone who tells you the law is settled in your favor is selling something. What exists is a line of cases that points in a direction, and in June 2026 that line got considerably longer.
Jones: the trespass case that does not help here
In United States v. Jones, 565 U.S. 400 (2012), federal agents attached a GPS tracker to a car and followed it for 28 days. The Court held that was a search. But read why: the majority rested on the fact that “the Government physically occupied private property for the purpose of obtaining information.” It was a trespass case.
That reasoning does not reach Flock. Nobody attaches anything to your car. The camera sits on a pole on a public road and photographs what is in plain view. If Jones were the only case, the government would win this argument easily.
Carpenter: the case that matters
Six years later the Court decided Carpenter v. United States, 585 U.S. 296 (2018). The government had obtained 12,898 cell-site location points covering Timothy Carpenter’s movements over 127 days, roughly 101 points per day, without a warrant. It argued that because the records belonged to the phone company rather than to Carpenter, the third-party doctrine applied and there was no search.
The Court disagreed, and the language is the reason this case matters to license plate readers. It held “that an individual maintains a legitimate expectation of privacy in the record of his physical movements,” and it refused to extend the third-party doctrine, drawing “a world of difference between the limited types of personal information” in earlier cases “and the exhaustive chronicle of location information casually collected” by modern systems.
Carpenter is about aggregation. Not any single data point, which is individually innocuous, but the picture that emerges when you have enough of them. One photograph of a car at an intersection tells you almost nothing. Ninety photographs over three months tells you where someone sleeps, works, worships, drinks, and who they spend Tuesday nights with.
Chatrie: the 2026 decision that closed two escape hatches
On June 29, 2026 the Supreme Court decided Chatrie v. United States, 609 U.S. ___ (2026), No. 25-112. Police investigating a credit union robbery in Midlothian, Virginia obtained a geofence warrant directing Google to hand over Location History data for every phone inside a 150-metre radius around the time of the robbery. The Court held that acquiring that data was a Fourth Amendment search, because a person has a reasonable expectation of privacy in cell-phone location information.
It is not an ALPR case, and it does not decide this question. But it closed the two doors the government usually walks through in a plate reader argument.
“It was only a short window.” The government argued that pulling a couple of hours of location data is too little to be a search. The Court rejected it, quoting Jones that even short-term monitoring can reveal “a wealth of detail about [a person’s] familial, political, professional, religious, and sexual associations,” and Kyllo for the proposition that where the Fourth Amendment applies, “it applies regardless of the quality or quantity of information the government obtains.” That matters here because the aggregation framing above, useful as it is, invites a response that a handful of reads is not enough. Chatrie says the threshold argument is not the whole game.
“You gave it to a company.” The government argued the third-party doctrine stripped any privacy interest because the data sat on Google’s servers. The Court refused, holding that Carpenter’s refusal to extend the doctrine to cell-site records applies “as well or better” to Location History. Plate reader data also lives on a vendor’s servers rather than in a squad car, and the same answer should follow.
The vote is worth knowing, because it tells you how durable this is. Justice Kagan wrote for the Court, joined by Chief Justice Roberts and Justices Sotomayor, Kavanaugh and Jackson. Justice Gorsuch concurred in the judgment. Justices Alito and Barrett dissented, with Justice Thomas joining part of Alito’s dissent. The judgment below was vacated and remanded.
Three different technologies people keep merging into one
These get conflated constantly, including by lawyers, and the differences decide cases. All three are location surveillance. They are governed differently.
Cell-site location information. Historical records held by your carrier showing which towers your phone connected to. That is Carpenter, and getting it is a search.
Geofence and stored location history. A demand to a company like Google for everyone who was in a defined area at a defined time. That is Chatrie, and that is a search too.
Cell-site simulators, the devices that impersonate a cell tower so nearby phones connect to them and reveal their location. Often called stingrays. The Supreme Court has never decided a case about them. Litigation over them has been in state courts and lower federal courts, and the results are not uniform.
None of those three is a plate reader. A plate reader photographs a car, not a phone, and no case in that line is about vehicles.
Which produces the asymmetry a Wisconsin reader should sit with. Under Wis. Stat. § 968.373, Wisconsin already forbids an officer from identifying or tracking the location of a “communications device,” meaning any wireless or mobile device, without first obtaining a warrant. The exceptions in sub. (8) are narrow: the subscriber consents, or there is an emergency involving danger of death or serious physical injury.
So in Wisconsin, tracking the phone in your pocket takes a warrant, by statute. Tracking the car that phone is riding in, across a network of thousands of cameras, takes nothing. Same person, same trip, same information about where you went, and two completely different legal regimes. That gap is not the product of a considered legislative choice about cars. It is the product of a statute written for phones and a technology that arrived afterward.
Where that leaves an ALPR argument
The defense argument writes itself, and it has not yet been definitively won or lost: a query across a national network of cameras, returning months of a specific vehicle’s movements, is closer to the exhaustive chronicle in Carpenter than to an officer standing on a corner writing down plates. Courts around the country are working through versions of this question right now, with mixed results, and Wisconsin appellate courts have not squarely resolved it.
What that means practically is that this is a live motion, not a lost one, and it is worth filing in the right case.
What Wisconsin law does and does not say
There is no Wisconsin statute we could find that governs ALPR retention, access, audit, or purpose limits. We looked. If one exists we will correct this page. What that absence means is that the rules constraining a Wisconsin department’s use of Flock are its own written policy and its contract with the vendor, and both of those are things a defense lawyer can demand and read.
Two Wisconsin statutes do give you real leverage.
The public records law. Wis. Stat. § 19.35(1)(a) says that “any requester has a right to inspect any record,” subject to exceptions. People call this FOIA out of habit; the federal Freedom of Information Act applies to federal agencies, and Wisconsin has its own, broader-in-some-respects law. It is the mechanism residents have been using around the country to find out how many cameras their city has, what the retention period is, how many searches were run last year, and what reasons were typed into the box.
Criminal discovery. Wis. Stat. § 971.23(1)(g) requires the district attorney, on demand, to disclose physical evidence intended to be offered at trial. And § 971.23(1)(h) requires disclosure of “any exculpatory evidence,” full stop. That second one is short, and it is the sentence that matters most in this area.
How this actually shows up in Wisconsin cases
Plate-reader data rarely arrives labeled as the centerpiece. It arrives quietly, inside a report, doing a specific job. Recognizing the job is how you know what to attack.
In an OWI case, it builds the timeline. The State wants to establish when you were driving, because the chemical test happened later and the defense of drinking after driving depends on the gap. A camera hit at 11:42 p.m. is offered to close that gap. What is worth checking: whether the timestamp is the camera’s clock or the server’s, whether the clock was synchronized, and whether the photograph actually shows a driver at all. A plate proves a car moved. It does not prove who was in it, and in a surprising number of cases that distinction is the case.
In a drug case, it builds a pattern of travel. Repeated trips to a particular address, or trips to a source city, get offered as evidence of distribution rather than possession. This is the use that most directly implicates the aggregation reasoning in Carpenter, because the evidentiary value comes entirely from the accumulation. A single trip proves nothing and everyone knows it; the State is relying on the chronicle.
In a domestic case, it establishes presence. Whether someone was at an address, in violation of a no-contact provision or during an alleged incident, is often contested and often uncorroborated. Camera data can settle it. It can also settle it in the accused person’s favor, which is why the exculpatory request matters here more than anywhere.
In a property crime, it is frequently the entire identification. Nobody saw a face. A vehicle matching a general description passed a camera near the scene within a time window, and the plate came back to your client. In that posture the identification is the case, and the confidence score, the raw image, and the list of other vehicles the system flagged are not side issues. They are the defense.
What a defense lawyer does with license plate evidence
This is the part of the post that is actually about your case.
1. Demand the audit trail, not just the hit
When the State says a Flock camera puts your car near a scene, the report you get in discovery is usually a summary: a plate, a time, a place, a photograph. That is the output. The audit trail is the input, and it answers questions the summary hides:
- Who ran the search? A named officer on this case, or someone else entirely whose results were passed along?
- When was it run? Before the investigation had a suspect, or after your name came up and someone went looking for corroboration?
- What reason was typed in? This is the Menasha field. If the stated reason does not match the case, that is impeachment material, and in the wrong circumstances it is the beginning of a suppression motion.
- How wide was the query? One agency’s cameras, or a multi-state network?
- Was there a warrant? Very often the answer is no, because nobody thought one was required.
2. Attack the identification, not just the legality
ALPR systems misread plates. Ones and sevens, Bs and 8s, dirty plates, angled plates, snow. The vehicle-fingerprint matching is probabilistic and returns similar vehicles, not identical ones. A dark grey SUV with a roof rack is not a fingerprint, it is a category.
Ask for the confidence score, the raw image rather than the cropped thumbnail, and the list of other candidate vehicles the system returned and the officer did not pursue. That last one is discoverable, and it is frequently where the case gets interesting.
3. Use it affirmatively, because it cuts both ways
This is the point most coverage misses entirely. The same network that can put your car near a scene can prove your car was eleven miles away at the time.
If Flock data is exculpatory, § 971.23(1)(h) requires the State to disclose it. The State does not always know it exists, because nobody ran that search. Ask early, because retention windows are short. A defense request made three months after the incident may be a request for data that no longer exists.
That timing point is the single most practical thing in this post. If a license plate reader might help you, the clock is measured in weeks.
4. Send a preservation demand before anything else
Retention periods are short and they run whether or not anyone has been charged. By the time a case is charged, a preliminary hearing is held, and discovery is exchanged, the window may have closed on data that would have helped.
A preservation demand should go out in writing, immediately, and should be specific enough that nobody can later claim they did not understand it. At minimum it should name:
- the vehicle, by plate and by description
- the date and time range, drawn wider than the incident itself
- the geographic area, including cameras the client’s own route would have passed
- the audit logs for any search already run on that plate, by any agency
- the raw images, not the processed or cropped versions
- the confidence scores and candidate lists for any match
Send it to the investigating agency and to the district attorney. Data that is routinely overwritten is not destroyed in bad faith, which is exactly why the demand has to arrive before the overwrite rather than after.
5. File the constitutional motion in the right case
Not every case. A single camera hit corroborating something you have already admitted is not the vehicle for a Carpenter argument. A months-long retrospective query across a national network, run without a warrant, producing the pattern-of-movement evidence that is the actual backbone of the State’s case, is a different matter. That is the fact pattern Carpenter was written about, even though it was written about phones.
What people are doing about it, and what you can do
Public records requests. Under § 19.35(1)(a) you can ask your municipality for its ALPR policy, its Flock contract, its retention period, the number of cameras, the number of searches run in a period, and the audit logs with personal identifiers redacted. Requests do not have to be on a form or in legal language. Put it in writing, be specific about the records you want, and keep a copy of what you sent and when.
Showing up. Camera contracts get renewed by city councils and village boards in public meetings, usually as consent-agenda items nobody reads. The communities that have changed course did it because residents appeared with specific questions about retention, sharing and audits.
Litigation. Civil suits challenging ALPR networks on Fourth Amendment grounds have been filed in several states. They are ongoing. We are not going to characterize their odds.
Asking your own department. Whether your agency shares into the national network, and whether it requires a case number for a search, are questions with answers, and the answers are public records.
The aggregation math, in plain numbers
It is worth sitting with the scale for a moment, because the constitutional argument depends on it and abstractions do not land.
In Carpenter the government had 12,898 location points across 127 days. The Court described that as an exhaustive chronicle, and it was: about 101 points a day, enough to reconstruct a life.
Now consider a driver in a mid-sized Wisconsin city with cameras at the main intersections. Commuting five days a week past four cameras, twice a day, is forty records a week without a single unusual trip. Over a 30-day retention window that is roughly 170 records. Over a year, if retention were extended to a year, it is more than two thousand.
None of those records is secret. Every one of them captured a car on a public road in plain view, which is exactly the government’s argument. The response is Carpenter’s: the question is not whether any single observation was private, but whether the compiled record is the kind of thing the Fourth Amendment was written to protect. A person who noticed a police officer standing at one intersection writing down plates would not think their privacy had been invaded. A person handed a printout of every intersection they crossed for a month would think something quite different, and the printout is the product on sale.
Who is suing, and what they have actually won
Most reporting on plate readers describes outrage. Less of it describes litigation, which is where the question gets answered. Here is the record, with the wins stated at their real size rather than the size the press release implies.
The ACLU’s campaign, and what it consists of
The ACLU runs a national campaign against ALPR deployment, “Get the Flock Out”, built on a decade of work that began with its 2013 report on plate reader tracking. Its recent national activity is advocacy and legislative rather than litigation:
- February 2026. Released model ALPR privacy legislation for states, setting retention, access and audit requirements.
- April 2026. Filed an amicus brief in a Fourth Circuit appeal arguing that ALPR networks give government unprecedented surveillance powers that upset traditional expectations of privacy.
- May 2026. Backed a bipartisan amendment to the federal highway funding bill that would have barred cities and states from using ALPR cameras except for tolling. It did not pass.
The lawsuits
Marin County, California, 2021, settled. The Electronic Frontier Foundation and three ACLU affiliates sued the Marin County Sheriff in October 2021 for sharing plate data with ICE, CBP and out-of-state agencies. In May 2022 the Sheriff settled and agreed to stop sharing plate and location data outside California. The settlement binds his successors. This is the clearest win on this list, and note what it is: a limit on sharing, not a ruling that the cameras are unconstitutional.
San Jose, California, filed November 2025. The ACLU and EFF sued over what they describe as warrantless ALPR mass surveillance. Filed, not decided.
ICE contracts FOIA, 2018. A Freedom of Information Act suit seeking records of ICE’s contracts with private ALPR vendors for immigration enforcement.
Norfolk, Virginia. The lawsuit that most directly asks our question, brought by two Norfolk residents against a city network of roughly 175 Flock camera clusters, arguing the dragnet is a warrantless search. A federal court ruled for the city in early 2026 and it is on appeal to the Fourth Circuit, which is the appeal the ACLU’s April 2026 brief supports. This paragraph describes press reporting on pending litigation, not a decided rule of law.
The suppression fights in criminal court, with the score kept honestly
The civil suits ask whether these systems should exist. The suppression motions ask the question that decides actual cases: does the evidence come in? That fight is happening now, and the record so far is worth reading closely, because it contains one win, two reversals of fortune, and a set of facts every driver should know.
The win: Bell. In Bell v. Commonwealth, 113 Va. Cir. 316 (Norfolk Cir. 2024), a Virginia trial judge held that “the collection and storage of license plate and location information by the FLOCK system” required a warrant, because the system “collects and records” a vehicle’s movements in a manner “akin to cellular telephones.” Suppression granted. For about a year, that was the leading defense authority in the country.
The reversal: Church. The same reasoning was then applied by the same circuit court to suppress statements in Commonwealth v. Church, and on October 14, 2025 the Court of Appeals of Virginia reversed, in an unpublished opinion. With 172 cameras and 30-day retention, the court held Norfolk’s system merely “augmented” visual surveillance of what was in plain view on a public road, relying on United States v. Knotts, and required no warrant.
The facts of Church deserve attention separately from the holding, because they show the timeline machine doing exactly what this post describes. Church told a detective what route he had driven. The detective ran the Flock system before the interview. No image showed Church’s vehicle at the intersection where he said he turned, and three images showed him traveling in a different direction. His own route statement became the impeachment. The system does not care whose story it contradicts, which is one more reason what you say to police before you have a lawyer matters as much as what any camera saw.
The confirmation: Robinson. On April 7, 2026 the same court decided Robinson v. Commonwealth as a published opinion, which makes it binding precedent in Virginia. A detective investigating a string of early-morning burglaries had a surveillance still of a white BMW SUV with black rims and no visible plate. He searched the Flock database by make and model alone, found the vehicle by its “distinctive black rims,” pulled the plate from the returned image, and identified the owner through the DMV. Suppression denied, affirmed. Read that sequence again: the identification began with no plate at all. That is the vehicle fingerprint working as designed, in a reported appellate opinion.
The federal data point: Jackson. In United States v. Jackson, No. 24-cr-10010-JWB (D. Kan. May 29, 2025), a federal judge denied suppression after a full evidentiary hearing on how Flock actually works, with testimony from officers and a Flock attorney. The order’s findings of fact are useful to either side: close to 100,000 Flock cameras deployed nationally, cameras photographing every passing rear plate around the clock, and all photos and data owned by the local agency or customer rather than by Flock.
The honest scoreboard. As of this writing, the only outright suppression win is Bell, a trial-level decision whose reasoning was rejected on appeal in its own jurisdiction. The appellate decisions to date have gone to the government. What keeps the question open is that those decisions predate or do not grapple with Chatrie, they concern one city’s 172-camera network rather than the national search function, and the parallel civil challenge is in a federal court of appeals now. A lawyer telling you ALPR evidence gets suppressed today is overpromising. A lawyer telling you the issue is settled against you is doing the same thing.
The California decision, stated accurately
The ACLU Foundation of Southern California and EFF did win a California Supreme Court decision about ALPR records, ACLU Foundation of Southern California v. Superior Court, S227106, decided 31 August 2017. It is frequently described as holding that plate reader data cannot be kept secret. That is not what it says, and the difference matters if you are relying on it.
The Court held that ALPR scan data are not within the California records act’s exemption for “records of investigations,” rejecting the trial court and Court of Appeal on that point. It then agreed that the public interest in withholding raw scan data clearly outweighed the interest in disclosure under the catchall exemption, and remanded to consider whether the data could reasonably be anonymised or redacted so that the balance would shift.
So: a real win on the categorical question, no raw data released, and an open question on anonymised data. We set it out this way because a Wisconsin lawyer citing the press-release version to a Wisconsin judge will be corrected, and should be.
Why the undecided cases matter as much as the decided ones
A decided case gives you a rule. A pending case gives you something almost as useful: a record of which arguments serious institutional litigants think are worth their money, and which ones the government is having to answer.
That is not an abstraction in a suppression posture. When you file a motion in an area with no controlling authority, the judge’s first question is whether anyone else is taking this seriously or whether you invented it last week. Being able to say that this exact question is pending in a federal court of appeals, that the ACLU filed a brief in it in April 2026, and that the Supreme Court decided a location-privacy case two months later that cuts against the government’s usual answers, is the difference between a novel argument and a frivolous one.
It also tells you where the law is heading, which matters for advice. A client deciding whether to take a plea today is making a bet about what the record will look like on appeal in eighteen months. Pending litigation is the best available information about that.
The honest caveat: pending means undecided, and some of these will lose. The Norfolk plaintiffs lost in the district court. We cite them because the argument is live and being pressed by capable counsel, not because we know how it ends.
What none of this is
None of it is Wisconsin law. No Wisconsin appellate court has decided whether ALPR network searches implicate Article I, Section 11 of the Wisconsin Constitution or the Fourth Amendment, and no Wisconsin statute regulates these systems. Everything above is persuasive at best. It tells you the arguments are live and being taken seriously by serious lawyers. It does not tell you how a Racine, Kenosha or Walworth County judge will rule, because nobody has asked one yet.
DeFlock, the camera cutters, and the right way to win this fight
The anger over these systems has a name now. DeFlock started as a mapping project and became a movement: deflock.me, built by a software developer named Will Freeman, crowdsources the location of every ALPR camera volunteers can find, the way earlier generations of drivers mapped speed traps. Flock sent Freeman a letter threatening legal action over the project. The Electronic Frontier Foundation took him on as a client and the company backed down. Mapping where cameras sit on public streets, photographing them, and organizing against them at city council is core First Amendment activity, and #DeFlock now travels well beyond the map.
Then there is the other thing happening, and we need to be direct about it.
People are going to jail over these cameras. Across the country, prosecutors are charging people who cut down, saw off, ram, or steal Flock cameras, and the reporting shows the same story on repeat: someone decides the surveillance tramples their civil liberties, takes a tool to a pole, and trades a policy grievance for a felony case. A 20-year-old West Virginia man was charged with two felonies over a cut-down camera, and roughly twenty thousand strangers flooded social media with joke alibis on his behalf. An 18-year-old in Florida faces felony charges over several sawed-down cameras. A New Mexico man faces nine felony counts. In one Ohio county, felony charges over a destroyed camera were later dismissed, which is worth noticing, and which still cost that man an arrest, a mugshot, and months inside a criminal case. Those are press accounts of pending or resolved charges, not judicial findings, and we cite them for the pattern rather than for any individual’s guilt.
That volume of cases is itself the story. When ordinary people with no record start risking prison to take down government cameras, the technology has hit a boiling point that policy has not caught up with. The anger is data. It is also, legally speaking, a terrible plan.
What it costs in Wisconsin, specifically. Intentionally damaging someone else’s property is criminal damage under Wis. Stat. § 943.01, a Class A misdemeanor carrying up to 9 months in jail and a $10,000 fine under § 939.51(3)(a). If the damage exceeds $2,500, measured by repair or replacement cost, whichever is less, it becomes a Class I felony under § 943.01(2)(d), which carries up to 3 years and 6 months and a $10,000 fine under § 939.50(3)(i). A mounted camera system with its pole, solar panel and installation makes the $2,500 fight a real one, and walking away with the hardware adds theft exposure under § 943.20 on top. A felony record for a camera the city can reinstall in an afternoon.
And notice the bitter mechanics: the network photographs the vehicle that drove to the pole. More than one camera cutter has been identified by the very system he was cutting down. You do not beat a surveillance network by handing it its most compelling use case.
The record shows the fight is winnable without a hacksaw. Everything else on this page is the proof. More than fifty localities have walked away from Flock contracts in a year. El Cerrito voted its contract dead and saved $315,000. Louisville deactivated its cameras. Two San Diego council members moved against renewal within a day of organized testimony. A Norfolk trial judge suppressed Flock evidence, the civil challenge is in a federal appeals court, and the Supreme Court just spent June closing off the government’s two favorite arguments. Council votes, records requests, lawsuits, and suppression motions are slower than a saw. They are also how this actually ends, and nobody doing them goes to jail.
If you are reading this because you already took the faster route and are now charged under § 943.01 or anything like it, that is not a lecture moment, it is a defense case, and the valuation line between the misdemeanor and the felony is exactly the kind of fight we have. Call us.
What good policy would look like, since Wisconsin has none
We are a defense firm, not a policy shop, but the gaps here are specific enough to name, and every one of them is something a city council can put into a contract without waiting for the Legislature:
- A case number requirement. No search runs without an open case attached to it. This alone would have stopped the Menasha searches at the keyboard.
- Structured reasons instead of free text. A dropdown that an auditor can count, not a box that accepts the word “welfare.”
- Supervisor approval for network-wide queries. A search of one city’s cameras and a search of a multi-state network are different acts and should not carry the same friction.
- Published audit statistics. Number of searches, number flagged, number referred for discipline, published quarterly. Several vendors already support this; it is a setting.
- A stated retention period the public can find, and a prohibition on extending it retroactively.
- Disclosure of sharing partners. Residents are entitled to know which other agencies can query cameras their taxes paid for.
None of that requires believing the technology is bad. It requires believing that a system which logs everything and prevents nothing is only half built.
Image credits
Eight photographs, each taken by someone who documented a plate reader where they live and released it under an open licence. None shows Wisconsin equipment, and none relates to any matter this firm has handled. Follow the links; the credit is the only thing we can give back for work we did not pay for.
- MiracleMiles and Tony Webster, licensed CC BY 4.0.
- Bruxton, LemononoM, MeridioOceano and Epicdeflocker64, released into the public domain under CC0 1.0.
- Dugan Meyer, the reader concealed in a traffic barrel, licensed CC BY 4.0. Cropped and resized, not otherwise altered.
The five diagrams are our own: what the system records, the aggregation figures in Carpenter, the summary report against the audit trail, the retention clock, and the public records request. The “Reason for search” field is also ours, a reconstruction of the justification box described in reporting on the Menasha case rather than a screenshot of the vendor’s software. Reuse any of them with attribution if they are useful to you.
Keep reading
- Can the Police Legally Lie to You in Wisconsin? Yes. What That Means Inside an Interview Room. The Menasha case ended with statements to investigators. The rules for that room are not what most people assume.
- Arrested but Not Charged: The Benefit of the Doubt, and Who Actually Gets It. The window between arrest and charging is where the preservation demand on this page actually gets sent.
- Can You Refuse the New Roadside Saliva Test in Racine? What Every Driver Needs to Know. The other new enforcement technology on Wisconsin roads, and what refusing it does and does not cost you.
Why we wrote this
We defend people in Racine, Kenosha and Walworth Counties. Over the last two years, license plate reader data has gone from something we saw occasionally to something we expect. It shows up in OWI cases to establish a timeline, in drug cases to establish a pattern of travel, in domestic cases to establish presence, and in property crime cases as the entire identification.
Most of the time it is used exactly as intended. The Menasha case is a reminder that a system with thousands of cameras, a national search function and a free-text justification box will occasionally be used for something else, and that the only reason anyone found out was a log file.
If you are facing a charge and there is camera evidence in it, contact Cafferty, Scheidegger & Johnson for a free, confidential consultation, or call (262) 632-5000. We answer 24/7. If the charge is a traffic citation, that is racineticket.com; if it is impaired driving, that is racineowi.com.
General information about Wisconsin law, not legal advice, and reading it does not create an attorney-client relationship. Every case turns on its own facts. The Menasha case is described from published reporting and the criminal complaint that reporting quotes; that defendant has a post-conviction motion pending. Statutes change; confirm current text at docs.legis.wisconsin.gov.