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 = "PA" and vendor = "Motorola Solutions" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: city, amount, spend_date (date)

vendor 1

  • Motorola Solutions · 3 ✖

state 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
2515 2515 Motorola Solutions Jefferson Hills PA 2024-10-02 cloud video storage (approve contract) 99768.0 Discussion to approve the Jefferson Hills Police Department to enter into a 5-year contract agreement with Motorola Solutions to transition from limited on-site video storage to unlimited Cloud based video storage, which includes redaction software and all necessary police equipment upgrades in the amount of $99,768.60 or five equal annual payment of $19,953.72 https://www.jeffersonhillsboro.org/AgendaCenter/ViewFile/Minutes/_10022024-63 https://mytown.theboringparts.com/city/jeffersonhillsboro.org/2024/#m1560134 sv:motorola:motorola stated 1 0 0 PA
2686 2686 Motorola Solutions Ephrata PA 2025-05-12 body camera storage subscription (extend contract) 80712.0 That Borough Council authorize the Police Department to enter in the 3-year contract extension with Motorola - QUOTE-3053788 to extend the Mobile Video Recorder / Body Worn Camera data storage subscription for three (3) years in the total amount of $80,712 over the life of the extension effective in May of 2027 through April of 2030. https://www.ephrataboro.org/AgendaCenter/ViewFile/Minutes/_05122025-1378 https://mytown.theboringparts.com/city/ephrataboro.org/2025/#m1354700 sv:motorola:motorola stated 1 0 0 PA
2688 2688 Motorola Solutions Ephrata PA 2025-04-21 body camera storage (renew) 80712.0 Motorola will lock pricing now at $80,712 over the life of the extension. https://www.ephrataboro.org/AgendaCenter/ViewFile/Minutes/_04212025-1368 https://mytown.theboringparts.com/city/ephrataboro.org/2025/#m1354667 sv:motorola:motorola stated 1 0 0 PA

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