St. Petersburg Council Sends Flock Camera Network to Committee Review

The St. Petersburg City Council voted unanimously this week to refer the city's automated license plate reader program to its Public Services and Infrastructure Committee, opening the first substantive public review of a surveillance network that has grown to roughly 50 cameras since 2022. The referral came after residents packed the chamber to question how the cameras are used, who can search the data they collect and how long that data is retained.

The system is operated by Flock Safety, a vendor whose cameras photograph passing vehicles and log identifying details into a searchable database. Unlike a conventional security camera that records footage reviewed only after an incident, the Flock network builds a continuously updated record of where specific vehicles have been, and that record can be queried across participating agencies well beyond city limits.

For Tampa Bay residents, the review puts a concrete local question on the table: whether a technology adopted through routine procurement should continue operating under rules the council has never debated in public.

How St. Petersburg got here

Flock cameras first appeared in St. Petersburg through a police department pilot program in 2022. In January 2024, the council approved a five-year contract valued at $730,250 that expanded the deployment to roughly 50 cameras. That contract passed as part of a broader consent agenda, meaning it was approved without separate discussion or a dedicated vote on the surveillance question.

Council members have since acknowledged that the procurement path obscured the policy stakes. Council Vice Chair Richie Floyd pushed for the current review, asking for answers on how police use the system, which outside agencies can access St. Petersburg data, how long records persist and what audit controls exist for individual searches.

The pressure did not originate inside city hall. An organized residents' group has spent months documenting camera locations and pressing council members for records, and the referral vote followed a public comment period dominated by opponents of the program. Separately, some cameras in the area have been vandalized, which police have investigated as property crimes.

What the technology does

An automated license plate reader captures an image of a passing vehicle and converts the plate into text, storing that string alongside a timestamp, a location and often descriptive details about the vehicle such as color, body type and visible features. Each individual record is unremarkable. The aggregate is not.

Because the readers operate continuously and because participating agencies can share databases, a search can reconstruct a vehicle's movement history across a wide geography. Investigators use that capability to locate stolen cars, track suspects in violent crimes and find missing persons, and police departments across Florida have credited the systems with clearing cases that would otherwise have stalled.

The civil liberties objection is that these searches generally do not require a warrant. A detective with database access can query a plate without judicial authorization, and the resulting record can reveal patterns that courts have treated as sensitive in other contexts, including visits to medical providers, houses of worship, attorneys or political meetings.

That concern is not hypothetical in Tampa Bay. Multiple law enforcement officers in the region have been arrested and accused of misusing license plate reader databases to track individuals for personal reasons, which is the specific failure mode that audit requirements are designed to catch.

The statewide backdrop

The St. Petersburg debate is arriving as the technology draws attention at the state level. Governor Ron DeSantis said this week that the cameras are useful tools for law enforcement and called on the Legislature to pass legislation regulating their use, a position that acknowledges both the investigative value and the absence of a clear statutory framework.

Florida currently has no comprehensive statute governing automated license plate readers. Individual agencies set their own retention periods, access rules and sharing agreements, which means practices differ substantially between neighboring jurisdictions. A driver crossing from one Tampa Bay municipality into another may be subject to entirely different rules without any way to know it.

Several other states have enacted specific limits, typically addressing retention windows, permissible purposes for a search, audit logging and restrictions on sharing with out-of-state or federal agencies. Any Florida bill would have to reconcile those elements with the state's strong public records law, which governs what portions of such systems are disclosable.

What it means for Floridians

The immediate effect is procedural. Referral to committee does not suspend the program, remove any cameras or change how the police department operates the system today. It creates a forum in which the department must explain its practices on the record and in which council members can propose binding policy.

The broader effect concerns how cities acquire surveillance capability. St. Petersburg's cameras arrived through a contract vote rather than a policy vote, a pattern that has repeated in municipalities across Florida. The review is likely to prompt questions in other city halls about whether surveillance procurement should require a separate public hearing regardless of contract size.

Residents also have a practical interest in the retention question. A short retention window limits the historical reconstruction a search can produce while preserving the tool's value for active investigations, since most investigative queries concern recent events. A long window preserves the full history and the full privacy exposure along with it.

Local impact across the state

Flock and comparable systems are in use in cities and counties throughout Florida, from South Florida municipalities to Central Florida suburbs and North Florida sheriff's offices. Because agencies frequently opt into data sharing, a camera in one jurisdiction can contribute to a search initiated hundreds of miles away.

That interconnection means the St. Petersburg review has effects beyond Pinellas County. If the council imposes limits on outbound data sharing, agencies elsewhere lose visibility into St. Petersburg traffic. If it does not, the current arrangement continues as the regional default.

Sheriff's offices in less populous counties have argued that shared networks are particularly valuable to them, since they cover large geographic areas with small staffs and rely on regional data to track vehicles moving between jurisdictions. Any statewide legislation would have to weigh that operational reality against uniform privacy standards.

The public records question

Florida has among the broadest public records laws in the country, and that framework interacts with surveillance technology in ways that are not always intuitive. Records generated by a government agency are presumptively public unless a specific statutory exemption applies, and active criminal investigative information carries such an exemption.

Automated license plate reader data occupies contested ground within that structure. The individual reads are collected continuously rather than as part of any particular investigation, which complicates the argument that they constitute investigative information. Audit logs showing which officers ran which searches sit in a different category and are generally more accessible.

Those audit logs are the practical accountability mechanism. A search that reveals a pattern of queries unrelated to any case is how misuse is identified, and the value of an audit log depends entirely on whether anyone reviews it. Several agencies nationally have discovered misuse only after an external complaint prompted a review that would not otherwise have occurred.

Residents seeking information about the St. Petersburg system can request records through the city, and the committee review is likely to produce a more organized public accounting than individual requests would.

How other Florida cities have handled it

Municipalities across Florida have taken different approaches to license plate readers, and the variation illustrates that no single model has become standard. Some cities adopted the technology through police department operating budgets without any council vote at all, since the expenditure fell below thresholds requiring approval.

Others have adopted written policies specifying retention periods, permissible search purposes and supervisory approval requirements before a query can be run. Those policies are internal directives rather than ordinances, which means a department can revise them without returning to elected officials.

A smaller number of jurisdictions have codified rules in ordinance form, which requires a council vote to change and creates a more durable constraint. That is the approach the St. Petersburg review could produce if council members choose to move beyond a policy recommendation.

County sheriff's offices operate under a different accountability structure entirely, since sheriffs are independently elected constitutional officers rather than department heads reporting to a commission. A county commission controls a sheriff's budget but has limited authority over operational decisions, which places surveillance policy questions in a different posture at the county level than at the municipal one.

What the review will likely examine

Committee reviews of surveillance programs tend to converge on a common set of questions, and the ones Council Vice Chair Richie Floyd has raised track that pattern closely. Retention period is the first: how long a record of a vehicle passing a camera remains searchable after it is collected.

Access scope is the second. That covers which St. Petersburg personnel can run a search, whether supervisory approval is required, and which outside agencies can query the city's data through shared network arrangements.

Permissible purpose is the third. Some jurisdictions restrict searches to specific enumerated categories, such as active investigations into enumerated offenses, while others permit any law enforcement purpose. The narrower the enumeration, the easier misuse is to identify in an audit.

Audit and reporting is the fourth, covering whether search logs are reviewed on a schedule, who conducts that review and whether aggregate statistics are published. A program with strong rules and no audit function relies entirely on individual compliance, which is the condition under which the documented misuse cases elsewhere in the region occurred.

What is next

The Public Services and Infrastructure Committee will take up the matter and is expected to request documentation from the police department covering search volumes, audit records, retention settings and the list of agencies with access. Committee findings would return to the full council, which could direct policy changes, add contract conditions or leave the program unchanged.

The existing contract runs through its five-year term, which limits the council's near-term options. Cancellation would carry contractual consequences, so the more likely path is a set of operating rules layered on top of the current agreement, addressing retention, permissible search purposes and mandatory audit review.

At the state level, whether a regulatory bill emerges in the next legislative session will depend on whether lawmakers take up the governor's call. A statewide standard would supersede local variation, which would resolve the patchwork problem but could also preempt whatever rules St. Petersburg adopts in the meantime. Local officials reviewing the program now are effectively working against an uncertain deadline.