Hollywood, Florida • Primary-source investigative summary

Eleven years.
$5.5 million.
“The entire city perimeter.”

Hollywood's police license plate reader program began in 2014 with hardware that uploaded plate reads to a national commercial database from its first day — a network enrollment the Commission was never separately asked to approve. Eleven years and roughly $5.5 million later, the police department's stated goal is to “blanket the City” with cameras “covering the entire city perimeter” — a sentence that appears in a budget narrative, not in any policy the Commission ever debated. Along the way: a use policy that predates the program's first authorization by 40 months, contracts that took effect before the votes that authorized them, and a vendor “exit” in 2025 that wasn't one — new Vigilant cameras were being enrolled in the same national database even as the old Vigilant contract was terminated.

$5.5M+
Documented police ALPR expenditures (conservative)
2014–2025. Excludes unknowns: full Phase 1/3 costs, recurring LEARN subscriptions, ceiling purchases.
~75%
Of ALPR votes passed on the consent agenda
~19 of ~27 votes. Two staff presentations in eleven years.
40+
Months the ALPR policy predates the first Commission vote
SOP 228.1: October 2010. First authorization: February 2014.
3
Counties in HPD's plate-data reach
Broward + Miami-Dade + Pinellas, via two $0 MOUs whose titles never say “license plate.”
Flock Safety network (2024–present)
60 city cameras + 6 Emerald Hills district cameras + unknown private “Hollywood Safe” cameras
Vigilant/LEARN (2014–present — still growing)
7+ new LEARN-enrolled cameras since 2025 / 7 ALPR trailers (status post-termination unclear)
Vendors Vigilant/Motorola (via Safeware → Vetted → ER Tech) Flock Safety (via Insight Public Sector) gtechna (parking) Blue Line Solutions (school zones)

Hollywood's police ALPR program spans eleven years, four procurement vehicles, and one constant: from the founding purchase in February 2014 — a quotation co-branded “Vetted Security Solutions & Safeware Inc — The Safeware Team” with Vigilant Solutions hardware — every camera specified a connection to LEARN, Vigilant's national commercial plate-read database. The founding document says it plainly: the trailers communicate “through cellular directly to the LEARN server.” The Commission approved equipment; it was never separately asked whether Hollywood's plate reads should flow into a national commercial database. That enrollment was a technical specification in a vendor quote, not a policy decision — and it has now outlasted the vendor relationship that created it.

Date
Action
Amount
Funding / method
Feb 2014
R-2014-038 — founding purchase: Vigilant MERC-LPR trailers, “The Safeware Team,” LEARN-connected from day 1
$146,838
US Communities piggyback (consent)
Jul 2014
R-2014-204 — three-phase CCTV/ALPR program + Vigilant ESA (ESA executed one week before the vote)
$1,500,000
Incl. $329,506 federal forfeiture (Phase 2)
2015–2016
More trailers + camera poles + MERC-V video trailers; RTCC concept first appears in a procurement form
$231,009
UASI grant + forfeiture + piggyback
2018
R-2018-023 — maintenance RFP; SECG wins. The only competitive ALPR solicitation in eleven years
$275,440
Competitive RFP (consent)
2018–2023
Four JAG grant purchases — fixed cameras and trailers, via county pass-throughs
~$157,000
Federal JAG grants (consent)
2019
Two Safeware fixed-LPR installs: A1A beach approach + Washington Park residential corridor
$103,290
UASI 2017 + JAG 2016 grants
Apr 2022
R-2022-110 — Vetted BPA under the “Best Interest” exception: no competitive bid of any kind
$325,000
§38.41(C)(9) exception (consent)
Sep 2023
R-2023-270 — Vetted service agreement (7 ALPR trailers + 53 CCTV); $661K/yr ceiling; routing form dated 5 months pre-vote
$186,448
§38.41(C)(11)(a) maintenance exception (consent)
Sep 2023
R-2023-265 — Insight Public Sector general IT BPA on OMNIA/Cobb County contract — the same vehicle used for Flock a year later
$500,000 ceiling
OMNIA piggyback (consent)
Sep 2024
R-2024-315 — Flock Safety: 60 Falcon cameras via Insight. Contract term began ~July 16 — two months before the vote
$459,000 ($1M ceiling)
OMNIA piggyback (regular agenda)
Sep 2024
R-2024-308 — UASI FY2023 grant incl. 2 more ALPRs; found only by scraping DocumentCenter, not in Legistar search
$333,497 ($80K ALPR)
Federal UASI grant
Mar 2025
R-2025-083 — “Dual-Purpose Camera Systems”: new Vigilant LPR + Avigilon CCTV, scope of work says “bring them into LEARN.” Neither “Vigilant” nor “LEARN” appears in any Commission-facing document
$1,200,000 ceiling
GSA piggyback (regular agenda, no discussion)
Aug 2025
R-2025-279 — Vetted terminated early at the city's request; equipment return negotiated by email
Termination for convenience
Total documented
Conservative police-ALPR total. Excludes: full Phase 1/3 execution costs from the 2014 $1.5M program; recurring Vigilant/LEARN subscriptions (never separately disclosed); purchases under the Vetted $661K and Insight $500K ceilings; the parking LPR program (~$446K+, separate); and school-zone speed cameras ($0-to-city revenue share, $1.74M year-one citations).
~$5.5M+
The 60-year property commitment nobody voted on as a program

Three fixed ALPR sites sit on private property under 10+10-year auto-renewing access agreements: 5999 Pembroke Road (Walgreens, 2020 — since transferred to Limestone WGFL LLC), 5650 Stirling Road (ARSC Inc., 2022), and 2700 N State Road 7 (Storage Express III, 2025). Combined maximum commitment: 60 years of surveillance obligations, each approved individually as a routine item. The agreements run with the property — a future owner inherits the cameras. And the labels diverge: the Commission-facing resolution titles say “CCTV Project”; the signed agreements say “A.L.P.R Equipment.”

Hollywood runs three separate LPR programs under three departments — police, parking enforcement, and school-zone speed cameras — with no combined data governance, retention, or oversight policy anywhere in the Commission record. The police network alone now reaches across three counties.

The observation vs. tracking distinction
Observation

An officer sees a plate in public. One data point, bounded by time, attention, and presence.

Systematic tracking

Networked cameras log every passing vehicle's plate, image, location, and time into searchable databases — a retroactive movement record. The Supreme Court recognized the difference in Carpenter v. United States (2018).

Hollywood's own department describes the goal: cameras “covering the entire city perimeter.” Perimeter coverage is not observation. It is a log of everyone who enters or leaves.

Flock Safety
60 Falcon cameras + FlockOS Advanced + “Hollywood Safe”
What it captures

Plate, state, vehicle type, make, color, missing/covered plates, bumper stickers, decals, roof racks — a machine-learning “Vehicle Fingerprint” per read. Flock's January 2024 terms added audio capture to the footage definition; the Commission was never told.

Network

State and nationwide plate lookups across other agencies' and private Flock cameras; real-time NCIC integration; unlimited custom watchlists.

The private layer

“Hollywood Safe” lets residents and businesses register or integrate private cameras — including live feed access for HPD — growing the network beyond the 60 authorized cameras by an unknown number. Emerald Hills' tax district added 6 more on its own.

Data terms

30-day server deletion — but Flock keeps a perpetual, irrevocable license to use footage as anonymized “Aggregated Data” for commercial purposes, surviving termination. Hardware stays Flock's property.

Vigilant / Motorola LEARN
2014–present — the network that outlived its own “exit”
Eleven years of reads

Every Hollywood Vigilant camera since 2014 uploaded to LEARN, a national commercial database holding billions of plate reads. Enrollment appeared only in vendor quotes — never in a resolution.

Still growing

March 2025: new Vigilant cameras at Lyons Park, Pembroke Road, and State Road 7, installed by ER Tech/Broadcast Systems with scope-of-work instructions to “bring them into LEARN” — under a $1.2M ceiling allowing more sites without another vote.

The data question

Terminating Vetted did not retrieve anything: eleven years of Hollywood-contributed reads remain on Motorola's platform with no publicly disclosed retention limit.

Cross-county data sharing
Two $0 MOUs, February 5, 2025 — consent agenda, no discussion
Miami Beach PD (R-2025-038)

Full access to Miami Beach's Vigilant LPR criminal-justice system. Resolution title: “MOU with Miami Beach Police Department.” The words “license plate” appear nowhere in it.

Pinellas Sheriff (R-2025-037)

FDLE LPR hot-list extracts via the Sheriff's Axon platform. Same stealth titling; same consent agenda; items 20 and 21, passed together without a word.

Why 2025?

FBI CJIS Memo 2022-11 reclassified FDLE LPR extracts as Criminal Justice Information requiring formal agreements — the 2+ year gap suggests informal sharing predated the paperwork.

Parking + school zones
Separate departments, separate vendors, no shared policy
Parking LPR (gtechna)

Citation enforcement; garage and mobile units; codified into the city code in July 2025 at a public hearing with zero speakers.

School-zone cameras (Blue Line Solutions)

$0-to-city revenue share: 28,030 citations and $1.74M in year one, with $504K to the vendor and the remainder funding “police technology citywide” — enforcement revenue cross-subsidizing the surveillance build-out.

How it was bought

One competitive bid in eleven years. Everything else rode piggybacks, grants, and exceptions — usually on consent, sometimes before the vote.

The sole-source lock-in chain

A 2014 cooperative purchase became a decade of dependency no one ever chose out loud.

1
2014 — Safeware/Vigilant selected via US Communities piggyback. The form asks whether the purchase might restrict future procurement to a single vendor. Answer: No.
2
2014–2021 — every hardware addition uses the same cooperative contracts, deepening Vigilant integration.
3
2022 — “Best Interest” exception (§38.41(C)(9)): $325,000 to Vetted with no competitive bid of any kind.
4
2023 — maintenance-with-original-vendor exception (§38.41(C)(11)(a)): the incumbent is now formally exempt from competition.
5
2025 — exiting requires the vendor's cooperation: equipment return, access revocation, password handover, negotiated by email.
The cooperative-contract mechanism — marketed as competitive because someone else's government ran the bid — produced eleven years of vendor lock-in the Commission never faced as a decision.
Contracts first, votes second — a systemic pattern

At least four major instruments were operative before the Commission authorized them: the 2014 Vigilant ESA (executed one week pre-vote), the 2023 Vetted service agreement (routing form dated five months pre-vote), the 2024 Flock contract (term running two months pre-vote), and the 2025 Storage Express property agreement (signed two months pre-vote). The City Manager also extended the Vetted BPA in May 2023 without Commission authorization — disclosed only in a WHEREAS clause months later. The votes ratify what is already happening; they do not decide it.

What the agenda title said
What the document actually was
“CCTV Project” (property access resolutions, 2020–2025)
Signed agreements titled “A.L.P.R Equipment” — 20-year license plate reader installations
“Dual-Purpose Camera Systems” (R-2025-083, $1.2M)
Vigilant LPR cameras with instructions to “bring them into LEARN” — neither word appears in any Commission-facing document
“MOU with Bob Gualtieri, As Sheriff Of Pinellas County”
ALPR–FCIC integration: FDLE license plate hot-list extracts
“MOU with Miami Beach Police Department”
Full access to Miami Beach's Vigilant LPR criminal-justice system
“Insight Public Sector” general IT agreement (2023)
The contract vehicle that delivered 60 Flock surveillance cameras twelve months later
$6.27 million in named surveillance projects vanished from the capital plan — and re-emerged as piggyback purchases

The FY2021 and FY2022 budgets scheduled four named CCTV/ALPR corridor phases — State Road 7, I-95, Sheridan Street, Hollywood Boulevard — totaling $6.27M, debt-financed. In the FY2023 budget, all four phases are simply gone: no vote, no explanation, replaced by a $300K generic line. The 2019 bond didn't absorb them ($72.55M went to the police headquarters, $0 to CCTV/ALPR — confirmed on the city's own GOB page). Instead, the corridor build-out resurfaced through procurement: the 2025 Storage Express access agreement and ER Tech contract execute the State Road 7 plan — outside the capital-planning system that once named it, at a fraction of the visibility. Budget goals show the same pattern in miniature: "purchase six ALPRs" appears as a goal in FY2023 and FY2024, then as a completed accomplishment in FY2025 — with no identifiable Commission vote in between. Six LPRs and fifteen CCTV cameras reported purchased in FY2024 correspond to no resolution in the record.

Hollywood has a written ALPR policy — and its history, obtained through public records requests in 2026, tells the governance story better than any single contract. HPD's SOP 228.1 was written in October 2010 — forty months before the Commission's first ALPR vote — and re-certified word-for-word in August 2013, six months before that vote. The department was maintaining governance documents for a surveillance program the Commission had not yet authorized. Across four versions and fifteen years, the policy's accountability mechanisms did not grow with the program. They shrank.

Version
What changed
Oct 12, 2010 — original (Lt. Scott Pardon)
Mobile patrol units only; NCIC/FCIC hot lists; quarterly paper LPR Alert Log; 365-day retention. Predates any Commission authorization by 40 months.
Aug 13, 2013 — “First Review”
Word-for-word identical to 2010 — an accreditation box-check, six months before the first ALPR vote (Feb 2014).
Apr 30, 2020 — first substantive revision (Chief O'Brien)
Finally acknowledges reality six years in: adds trailers, Vigilant's TAS software, the Fusion Center, PowerDMS. Replaces the quarterly log with a per-event Shift Commander's Log.
May 15, 2025 — current (Chief Devlin)
Names Motorola and Flock; sets 1-year/30-day query windows — and removes the standing accountability log entirely, leaving only arrest-affidavit language. Four pages for a three-county, multi-network program.
Measured against the state's own guidelines: written as if the networks don't exist

FDLE's CJJIS Council issued statewide ALPR guidelines on November 13, 2024 — annual audits, enumerated permissible purposes, agency data ownership, dissemination recordkeeping. HPD revised SOP 228.1 six months later, in May 2025, and adopted none of it: no audit procedure, no enumerated purposes, no dissemination logging, no chief-executive sign-off for data sharing, and no reconciliation with Flock's perpetual commercial license over the footage. The same RTIC personnel who deploy and operate the system are also its designated administrators — operators, users, and auditors in one. The policy's data-sharing clause copies the permissive half of FDLE's language and omits the accountability half.

The retention numbers are not what they seem

SOP 228.1's stated retention — one year for Motorola data, 30 days for Flock — governs only HPD's own query window. It does not touch the eleven years of Hollywood plate reads held on Motorola's LEARN platform with no disclosed limit, or Flock's perpetual right to the footage as commercial “Aggregated Data.” The policy limits what officers can search. It does not limit what the vendors keep.

What's unclear

These are factual gaps, not accusations. The record establishes what was bought, when, through what mechanisms, and under what policy. The following questions remain genuinely unanswered.

On the data
What happened to eleven years of Hollywood-contributed plate reads on the LEARN platform after the Vetted termination? Nothing in the termination correspondence addresses data disposition.
Do the FDLE-recommended annual ALPR audits happen at all? The policy doesn't mention them; no audit record has surfaced.
How many private cameras feed HPD through “Hollywood Safe”? The effective network size is unknown even in order of magnitude.
On the contracts
The full executed Flock Safety contract appears nowhere in the public record — only the reseller's quotation made it into Legistar.
Were purchases made under the Vetted $661K and Insight $500K ceilings beyond the documented amounts?
The executed 2014 Vigilant ESA — with the language revisions the Commission required as a condition of its only substantive amendment in eleven years — has never been located.
On the record
What ALPR program existed before 2014? A use policy written in 2010 and re-certified in 2013 strongly implies one — grant-funded, loaned, or below the Commission threshold.
The 6 LPRs and 15 CCTV cameras reported as FY2024 accomplishments match no identified resolution. What procurement authority bought them?
Where are the 60 Flock cameras? No public map exists.
Who maintained the camera network between February 2021 and April 2022? A ~14-month gap separates the SECG contract's end and the Vetted BPA.
What to ask for

The Commission has voted twenty-seven times on this program. It has deliberated about twice. Ask it to govern.

These safeguards do not remove the tracking capability — they make it visible, measurable, and politically accountable. The deeper question, which the record supports asking plainly, is whether a system built this way can be constrained by policy at all.

Transparency
📊
Publish the executed Flock contract and a camera map
The public record contains a reseller quotation, not the contract. Publish the agreement, its data terms, and where the 60 cameras are.
🔍
Annual public transparency report — per FDLE's own guidelines
Reads, queries, hot-list alerts, external agency access, audits performed. The state guidelines HPD's policy ignores already prescribe this.
📋
End stealth titling
Require that any resolution touching license plate readers says so in its title. “CCTV Project” and “Dual-Purpose Camera Systems” concealed ALPR expansions from anyone reading the agenda.
Governance
📄
A real vote on the Vigilant/LEARN relationship
The Commission has never been asked whether Hollywood should participate in a national commercial plate database. Eleven years in, with new cameras still being enrolled, put the question on a regular agenda — including what happens to the historical data.
One policy for three programs — with separated oversight
Police, parking, and school-zone LPR run under three departments with no unified retention, access, or audit rules — and the police system's operators are its own auditors. Adopt a single Commission-approved policy with oversight independent of the RTIC.
🔒
Restore the accountability log the 2025 revision deleted
From 2010 to 2020 the policy required a standing record of LPR alerts. The current version keeps no log at all. Reinstate it — and add the FDLE-recommended annual audit.
🎤
No surveillance on consent; no ratifying after the fact
Require surveillance items to appear on the regular agenda with staff presentation, and prohibit executing surveillance contracts before the authorizing vote — the documented pattern in 2014, 2023, 2024, and 2025.

Make your presence
known.

“Blanket the City” is currently a budget-narrative goal, not a debated policy. Public presence at Commission meetings is what turns departmental momentum into a public question.

  • Attend City Commission meetings: Ask who approved the goal of covering “the entire city perimeter,” what happened to eleven years of LEARN data, and why ALPR items appear under titles that never mention license plates.
  • Email your commissioner: Ask them to put the Vigilant/LEARN relationship and a unified three-program LPR policy on a regular agenda — and to require that surveillance contracts stop taking effect before the votes that authorize them.
  • Share this page: Help neighbors understand what has been built, what it can do, and what questions remain unanswered.
  • Help with public records work: Contact deflockbroward@proton.me to assist with records analysis or community outreach.