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 state = "IL" and vendor = "Mark43" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: spend_date (date)

vendor 1

  • Mark43 · 3 ✖

state 1

ledger 1

Link rowid vendor city state spend_date product amount ▲ quote source_document mytown_record ledger amount_type dup_rank geo_suspect anomaly state_norm
3849 3849 Mark43 Aurora IL 2025-08-05 CAD/RMS system (approve contract) 4020267.0 A Resolution authorizing the director of purchasing to enter into a five year agreement with Mark43, Inc. of New York, New York and ancillary vendors at a cost of $4,020,267.64 for the purposes of obtaining a CAD/RMS system and developing interfaces required for system functionality. https://legistar1.granicus.com/aurora-il/meetings/2025/8/4507_M_Committee_of_the_Whole_25-08-05_Meeting_Minutes.pdf https://mytown.theboringparts.com/city/aurora-il/2025/#m74213 sv:rms:mark43 stated 1 0 0 IL
3851 3851 Mark43 Aurora IL 2025-08-12 CAD/RMS system (enter into a five year agreement) 4020267.0 A Resolution authorizing the director of purchasing to enter into a five year agreement with Mark43, Inc. of New York, New York and ancillary vendors at a cost of $4,020,267.64 for the purposes of obtaining a CAD/RMS system and developing interfaces required for system functionality. https://legistar1.granicus.com/aurora-il/meetings/2025/8/4527_M_City_Council_25-08-12_Meeting_Minutes.pdf https://mytown.theboringparts.com/city/aurora-il/2025/#m74193 sv:rms:mark43 stated 2 0 0 IL
3853 3853 Mark43 Aurora IL 2025-07-21 CAD/RMS system (authorize agreement) 4020267.0 A Resolution authorizing the director of purchasing to enter into a five year agreement with Mark43, Inc. of New York, New York and ancillary vendors at a cost of $4,020,267.64 for the purposes of obtaining a CAD/RMS system and developing interfaces required for system functionality. https://legistar1.granicus.com/aurora-il/meetings/2025/7/4673_M_Infrastructure_and_Technology_Committee_25-07-21_Meeting_Minutes.pdf https://mytown.theboringparts.com/city/aurora-il/2025/#m74081 sv:rms:mark43 stated 3 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);