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:rms:mark43" and state = "FL" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: amount_type, spend_date (date)

vendor 1

state 1

ledger 1

  • sv:rms:mark43 · 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
2907 2907 Mark43 Bay Harbor Islands FL 2023-11-08 RMS and CAD systems (purchase) 406608.0 Consideration and Approval to expend the first installment payment of $80,000 allocated in Fiscal Year 2023-2024 budget to MARK43 for acquisition of a new Records Management System and Computer Aided Dispatch System at a total cost of $406,608, under a five-year contract. https://bayharborislandsfl.api.civicclerk.com/v1/Meetings/GetMeetingFileStream(fileId=6646,plainText=false) https://mytown.theboringparts.com/city/bayharborislandsfl/2023/#m831176 sv:rms:mark43 stated 1 0 0 FL
3904 3904 Mark43 Coral Gables FL 2026-05-19 RMS enhancements (authorize purchase) 265000.0 A Resolution of the City Commission accepting the recommendation of the Police Department to authorize the purchase of enhancements from Mark 43 as a “Sole Source Procurement,” in an estimated amount of $ 265,000.00 pursuant to Section 2-689 of the City’s Procurement Code. https://coralgables.legistar1.com/coralgables/meetings/2026/5/5019_M_City_Commission_26-05-19_Meeting_Minutes.pdf https://mytown.theboringparts.com/city/coralgables/#m5073 sv:rms:mark43 recommended 1 0 0 FL
3637 3637 Mark43 Miramar FL 2023-03-15 RMS software maintenance (purchase) 161300.0 Temp. Reso. #R7830 approving the purchase of maintenance services from Insight Public Sector for the Mark 43 Records Management Software System in the amount of $ 161,300 in FY 23, for the period February 13, 2023, to September 30, 2023. https://miramar.legistar1.com/miramar/meetings/2023/3/1149_A_CITY_COMMISSION_REGULAR_MEETING_23-03-15_Meeting_Agenda.pdf https://mytown.theboringparts.com/city/miramar/2023/#m319607 sv:rms:mark43 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);