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:rms:tyler_ps" and state = "IL" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: amount_type, spend_date (date)

state 1

ledger 1

  • sv:rms:tyler_ps · 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
3632 3632 Tyler Technologies (public safety) Naperville IL 2023-09-19 CAD/RMS software (approve contract) 5279236.0 Approve the award of RFP 22-309, Computer Aided Dispatch/Mobile Data System/Law Enforcement Records Management System, to Tyler Technologies, for an amount not to exceed $5,279,236.50, plus a 3% contingency on implementation cost, and for a ten-year term https://naperville.legistar1.com/naperville/meetings/2023/9/3042_M_City_Council_23-09-19_Meeting_Minutes.pdf https://mytown.theboringparts.com/city/naperville/2023/#m325317 sv:rms:tyler_ps ceiling 1 0 0 IL
3059 3059 Tyler Technologies (public safety) Bloomington IL 2023-06-12 public safety suite maintenance (amend contract) 191897.0 Item 7.I. Consideration and Action to Approve an Amendment to the Contract with Tyler Technologies for Annual Maintenance of the Enterprise Public Safety Suite and the Addition of the Enforcement Mobile Solution in the Amount of $191,897.56, as requested by the Police Department. https://bloomingtonil.api.civicclerk.com/v1/Meetings/GetMeetingFileStream(fileId=4027,plainText=false) https://mytown.theboringparts.com/city/bloomingtonil/2023/#m725336 sv:rms:tyler_ps stated 1 0 0 IL
3649 3649 Tyler Technologies (public safety) Lombard IL 2024-08-15 records management software (renew) 43317.0 Request for a waiver of bids and approval of a one (1) year Agreement with Tyler Technologies in the amount of $43,317.27 for Records Management Software for accessing past police records that are not available through existing records management software through DuPage County. https://legistar1.granicus.com/Lombard/meetings/2024/8/7572_M_Village_Board_of_Trustees_24-08-15_Minutes.pdf https://mytown.theboringparts.com/city/lombard/2024/#m302521 sv:rms:tyler_ps stated 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);