surveillance_spending

A DISCOVERY INDEX of surveillance and police-technology dollar figures found in local government meeting records across 130+ named vendors — NOT a table of confirmed spending, and NOT safe to SUM. An audit on 2026-07-29 found aggregate views were adding amounts that must not be added: the same procurement recurs at committee, council, approval, amendment and renewal stages; "not to exceed" figures are authorization ceilings, not payments. Use the canned query "the CONSERVATIVE total" for any number you intend to publish, and "data-quality report" to see what is flagged. Columns added for this: `amount_type` (stated / ceiling / proposed / recommended / estimated), `dup_rank` (>1 = redundant copy), `geo_suspect` (city disagrees with the source link), `anomaly` (implausible figure), `state_norm` (normalized state). Vendors covered include ALPR (Flock, Vigilant, Genetec), body cameras/tasers (Axon, WatchGuard, Utility, Getac), gunshot detection (ShotSpotter/SoundThinking), face recognition (Clearview AI, DataWorks Plus), fingerprint biometrics (Idemia AFIS/Livescan, filed separately under `sv:biometrics`), data fusion and OSINT (Fusus, Peregrine, LexisNexis Accurint, Thomson Reuters CLEAR), phone forensics (Cellebrite, GrayKey, Magnet), drones (Skydio, BRINC, DJI), cameras/VMS (Verkada, Avigilon), cell-site simulators, CAD/RMS records systems, photo enforcement, jail-call and student monitoring. Every row carries a VERBATIM quote from the minutes and a link to the source document, and a row only publishes if that quote was found character-for-character in the source text. READ THE `ledger` COLUMN: `sv:<category>:<vendor>`. `radio_infra` (two-way radios), `rms` (records/CAD software), `biometrics` (fingerprints) and `not_surveillance` are NOT surveillance sensors — exclude them before quoting any surveillance figure.

Data license: CC BY 4.0 · Data source: MyTown

2 rows where ledger = "sv:alpr:vigilant", state = "FL" and vendor = "Vigilant Solutions" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: spend_date (date)

vendor 1

  • Vigilant Solutions · 2 ✖

state 1

ledger 1

  • sv:alpr:vigilant · 2 ✖
Link rowid vendor city state spend_date product amount ▲ quote source_document mytown_record ledger amount_type dup_rank geo_suspect anomaly state_norm
3684 3684 Vigilant Solutions Doral FL 2021-08-11 ALPR cameras (purchase) 83105.0 AUTHORIZING THE CITY MANAGER TO PURCHASE LICENSE PLATE READER CAMERAS AND ASSOCIATED EQUIPMENT FROM VETTED SECURITY SOLUTIONS, AS A SOLE SOURCE PROVIDER BY VIGILANT SOLUTIONS EXCLUSIVE AND PREFERRED RESELLER IN THE STATE, IN AN AMOUNT NOT TO EXCEED $ 83,105.00; https://legistar1.granicus.com/Doral/meetings/2021/8/1352_A_Council_Meeting_21-08-11_Meeting_Agenda.pdf https://mytown.theboringparts.com/city/doral/2021/#m278691 sv:alpr:vigilant ceiling 1 0 0 FL
3596 3596 Vigilant Solutions Pembroke Pines FL 2025-02-19 LPR trailer retrofit (approve contract) 49975.0 TO APPROVE ENTERING INTO AN AGREEMENT WITH VETTED SECURITY SOLUTIONS, LLC ., AS THE SOLE SOURCE AUTHORIZED RE -SELLER AND SERVICE PROVIDER OF VIGILANT SOLUTIONS, INC. IN THE STATE OF FLORIDA, FOR RETROFITTING TWO MOBILE VIGILANT SOLUTIONS’ LICENSE PLATE READER (LPR) TRAILERS IN THE AMOUNT OF $ 49,975.76 AND TO ENTER INTO A ONE-YEAR MAINTENANCE AGREEMENT FOR OTHER LPR TRAILERS AND EQUIPMENT, IN AN AMOUNT NOT TO EXCEED $ 30,000, PURSUANT TO SECTION 35.18(C)(3) AND 35.18(C)(7)(D) OF THE CITY’S CODE OF ORDINANCES. https://ppines.legistar1.com/ppines/meetings/2025/2/1699_A_City_Commission_25-02-19_Meeting_Agenda.pdf https://mytown.theboringparts.com/city/ppines/2025/#m337037 sv:alpr:vigilant ceiling 1 1 0 FL

Advanced export

JSON shape: default, array, newline-delimited

CSV options: 

CREATE TABLE surveillance_spending (
  vendor TEXT, city TEXT, state TEXT, spend_date TEXT, product TEXT,
  amount REAL, quote TEXT, source_document TEXT, mytown_record TEXT, ledger TEXT, amount_type TEXT, dup_rank INTEGER, geo_suspect INTEGER, anomaly INTEGER, state_norm TEXT);
CREATE INDEX ix_surv_vendor ON surveillance_spending(vendor);
CREATE INDEX ix_surv_state ON surveillance_spending(state);
CREATE INDEX ix_surv_amount ON surveillance_spending(amount);
CREATE INDEX ix_surv_ledger ON surveillance_spending(ledger);