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 = "sv:radio_infra:motorola", state = "IL" and vendor = "Motorola Solutions" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: amount_type, geo_suspect, spend_date (date)

vendor 1

  • Motorola Solutions · 3 ✖

state 1

ledger 1

  • sv:radio_infra:motorola · 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
2832 2832 Motorola Solutions Woodstock IL 2026-03-03 two-way radios (purchase) 212100.0 Approval of Resolution #26-R-16, known as DOC. 2, that authorizes the City Manager, or his designee, to execute a purchase agreement with Motorola Solutions for the acquisition of 40 APX N50 portable radios and accessories for a total of $212,100. https://www.woodstockil.gov/AgendaCenter/ViewFile/Minutes/_03032026-583 https://mytown.theboringparts.com/city/woodstockil.gov/#m1152512 sv:radio_infra:motorola stated 1 0 0 IL
3331 3331 Motorola Solutions DuPage County IL 2025-01-08 two-way radios (amend) 55582.0 ETS-R-0074A-21 - Amendment to Resolution ETS-R-0074-21, issued to Motorola Solutions, Inc. PO 921051/5522-1, to allow for the exchange of Remote Speaker Microphones as requested by Fire agencies, to increase the funding in the amount of $55,582.20, resulting in an amended contract total of $37,410,364.43, an increase of 0.15%. https://dupage.legistar1.com/dupage/meetings/2025/1/11023_M_ETSB_-_Emergency_Telephone_System_Board_25-01-08_Summary.pdf https://mytown.theboringparts.com/city/dupage/2025/#m560269 sv:radio_infra:motorola stated 1 1 0 IL
2737 2737 Motorola Solutions Vernon Hills IL 2025-06-03 two-way radios (authorize payment) 33046.0 An ordinance authorizing the payment of annual airtime subscription fees to Motorola for Police operations on Starcom 21 radio system in an amount not to exceed $33,046.00. https://www.vernonhills.org/AgendaCenter/ViewFile/Agenda/_06032025-1296 https://mytown.theboringparts.com/city/vernonhills.org/2025/#m1298661 sv:radio_infra:motorola ceiling 1 0 0 IL

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