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

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: product, amount_type, spend_date (date)

vendor 1

state 1

ledger 1

  • sv:forensics:cellebrite · 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
3621 3621 Cellebrite Ocala FL 2025-04-01 forensic software (renew) 86380.0 Approve one-year contract renewal of the agreement with Cellebrite, Inc., for forensic software with an estimated expenditure of $86,380 https://ocala.legistar1.com/ocala/meetings/2025/4/3391_M_City_Council_25-04-01_Synopsis.pdf https://mytown.theboringparts.com/city/ocala/2025/#m328678 sv:forensics:cellebrite estimated 1 0 0 FL
3900 3900 Cellebrite Ocala FL 2026-04-07 forensic software (renew) 56910.0 One-year renewal of the contract with Cellebrite, Inc., for Ocala Police Department forensic software with an annual expenditure of $56,910 https://ocala.legistar1.com/ocala/meetings/2026/4/3570_M_City_Council_26-04-07_Synopsis.pdf https://mytown.theboringparts.com/city/ocala/#m6151 sv:forensics:cellebrite stated 1 0 0 FL
3620 3620 Cellebrite Ocala FL 2025-04-15 licensing (budget) 8800.0 Adopt Budget Resolution 2025-145 amending the Fiscal Year 2024-25 budget to accept and appropriate a donation from Kimberly’s Center for Child Protection to purchase Cellebrite licensing totaling $8,800 https://ocala.legistar1.com/ocala/meetings/2025/4/3392_M_City_Council_25-04-15_Synopsis.pdf https://mytown.theboringparts.com/city/ocala/2025/#m328684 sv:forensics:cellebrite 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);