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

3 rows where ledger = "flock", state = "ID" and vendor = "Flock Safety" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: city, product, amount, spend_date (date)

vendor 1

  • Flock Safety · 3 ✖

state 1

ledger 1

  • flock · 3 ✖
Link rowid vendor city state spend_date product amount ▲ quote source_document mytown_record ledger amount_type dup_rank geo_suspect anomaly state_norm
2323 2323 Flock Safety Kimberly ID 2025-09-09 approve the purchase 25000.0 Flock Safety – City monitor – traffic- life safety health – video system – 4 fixed locations in city limits = initial cost of $12,500.00 installed , including licensing for equipment for one year, plus $12,500.00 for the second year ending fiscal year 2027 , for a total cost of $25,000.00 . https://www.cityofkimberly.org/AgendaCenter/ViewFile/Minutes/_09092025-197 https://mytown.theboringparts.com/city/cityofkimberly.org/#m1587664 flock stated 1 0 0 ID
2324 2324 Flock Safety Kimberly ID 2025-08-26 approve the purchase 25000.0 Council Member Tomlinson motioned to approve the purchase of the Flock Safety Monitor Video system. 4 fixed locations in city limits = initial cost of $12,500.00 installed , including licensing for equipment for one year, plus $12,500.00 for the second year ending fiscal year 2027 , for a total cost of $25,000.00 . https://www.cityofkimberly.org/AgendaCenter/ViewFile/Minutes/_08262025-196 https://mytown.theboringparts.com/city/cityofkimberly.org/#m1587665 flock stated 1 0 0 ID
1877 1877 Flock Safety Twin Falls County ID 2024-03-04 allocate 12700.0 TFPD Lieutenant Garner requested to allocate $12,700 from contingency funds to supplement encumbered funds from FY2023 and budgeted FY2024 funds towards an agreement with Flock Safety for the continued use of 12 Automated License Plate Reader (ALPR) Flock Safety Falcon cameras. https://twinfallsid.api.civicclerk.com/v1/Meetings/GetMeetingFileStream(fileId=12598,plainText=false) https://mytown.theboringparts.com/city/twinfallsid/2024/#m737544 flock stated 1 0 0 ID

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);