Davie, Florida • Primary-source investigative summary
Six years.
$695,000+.
Zero votes on Flock.
What the public record shows about Davie’s multi-vendor license plate reader program: how it was built, who decided, what it can do, and what residents have never been asked.
Between 2019 and 2025, Davie’s Police Department built a multi-vendor Automated License Plate Reader program spanning two distinct technology ecosystems, 13 documented purchase orders, and nearly $700,000 in expenditures. Flock Safety — the newer, larger ecosystem — was built entirely without a Town Council vote, public workshop, or published staff recommendation. The earlier Vigilant program received two Council votes; the fixed camera infrastructure those votes did not explicitly cover, and nothing Flock-related ever did.
160.03.100.521-53407 — Other Svc- Fed Forf Exp Justice. Funded by federal asset forfeiture Millenium combined POs (incl. 2019-00000887) →R-2019-186 (July 31, 2019, passed 4-0) authorized "two mobile LPR systems from Millenium Products." R-2021-066 (March 17, 2021, passed by Council, signed by Mayor Judy Paul) authorized the Enterprise Service Agreement for software maintenance and LEARN access. The ILP analytical platform (purchased starting 2022) and the 8 fixed cameras (2021) were procured administratively — neither falls within the explicit scope of what either resolution authorized.
Before Davie purchased a single Flock camera, the Police Chief signed three documents in a 32-day window that formalized the Department’s surveillance relationships — connecting it to a state law enforcement database 330 miles away, a private camera-sharing network, and a vendor whose access rights outlast any individual contract. None of these commitments went before the Town Council. None received public notice. All three preceded the first camera purchase.
The Panama City Beach interagency agreement is not unique to Davie. Pembroke Pines (analysis coming soon!) has an identical agreement with the same agency, using the same Flock platform integration. Both agreements connect South Florida police departments to FDLE extract files through a shared vendor relationship with an agency 330+ miles away. The mechanism — Flock as law enforcement data infrastructure between otherwise unrelated agencies — is the same in both cases.
Police Chief Stephen Kinsey signs an interagency agreement with the Panama City Beach Police Department (330+ miles away). PCB receives FDLE-sourced LPR extract files and agrees to deliver them to Davie via “an existing integration between CJA and contracted LPR vendor (FLOCK) twice a day.” The agreement covers wanted persons, stolen vehicles, sex offenders, suspended licenses, and similar FDLE hotlist categories. No camera purchase has occurred. No public vote. No public notice. PCB Chief Talamantez signed six days later, on August 31.
View Panama City Beach MOU →The Police Chief signs a five-year MOU with Flock Group, Inc., granting the Department access to footage from cameras operated by Non-Agency End Users — homeowners associations, businesses, private residents — who participate in Flock’s shared network. No purchase order. No public vote. No public notice.
View Flock MOU →Section 6.4 of the Government Agency Terms creates a “No-Fee Term” for continued access to the shared private network that survives contract termination indefinitely unless separately and explicitly terminated. The signed agreement commits the Department to Flock’s terms governing data sharing, retention, and third-party access.
View Agency Agreement →By this point: the FDLE hotlist pipeline was in place. The contractual relationship with Flock’s private camera network was formalized. Access rights that outlast any contract had been created. The hardware purchase was the last step in a network that was already operational.
- Three surveillance commitments signed before the first camera purchase — confirmed by document dates
- PCB agreement signed August 25; first camera PO in October — 60+ days later
- FDLE hotlist access (wanted persons, stolen vehicles, sex offenders, suspended licenses) was operational via Flock before Davie had a single Flock camera
- Police Chief signed the PCB MOU and Flock MOU; Town Purchasing Manager signed the Agency Agreement — in no case was the Town Council or Town Manager involved in a documented approval
- The same MOU structure appears at Pembroke Pines (analysis coming soon!), using the same PCB-to-Flock pipeline
- How many privately-operated Flock cameras in or near Davie are accessible through the MOU
- Whether private camera owners know their footage is accessible to law enforcement
- Whether any Town official other than the Police Chief reviewed these agreements
- Whether the No-Fee Term in Section 6.4 has ever been separately terminated
- How many other interagency agreements of this type exist — PCB is the only one confirmed in the record
The Panama City Beach agreement reveals that Flock’s role extends beyond camera hardware. It functions as law enforcement data infrastructure connecting agencies with no other operational relationship — in this case, two departments 330+ miles apart — through a shared vendor integration. The FDLE hotlist pipeline, the private camera network access, and the inter-agency data sharing are all part of the same platform. Town Council authorized none of them.
These systems capture more than license plate numbers. The distinction between a single observation and systematic tracking infrastructure is not philosophical — it is technical and legal. A police officer noting a vehicle in public is one data point. Networked cameras logging every vehicle’s plate, location, time, image, and descriptors across a searchable national database retained for years is something categorically different. Courts have recognized this distinction, and it applies directly to what Davie has deployed.
Plate characters, vehicle images, time, and location for every vehicle in camera range — including vehicles with no connection to any investigation.
Pools plate data from thousands of agencies nationwide. Davie officers searching LEARN search a national database. Davie’s captures are potentially visible to other agencies on the network. The record does not establish which agencies have this access or under what conditions.
An analytical layer that identifies patterns across reads, suggests investigative leads, and cross-references commercial data sources. An intelligence platform, not just a plate reader. ILP subscription costs increase automatically by 4% annually — confirmed verbatim in the vendor quote.
General Order 501 specifies 30-day tactical access and a 3-year maximum within the Vigilant/LEARN platform. The General Order may not address data exported from vendor platforms into case files.
Defined in the signed Agency Agreement (Section 1.29) as “the unique vehicular attributes captured through Services such as: type, make, color, state registration, missing/covered plates, bumper stickers, decals, roof racks, and bike racks.” The system identifies individual vehicles beyond plate numbers alone.
Wing LPR (plate search), Wing Replay (7-day footage replay from integrated third-party cameras), Wing Livestream (real-time video). Hotlists trigger automated alerts from NCIC, AMBER Alerts, and manually entered local watchlists.
Under the Panama City Beach interagency agreement, Davie PD receives FDLE-sourced extract files twice daily through Flock’s platform — wanted persons, stolen vehicles, sex offenders, suspended licenses, and similar categories. This pipeline was signed before Davie owned a single Flock camera.
Under the MOU, officers can search footage from privately-owned Non-Agency End User cameras for investigative purposes — cameras not in the Town’s POs, not paid for by the Town.
Agency Agreement specifies 30-day rolling deletion on Flock’s platform; Wing Replay retains footage 7 days. The record does not establish what retention rules apply to footage downloaded into case files.
About the observation vs. tracking distinction
Officials and vendors often frame ALPR in terms of what officers can already observe: license plates are visible in public, so there’s no expectation of privacy. That framing is accurate for a single observation, but doesn’t apply to what networked, automated, retained systems do.
The difference is friction. A police officer who spots a plate and moves on produces a single data point requiring time and human judgment. Automated cameras scanning every vehicle at multiple locations, logging each read to a searchable database retained for years, produce something different in kind: a reconstruction capability allowing retroactive tracking of where a vehicle has been.
Courts have recognized this. In Carpenter v. United States (2018), the Supreme Court held that accessing historical location data requires a warrant — because the volume and granularity of long-term tracking is categorically different from ordinary surveillance even in public spaces. The ALPR context is analogous: what the accumulation of automated reads makes possible over time differs from what any single observation permits.
About the LEARN national network
LEARN pools plate read data from law enforcement agencies across the country. When an officer in Davie searches a plate, results can include reads from jurisdictions far outside Broward County. This also means Davie’s reads — vehicles captured by Davie cameras — may be visible to other agencies querying LEARN.
The scope of that sharing is not established in the documents reviewed. The record does not show which agencies have LEARN access or under what conditions Davie reads are visible to outside departments. This is a documented open question, not speculation.
How $695,000 in surveillance infrastructure was — and wasn’t — authorized.
The procurement mechanism matters as much as the technology. What follows is a precise account of how Davie’s ALPR program was built, drawn from what the record shows and what it does not.
The Town Council voted twice on the Vigilant program (R-2019-186, 2019; R-2021-066, 2021). It has never voted on any aspect of the Flock Safety program — not the pre-purchase agreements, not the cameras, not the multi-year commitments, not the CRA allocation.
Three surveillance agreements — the Panama City Beach FDLE pipeline, the Flock MOU, and the full Agency Agreement — were all signed by the Police Chief in a 32-day window before the first camera purchase. No Town Manager approval is documented. No Council action preceded or followed.
Resolution R-2019-186 authorized "two mobile LPR systems." In 2021, PO 2021-00000688 ($123,056) funded 8 fixed cameras with poles, trenching, and permanent battery infrastructure — a physically different deployment. R-2021-066 authorized the software agreement, not hardware. No separate Council resolution authorizing the fixed installation appears in the record.
The first $109,485 purchase was coded to a federal asset forfeiture account. Asset forfeiture funds are not appropriated through the general budget process and receive less public scrutiny than regular general-fund appropriations.
The Davie CRA — a separate legal entity — contains a $9,000 Flock line in its FY2026 budget, categorized under “software and industry development.” Both FY2025 and FY2026 budgets were adopted by 5-0 consent vote with no recorded discussion. Across 27 CRA board meetings reviewed (September 2023 through October 2025), there is zero recorded mention of Flock Safety, ALPR, license plate readers, cameras, or surveillance technology.
In April 2025, the CRA Board ratified 559 Town and CRA contracts in a single 5-0 consent vote (CRA Resolution R-2025-013). Contracts included Vigilant Solutions, Millenium Products, Clearview AI, GrayKey, and Berla iVE. No deliberation recorded for any of them. Flock Safety did not appear on this list — and does not appear in the Town’s October 2025 master contract registry either.
As of October 7, 2025, Flock Safety does not appear in the Town’s 582-contract master registry (Town Contract List). Davie has an ongoing vendor relationship with active purchase orders and annual CRA budget allocations, but no formally registered contract in the Town’s own contract management system. The record does not show an explanation for this gap.
Each step is individually defensible under administrative rules. Taken together, they describe a program built, expanded, and committed to multi-year contracts without public deliberation at any stage.
The broader surveillance stack
The April 2025 bulk ratification revealed ALPR is one piece of a much larger surveillance technology environment. Every tool below was approved in the same 5-0 consent vote, no recorded deliberation for any of them. This section documents it for context: the governance pattern applies across the full technology environment. Deflock Broward’s specific focus is license plate readers.
- Vigilant Solutions LEARN/ILP
- Millenium Products (LPR hardware)
- Flock Safety Wing Suite ⚑ absent from ratification list
- Verra Mobility (red light cameras)
- CovertTrack Group (GPS tracking, 2 contracts)
- Clearview AI (active through Sept 2027)
- DataWorks Plus (biometrics / mugshot)
- GrayKey / Magnet Forensics (iPhone unlocking)
- Magnet Axiom, Griffeye ML, Witness-DV Examiner
- MSAB / XRY
- Oxygen Forensics
- Berla iVE — extracts location history, contacts, and recent destinations from vehicle infotainment systems
- Pen-Link (communications analysis)
- L8NT (open source intelligence)
- Callyo (investigative software)
- LeadsOnline (pawn/secondhand reporting)
- BRINC Drones
- Axon (body camera / investigative platform, 2 contracts)
Every item above approved in a single consent vote. No deliberation recorded for any of them. Source: CRA Resolution R-2025-013, April 2025.
The procurement record establishes that the program exists, what it cost, and how it was authorized. The following are factual gaps the record does not answer — neutral, open questions, not accusations.
Who requested the initial Vigilant deployment in 2019? Who decided to add Flock in 2022? The Vigilant ESA procurement chain is documented through R-2021-066: Captain Jeremy Stone requested it, Purchasing Manager Brian K. O’Connor approved it, Budget and Finance approved it, Town Administrator Richard J. Lemack approved it, Council passed R-2021-066, Mayor Judy Paul signed the contract. No equivalent chain is documented for any Flock decision — no staff report, budget justification, or internal recommendation appears in the public record at any stage. Whether the Town Manager or elected officials had input is not established.
Resolution R-2019-186 (July 31, 2019) authorized "two mobile LPR systems." PO 2021-00000688 ($123,056) deployed 8 fixed cameras with poles and trenching. Whether a separate Council authorization exists for the fixed infrastructure — or whether it was executed administratively without a Council vote — is not established in the record.
Purchase orders document a minimum of approximately 35 Flock Falcon cameras plus 8 fixed Vigilant cameras plus mobile units. Actual current deployment is not established in the documents reviewed.
The $9,000 FY2026 CRA Flock line may fund separate cameras within the CRA boundary, or it may be a cost allocation from the PD’s existing fleet. The record does not establish which. Who operates them, whether General Order 501 governs them, and whether they are under a separate or shared Flock account is not documented.
Flock Safety does not appear in the Town’s October 2025 master contract registry, despite active purchase orders and annual budget allocations. Vigilant Solutions and Millenium Products do appear. The record does not show an explanation for why an ongoing vendor relationship is absent from the Town’s formal contract management system.
The Panama City Beach interagency agreement specifies that Davie receives FDLE LPR extracts twice daily via Flock. The agreement does not specify which extract categories are included, what retention applies to those files on Davie’s end, or whether FDLE authorized downstream redistribution through a private vendor. Whether other interagency agreements of this type exist — PCB is the only one confirmed in the record — is not established.
Which agencies can query Davie’s plate reads through LEARN? Under what conditions? With what accountability? The record confirms Davie is connected to LEARN and subscribed to ILP. It does not establish the scope of cross-agency access or what audit mechanisms govern it.
How many privately-operated Flock cameras accessible to Davie PD through the MOU are located in or near Davie? Do those camera owners know their footage is accessible to law enforcement? The MOU grants access; the documents reviewed do not establish its scope.
General Order 501 specifies retention limits within the Vigilant/LEARN platform. When footage is exported into case files, the record does not establish what retention rules apply to those copies, or whether those exports are tracked and audited.
Flock subscriptions plus ILP renewal (with 4% annual escalator) plus CRA contribution plus message board maintenance equals an unknown current annual cost. No document in the reviewed set provides a current total annual expenditure figure for the combined program.
Concrete asks for elected officials.
Residents should expect specific, enforceable commitments — not general assurances. These safeguards do not eliminate the underlying tracking capability. They make it visible, measurable, and politically accountable. If the Town and CRA cannot commit to them, residents are being asked to accept expanding surveillance infrastructure on trust alone.
Get involved.
This program was built without public deliberation. Changing that requires public presence.
- Attend Town Council: Ask about retention limits, access controls, LEARN sharing, interagency data agreements, and independent auditing during public comment.
- Attend CRA Board meetings: Ask them to explain the FY2026 Flock line item and why Flock has no registered contract in the Town system.
- Share this page: Help neighbors understand what has been deployed, who decided, and what questions remain unanswered.
- Help analyze records: Email deflockbroward@proton.me to assist with public records work or community outreach.
- Millenium Products — combined purchase orders 2019–2025 (Vigilant ecosystem: POs 2019-887, 2020-100, 2021-688, 2022-516, 2023-704, 2024-536, 2024-614, 2025-230, 2025-683)
- Insight Public Sector — combined purchase orders 2022–2025 (Flock ecosystem: POs 2023-217, 2023-409, 2024-273, 2025-617)
- Flock Data Sharing MOU — signed before first camera purchase (Aug. 30, 2022)
- Flock Agency Agreement with addendum — signed by Police Chief (Sept. 26, 2022)
- Panama City Beach PD Interagency Agreement — FDLE LPR extracts via Flock twice daily; Davie Chief signed Aug. 25, 2022 — before first camera purchase
- General Order 501 — LPR Systems use policy (effective Sept. 6, 2023)
- CRA FY2026 Adopted Expenditures Budget — Flock Safety line item ($9,000)
- CRA FY2025 Adopted Expenditures Budget
- CRA Resolution R-2025-013 — 559 contracts ratified in bulk (Apr. 16, 2025)
- Town master contract list — Flock Safety absent (Oct. 7, 2025)
- Notice of Intent NTSS-JA-21-09 — Software Maintenance and Access to License Plate Data (Vigilant Solutions)
- CRA 2025 Redevelopment Plan — community policing framing without mention of surveillance technology