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:camera:verkada", state = "AZ" and vendor = "Verkada" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: amount_type, dup_rank, geo_suspect, spend_date (date)

vendor 1

  • Verkada · 3 ✖

state 1

ledger 1

  • sv:camera:verkada · 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
2433 2433 Verkada Flagstaff AZ 2026-05-05 Verkada Security Systems (amend) 200000.0 Approve the expenditure on a cooperative purchase with Corporate Technologies Solutions, LLC to increase the contract amount by $200,000.00, for a revised total not to exceed $500,000.00, for City-Wide Verkada Security and Protection Systems. https://public.destinyhosted.com/agenda_publish.cfm?id=35247&mt=ALL&get_month=5&get_year=2026&dsp=min&seq=4735 https://mytown.theboringparts.com/city/aq-35247/#m6754790 sv:camera:verkada ceiling 1 1 0 AZ
3615 3615 Verkada Paradise Valley AZ 2024-10-10 CCTV program and cameras (approve contract) 159965.0 Approve contract CON-25-015-IT with Logicalis, Inc, for refresh of CCTV servers and cameras by installing new Verkada CCTV program and cameras, authorize the Town Manager to execute the agreement in the amount of $159,965.07, and waive the 14-day waiting period to execute the agreement. https://paradisevalleyaz.legistar1.com/paradisevalleyaz/meetings/2024/10/1850_A_Town_Council_24-10-10_Meeting_Notice_and_Agenda.pdf https://mytown.theboringparts.com/city/paradisevalleyaz/2024/#m331265 sv:camera:verkada stated 1 0 0 AZ
3310 3310 Verkada Taylor AZ 2025-06-17 Command Connector licenses (amend) 5620.0 Motion to approve Knight Watch, current vendor, for Verkada Command Connector and five (5) year licenses for seven (7) existing cameras in the amount not to exceed $5,620. Funded through Police Contractual Services. https://taylor.granicus.com/AgendaViewer.php?view_id=1&clip_id=393 https://mytown.theboringparts.com/city/gr-taylor/#m565391 sv:camera:verkada ceiling 2 0 0 AZ

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