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:fusion:lexisnexis", state = "NC" and vendor = "LexisNexis / Accurint" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: spend_date (date)

vendor 1

  • LexisNexis / Accurint · 3 ✖

state 1

ledger 1

  • sv:fusion:lexisnexis · 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
3665 3665 LexisNexis / Accurint Greensboro NC 2021-03-16 Accurint Virtual Crime Center (renew) 102000.0 Resolution Authorizing a Subscription in the Amount of $102,000 Between the Greensboro Police Department and LexisNexis Risk Solutions FL Inc. https://legistar.granicus.com/greensboro/meetings/2021/3/1904_M_City_Council_21-03-16_Meeting_Minutes.pdf https://mytown.theboringparts.com/city/greensboro/#m289300 sv:fusion:lexisnexis stated 1 0 0 NC
3532 3532 LexisNexis / Accurint Winston-Salem NC 2025-10-13 BuyCrash reporting solution (renew contract) 49560.0 Resolution Authorizing Contract Renewal with LexisNexis Coplogic Solutions, Inc., and Addition of BuyCrash Reporting Solution - $49,560 https://winston-salem.legistar1.com/winston-salem/meetings/2025/10/2762_M_Public_Safety_Committee_25-10-13_Summary.pdf https://mytown.theboringparts.com/city/winston-salem/2025/#m365442 sv:fusion:lexisnexis stated 1 0 0 NC
2560 2560 LexisNexis / Accurint Yadkin County NC 2025-12-15 Advanced People Search software (approve paying) 1600.0 There are eight LexisNexis invoices for the Advanced People Search software that the Tax Office uses. The total of those invoices is $1,600.00. https://www.yadkincountync.gov/AgendaCenter/ViewFile/Minutes/_12152025-1058 https://mytown.theboringparts.com/city/yadkincountync.gov/2025/#m1505746 sv:fusion:lexisnexis stated 1 0 0 NC

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