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 = "OK" and vendor = "Grayshift / GrayKey" sorted by amount descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: city, geo_suspect, spend_date (date)

vendor 1

  • Grayshift / GrayKey · 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
3221 3221 Grayshift / GrayKey Oklahoma City OK 2024-05-21 GrayKey units (purchase) 133085.0 Resolution authorizing the sole source purchase of two annual licenses for GrayKey units, Magnet Forensics (COKC00027), $133,085, retroactive to May 1, 2024 through April 30, 2025; and approving End User License Agreement. https://okc.primegov.com/Public/CompiledDocument/64837 https://mytown.theboringparts.com/city/okc/2024/#m640657 sv:forensics:grayshift stated 1 1 0 OK
2849 2849 Grayshift / GrayKey Ardmore OK 2026-07-20 GrayKey license (renew) 36996.0 Consideration and Possible Action on the Renewal of a GrayKey Mobile Extraction Device License Agreement by and between the City of Ardmore and Carahsoft Technology Corporation, for the Ardmore Police Department Crime Scene Investigation Forensic Lab, through Oklahoma State Contract SW1041, in the Total Amount of $36,996.30 https://www.ardmorecity.org/AgendaCenter/ViewFile/Agenda/_07202026-1943 https://mytown.theboringparts.com/city/ardmorecity.org/#m1005448 sv:forensics:grayshift stated 1 0 0 OK
2717 2717 Grayshift / GrayKey Ardmore OK 2025-09-15 iPhone/Android extraction device (renew) 33891.0 Consideration and Possible Action for the Renewal of the Advanced License for the GrayKey Mobil Extraction Device for the Ardmore Police Department Forensic Lab utilizing NASPO Contract SW1022C from Carahsoft Technology Corporation to be valid from September 27, 2025 to September 26, 2026 in the Total Amount of $33,891.00 https://www.ardmorecity.org/AgendaCenter/ViewFile/Agenda/_09152025-1826 https://mytown.theboringparts.com/city/ardmorecity.org/2025/#m1327261 sv:forensics:grayshift stated 1 0 0 OK

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