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

4 rows where state = "CA" and vendor = "Flock" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: amount_type, spend_date (date)

vendor 1

  • Flock · 4 ✖

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
2023 2023 Flock San Jacinto CA 2024-08-20 appropriate for purchase 91500.0 Appropriate $91,500 for the purchase of Flock camera rights to facilitate the implementation of a Real Time Crime Center https://sanjacintoca.iqm2.com/Citizens/FileOpen.aspx?Type=12&ID=1033&Inline=True https://mytown.theboringparts.com/city/iq-sanjacintoca/2024/#m881678 flock stated 1 0 0 CA
1790 1790 Flock San Dimas CA 2026-05-19 discussed existing contract 35000.0 Staff previously reported on Flock: 14 existing cameras; contract amount is $35,000 annually through Feb 2028; new units cost 5,150 dollars each. https://sandimasca.primegov.com/Public/CompiledDocument/16758 https://mytown.theboringparts.com/city/sandimasca/#m572435 flock stated 1 0 0 CA
2316 2316 Flock Calimesa CA 2023-05-22 add 24000.0 A request by the City Manager to add Flock cameras with a projected cost of $24,000. https://www.cityofcalimesa.net/AgendaCenter/ViewFile/Minutes/_05222023-147 https://mytown.theboringparts.com/city/cityofcalimesa.net/2023/#m1579056 flock stated 1 0 0 CA
1548 1548 Flock Bishop CA 2024-08-12 approve agreement 7000.0 Review and approve Flock Camera agreement to provide the City with two new surveillance cameras on City property with a cost not to exceed $7,000.00. https://bishop-ca.granicus.com/AgendaViewer.php?view_id=1&clip_id=1542 https://mytown.theboringparts.com/city/gr-bishop-ca/2024/#m150756 flock ceiling 1 0 0 CA

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