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:milestone" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: amount_type, geo_suspect, spend_date (date)

state 3

vendor 1

ledger 1

  • sv:camera:milestone · 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
3801 3801 Milestone Systems Anchorage School District AK 2013-06-03 video management system (award contract) 398889.0 It is the Administration’s recommendation the School Board approve and authorize the Superintendent to award a contract for the Network IP Camera Video Management System to Siemens Industry, Inc., in the amount of $398,889 for an initial installation at 33 district sites and to become the district-wide standard video management system integrator, using Milestone Systems, Inc. video management system, through December 31, 2017. https://go.boarddocs.com/ak/asdk12/Board.nsf/BD-GetMinutes?open&id=96DSB271CF6D https://mytown.theboringparts.com/city/bd-ak-asdk12/#m189905 sv:camera:milestone recommended 1 1 0 AK
3065 3065 Milestone Systems Tulsa County OK 2024-11-25 Corporate Device Channel License and Maintenance (approve payment) 89250.0 Creditor: ISG Technology Inc.; Fund: 505; Item: Invoice #ISG358785; Purpose: Milestone Systems - Corporate Device Channel License and Maintenance: Amount Paid: $89,250 https://tulsacook.api.civicclerk.com/v1/Meetings/GetMeetingFileStream(fileId=8179,plainText=false) https://mytown.theboringparts.com/city/tulsacook/2024/#m712300 sv:camera:milestone stated 1 0 0 OK
3495 3495 Milestone Systems Mobile AL 2023-02-14 XProtect video management software (approve purchase order) 19341.0 Approve purchase order to CDW Government, LLC for Milestone Xprotect video management software for MPD; $19,341.91 (sponsored by Mayor Stimpson) (submitted by John Paine, Purchasing Dept.). https://mobileal.api.civicclerk.com/v1/Meetings/GetMeetingFileStream(fileId=677,plainText=false) https://mytown.theboringparts.com/city/mobileal/2023/#m454769 sv:camera:milestone stated 1 0 0 AL

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