Flock Cameras in Tampa Bay: Where They Are, the Misuse Arrests, and What the Law Actually Says

On the night of the St. Petersburg mayoral primary in August 2026, the two candidates headed to the November runoff were arguing about a camera. Charlie Crist said he would support a moratorium on the city’s Flock cameras until, in his words, “we really understand comprehensively what they’re used for.” Mayor Ken Welch defended them and pointed to the city’s privacy protections. On August 27 the City Council voted unanimously to send the city’s Flock contract to its Public Services and Infrastructure Committee for review. That referral, and what it can and cannot fix, is covered below.

The argument did not come from nowhere. Over roughly five weeks this summer, three Florida law enforcement officers were criminally charged over the misuse of these systems, one agency’s cameras were suspended entirely, and the company that runs the network announced it would tighten its own rules. Every one of those cases was built on the same thing: the system’s own search log.

This page is the full picture for Tampa Bay. What the cameras are, where they are, what happened this summer, what Florida law actually says, and what it means if a plate reader is anywhere in your case.

What a Flock Camera Is

Flock Safety is a private company that sells automated license plate readers, usually a small camera on a pole at an intersection, a neighborhood entrance, or a parking lot. Each camera photographs every vehicle that passes and logs the plate number, the date, the time, the location, and a description of the vehicle, including make, color, and identifying details like racks or bumper stickers.

Those captures flow into a searchable database. A participating agency can set alerts for wanted plates, and an officer with access can search a plate and see everywhere the network has recorded it. Agencies commonly share access with each other, and private owners like homeowner associations and retailers can share their cameras’ data with police.

Two features define the system. It records everyone, not just suspects. And it remembers, which means a search does not just show where a car is. It shows where a car has been.

Where They Are in Tampa Bay

St. Petersburg has installed 50 Flock cameras under the current administration, and Florida Politics has reported the city spent $730,250 on them. Pinellas County commissioners asked Sheriff Bob Gualtieri for a presentation on the technology at their July 21 meeting. Tampa police use Flock along with the company’s audit tool, and agencies across Hillsborough, Pinellas, and Pasco counties participate in the network. Beyond law enforcement, the cameras sit at big-box parking lots and neighborhood entrances across the region, installed by the property owners themselves.

Nobody publishes an official public map, but crowd-sourced projects like DeFlock and the EFF’s Atlas of Surveillance track reported locations, and local coverage of the buildout has accelerated as the cameras multiplied. The honest summary is that if you drive in Tampa Bay, your plate is being recorded, and the record is searchable by people you have never met.

What Florida Law Says About the Cameras Themselves

As of this writing, Florida’s plate reader statutes cover less ground than their titles suggest. Sections 316.0777 and 316.0778 are written for automated license plate recognition systems, and they do real work. They require a retention schedule with a maximum period, so the data cannot be kept indefinitely. They make the images and the data confidential and exempt from public records. They let you request the information tied to your own tag, unless it is part of an active investigation. And they say a plate reader may not be used to issue a traffic citation. What those sections do not do is say who inside an agency may run a search, require anyone to audit the searches that get run, or attach a penalty when someone abuses the system. They also govern cameras placed in the state highway right of way, which leaves the camera at a private apartment gate or a retail lot outside them. So a great deal still comes down to each agency’s own policy and the vendor’s terms of service, which is why Flock could announce by press release that default retention is dropping from thirty days to seven and that searches will require a case number by the end of the year. When the rules live in a company’s settings panel, the company can change them, in either direction, without anyone’s vote.

The constitutional question is larger and unsettled. In Carpenter v. United States, 585 U.S. 296 (2018), the Supreme Court held that accessing historical cell site location records is a Fourth Amendment search, because people have a reasonable expectation of privacy in the whole of their physical movements. And on June 29, 2026, the Court extended that in Chatrie v. United States, 609 U.S. ___ (2026), holding that police acquisition of Google Location History is a search. The Court’s reasoning described location databases as enabling retrospective surveillance that runs against everyone, not just people under investigation, and that travels back in time.

Every word of that description fits a license plate reader network. A plate is not a phone, and courts have not yet settled how far Carpenter and Chatrie reach into ALPR databases, but the direction of the law is plain: the Supreme Court keeps holding that assembling a detailed retrospective record of a person’s movements is a search. The fight over whether that covers fifty cameras logging every car in St. Petersburg is coming, and cases in this region could be where it happens.

The Public Records Fight, and the One Request You Can Actually Make

A man in Oregon has collected more than $300,000 from local governments in Washington State, and the way he did it explains something important about how this data is stored.

Between September 2024 and October 2025, Jose Rodriguez filed 53 public records requests with Washington cities and counties. He was not asking for anything sweeping. Each request sought the images and data logs from that jurisdiction’s plate reader cameras during a single 30 minute window on a single day.

Many of the agencies could not produce them. According to reporting by Cascadia Daily News, the obstacle was the architecture: the records sat on the vendor’s cloud, subject to a rolling 30 day deletion and a 100 image download limit, so an agency that moved slowly found the responsive records were simply gone. Fifteen local governments have settled with Rodriguez, in amounts ranging from $5,000 to $40,000, for more than $300,000 in total. Sedro-Woolley and Stanwood each paid $40,000. In November a Skagit County judge, Elizabeth Neidzwski, ruled that the images are subject to Washington’s Public Records Act and are not exempt from disclosure.

The consequence was not only financial. At least 13 of the 53 jurisdictions that received one of his requests have since canceled their camera contracts or switched the cameras off. Then, at the end of March 2026, Washington’s governor signed a law exempting plate reader images and data from that state’s public records act, which removes the basis for the kind of request Rodriguez had been filing.

None of That Would Work in Florida

Florida reached the same destination years earlier and by a different route. Under section 316.0777(3), images and data containing personal identifying information obtained through a plate reader system, and the personal identifying information within them, are confidential and exempt from section 119.07(1) and from Article I, section 24(a) of the Florida Constitution. A blanket request of the kind Rodriguez filed does not get you anywhere here, because the exemption is already written into the statute.

But the same statute gives a Florida driver something Washington’s new blanket exemption does not obviously give. Section 316.0777(4)(b) says that information relating to a license plate registered to an individual may be disclosed to that individual.

It is narrow, and it is real. You cannot ask what the cameras recorded about the neighborhood. You can ask what they recorded about your own tag.

There is one carve out in the same sentence, and it matters: the disclosure does not apply where the information is active criminal intelligence information or active criminal investigative information. So a person under active investigation is exactly the person who will not receive it that way. In a case, the route to those records runs through discovery instead, which is the section below.

The other half of the Washington story travels intact, though. Section 316.0777(2)(d) says the records may not be retained longer than the maximum period in the retention schedule established under section 316.0778. There is a ceiling, and it means the same thing here that it meant there: this evidence has a shelf life, and the clock is already running on the day of the stop. Fifteen Washington governments wrote settlement checks in part because the records disappeared while everyone was still arguing about whether they had to hand them over.

The Misuse Record, Case by Case

The sections that follow are the documented misuse cases, in the order they came to light, starting with the five weeks in Florida that made this page necessary. Each one ends the same way: the search log, not the camera, is what told the story.

The Three Florida Cases, in Five Weeks

Sumter County, July 23. An arrest warrant issued for a sheriff’s detective accused of using the Flock system, the DAVID driver database, and a court records system to monitor her husband’s ex-wife, allegedly creating false electronic records to make the searches look like legitimate investigations. She was charged with official misconduct and offenses against computer users. The sheriff then suspended the agency’s use of Flock cameras outright and ordered a complete audit of all database activity.

Sarasota, August. A Sarasota police officer was fired and arrested over alleged misuse of the Flock and DAVID databases. The detail that should stop every reader: by the department’s own account, it learned about the problem from a USA Today reporter rather than from its own auditing. An agency-wide audit followed.

Haines City, August. A police officer was charged with offenses against users of computers and official misconduct after investigators alleged he searched the Flock system for his estranged wife’s vehicle 717 times between September 2024 and June 2026. According to the reporting, the justifications entered for the searches included criminal motor vehicle offenses, drugs and narcotics, and assault and battery, while the vehicle was not part of any investigation and appeared in no crime database.

Three agencies, three officers, the same pattern, and in every instance the proof was the system’s own log: who searched, what they searched, when, and the reason they typed into the box.

Florida is not an outlier. The Washington Post reported in August that at least 50 law enforcement officers around the country have been charged with or accused of misusing Flock’s network and related systems, frequently to look up exes and romantic interests. The company itself has acknowledged the problem by tightening its own rules, which is covered below.

The Two Charges, and Why the Reason Field Is the Whole Case

Two Florida felonies are doing the work in these prosecutions, and both turn on the search log rather than the camera. The officers charged this summer face versions of the same pair, and understanding them explains what that log actually is.

Offenses against computer users, section 815.06. The statute makes it a third degree felony to access a computer system willfully and knowingly “without authorization or exceeding authorization.” The words that matter are the last two. These officers had valid logins. The theory of the charge is that a real password used for a personal purpose exceeds the authorization that came with it. The statute contains an exemption for someone acting within the scope of lawful employment, which is precisely what a personal search is not.

Official misconduct, section 838.022. This one makes it a third degree felony for a public servant to knowingly and intentionally obtain a benefit or cause unlawful harm by falsifying an official record. Read that against the allegation that an officer typed “Drugs/Narcotics” as the reason for searching a spouse’s plate. The charge treats the reason field itself as an official record, which means the little dropdown justification an officer selects is not decoration. It is a record whose falsification Florida treats as a felony.

That is worth sitting with, because it cuts both ways. It is what makes the misuse chargeable, and it is what makes every search in the system reviewable evidence.

A Fourth Florida Case, and the Citation That Came With It

A Brevard County deputy who had just been named his agency’s Deputy of the Year resigned after investigators audited the plate reader logs and found he had looked up his ex-girlfriend’s tag. He is the fourth Florida case on this page. News 6 reported on August 20, 2026 that the deputy, Michael Fultz, hired in 2024 and named Deputy of the Year in 2025, resigned in May after a 43 page internal investigation. 404 Media obtained the file and published it on August 27. The reason he entered in the system was “investigation.” He denied using it to spy on her and said he may have been showing her how it worked. The reporting also documents conduct well outside the scope of this post, including a photograph in which News 6 says he appears to perform a Nazi salute, and images investigators obtained involving his service weapon. Investigators concluded termination was warranted, and he was permitted to resign instead. He apologized for poor decisions and said he disagreed with parts of the report.

Two things in that file matter here. The first is the reason field again, for the fourth time in five weeks. A free text box is still the only thing standing between a search and an audit, and “investigation” is still enough to fill it.

The second is a traffic stop, and a defense lawyer should not skip it. News 6 reported that a Florida Highway Patrol trooper clocked him on his motorcycle at 111 miles per hour on US 192 near Melbourne, and issued a civil citation for six to nine miles per hour over the limit. There was no arrest. Since July 1, 2025, Florida has had a criminal statute for exactly this range of conduct. Section 316.1922 makes dangerous excessive speeding a crime where a driver exceeds the limit by 50 miles per hour or more, or reaches 100 miles per hour or more in a manner that threatens the safety of other persons or property, and a first conviction carries up to 30 days in jail, a $500 fine, or both. Whether that stop met those elements depends on the posted limit at that location and on the manner of riding, and neither is established in the public reporting. What is established is the gap between the number on the radar and the number on the ticket.

An Officer Explains the Reason Field, in His Own Words

A Georgia officer ran 56 plate reader searches on a former partner, and then had to explain what he had typed in the reason box. Everything else on this page about that box is an inference drawn from the shape of the tool: free text, no audit behind it, and nothing stopping an officer from typing whatever clears the screen. WIRED obtained an internal police investigation through a public records request on August 27, 2026 that removes the inference. He was asked why he filled the box in the way he did, and he answered.

According to the internal report, written by Sergeant Jabbar Braithwaite of the Alpharetta Police Department in suburban Atlanta, patrolman Dustin Bozzo ran 56 Flock searches between March and May on the license plate of a former romantic partner who was then a fellow officer at the same department. He ran 18 more on her uncle’s vehicle, which she was borrowing after a crash, between April 5 and April 14. When a third officer’s car kept appearing near hers in the results, he ran that plate 29 times. That is 103 searches across three vehicles in roughly two months.

Citing the Flock audit logs, the report says Bozzo “almost always selected either ‘Wanted Person’ or ‘Traffic Infraction'” as his reason. Asked why, he told investigators that doing so was “just a quick keystroke.”

The rest of the file is worth reading for what it does not find. Bozzo said he was checking that she had arrived home safely and denied any intent to intimidate or cause harm, and Braithwaite wrote that he found no evidence undermining that claim. The conclusion did not turn on it. Braithwaite told him that “regardless of his stated motivation,” the use was “inconsistent with Department policy and the authorized use of the system.” Bozzo was placed on paid leave on July 20 and resigned on August 5. Lieutenant Jason Hiott told WIRED that a criminal investigation remains open with the department’s Criminal Investigations Division. WIRED counts at least 45 documented incidents nationally of officers misusing these systems to look up or track current or former romantic partners.

For a Florida case, the operative fact is the one that made the story possible. Every one of those 103 searches wrote a row to a log carrying the user, the timestamp, and the reason selected. That log is how a department reconstructed two months of conduct after the fact, and it is the same record described in the records demand below. A reason field that an officer can clear with a quick keystroke is weak protection against misuse and strong evidence about how a search was actually justified. Those two things are not in tension. They are the same fact seen from opposite ends.

An Audit Caught One Before a Reporter Did

On August 26, 2026, CNN reported the arrest of a Shively, Kentucky officer who investigators say ran 2,048 Flock searches on two vehicles registered to the mother of his child, from January into May, across Kentucky and Indiana. He typed that the searches were part of a drug investigation. Officials said she was never the subject of one and that nothing in her history suggests she ever had been. Of those searches, 241 happened while a court order of protection was in force, between April 17 and May 6. He is charged with five counts of official misconduct and five counts of unlawful access to a computer, he is suspended without pay, and he has not yet been arraigned. None of it has been proven.

By now the conduct is familiar from the three Florida cases above. What found it is the new part. Flock’s own auditing software flagged the search pattern on a Monday, and he was in custody by Tuesday. No journalist filed a records request first, and no supervisor caught it. The company has begun requiring departments to run that tool.

That changes what exists to ask for. Every search in one of these systems already generated a record carrying the user’s name, the time, and the reason typed into the box. An audit layer running on top of those records produces output of its own: what it flagged, when it flagged it, and what the agency did next. Where a plate reader touched a case, that material belongs in the same records demand described in the next section.

The Institute for Justice, which has sued over these camera networks on Fourth Amendment grounds, has counted at least 47 instances of officers disciplined for using them on romantic interests. Its researcher told CNN there are many reasons to think that figure is only the tip of the iceberg, because a great deal of it has never been reported or detected.

An Audit Found 2,055 Searches of One Plate

On August 31, 2026, the Jackson County, Indiana prosecutor charged a former sheriff’s deputy, Skylar Thompson, over his use of the county’s plate reader system. The number in the filing is 2,055. That is how many searches of a single license plate he is alleged to have run between December 31, 2025 and August 2, 2026.

Each of those searches asked him to type a reason. According to the charges he entered “City Planning/Traffic Analysis” every time, and he had never been assigned duties involving city planning or traffic pattern analysis.

Nobody reported him. The sheriff’s office found the pattern during a routine internal audit of its own camera system, and referred the matter to the Indiana State Police for an independent investigation. The prosecutor’s office stated the principle this way: “Law enforcement officers are entrusted with access to sensitive information and investigative tools, and that access must be used responsibly and only for legitimate law enforcement purposes.”

The charges and the headlines do not match. Several outlets have described this as a stalking case, and one station’s headline says he was charged with stalking while its own article lists something else. The counts actually filed are official misconduct, a Level 6 felony, and fraud, a Class A misdemeanor. Stalking is not among them. He is charged and not convicted, and the reporting does not identify whose plate it was.

Set this beside the Kentucky audit above and the shape repeats. These cases do not surface because someone noticed a patrol car in a rear-view mirror. They surface because the system keeps a log of who searched what and why, and because somebody read it. The reason field is doing the same work here that it did there: the second charge is about what he typed to justify the searches.

The number is the argument. Two thousand and fifty five searches sat inside one county’s system for seven months, and an audit is what produced them. In an ordinary case where a plate reader put an officer behind a car, that same log exists, and it is almost never requested. What to ask for is in the records section below.

A Search That Crossed Every State Line, and the Record Beside It

One Texas sheriff’s office searched plate reader cameras across the entire country looking for a single woman. The other cases on this page are local, an officer or a department or a county at a time. This is that same mechanism at national scale, and it is the clearest illustration here of why the network matters as much as the camera.

404 Media reported, revisiting its own May 2025 work, that the Johnson County, Texas Sheriff’s Office searched Flock nationwide for a woman who had self-administered an abortion. The search reached into states where abortion is legal, and it ran more than two weeks after the abortion itself. Sheriff Adam King told 404 Media the reason was a welfare concern: the “family was worried that she was going to bleed to death, and we were trying to find her to get her to a hospital.”

The Electronic Frontier Foundation obtained court records from the underlying case. An arrest affidavit, filed against the woman’s partner over alleged threats at gunpoint, records that “it was discussed at the time with the District Attorney’s Office and learned the State could not statutorily charge [the woman] for taking the pill to cause the abortion or miscarriage.” Police documents categorized the work as a “death investigation.”

This post does not tell you what anyone was thinking, and it takes no position on abortion. Both would be beside the point. What the documents allow is narrower and more useful: the stated reason for a search and the contemporaneous record of what the office was doing can be laid side by side and compared. In this instance the stated reason was a welfare check, the search ran nationwide more than two weeks later, and a prosecutor was being consulted about charges in the same period. Whether those facts sit comfortably together is a question a reader can answer without any help from a lawyer.

The transferable point for a Florida case is the reach. These systems are national by default. Departments can open their records to agencies elsewhere, which means a camera bought by one municipality becomes searchable by investigators in another state, under that agency’s policies rather than this one’s. Florida’s plate reader statutes govern retention and confidentiality for cameras here. They do not follow a Florida plate into a database queried from somewhere else, and they say nothing about what reason a distant agency has to type before it runs the search. When a plate reader appears in a case, the questions in the records demand below are not only who searched and why, but which agency, on whose network, and under which rules.

What the Intelligence Bulletins Say, and Why That Reaches a Traffic Stop

Police intelligence centers have been circulating bulletins about the people who object to these cameras. The rest of this page concerns the cameras themselves. This part concerns the paperwork moving among police about the public near them, and it is the piece of the story that touches a Florida case most directly.

404 Media reported on August 12, 2026, working from intelligence bulletins obtained through public records requests, that fusion centers have been briefing law enforcement about opposition to plate reader cameras. Fusion centers are information-sharing partnerships between local, state, and federal agencies, and the documents are intelligence bulletins, many marked “Law Enforcement Sensitive.” The reporting builds on earlier bulletins published by investigative journalist Dan Boguslaw. Documents came from the Central Florida Intelligence Exchange and the North Florida Fusion eXchange among others, and one Wisconsin bulletin circulated through the Northeast Florida Fusion Center.

The Florida detail matters. A July 28 bulletin from the North Florida Fusion eXchange names eleven Florida cities that signed up for a scheduled week of public meetings, townhalls, and marches about plate reader surveillance. The same bulletin lists seven instances of cameras being damaged or removed in Florida, and instructs law enforcement to “remain vigilant when observing or responding to suspicious activity near ALPR sites.” Other bulletins tell police to “increase patrols around ALPR.” A Wisconsin bulletin distributed through a Florida fusion center describes “extensive and ongoing chatter on social media platforms such as Facebook and TikTok regarding various methods to interfere with or physically destroy Flock LPR cameras.”

The founder of the camera-mapping project named in those bulletins told 404 Media that the project “has never called for disabling cameras or covering license plates, contrary to what recent law enforcement bulletins claim,” that more than 100 contracts have been canceled through ordinary public engagement, and that some accounts using the project’s name are not affiliated with it. A Flock spokesperson said the company condemns damaging equipment, that it has seen few reports of vandalism, and that “people have every right to make their voices heard.”

Here is the legal significance, and it is not abstract. An intelligence bulletin is not evidence of anything. It is a forecast, assembled from open sources, of what an agency believes may happen. The same Colorado bulletin that warns about camera vandalism also records a neo-Nazi group’s recruitment drive to sabotage cameras that then “lost traction,” and 404 notes there is no indication in the document that the group ever acted. A document that records a threat which never materialized is a useful reminder of what these products are.

But a bulletin has an effect on the law even though it is not evidence. Whether a stop was lawful is measured by what the officer reasonably suspected at the moment of the stop, judged on the facts known to that officer. When a briefing has told officers to watch for suspicious activity near camera installations, and has framed lawful political organizing and criminal vandalism in the same document, that briefing becomes part of what the officer knew. Where a stop happens near a camera site, the existence, content, and distribution of any such bulletin is a discoverable fact and a fair subject for a suppression hearing. The same bulletin notes that on June 25, 2026, University of South Florida Police located a device during a traffic stop that could be used to identify camera locations. This post takes no position on that matter and predicts nothing about it. The point is the order of the questions: what justified the stop, what the officer knew before it, and where that knowledge came from.

The Company’s Side of the Ledger

The cases above are about officers. This group is about the vendor: what Flock is building on top of the cameras, how it coaches its customers, what happened to one officer who objected, and what it changed in August 2026 when the pressure arrived.

The Camera the Hackers Took Apart

On September 16, 2026, 404 Media and WIRED published a joint investigation built on a Flock camera that a hacker collective had removed from above a roadway, copied, and handed to reporters through the transparency group Distributed Denial of Secrets. This was a physical removal of one device and a copy of what was stored on it, and the reporting says so; it was not a breach of Flock’s network, and nobody was tracking anyone with it. Flock’s statement was that removing and tampering with a camera is illegal and that it had not been given enough detail to assess the claims. Taking a camera down is a crime, and a former Rhode Island officer who was investigated after objecting to the cameras told the reporters that sabotage will only convince police the tool is necessary.

What the copy showed is the part that matters for a case. A typical passing vehicle triggered about 28 photographs, and some triggered more than 100. Across about 21 days of recovered logs, the one camera photographed roughly 50,200 vehicles and generated about 1.6 million images, around 3,300 vehicles on a typical day. The software on the device explicitly detects people, along with vehicles, plates, and bicycles, and logs where the person is in the frame and how confident the detection is. The reporters found no face recognition in use. The camera does not read the plate itself or identify the make, model, and color; it selects and crops frames and sends them over a cellular connection to Flock’s servers, where those determinations are made. And the plate detector was broad in what it treated as a plate: it cropped bumper stickers, dealership frames, and in one clip an American flag patch on a motorcycle rider’s saddlebag. Flock had described the cameras as protected by on-device encryption; the key that unlocked the stored video was found on an unencrypted section of the same device.

For anyone whose stop began with a plate reader alert, this adds detail to the discovery requests above. The hit in the report is a server’s reading of a few cropped frames chosen from dozens, produced by a detector that will crop a sticker. The frames themselves, the confidence attached to the read, and what the officer did to verify the alert before the stop are the records that show whether the read was right, and a misread is a stop with nothing under it. The same week, an Electronic Frontier Foundation analysis of Flock audit logs found officers across dozens of departments entering “LMAO,” “idk,” “hehe,” and keyboard mashing as the reason for nationwide searches, which is one more reason the reason field in your case is worth reading.

The AI Layer Flock Is Building on Top

In August 2026, WIRED reconstructed the code of a new Flock product called OS Investigate, an AI tool for police that the reporting describes as able to identify drivers and track vehicles by their patterns of movement alone. The files came from Flock itself: more than 450 of them, served publicly by the company’s own login pages.

The code WIRED examined ships with 69 prewritten prompts an officer can select and submit. Nineteen of them hunt for patterns rather than looking up a record, and fourteen call for no plate, no name, and no description at all. One preloaded prompt finds potential witnesses by listing the vehicles most seen in a chosen neighborhood. Another flags cars that visited multiple gas stations between midnight and 5 am. Another takes a single plate and returns the car’s “associates,” ranked by how often other vehicles pass the same cameras within a two-minute window. The tools behind those prompts reach arrest records, dispatch logs, case files, and commercial databases holding dates of birth, phone numbers, and relatives.

The detail that matters most for the reason-field analysis above: WIRED found that the justification box in the new tool accepts whatever an officer types, and that where a department requires a case number, the form checks only that the entry is at least three characters long. Florida treats the reason field as an official record, so the looser the field, the more the audit trail becomes the whole story. Flock, for its part, told WIRED the product is still in development and being tested with a small group of agencies, and it did not dispute the capabilities described. For years the company’s public position was that its cameras “cannot recognize, identify, or track individuals.”

Days before the WIRED story ran, Flock announced its own set of guardrails: a seven day default retention period for plate data on new customer accounts, a requirement that searches carry a criminal case number, and automatic lockouts for abnormal search activity. The seven day default applies to new customers, and agencies already on the platform keep their existing retention settings unless they opt in, so what your local department retains still depends on your local department. The announcement is linked in the reading list below.

The backlash has turned municipal. Since the start of 2026, city councils in more than twenty states have voted to cancel, decline, or switch off Flock contracts, and Fort Collins, Colorado removed all fifteen of its cameras in July. The most consequential departure is Los Angeles: an internal audit presented to the Los Angeles Police Commission in 2026 documented 161 false stolen-vehicle alerts in a two month window, a false positive rate of 32.3 percent, and the department moved away from the platform afterward. For anyone whose stop began with a plate reader alert, that number is not trivia. An alert is only as good as the hotlist and the read behind it, and a documented one-in-three error rate in a major department is exactly the kind of record a defense lawyer asks for.

For anyone facing a charge in which a plate reader appears, the update changes the discovery questions. If a pattern search rather than a plate hit is what put a vehicle in the case, then the prompt the officer ran, the reason typed into that box, and the audit log behind the search are all records a defense lawyer can demand and examine.

The Vendor’s Coaching Guide for Police, and Why It Reads Like a Document Index

404 Media obtained a Flock coaching guide for police in August 2026, a PDF on how to speak to city councils about public safety technology, paired with a company webinar titled “How to Speak to City Councils: Meeting the Moment with Confidence.” A local activist provided the document and 404 kept them anonymous. Flock did not immediately respond to a request for comment.

The guide’s advice, as quoted in that reporting, is candid. On the question of whether plate readers amount to mass surveillance, it tells agencies not to fight the label at all. The stated reasoning is that opponents will never be talked out of the term, so a meeting should not be spent trying. Pivot to governance instead, and show that the system can be audited, reviewed, and held accountable. On money, it suggests reframing the financial discussion toward the cost of unresolved crime rather than the price of the cameras. On timing, it is more specific still. Brief city managers early. Meet council members before votes occur. Share policies proactively, so that a public comment period is not the first introduction to the program. The phrase the coverage led with was “own the narrative before someone else does.”

The guide holds up two cities as successes. In Oakland, California, which it calls one of the most scrutinized public safety technology debates in the state, more than 140 public comments and opposition from the city’s Privacy Advisory Commission did not stop approval. The guide’s explanation is that the conversation shifted when officials stopped asking the public to trust the technology and started showing how it could be audited and reviewed. In Richmond, California, the contract lapsed after the city’s cameras appeared in the company’s national lookup tool and officials worried about federal immigration access under state and local sanctuary law. Department leadership then presented two and a half years of local results, which the guide puts at 274 arrests and 259 vehicle recoveries, and the council voted 4 to 3 to reinstate the system. Sarah T. Hamid of the Electronic Frontier Foundation described the underlying asymmetry to 404: the vendor controls the facts, and city staff are rarely positioned to challenge them.

Read as a resident, that document is cynical. Read as a defense lawyer, it is more useful than that, because a sales script is a set of concessions about what exists.

An agency cannot promise a council that a program is auditable unless there is an audit trail. It cannot offer to share policies proactively unless a written policy exists. And a department that stood up in Richmond and gave a council 274 arrests and 259 recoveries across thirty months was reading from a count somebody maintains. None of those three documents is created for a defense lawyer. All three are created, and the vendor’s own coaching guide says so in the course of teaching police how to talk about them.

In Florida, that observation has statutory teeth. Section 119.011(12) defines a public record as any material, regardless of physical form, made or received in connection with the transaction of official business by an agency. Received is the operative word. A vendor’s coaching guide sitting in a police department’s inbox is a public record, and so is the email traffic arranging a pre-vote briefing. Section 119.07 supplies the mechanics. Subsection (1)(a) gives any person the right to inspect and copy. Subsection (1)(e) requires an agency claiming an exemption to state the basis for it and cite the statute. Subsection (1)(f) requires the reasons in writing and with particularity if the requester asks. And subsection (1)(h) is the one worth knowing before anything else: once a written request has been made, the record may not be disposed of for 30 days.

Two limits belong here, because a page that promised more than the statute delivers would be doing the same thing the guide does. First, a public records request is not criminal discovery. Section 119.07(8) says the section is not intended to expand or limit the discovery rights that Rule 3.220 of the Florida Rules of Criminal Procedure already provides. They are separate tracks, and each one reaches material the other may not. Second, whether the company itself can be made to answer a Florida records request is unsettled. Section 119.011(2) defines an agency to include a private corporation or business entity acting on behalf of a public agency, which is at least the right question to ask about a contractor holding a city’s data, but no Florida court has answered it as to this vendor and nobody should tell you otherwise.

One addition, because it sits at a higher level than the statute. The right to inspect public records in Florida is constitutional as well as statutory. Article I, Section 24(a) gives every person the right to inspect or copy any public record “made or received in connection with the official business of any public body, officer, or employee of the state, or persons acting on their behalf,” and Section 24(c) makes the provision self-executing. That phrase about persons acting on an agency’s behalf mirrors the statutory definition discussed above, which means the question of whether a contractor holding a city’s data has to answer a request does not rest on a statutory definition alone. It remains undecided as to any plate reader vendor, and it is a better question than it looks.

The point stands without the unsettled part. The company’s own script for a council meeting promises that the program is governed, audited, and documented. When one of these cameras turns up in a case, that promise is the thing to hold them to, and the records that prove or disprove it are obtainable by two independent routes.

What the Company Has Told Councils, and What Turned Out Not to Be True

The coaching guide above teaches an agency what to say to a council. A separate record covers what the company has said to councils itself. In a report published July 2, 2026, ACLU attorneys Chad Marlow and Jay Stanley collected instances of the company misdescribing its own product to the governments buying it.

In Oshkosh, Wisconsin, in April 2026, the company’s chief information security officer told the city council the system did not “create a pattern or heat map of an individual’s movement.” The city learned the next morning that it did. The council revoked its approval, which the report records as the shortest span between a city approving a contract and cancelling it: one day.

In Loveland, Colorado, the company told the police chief that federal agencies no longer had access to the city’s plate readers, and its chief executive told the press that federal data sharing was not an issue because the company held no federal contracts. It later acknowledged contracts with Customs and Border Protection and the Department of Homeland Security for pilot projects that gave those agencies direct access. In Urbana, Illinois, in 2021, it told council members it had worked with groups like the ACLU to design the system. The ACLU says it never partnered with the company.

None of that is evidence in anybody’s criminal case, and I am not going to pretend otherwise. What it changes is the weight of an assurance. When an agency tells a court, or tells a defense lawyer, what this system can and cannot do, that description came from somewhere. The presentation, the contract, the demonstration, and the emails around all three are records held by a public agency, and chapter 119 reaches them. A claim about the technology is checkable against the documents the agency relied on when it bought the technology. That is a better position than arguing about capability in the abstract.

The Officer Who Objected, and What Was Used to Build a Case Against Him

WIRED published a long account on August 18, 2026 of Noel Pichardo, a Pawtucket, Rhode Island patrolman who noticed Flock cameras appearing across his district in the fall of 2023 and could not find out how they had been approved. Pawtucket had run a free 60-day Flock pilot in 2021 with 17 cameras, which the ACLU of Rhode Island said went up without notice to the city council; the chief apologized and said the department would communicate better. In September 2023 the city signed a two-year deployment worth $128,000 for roughly 20 cameras. There was no public vote beforehand. Officials described installing them as an “administrative prerogative.”

Pichardo told a local paper the system was a “grave threat” and gave him “1984 vibes,” and said he had learned the scale of the deployment from the newspaper rather than from his own department. Two weeks later the department opened an internal investigation, on a complaint from the chief, citing among other things a rule titled “Criticism & Malicious Gossip.” His union’s attorney concluded the speech was constitutionally protected and warned the city; the department had sought a six-month suspension and settled at 30 days without pay, in an agreement that expressly denied the comments were protected. Five internal investigations followed in under two years. He resigned in July 2025, two days after being handed a recommendation for termination.

The detail that belongs in this post sits in a parenthesis in WIRED’s account. To build the final case, investigators reconstructed nearly an entire workday of Pichardo’s movements using dispatch records, time sheets, cruiser GPS, and the location data transmitted by his body camera. They placed him at about four hours and 57 minutes inside police or union buildings rather than on patrol, in a complaint running 25 pages and 32 administrative charges. WIRED’s aside: they did not use Flock data, because they did not need to. A department that wants to know where one person spent a day already has several ways to find out, and a plate reader network is only the newest of them.

Two things about this account cut against a simple reading, and both belong here. The first is that Pichardo does not dispute all of the conduct. A sustained complaint over his treatment of a delivery driver drew a 40-day unpaid suspension, and he told WIRED his behavior there was indefensible. His union, which had backed him over the newspaper interview, says it saw no evidence that the later investigations were retaliatory and believed a comparable officer would have been disciplined similarly. His position is that the rules were enforced differently against him. That dispute is not resolved, and this post does not resolve it.

The second correction runs against the officer and toward the argument this post has been making all summer. Testifying to a Rhode Island legislative committee, Pichardo said that officers’ use of these systems could not be monitored. That is not accurate. The systems maintain user logs and run audits, and Pichardo acknowledged the distinction to WIRED afterward, arguing that a log is only as good as whoever reads it. He is right about the second part and wrong about the first, and the difference matters in a courtroom. The log is the reason the Georgia, Kentucky, and Florida misuse cases documented in the sections above are known at all, and it is the record a defense lawyer can demand when a camera started the case.

The August 2026 Guardrails, in the Company’s Own Words

On August 13, 2026, Flock’s chief executive published a list of changes, and the post is worth reading directly because several of its concessions are the arguments this page has been making, now in the vendor’s own voice.

The headline change is retention. The default falls from 30 days to seven, paired with an “Evidence Mode” that lets detectives preserve specific data in cold storage for an active investigation. The company’s stated reason is that over 90 percent of searches without a full plate happen within a week. Existing customers keep whatever retention period they already have, so the number in any particular case remains a per-agency question that only the contract answers.

The accountability changes concede more. Audit Assistance, the tool that flags abnormal search behavior for administrator review, becomes mandatory for every law enforcement customer by the end of the year, with automatic lockouts when activity meets the criteria. The post says those reviews “have been associated with arrests of several law enforcement officers who allegedly abused the system.” Case codes become required for every search by year end, with emergency bypasses flagged for review. And a new offense filter lets a city decide which categories of offense other agencies may search its cameras for, with the company’s own example being a city that blocks searches related to immigration enforcement. Read that list against the misuse sections above. Mandatory audit flagging, mandatory reasons, and sharing filters are a company agreeing, in product form, that the reason field was the whole case.

One number in the post deserves its denominator read aloud. The company reports “fewer than 9 human-reported errors for every 1 million alerts.” That counts errors somebody noticed and reported, measured against all alerts. The Los Angeles audit described earlier on this page measured something different, wrong stolen-vehicle hits as a share of hits, and found roughly a third. Both can be true at once. They are answers to different questions, and the difference between them is the space where a wrongful stop lives.

For a defense file, the retention change points one direction: faster. A seven-day default means the reads that could help a client can be gone before the first court date. The preservation demand is now same-week business, and Evidence Mode preserves what the State selects, not what the defense needs. Nothing stops a defense lawyer from demanding preservation on day one, and after this change, nothing excuses waiting.

The Pushback, City by City

Since early 2026 the fight has moved into county commissions and council chambers, including ours. These sections follow it from Tallahassee to Manatee, through two councils that went opposite ways, to a city that said no and got cameras anyway, and home to St. Petersburg.

The Governor Says It Is Out of Control

On August 26, 2026, Governor DeSantis said license plate reader use in Florida is “out of control.” Speaking at Florida International University, he said the technology has expanded far beyond toll collection into criminal surveillance, warned against creating a surveillance state, and said statewide restrictions would have to come from the Legislature, where he is reviewing another state’s approach as a possible model.

That statement arrives weeks after the three Florida officer cases documented above, and it lands on the same pattern. If a bill follows, the open questions are the ones this post keeps returning to: who may search the database, what reason they need, how long the captures are kept, and who audits the logs.

The same month supplied a reminder of the failure mode that involves no misuse at all. In Wisconsin, body camera video showed officers stopping a family at gunpoint on an interstate after a Flock alert flagged their car as connected to a homicide investigation. The vehicle had already been investigated and cleared, and Milwaukee police said human error had left the alert in the system. Nobody in the car had anything to do with the case. An alert is a claim about a database entry, and the entry can simply be wrong, which is why the records demand in the next section starts with the alert itself.

Florida Pulls Every Plate Reader Permit on State Roads

On Monday, August 31, 2026, the Florida Department of Transportation revoked its active permits for automated license plate readers in state highway rights of way, and said it will approve no new ones. Agencies have 30 days to take the cameras down. If they do not, the Department says it will remove them itself. The order covers the state highway system, the interstates included.

The memo gives its own reason. Florida law “limits the issuance of permits for LPR systems to law enforcement agencies,” and “the recent exponential increase in deployments along our roadways, coupled with concerning reports of misuse, data privacy concerns, and surveillance schemes merit immediate action to preserve Floridians’ sovereignty and quality of life.”

The Governor had already put it in plainer words. “I think these cameras, the license plate readers, I think it’s out of control.” He gave a misuse example too, describing “an officer in Florida who was using the LPR data to track like an ex-girlfriend or something like that.” He did not name the case. The misuse record above collects the Florida ones that have surfaced so far.

The scope is narrower than the headline. This order reaches cameras in state highway rights of way. It does not reach a camera on a city street, a county road, or private property. The reader at a subdivision gate, the one on a shopping center pole, the one a municipality put up on its own road: none of them are touched by this. Reporting on the order notes the Legislature could take the wider question up next year.

Some agencies are going further than the order requires. The Putnam County Sheriff’s Office announced it is discontinuing and removing all of its plate readers, not only the ones on state roads. Sheriffs in Franklin and Liberty counties have announced the end of their programs, and police agencies across northeast Florida have stopped using the cameras.

Two days earlier, Sheriff Chris Nocco’s letter ending the Pasco County agreement drew the same line from the other side. He told his commissioners that ending the county agreement would not touch readers on private property, or “cameras placed in State-owned right-of-ways which are governed by the Florida Department of Transportation.” Those were the cameras nobody at the county level controlled. The Department that did control them has now acted. The private ones he was pointing at are still up.

What this changes in a case, and what it does not. A camera that comes down on September 30 ran until September 30. Every read it took before then is a record that already exists. Taking the pole down does not delete the log, the search history, or the reason an officer typed to justify pulling a plate. If a plate reader is anywhere in your case, the demands in the records section below are unchanged by this order.

If anything the first question gets sharper. Where the camera sat on a state road, the dates now carry weight of their own: what the permit status was on the day of the read, when the removal actually happened, and whether the agency kept running the camera past the deadline. And where it sat on a city street, a county road, or a private lot, this order does not reach it at all. Which is the same question it always was. Whose camera was it.

The Pinellas Sheriff Defends the Cameras, and Describes What They Cannot Do

On Wednesday, September 2, 2026, Pinellas County Sheriff Bob Gualtieri held a news conference defending his agency’s use of automated plate readers. He said the debate had blurred the difference between a plate reader and continuous surveillance, and that “misinformation about what ALPR is and what it does is unhelpful.” On the technology itself: “We cannot fight crime in the stone age.” On the pressure to drop it: “As we cannot defund the police, we can also not de-tool the police either.”

One sentence in that news conference is worth more to a defense lawyer than the rest of it combined. Describing the limits of the technology, the Sheriff said ALPR “identifies vehicles, it doesn’t even confirm that a particular person was behind the wheel or in a vehicle.” He offered that as reassurance about privacy, and it doubles as a plain description of the evidentiary gap. A plate read puts a registration on a road at a time. Connecting a specific human being to that vehicle is a separate question, and the camera does not answer it. That distinction is the whole fight in the actual physical control cases, where identity and control are what the State has to prove.

The numbers he gave are the clearest public picture of how deep one Florida county’s network runs. Pinellas has used plate readers since 2006. The agency has 73 fixed readers, mobile readers mounted on trailers, and plate reading built into the dash camera systems in all 560 patrol vehicles. The systems come from Flock Safety, Motorola, and Axon. He said 23 of the 73 fixed readers sit under Department of Transportation permits, which is the slice the state order above actually reaches. Reporting on the order put the countywide removal at about 29 cameras, which leaves the larger network in place.

He defended the results as well, saying vehicle thefts in the agency’s primary service area fell 56 percent over a decade, from 529 in 2015 to 230 in 2025.

On accountability he went further than the company has. He said an officer who misuses the system faces termination and criminal prosecution, and he backed statewide standards including mandatory written policies, audits, and a prohibition on using the systems to monitor First Amendment activity. For a defendant that is a useful concession, because a policy is a document and an audit is a record. Both can be demanded. The records section below lists what to ask for.

Two admissions in the same news conference are worth more than all of the reassurance around them. Asked about the searches themselves, the Sheriff acknowledged that the software does not actually require a case number, even though the agency’s own policy requires deputies to enter one. On oversight, he said, “We have to trust our people, we have to trust but verify,” and acknowledged that his office does not currently have the automated auditing capability he would like to have.

Read those two together and they describe the gap this entire page is about. Every Florida misuse prosecution covered above turned on what an officer typed into the reason field. If the system does not force that entry, then the field is a matter of habit rather than a control, and if the auditing is not automated, then nothing catches a bad entry until somebody goes looking. That is not an accusation about any particular deputy. It is a description of what the records will and will not show, offered by the official who runs the system, and it is the reason the audit log is worth demanding rather than assuming. The records section below lists what to ask for.

The county is moving the other way at the same time. On Tuesday, September 1, 2026, Pinellas County Commissioner Vince Nowicki filed a resolution directing the county to end its contracts, subscriptions, and data sharing arrangements with plate reader providers, to remove existing cameras within 30 days, and to stop renewing, extending, or replacing any such agreement. The resolution also calls on the Sheriff’s Office and the municipalities inside the county to end their own contracts. It could be taken up at the commission’s September 10 meeting. Nowicki put his reasoning plainly: “I think we will look back and say, ‘Was this too far?’ And I think that time is here.” The Sheriff has said his office will not voluntarily remove cameras from county roads. A county resolution does not bind an independently elected sheriff, so both tracks can run at once.

The Cancellations Kept Coming Through September, and the Scale Underneath Them

Asheville, North Carolina voted five to two on August 25, 2026 to end its contract, and its eleven cameras come down; the resolution also directs city employees to stop searching and sharing the data already collected while existing records are handled under the retention rules. Knox County, Tennessee commissioners voted unanimously on Monday, August 31 to switch off and remove readers at dozens of locations within 30 days, and to remove the associated data on the same clock unless it belongs to an active investigation.

The scale is worth stating carefully, because the best available numbers are not official ones. ABC News reported on September 1, 2026 that more than 135,000 automated plate recognition cameras have been identified nationwide and that four of every five are made by this one company, both figures drawn from the crowd-sourced DeFlock project rather than from any government inventory, and that more than 50 cities and counties have cancelled or deactivated such cameras this year, a count it attributes to Politico. Nobody publishes an authoritative map, which is a fact about the subject rather than a gap in the reporting.

For a case, a cancellation is a date, not an erasure. A camera switched off in September still recorded everything it recorded before September, and those reads sit in a database that a retention schedule governs. Knox County ordering the data removed within 30 days is the unusual part, and it is the reason a preservation demand goes out early rather than after the first court date. Canceling a contract is not the same as removing the cameras, and neither one reaches the records already made.

Manatee Bans Flock From County Property, and the Numbers Underneath It

On August 26, 2026, FOX 13 reported that Manatee County commissioners voted five to nothing to keep Flock license plate readers out of county parks, county facilities, and county buildings. Sheriff Rick Wells told the station his office does not have plate readers at any of those locations and had no plans to install them.

The numbers reported alongside that vote are the reason it belongs in this post. The Manatee County Sheriff’s Office operates 79 Flock cameras and 134 license plate readers built by other manufacturers across the county. None of the 213 sits at a park or a county building, so the vote does not move a single existing camera. It forecloses a placement that was not being proposed.

That second figure is the one to sit with, and it is the local proof of the point made in the vendor section of this post. Most of Manatee County’s plate readers are not Flock cameras at all. A measure written around one company’s name reaches one company, and the majority of the county’s readers keep running under whatever terms that agency and those vendors agreed to. If a plate reader is in a Manatee case, the vendor is the first fact to establish, because it determines the retention period, where the data is stored, and which sharing network the agency joined.

The commission also heard about the limits of its own authority. MySuncoast reported that the county attorney advised commissioners the county can only ban the cameras in unincorporated Manatee County. Commissioner Amanda Ballard moved separately to require that plate reader applications come to the commission for approval, which is the piece of the day with forward force. For balance, the sheriff’s office says deputies used plate readers over five years to identify 37 homicide suspects and to locate 23 missing or endangered people.

The Council Vote That Went the Other Way

San Diego runs roughly 500 plate readers, and its council voted to keep them. Most of the council fights described on this page ended with cameras coming down or contracts lapsing. That is not the only way these votes go, and a page that only collected the cancellations would be giving a false picture of where this stands.

San Diego runs roughly 500 automated license plate readers, at a reported cost of about $2 million a year, tied to a smart streetlight contract the city approved in 2024. On November 5, 2025, the city’s own Privacy Advisory Board formally recommended that San Diego cease using the Flock system. On December 9, after nearly six hours of public comment in which hundreds of residents spoke and the majority opposed the technology, the City Council voted 5 to 3 to approve the police department’s surveillance use policies and let the readers continue. Councilmembers Sean Elo-Rivera and Henry Foster III voted no, one member abstained, and one was absent. The council did agree to revisit funding through a required annual review.

Read that sequence again, because it is the useful part. A city’s own privacy board studied the system and recommended ending it. Hundreds of residents turned out against it. The council heard all of it and voted to continue. Public opposition, even organized and sustained public opposition, is not a control on this technology. The annual review is a control. A privacy board recommendation is an input. A vote is the decision, and it can go either way.

Eight months later, in August 2026, a San Diego event producer named Anthony Ralphs addressed the same council in a Darth Vader costume with a voice changer, opening with the line that the emperor is a fan of Flock. He told 404 Media he had spent months attending meetings in professional attire citing legal precedent, that it had not worked, and that “you can’t spell activism without ‘act.'” No ordinance followed the costume either.

The point for anyone with a case rather than a cause is that none of this changes the record. Whether a council keeps the cameras or removes them, the searches that already ran are logged, and those logs are still there to be demanded. A vote decides what happens next. It does not reach backward into the case sitting in front of you.

A City Said No, and the Cameras Arrived Anyway

A city council can vote these cameras down and still end up surrounded by them. Other sections here describe councils voting one way or the other. This one describes what a council vote actually controls, which is less than many folks assume and is the practical answer to a question this post gets asked often.

404 Media reported on August 10, 2026 on Norman, Oklahoma, where Flock made two presentations over three years at the police department’s request and all nine city council members voted no. Mayor Stephen Tyler Holman told 404 that the sticking points were not philosophical but operational, and they are the same questions this post keeps returning to: “Questions about data storage and how long and who has access to it… you’re gathering data on every single car vehicle that goes in and out of the city of Norman, regardless of if they’ve committed a crime or not, and then that’s stored for 30 days on some kind of database? Who has access to it? How secure is it?” Some council members argued the retention period should be an hour, or thirty minutes. Holman said the company’s pitch centered on amber alerts, silver alerts, and finding people with Alzheimer’s who had wandered off, and that at the most recent presentation the company suggested people would learn Norman had no cameras and come there to commit crimes.

Norman’s council said no, and the cameras are in Norman anyway. Cleveland County, where the city sits, approved twenty cameras for the county sheriff’s office. Holman also told 404 that “there are numerous homeowners associations that use them too,” adding that “the city of Norman government does not. We’re, I guess, the only ones around here that don’t.”

That is the jurisdictional gap, demonstrated. A city council governs city property and city contracts. It does not govern the county sheriff, who is separately elected and separately funded, and it does not govern a private homeowners association, a condominium board, or the owner of a retail parking lot. The Manatee section above records the same limit in a Florida county, where the county attorney advised commissioners that they could only reach cameras in unincorporated areas.

Florida’s statutes have the same shape. As set out in the section on what Florida law actually covers, sections 316.0777 and 316.0778 impose a retention schedule and confidentiality on automated license plate recognition systems and govern cameras placed in the state highway right of way. They do not reach the camera at an apartment complex gate or in a shopping center lot, installed by the property owner, where a resident has no way to opt out of being recorded where they live. When a plate reader turns up in a case, the first question is not only which agency searched it, but who owns the camera and which set of rules, if any, applies to it. A municipal vote may not answer that at all.

A Florida Decoy Camera, and Three Charges That Each Turn on Something Different

Florida police 3D-printed a fake plate reader camera, and the man who cut it down was charged with three felonies. The rest of this page is about what these cameras do. This part is about what happens when somebody attacks one, and it is the most directly useful case here for anyone facing a charge in Florida.

404 Media reported on August 25, 2026, working from an arrest report, that after real Flock cameras were stolen in Oviedo between July 23 and August 3, an officer 3D-printed decoy cameras at home. The decoys were built to resemble real units but did not function and collected no data. Officers watched them from Sunday night through Thursday night, and Evan Meyer was arrested shortly after midnight on August 21 and charged with three felonies: attempted grand theft, criminal mischief with damage over $1,000, and a count for property crimes against computer equipment. The mayor told 404 Media she had no idea the operation was happening, and the department said it holds no records about the decoy’s creation, with “no meeting minutes, no text messages, and no emails regarding the production.”

The legally interesting part is that the three counts do not rise or fall together. Each one asks a different question, and the answers are not the same.

Criminal mischief is graded purely by value. Under section 806.13, damage of $200 or less is a second-degree misdemeanor, damage over $200 and under $1,000 is a first-degree misdemeanor, and damage of $1,000 or more is a third-degree felony. The statute grades on “the damage to such property,” which is the property that was actually damaged. On the reporting, that property was a few dollars of printed plastic.

Theft is also graded by value, at a different line. Under section 812.014, grand theft in the third degree begins at $750; below that the offense is petit theft. But this count was charged as an attempt, and on an attempt what a person believed he was taking does work that the completed offense would not. That is presumably why the arrest report records Meyer saying the camera cost “approximately $1,000-$5,000” and that he “knew it was an expensive real piece of equipment.” Belief can carry an attempt. It is a different question from whether damage crossed a dollar threshold.

The computer count is not about value at all, and that is the one people misread. Section 815.06(2)(c) makes it a third-degree felony to destroy, take, injure, or damage “equipment or supplies used or intended to be used in a computer, computer system, computer network, or electronic device.” There is no dollar threshold in that offense; the $5,000 figure elsewhere in the statute only elevates it to a second-degree felony. So arguing that the object was cheap does nothing to that count. The question there is whether a hollow plastic shell that recorded nothing is equipment used or intended to be used in an electronic device.

Two cautions before anyone reads a result into this. Nothing here predicts an outcome, and no one should. And these are the charges on an arrest report, not the charges the State ultimately files. The prosecutor files the information later and it frequently differs from what an arresting officer wrote. The transferable lesson is the method: when one act produces several counts, separate them by what each count actually requires. Value is a provable fact and worth attacking where the grade rides on it. Where the grade does not ride on value, attacking value is aimed at the wrong element.

St. Petersburg Sends Its Flock Contract to Committee, Four Years In

On August 27, 2026, the St. Petersburg City Council voted unanimously to refer the city’s contract with Flock Safety, and the police department’s use of the cameras, to the Public Services and Infrastructure Committee. Council Vice Chair Richie Floyd asked for the referral. Florida Politics reported the meeting and laid out how the network got built.

The city started with a 25-camera pilot in 2022, run by the police department. That rollout never went to elected officials for a vote. Two years later a five-year contract worth $730,250 nearly doubled the network to 50 cameras. That one did reach the Council, but it arrived on the consent agenda and passed with no questions from members and no public discussion. The city now runs roughly 54 cameras. So a four-year-old surveillance program is getting its first real public hearing after the cameras are already up, which is the ordinary sequence rather than the exception.

Floyd asked the committee to look at how the police department uses the system, who can access the data, how long the information is kept, and what controls govern searches and information sharing. Those four are the right four. They are the same four this post has been circling in every section above, and they are the four that decide what a plate reader is worth in an actual case.

Residents at public comment raised Fourth Amendment concerns, and one attorney who spoke made a specific prediction: that when courts find this technology unconstitutional, evidence gathered through it will be thrown out of criminal prosecutions.

That prediction is the weakest argument in the room. As the database-stop section below sets out in detail, a federal judge in the Middle District of Florida dismissed exactly that theory in October 2025, with prejudice, in a case about plate readers mounted at all three bridges onto Marco Island. The court held there was no cognizable privacy interest and no search at all, distinguished Carpenter on the ground that a car is not a phone, and cited federal district decisions from four other states reaching the same result. Florida’s own search and seizure provision, Article I, Section 12, is written to be construed in conformity with the Fourth Amendment as the United States Supreme Court interprets it, so it does not carry a resident further than the federal claim goes. The suppression theory is not frivolous and the state constitutional question genuinely is open, but a plan that depends on courts changing their minds is a plan with no date on it and a losing record so far.

The reason that matters is not to score a point against a neighbor at a podium. It is that the weak argument crowds out the strong one. Retention periods, who may run a query, whether every search is logged with a stated reason, whether the data joins a multistate network, and whether outside agencies can reach into it are not constitutional questions at all. They are contract terms and written policy. They can be changed by a city council in a committee room, on a schedule the city controls, without asking a court’s permission and without waiting for anybody’s appeal. That is the fight that is actually available, and it is the one Floyd’s four questions describe.

For anyone planning to follow the committee process, the useful documents are the ones the sections above describe: the current contract and its retention term, the department’s written policy, and the search audit logs showing who ran queries and what reason was typed into the field. All three are obtainable, and the audit logs in particular are what exposed misuse by officers elsewhere in Florida this year. A committee that reads those three things before it votes will know more about the program than the Council did when it approved the contract.

Pasco Ends Its Agreement, and the Sheriff Explains Exactly What That Does Not Reach

This one is in Tampa Bay, and the most useful paragraph in it was written by the sheriff who opposed the change. FOX 13 reported on August 27, 2026 that Pasco County Sheriff Chris Nocco told the Board of County Commissioners he is terminating the interlocal agreement that allows license plate readers in county rights-of-way, effective September 30, 2026. The board had passed that agreement unanimously on December 10, 2024. He is ending it, in his own words, because it was clear from the meetings on August 11 and August 25 that a majority of commissioners no longer support it, and he made plain that he disagrees with them.

His letter says removing the cameras will affect the solvability of crimes and the ability to locate missing and endangered children and adults, including victims of human trafficking, and will strain an already limited agency. Take that seriously rather than waving it away. It is the same argument the vendor makes, made here by an elected official who has to answer for unsolved cases.

His next paragraph is a warning rather than a concession. Sheriff Nocco told the commissioners that they will keep hearing complaints about plate readers in Pasco after the agreement ends, because there are currently more license plate readers placed by private entities than by the Sheriff’s Office, and terminating the county’s agreement will not touch readers installed by private property owners on their own property, such as community development districts, homeowners associations, and retail establishments, or cameras in state-owned rights-of-way, which are governed by the Florida Department of Transportation.

Read that against the two sections above on what a council vote controls and what Florida’s plate reader statute actually reaches. A sheriff has now put the same limit in writing, from the other side of the argument. The county agreement governed county rights-of-way. It never governed the camera at the front gate of a subdivision, the one on a shopping center’s light pole, or the one FDOT permits on a state road. If a plate reader appears in a Pasco case after September 30, the first question is unchanged and now unavoidable: whose camera was it.

The letter also puts numbers on the agency’s own policy, and they are worth keeping for comparison. Nocco says Florida law permits plate reader data to be retained for as long as two years, while Pasco restricted itself to 30 days. He says searches were limited to felonies and selected misdemeanors, had to be tied to a call for service or a case number, and required deputies to document why they accessed the system. He adds that none of the abuses raised at the commission meetings had happened in Pasco County. That two-year figure is his characterization of the state retention schedule rather than a number this firm has verified against the schedule itself, so treat it as his statement and check the schedule before relying on it. The comparison still matters, because a 30-day policy and a two-year ceiling produce very different answers to the only question that counts in a case: is the record that would help you still in existence.

For anyone with a Pasco case, the practical consequence of a September 30 end date is a deadline rather than a relief. The agency keeps what it already collected, and the cameras it did not control keep running. A demand for the search logs behind a stop is worth making now rather than after the contract lapses and the institutional memory of who administered it moves on.

A Senate Investigation, and Two Arizona Towns That Agreed From Opposite Directions

On August 28, 2026 the fight stopped being municipal. Fortune reported that Senator Josh Hawley, who chairs the Senate Judiciary Subcommittee on Crime and Counterterrorism, sent a letter to Flock’s chief executive opening a formal investigation into the company’s collection, retention, and dissemination of camera data. The letter puts the network at more than 120,000 cameras across 49 states, scanning more than 20 billion vehicles a month, and contains a sentence worth repeating: “Congress never authorized the network your industry has built.” The company was given until September 8 to produce documents and has said it intends to cooperate.

Hours later Senator Bernie Sanders published a statement pledging legislation of his own, noting that newer versions of the technology can match images of people and vehicles against databases of phone numbers, relatives, and court records. Hawley and Sanders sit at opposite ends of the Senate. Their statements landed the same day.

The same thing happened in Arizona on a smaller scale and it is the more instructive half. Tempe, a city where roughly 63 percent of voters back Democrats, switched off its plate readers and said it would not look for a replacement vendor. Three hours later Cave Creek, a Republican-leaning town north of Phoenix, did the same. They are the ninth and tenth Arizona municipalities to drop or restrict the cameras in a year, after Chandler, Surprise, Pinal County, Sedona, Flagstaff, Sierra Vista, South Tucson, and Apache Junction.

Tempe’s reasoning should interest anyone with a plate reader in their case, because the city was not reacting to a scandal of its own. Its police department had used the cameras to help solve crimes, and its own monthly audits had turned up no misuse at all. Mayor Corey Woods put it plainly: the cameras helped officers do their jobs, and he did not discount that, but the risk of misuse was too great to keep them. Councilmember Bobby Nichols framed it as a legal test rather than a policy preference, saying a law enforcement tool should be used only where it is a narrowly tailored solution to a compelling government interest. A clean audit record was not treated as an answer to the structural question.

Cave Creek’s objection was structural in a different way, and it is the same point the vendor and swap sections above keep arriving at. Its officials concluded that because the network lets outside agencies search data collected locally, there was no way to protect residents’ privacy once their information left the town’s jurisdiction. The town could govern its own cameras. It could not govern who reached into them. One of its cameras had also been stolen from an intersection, and public works crews removed the rest for safekeeping.

Two numbers frame the argument on either side. By the company’s own account its cameras helped close roughly a million police investigations and locate about 10,000 missing people over the past year, and a spokesperson told Fortune that removing a working tool moves public safety backward, with cases taking longer and victims waiting longer. Against that, an August Washington Post investigation counted more than 50 law enforcement officers accused of, charged with, or convicted of misusing plate readers, including officers who used them to track former partners. Both of those things are true at once, and any argument that only reports one of them is not worth making in front of a judge.

For a case, the practical consequence is about records rather than politics. A Senate document demand with a September 8 return date will generate material about retention, access, and sharing that no defense request has previously reached, and a city that has switched its cameras off still holds everything they collected while they ran. Cancellation does not erase the data behind a case that has already begun, and the audit trail for a search that already happened outlives the contract that authorized it.

Where the Cameras Are Going Next

The last group is about the technology outrunning the argument. Drones, rival vendors with different rules, federal land, other people’s cars, and replacement cameras designed not to be seen. The common thread: every rule discussed on this page attaches to a word, and the new hardware keeps slipping the definitions.

The Cameras Are Getting Off the Poles

Everything above describes fixed cameras. As of this writing the same company sells an autonomous drone, and the plate reader has left the pole.

The aircraft is sold for what the industry calls Drone as First Responder, which means it launches on a dispatched call and arrives ahead of a patrol unit. The manufacturer states it is American made, that it flies at up to sixty miles per hour, and that its camera can read a vehicle license plate from two thousand feet. The company reports deployment across more than two hundred agencies and has described drones as among its fastest growing lines.

Tampa Bay is part of this. Agencies in the surrounding counties have moved to expand drone programs, with county agendas describing the purpose in terms of locating offenders, apprehension operations, and coordinated federal enforcement activity.

The regulatory picture is thinner than many folks assume. In August 2026 the President said the Flock question was being studied and that an administration position would follow within a few weeks. No ban was announced and no position was stated. The company’s own chief executive has described the landscape as very little state regulation and zero federal regulation outside of air safety.

What Pasco County is actually being asked to approve

The clearest local example appears to be on paper already. A Pasco County Board of County Commissioners agenda memorandum appears to describe a countywide Drone as First Responder network, with the Pasco County Sheriff’s Office as the applicant and the long-term owner. The scope is twenty one weather rated autonomous drone docks at proposed sites countywide, plus twenty two supplemental aircraft.

The money appears to be federal. The memorandum lists a total project cost of nine million dollars, funded one hundred percent by Community Development Block Grant Disaster Recovery dollars, with no other or leveraged funds. The national objective is recorded as low and moderate income area benefit or urgent need, and the beneficiary count is the county population.

Two things in that document deserve to be read carefully before anyone describes it as a done deal. The application status is listed as threshold review, and the implementation conditions state plainly that board approval establishes a Phase 1 project recommendation only, with funding commitment and notice to proceed still subject to final eligibility, environmental review, duplication of benefits review, procurement, funding availability, and execution of all applicable agreements. The schedule runs to a projected completion in 2031.

The stated purpose appears to be disaster response. The memorandum describes rapid damage assessment, search and rescue support, infrastructure inspection, and live situational awareness when roads are flooded, blocked, or unsafe. It also describes the point of the project in a sentence worth quoting, that it converts aerial response from equipment that must be transported to a scene into permanent infrastructure positioned before a disaster occurs.

That sentence appears to be the part a defense lawyer should sit with. Permanent infrastructure positioned in advance is what it appears to say, and the document indicates that the Sheriff’s Office will operate and maintain the network through its established unmanned aircraft program and its annual operating budget. Storms are not a daily event. An always ready aerial platform owned by a law enforcement agency would appear to be available every other day of the year, and a disaster mitigation funding document does not appear to be the place where anyone writes down the rules for what it does on those days.

None of that is an accusation, and nothing in the memorandum suggests otherwise. It is the reason to ask the question early rather than after a case begins. The policies that govern routine use, the retention schedule for footage collected outside a declared emergency, and the audit trail for who may task an aircraft are ordinary public records questions, and they are easier to ask now than to reconstruct later.

One clarification worth making, because it appears to have traveled with this story on social media. The agenda memorandum describes weather rated autonomous docks and supplemental aircraft, and it does not appear to name a vendor anywhere in the item. So a claim that any particular manufacturer has won this work does not appear to be supported by the document itself.

Why this is a different question, and not just a taller pole

The older cases allowing police to look down from aircraft were decided on facts that look nothing like an autonomous plate reader. They involved a person in a manned aircraft, flying where anyone could lawfully fly, looking during a single overflight at what was plainly visible from there.

A machine that reads and stores plates from two thousand feet is a different proposition, and the arguments run along lines courts have already accepted in other settings. One observation shows a moment, and a continuous record shows a pattern, which is the distinction that led the Supreme Court to require a warrant for historical cell site location records. The public exposure rationale also assumes an ordinary person could have seen the same thing, and no ordinary person reads plates from two thousand feet, automatically, and keeps the result. Older surveillance was limited by what it cost, and automation removes that limit.

None of this is settled in Florida. It is the argument, and it has to be made in the trial court to matter later.

If a drone is anywhere in your case, the records are different

A drone initiated contact leaves a different file than a fixed camera. The dispatch record that launched the flight and the reason recorded for it, the flight log with times, altitudes and track, the aircraft’s own video rather than only a plate photograph, the retention schedule that applies to aerial footage, the operator identity and certification, and the audit trail showing who later searched or exported any of it.

Aerial footage is often kept for a shorter period than the plate database, so the request has to go out early. A record that has already been deleted cannot be examined by anyone.

Flock Is Not the Only Vendor, and One System Skips the Plate Entirely

Flock is one company in a crowded field, and which rules protect you changes with the vendor. This page concentrates on Flock because Flock is what Tampa Bay bought. The ACLU cataloged the others in August 2026, and the names that come up in Florida procurement are Motorola Solutions, which sells the Vigilant system, Axon, Rekor, Genetec, and Leonardo. They are not interchangeable. They differ on how long data is kept, whether it lives on the agency’s own hardware or in the vendor’s cloud, and whether the agency joins a national sharing network by default. If a camera is anywhere in your case, the vendor is a fact worth establishing early, because the answer changes what records exist and how long they lasted.

One of those systems is different in kind, and it is worth understanding before it arrives. Leonardo markets an add-on to its ELSAG plate readers called SignalTrace. Instead of photographing a tag, it collects the radio signals that consumer electronics broadcast as they pass. The company’s own product page lists “fitness trackers, smartwatches, RFID tags and mobile phones,” and describes a system designed to identify groups of devices that “routinely travel together, even when a license plate number is not known.” It says the result “Allows law enforcement to recognize a specific vehicle included in an electronic signature, without the license plate number.” Leonardo also states that the system “does not decrypt or read content from devices.”

Two cautions before anyone draws conclusions from that. Some coverage of SignalTrace has added tire pressure sensors and infotainment systems to the list of what it collects, and Leonardo’s own page does not claim those. And no agency has been publicly identified as having bought or deployed it, so nothing here should be read as a description of what is running in Florida today.

The legal question it raises is genuine and nobody has answered it yet. Florida’s plate reader protections are built on a definition. Section 316.0777(1)(c) defines an “automated license plate recognition system” as “a system of one or more mobile or fixed high-speed cameras combined with computer algorithms to convert images of license plates into computer-readable data.” The retention ceiling, the public records exemption, the right to request the data tied to your own tag, and the bar on issuing a citation from a plate reader all attach to that definition. A device marketed on its ability to identify a vehicle without the plate number does not obviously convert images of license plates into anything. Whether the statute reaches it has not been litigated in Florida, and until it is, the safer assumption for a defense lawyer is that the answer is unsettled rather than favorable.

The practical consequence is the same one that runs through this whole post. The first question about a camera is never what it saw. It is whose system it was, what that vendor’s retention setting was on that date, where the data was stored, and who else held a copy. Those answers are written down somewhere, and they can be asked for.

The Cameras Reach Federal Land, and the National Parks

The National Park Service has bought Flock cameras and installed them at parks including Yosemite. Every other deployment on this page belongs to a city, a county, or a sheriff’s office. 404 Media reported that purchase on August 18, 2026, and reported that the agency plans to install cameras from Verkada as well, according to an internal Park Service document the outlet viewed.

Current and former rangers objected to their own agency’s purchase, speaking to 404 Media anonymously because they were not permitted to talk to the press. One said that “Flock protects property, not people or parks.” Another said that “every American should be free to visit our national parks without their location being traced and tracked by the federal government.” A third framed the concern as an operational one: “I fear for the day when a visitor’s National Park experience is interrupted by being pulled over and held at gunpoint because a license plate reader misread their plate.”

The Park Service told 404 Media that Yosemite “uses a traffic-monitoring system to measure vehicle counts, travel times and entrance-station wait times,” and that “the cameras are not connected to law enforcement or DMV databases.” That statement describes the traffic system. It is quoted here in full so a reader can see what it addresses.

The ranger’s fear is the part this post can put a number on. A misread plate producing a stop is not a hypothetical: as described in the section above on alert accuracy, an internal Los Angeles Police Department audit counted 161 false stolen-vehicle alerts in two months, a 32.3 percent false positive rate, and the department did not renew its Flock contract. An alert is a claim a machine makes about a database entry. When it is wrong, the officer approaching the car does not know that yet.

The reason federal land matters here is reach, not scenery. These cameras record a plate with color, make, model, and a timestamp, the data goes to law enforcement customers, it is generally queried without a warrant, and the national network means an agency in one state can search cameras in another. A drive through a park entrance becomes a dated record of a vehicle in a place, held in a system that other agencies can query. That is the same structure described in the nationwide search section above, applied to somewhere many folks would never think to expect it.

The Plan to Put the Cameras Inside Other People’s Cars

Flock planned to turn roughly 350,000 rideshare and delivery cars into moving plate readers. The section before this one describes a camera a city council cannot reach because a homeowners association owns it. This is the same problem with the camera moving.

404 Media reported on August 7, 2026 that a Flock presentation shared with the outlet shows the company planned to use around 350,000 Uber, Lyft, and delivery drivers to collect license plate data for its system, using dashcams installed in those drivers’ vehicles to scan the plates the drivers passed as they worked. Coverage of the reporting identifies the dashcam maker as Nexar, notes it is unclear whether the rideshare companies or the drivers themselves would have known what the cameras were collecting, and reports that Flock says the deal was never executed. That last point belongs here: what is documented is a plan, not a deployment.

A plan still tells you what the shape of the problem is, and this one is worth understanding before it arrives in some other form. A camera mounted on a pole has an address. It can be photographed, located on a map, tied to the agency that installed it, and made the subject of a records request asking who searched it and why. Every practical suggestion in the records-demand section below depends on being able to identify the camera.

A camera riding in a stranger’s car has none of those properties. It has no fixed location, because it was wherever that driver happened to be working. It is privately owned, by a gig worker who bought a dashcam. The data lands with a private company rather than with a police department, and law enforcement reaches it by querying that company. Nothing in that chain is a government camera in a government location under a government policy, which is what the current rules were written to address.

Whether Florida’s statutes reach an arrangement like that remains unsettled, and this post is not going to pretend otherwise. Section 316.0777 defines an automated license plate recognition system as cameras combined with computer algorithms that convert images of license plates into computer-readable data, and a dashcam performing plate recognition could plausibly satisfy that description. What has not been tested is how the statute’s obligations attach when the operator is a private company aggregating data from privately owned cameras rather than an agency running its own network. The practical consequence is the one that runs through this entire post: when a plate reader appears in a case, establish who owned the camera before arguing about what it recorded. That answer determines which rules apply, and in some configurations nobody has decided yet what the answer is.

Canceling Flock Is Not the Same as Removing the Cameras

Canceling a Flock contract does not always mean the cameras come down. A council votes, the contract ends, the coverage moves on, and the impression left behind is that the surveillance stopped. Sometimes that is what happened. Sometimes a different company’s cameras went up in the same places within weeks.

404 Media reported in August 2026 that a number of American cities dropped Flock’s plate readers and immediately replaced them with equivalent systems from Axon, the law enforcement contractor best known for Tasers and body cameras. NPR put names on two of them later that month: Denver signed a one year deal with Axon after ending its Flock arrangement, and Longmont, Colorado moved to an Axon system as well. NPR also reported that roughly 100 cities nationwide have deactivated cameras, rejected proposed deals, or canceled contracts, drawing on the DeFlock project’s tracking database.

Axon’s chief executive was direct about the trend, telling NPR the company is seeing a significant number of agencies wanting to come over and convert from their existing plate readers. A privacy researcher quoted in the same story gave the blunter version: you are replacing one color of camera for another.

Two details in the reporting change the practical picture, and they are the reason this section exists rather than being a footnote to the cancellation coverage.

The first is what the replacement hardware looks like. Per 404 Media, Axon advertises cameras that attach to an existing streetlamp and are designed to blend in completely with their surroundings. A Flock unit is recognizable once you know what to look for: a small dark housing on a slim pole, usually with a solar panel and a stub antenna, sitting near an intersection or a neighborhood entrance. Much of the practical advice on this page assumes you can stand at the spot where the reading happened and see the device. A camera built into a streetlight defeats that. So does the second detail, which is that Axon also collects plate data from cameras mounted inside patrol vehicles. A camera in a moving car has no fixed location at all. It read your plate wherever that car happened to be.

The product has a name, and its own page describes it plainly enough that no outside characterization is needed. Axon Lightpost combines plate recognition, live streaming, and vehicle attribute recognition, and Axon markets it as “expanding coverage without new poles, trenching, or delays.” It was built with a company called Ubicquia and it draws power through a NEMA seven pin photocell, which is the socket an ordinary LED streetlight already has on top of it. Axon says it “installs in under an hour on existing light poles.” The page describes capture “at high distances, day and night, at highway speeds,” across multiple lanes, and the reads feed into Axon Fusus, which unifies them with other connected cameras in a single operational view.

One line on that page is easy to skim past and is the one that matters procedurally. Among the deployment services Axon lists is help “obtaining attachment agreements.” An attachment agreement is a utility arrangement about hanging equipment on a pole. It is not a surveillance contract that a council votes on, and that is the point of the section above about cancellations. A camera that needs a new pole needs a budget line, a permit, and usually a public meeting. A camera that screws into a light fixture the city already owns can arrive through a paperwork channel that was never built to answer questions about retention, access, or audit logs.

Two cautions, because this technology is generating a great deal of confident writing that does not hold up. Widely shared social posts attach specific figures to these cameras, including an exact top speed and an exact capture distance. Those numbers do not appear on Axon’s own product page, which speaks in general terms about highway speeds and high distances, and says under an hour rather than any particular number of minutes. Treat the specific figures as unverified until somebody produces a spec sheet. Second, several aggregator articles about streetlight cameras cite recent court decisions by name for the proposition that limited plate reader use has been upheld. This firm has not pulled those decisions and does not repeat them here. The verified state of the law is the database-stop section below: a Florida federal court rejected the Fourth Amendment theory, and the state constitutional question is undecided.

The consequence for a case is the same one made in the section on other vendors above, now with a concrete example behind it. Retention period, who is allowed to run a query, whether the search is logged, whether the data joins a multistate network, and whether an outside agency can reach into it are all contract and policy questions, and the answers belong to whichever company holds the contract. A city ordinance written around one vendor’s name governs that vendor. A public records request addressed to a system the agency no longer uses returns nothing, and the nothing looks like an absence of evidence rather than a wrong address.

So the first question when a plate reader turns up in a case is not what the camera recorded. It is whose camera it was on the date in question, which is not always the company that was in the news. The agency’s current contract, its policy manual, and its audit logs are the documents that answer it, and all three are obtainable. A cancellation headline is not evidence that the surveillance stopped, and treating it as though it were is how a defense misses the records that actually exist.

When the Database Is the Reason for the Stop

When a plate reader turns up in a criminal case, it arrives as one sentence in a charging document. That sentence says what the cameras were used for, and it is the sentence a defense lawyer reads first. Everything else on this page concerns cameras, contracts, and policy. This part concerns the sentence.

404 Media reported in August 2026 on a Wisconsin criminal complaint, reviewed in that reporting, in which deputies used Flock to follow a car from Wisconsin into Michigan and back over the course of an afternoon. The probable cause section of the charging document, quoted in the article, reads in part: “Based on prior flock hits, the vehicle travels to Michigan frequently which is a known source State for Marijuana as it is legal there.” Deputies then coordinated to intercept the car and stopped it. The driver had been wanted on a bail jumping allegation tied to a domestic violence case. According to the court records described in the reporting, the bail jumping charge was dismissed and he was found guilty only of marijuana possession. This is Wisconsin law and a Wisconsin record, and this firm practices in Florida, so what follows is about the evidentiary move and not about what any of it meant under that state’s law.

Read the sentence again, because the important thing about it is grammatical. “The vehicle travels to Michigan frequently” is not something a deputy watched happen. Nobody observed frequency. That word is the output of a query run against stored historical reads, and it is a conclusion drawn from a database rather than an observation recorded by a witness. The reads themselves are individually trivial: a car passed a camera at a time on a date. The word doing the work in the affidavit is the aggregate.

Florida has the same move on the books, running in the opposite direction, and it is worth knowing about because it is the only recent Florida appellate decision in which plate reader data does real work. In Mathis v. State, No. 4D2024-1543 (Fla. 4th DCA Apr. 8, 2026), the Fourth District affirmed a second-degree murder conviction built substantially on circumstantial proof. Plate readers in Lighthouse Point captured the defendant’s car following the victim’s van into the city in the early morning, and captured it leaving in the same window a neighbor reported hearing noises. Then this, from the court’s own recitation: the car “was in Lighthouse Point for six minutes, and the license plate reader database indicated that [the] car had never been in Lighthouse Point before.”

Never before. That is the same kind of claim as “travels to Michigan frequently,” with the sign flipped. One case used a pattern of reads to make ordinary travel look suspicious. The other used the absence of reads to make one trip look singular. Both are assertions about what a database contains across time, and neither is a report of something a person saw.

Which is why both are testable, and testable in the same way. A claim of frequency invites a count. How many reads, across what date range, and does the number support the adverb, or does three hits in six months get described to a judge as “frequently”? A claim that a car had never been somewhere before is harder still, because proving a negative from a database requires that the database be capable of recording the positive. If the system retains data for thirty days, “never before” means “not in the last thirty days.” If the coverage has gaps, and every network has gaps, then an absence of reads is not evidence of an absence of the car. It is evidence that no camera in that particular set caught it. Those are different propositions and only one of them is what the sentence implies.

Where the constitutional argument stands in Florida includes authority that cuts against the driver. In Schemel v. City of Marco Island, No. 2:22-cv-79 (M.D. Fla. Oct. 17, 2025), residents sued over plate readers mounted at all three bridges onto the island, which recorded every vehicle entering and leaving with the date and time and, on the allegations, retained the data for at least three years. The court dismissed the Fourth Amendment claim with prejudice, holding the complaint pleaded no cognizable privacy interest and no search at all. It distinguished Carpenter v. United States on the ground that a car is not a phone, that people leave their cars while they carry their phones everywhere, and that the island cameras revealed only entry and exit rather than the whole of anyone’s movements. The order cites federal district decisions from Ohio, Nebraska, Alabama, and Illinois reaching the same conclusion about plate readers. Anyone who tells you a Florida court has held that plate reader surveillance is a search has it backwards.

The closest any challenge has come is Schmidt v. City of Norfolk, No. 2:24cv621 (E.D. Va.), the Institute for Justice’s suit over Norfolk’s 172-camera network, where residents showed their own cars had been photographed hundreds of times in a few months. That case survived a motion to dismiss, with the court citing Carpenter, which is further than any other plate reader challenge has gotten. Then, as Courthouse News reported, Judge Mark Davis ruled for the city on the merits on January 27, 2026, reasoning that no search occurs when cameras take discrete pictures at different locations, and WHRO reported that he warned the answer could change and that the plaintiffs plan an appeal to the Fourth Circuit. So even the challenge that got furthest ended where the others did, with a warning attached. Scale, retention, and sharing are the variables courts keep naming, which means every vendor change to those settings moves the constitutional line one way or the other.

The same order left one door standing open, and named it as it went through. The plaintiffs had also pleaded claims under Article I, Sections 12 and 23 of the Florida Constitution, arguing, in the court’s summary, that state law recognizes more robust privacy rights. The court dismissed those claims without prejudice and declined supplemental jurisdiction over them, on the express ground that they raise novel or complex issues of state law and that state courts, not federal courts, should be the final arbiters of state law. So the federal theory was decided and the state constitutional question was not. It was handed to Florida’s courts, and as of this writing no Florida appellate decision has answered it for plate readers.

Those two sections are not interchangeable, and the difference decides which argument is worth making. Article I, Section 12 is Florida’s search and seizure provision, and it ends with a sentence that settles its own scope: “This right shall be construed in conformity with the 4th Amendment to the United States Constitution, as interpreted by the United States Supreme Court.” A following sentence applies the same ceiling to the exclusionary remedy, tying suppression to what would be inadmissible under United States Supreme Court decisions construing the Fourth Amendment. That language was added by amendment in 1982. So Section 12 cannot give a driver more than the Fourth Amendment gives, and any claim that Florida’s search and seizure clause is the more protective of the two is wrong on the text. Whatever happens with plate readers in the federal courts happens under Section 12 as well.

Article I, Section 23 carries no such clause. It reads, in full: “Every natural person has the right to be let alone and free from governmental intrusion into the person’s private life except as otherwise provided herein. This section shall not be construed to limit the public’s right of access to public records and meetings as provided by law.” It was added in 1980 and amended in 1998, it is written to stand on its own, and nothing in it points at federal doctrine. That is the only one of the two provisions capable of producing a different answer than the federal courts have reached, which is presumably why a federal judge declined to decide it and sent it back.

Nobody should oversell that. The obvious response is structural: Section 12 is the specific provision governing searches and seizures, it was amended precisely to bind Florida to federal law, and a court may well conclude that a general right to be let alone cannot be used to obtain what the specific clause forecloses. Whether Section 23 reaches criminal investigative activity at all is an open question and not a settled advantage. The honest statement is that the federal argument is closed in this district, the Section 12 argument goes wherever the federal one goes, and Section 23 is undecided and untested for this technology. That is a narrower thing than a right, and it is still the only place the argument has left to go.

Two more things about Mathis that matter more than the holding. First, the appeal raised sufficiency of the evidence and the constitutionality of the prison releasee reoffender statute. Nobody challenged the plate reader evidence at all, so the Fourth District decided nothing about its reliability, its foundation, or how a “never been here before” claim gets proven. Second, that is the general condition. A search of Florida appellate decisions turns up a handful of cases mentioning plate readers, and none of them tests the evidence. The data arrives, it gets described in a sentence, and it does its work.

So the practical list, when one of these shows up in a case, is short and it is documentary. Get the query rather than the conclusion: who ran the search, what reason was typed into the field, what date range was covered, and how many reads came back. Get the retention period for the system that produced them, because it sets the outer boundary of any claim about what did not happen. Get the coverage, because a negative is worth exactly as much as the completeness of the network behind it. And get the audit trail, for the reasons set out in the sections above. The sentence in the affidavit is a summary of a record. The record is the thing to read.

When the Plate Reader Log Is the Thing That Clears You

Everything above treats the log as something to demand because it may undercut the State. A Florida case pending right now shows the other half of that idea.

In August 2024, Robert Dillon, of Fort Myers, was arrested and accused of attempting to lure a child at a fast food restaurant in Jacksonville Beach. That restaurant is more than 300 miles from his home, roughly five hours away, and he says he had never been there. The connection between him and the accusation was a facial recognition match generated by an AI-assisted system operated by the Pinellas County Sheriff’s Office, which runs the program statewide.

Prosecutors dropped the charge. The arrest was later expunged. In June 2026 the ACLU and the ACLU of Florida filed suit on his behalf against the Jacksonville Beach Police Department, the Jacksonville Sheriff’s Office, the Pinellas County Sheriff’s Office and the officers involved.

According to the complaint, an automated license plate reader search had been run, and it showed no hits on his vehicle anywhere near that restaurant around the time of the offense. The lawsuit alleges that this, along with a restaurant employee’s statement that the suspect was a regular there, was not disclosed.

The same camera network that puts people at scenes had, on the plaintiff’s account, produced a record that he was nowhere near one. A log that records everything records absence as well as presence. A search that comes back empty for your tag, in a place the State says you were, is itself a piece of evidence.

Two cautions belong here in the same breath. These are allegations in a civil case that has not been answered or decided, and nothing above is a finding about any agency or officer. And an absence of reads is not proof of absence: cameras have gaps, a plate can be missed, and someone can travel a route no camera covers. What it is, is a piece of evidence that exists, that can be requested, and that almost nobody thinks to ask for when the machine output points the other way.

The mechanism underneath is the one this whole page keeps returning to. A system produces a score or a match. That output is a lead, and the work of turning a lead into a case is supposed to happen afterward. A plate reader alert is a claim that needs verifying, and so is a face that a program matches to somebody standing 300 miles away.

If a Plate Reader Is Anywhere in Your Case

If a plate reader started your case, the system that produced it kept records, and those records can be demanded. This is the practical half of the page, and it is what this firm actually does with everything above.

When a stop starts with a Flock alert or a plate search, the system that produced it kept records, and this summer proved exactly how detailed those records are. The logs reconstructed one officer’s searches going back to 2024, down to the count and the typed justification on each one. The same kind of record exists behind the alert or the search in a criminal case:

• The capture itself, with its timestamp, location, and photograph.
• The alert or the search that surfaced it, with the user who ran it and the reason entered.
• Whether the plate was actually on a valid hot list, and why.
• The agency’s policy on who may search and for what, and its audit records.

Those records answer real questions. Was the alert the true basis for the stop, or a story assembled afterward? Did the officer confirm the plate matched the car before acting on it? A misread plate or a stale hot list entry is a defective foundation for a stop, and the log is where a defect shows. The fuller treatment of how a plate reader stop gets challenged is on the firm’s ALPR and Flock camera stops page, alongside the law of the stop generally and search and seizure.

The arrests are also a caution against assuming the system is self-policing. One of the three agencies found out from a newspaper. Auditing exists where somebody demands the records, and in a criminal case, that somebody is the defense.

Questions About Flock Cameras

What are Flock cameras?

Flock cameras are automated license plate readers made by a private company called Flock Safety. Each one photographs every vehicle that passes, reads the plate, and logs the plate number, the time, the location, and details like the vehicle’s make, color, and identifying marks. The records go into a searchable database that participating law enforcement agencies can query, and many agencies share access with each other.

Does Pinellas County have Flock cameras?

Yes. St. Petersburg operates about 50 of them, agencies across Pinellas County participate in the shared network, and county commissioners asked the sheriff for a presentation on the technology at their July 21 meeting. On August 27 the St. Petersburg City Council voted unanimously to send its Flock contract to committee, covered in its own section, and the map section above shows what is publicly known about placement.

Does Tampa use Flock cameras?

Yes. Tampa police use Flock along with the company’s audit tool, and agencies across Hillsborough, Pinellas, and Pasco counties participate in the shared network, which means a plate photographed in one city can be searched by agencies in another.

What are Flock cameras used for?

Police agencies use them to alert on stolen vehicles and wanted plates, and to search where a particular plate has been seen. Homeowner associations and retailers install them too, and some share their data with law enforcement. The system is a record of vehicle movement first, and an investigative tool second, which is why who searches it and why matters so much.

How do Flock cameras work?

A camera photographs passing vehicles and software extracts the plate number and vehicle description. Every capture is stored with a timestamp and location. An officer with access can search a plate and see everywhere the network recorded it, and every search requires the officer to enter a reason. That search log is the detail this summer’s arrests turned on, because the system records who searched, what they searched, and the justification they typed.

Are Flock cameras legal in Florida?

There is no Florida statute written specifically for automated license plate readers as of this writing, so their use is governed by each agency’s own policy and the vendor’s terms rather than by a state law. Misusing the system is another matter. Officers charged this summer face felony counts under Florida’s computer crimes statute and the official misconduct statute. Whether the mass collection itself violates the Fourth Amendment is a live question the courts have not settled.

Are Flock cameras unconstitutional?

Nobody has a final answer yet. The Supreme Court held in Carpenter v. United States in 2018 that accessing historical cell phone location records is a Fourth Amendment search requiring a warrant, and in June 2026 it extended that reasoning in Chatrie v. United States, holding that police acquisition of Google Location History data is a search because people have a reasonable expectation of privacy in their movements. A plate reader database raises the same underlying question, a retrospective record of where you have been, assembled without a warrant. Courts are only beginning to apply these cases to license plate readers, and that fight is coming.

Do Flock cameras record speed or give tickets?

The standard Flock plate reader is not a speed camera and does not issue citations. It records that your vehicle passed a point at a time. Two cameras and two timestamps can imply speed, and investigators can use the records that way, but the device on the pole is a camera and a log, not a ticketing machine.

How long do Flock cameras keep data?

Florida law requires a maximum retention period, fixed by a state retention schedule, and within that ceiling the actual period is agency policy. It is also changing. Flock has said it is shortening its default retention from thirty days to seven and will require searches to be tied to a case number by the end of the year. Individual agencies can set their own periods, which is exactly why the answer in your case has to come from records rather than from a company press release.

Can I find out whether a Flock camera was used in my case?

Often, yes. If a plate reader alert or search led to your stop, the system holds a record of the capture, the search, who ran it, and the reason entered. Those records can be demanded in discovery, and agency audit records and policies are generally reachable as public records. The arrests this summer proved the logs are detailed enough to reconstruct an officer’s searches going back years.

Related: ALPR and Flock camera stops in Florida, when police can stop you, and the main criminal defense page.

Further Reading

The primary sources behind this post, so you can read what we read.

1. 404 Media and WIRED: Hackers Stole Flock’s Camera Software, Revealing How the Company Tracks Cars and People (September 16, 2026)
2. WIRED: Flock Has a Powerful New AI Tool for Police. We Got Its Code (August 2026)
3. Flock Safety’s own announcement of the seven day retention default and search safeguards
4. Jacksonville Today: the cameras spreading past public roads, with comments from Rory Safir
5. The Cool Down: Flock cameras aimed at apartment pools, quoting Rory Safir on the gap for HOAs, condominiums and apartments (August 2026)
6. NewsRadio WIOD Miami: Flock cameras explained, a radio segment with forensic lawyer-scientist Rory Safir on the privacy and public safety tradeoffs (August 2026)
7. Fla. Stat. 316.0777, the automated license plate recognition statute, full current text
8. Fla. Stat. 316.0778, the companion retention schedule provision
9. Washington Examiner: the city councils canceling Flock contracts across the country (August 2026)
10. Finding Flock: a running tracker of every city that has canceled or rejected the cameras
11. WCTV: Governor DeSantis calls license plate reader use out of control (August 26, 2026)
12. TMJ4 Milwaukee: the gunpoint stop caused by a stale Flock alert, with the body camera video (August 2026)

This page is general information about Florida law, not legal advice, and it does not create an attorney-client relationship. It describes publicly reported cases and pending charges, and every accused person is presumed innocent. Details are drawn from news accounts and public records current as of this writing, and camera counts, policies, and retention periods change. Every case turns on its own record, and past results do not guarantee a similar outcome.