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 state = "TX" and vendor = "Thomson Reuters CLEAR" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: spend_date (date)

vendor 1

  • Thomson Reuters CLEAR · 2 ✖

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
3661 3661 Thomson Reuters CLEAR Harris County TX 2024-05-16 Westlaw & CLEAR subscription (approve sole source exemption and execute agreement) 1608164.0 Request for approval of a sole source exemption from the competitive bid requirements and that the County Judge execute an agreement with West Publishing Corporation, d /b/a West, a Thomson Reuters Business in the amount of $ 1,608,164 for full compensation for services provided from January 1, 2023 - April 30, 2024 and to add funding for continued services for subscription to Westlaw and CLEAR Computer assisted legal & investigative research services for the Toll Road Authority through December 31, 2024 with four ( 4) one-year renewal options, Justification for 0% MWDBE Participation Goal: Ex https://harriscountytx.legistar1.com/harriscountytx/meetings/2024/5/1167_A_Commissioners_Court_24-05-16_Agenda.pdf https://mytown.theboringparts.com/city/harriscountytx/2024/#m290720 sv:fusion:thomson_clear stated 1 0 0 TX
3430 3430 Thomson Reuters CLEAR Edinburg TX 2024-02-20 CLEAR subscription (renew) 54683.0 Consider Authorizing the City Manager to Renew the Agreement with Consolidated Lead Evaluation and Reporting (CLEAR) from Thomson Reuters in the Amount of $54,683.40, and Authorize the City Manager to Enter Into a Thirty-Six (36) Month Agreement Through the Texas Department of Information Resources Purchasing Cooperative Contract DIR-LGL-CALIR-02 Relating Thereto. https://edinburgtx.api.civicclerk.com/v1/Meetings/GetMeetingFileStream(fileId=169,plainText=false) https://mytown.theboringparts.com/city/edinburgtx/2024/#m519389 sv:fusion:thomson_clear stated 1 0 0 TX

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