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:motorola:motorola" and state = "WY" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: spend_date (date)

vendor 1

state 1

ledger 1

  • sv:motorola: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
2416 2416 Motorola Solutions Lincoln County WY 2024-01-16 body cams & dash cams (approve vouchers) 233381.0 Motorola; Sheriff, body cams & dash cams $ 233,381.01 https://www.lincolncountywy.gov/Documents/Government/County%20Commissioners/Agendas%20And%20Minutes/2024/Minutes/OFFICIAL%20PROCEEDINGS%20%20january%2016,%202024...pdf https://mytown.theboringparts.com/city/rz-lincolncountywy.gov/2024/#m7720123 sv:motorola:motorola stated 1 0 0 WY
2498 2498 Motorola Solutions Green River WY 2026-03-17 body cameras (approve contract) 110039.0 Council Member Killpack moved to approve the agreement with Motorola Solutions, Inc., for the purchase of new V700 body cameras for the Police Department , in the amount of $110,039 and authorize the Mayor to sign the agreement, the Governing Body hereby finding that the commitment of Motorola Solutions, Inc., to provide the services specified for the term of years specified has been determined to constitute a significant benefit and advantage to the City and the Public, in that such services are not readily or economically available to the City in the absence of an extended term contract. https://www.cityofgreenriver.org/AgendaCenter/ViewFile/Minutes/_03172026-450 https://mytown.theboringparts.com/city/cityofgreenriver.org/#m1579550 sv:motorola:motorola stated 1 0 0 WY
2420 2420 Motorola Solutions Sheridan County WY 2024-10-01 video equipment (purchase) 6588.0 MOTOROLA SOLUTIONS INC $6,588.00 VIDEO EQUIPMENT https://www.sheridancountywy.gov/Document%20Center/Agendas%20And%20Minutes/Commissioners/2024/BOCC/10-01-2024%20Regular%20Meeting%20Minutes.pdf https://mytown.theboringparts.com/city/rz-sheridancountywy.gov/2024/#m7717530 sv:motorola:motorola stated 1 0 0 WY

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