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

2 rows where ledger = "sv:rms:versaterm", state = "FL" and vendor = "Versaterm" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: spend_date (date)

vendor 1

  • Versaterm · 2 ✖

state 1

ledger 1

  • sv:rms:versaterm · 2 ✖
Link rowid vendor city state spend_date product amount ▲ quote source_document mytown_record ledger amount_type dup_rank geo_suspect anomaly state_norm
4303 4303 Versaterm Tampa FL 2024-11-07 Street Smart software (approve contract) 147960.0 Resolution approving a Master Services and Software Agreement between Versaterm Public Safety US, Inc., ("Versaterm") and the City of Tampa relating to the use of Street Smart Software Application ("Software") from July 1, 2024 through June 30, 2025 for use by the Tampa Police Department and neighboring Law Enforcement Agencies in an amount of $147,960.71 as part of the UASI grant funding Resolution No. 2023-1335; authorizing execution thereof by the Mayor of the City of Tampa and attestation of the City Clerk; providing an effective date. https://tampagov.hylandcloud.com/251agendaonline/Documents/DownloadFileBytes/City_Council_REGULAR_-_November_7%2C_2024_2480_Minutes_11_7_2024_9_00_00_AM.pdf?documentType=2&meetingId=2480 https://mytown.theboringparts.com/city/ob-tampa-fl/2024/#m213373 sv:rms:versaterm stated 1 0 0 FL
4302 4302 Versaterm Tampa FL 2026-03-05 Mindbase platform (approve contract) 60237.0 Resolution approving Service Schedule No. 4 between Versaterm Public Safety US. Inc., ("Versaterm") and the City of Tampa relating to the purchase of a health and wellness platform know as Mindbase for use by the Tampa Police Department for $60,237; authorizing execution thereof by the Mayor of the City of Tampa and attestation of the City Clerk; providing an effective date. https://tampagov.hylandcloud.com/251agendaonline/Documents/DownloadFileBytes/City_Council_Regular_-_March_5%2C_2026_2785_Minutes_3_5_2026_9_00_00_AM.pdf?documentType=2&meetingId=2785 https://mytown.theboringparts.com/city/ob-tampa-fl/#m213564 sv:rms:versaterm stated 1 0 0 FL

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