Source: https://library.kansas.watch (JSON API: https://library.kansas.watch/library.json)
Publisher: Kansas Watch
Relevant To: Comprehensive ALPR abuse incident database (64 entries, JSON API); multiple entries directly relevant/cross-referencing BPA’s existing library
Verification Status: Verified
Notes: Confirmed via full-text fetch of both the site and its underlying JSON API. This is a publicly maintained, editorially reviewed index of ALPR abuse/misuse incidents run by Kansas Watch (kansas.watch), with community submissions credited to contributors including “DeflockSC” and “DeflockJoplin.” As of this review, the JSON feed contains 64 approved, categorized entries (last updated 2026-05-22) spanning 2019–2026, each with title, publication, URL, jurisdiction, agency, standardized abuse categories (false_arrest, stalking_targeting, data_breach, fusion_center_sharing, dragnet_surveillance, domestic_abuse_enablement, immigration_enforcement, protest_tracking, unauthorized_access, other), and a substantive description — structurally very similar to BPA’s own bpa_source library and Link Archive, and a strong candidate for periodic re-pull/cross-referencing rather than one-time cataloging. Notable overlaps and highlights: entry #62 documents the SAME Monroe County, FL Deputy Lamar Roman “Bad Monkey” stalking case already in BPA’s library (IDs 3582, 3596), confirming and cross-referencing that account. Entry #37 (Wyden/Krishnamoorthi FTC letter re: 35+ stolen Flock police accounts, no MFA required) and #36 (51 security vulnerabilities in Flock cameras found by researcher Jon Gaines, including a physical-access root-access exploit) are strong technical-accountability sources not yet in BPA’s library. Entry #45/#41 (Lenexa, KS police chief used ALPR to track and orchestrate a pretextual stop against a resident who wrote a critical op-ed about the department’s ICE-raid response — explicit “Make Your Own Case” directive) is an exceptionally strong example of ALPR-enabled retaliation against protected speech, worth a dedicated follow-up entry. Entry #35 (Flock rewrote its Terms of Service twice in three months, 147 documented changes, removing a “we do not own/sell Customer Data” clause and adding a perpetual data license) is a significant vendor-accountability data point. Entry #30/#31 (FBI/Houston HIDTA bulletin instructing Flock users to use vague search-reason text and avoid transparency-law-compliant agencies; Flock’s own redaction error that unmasked millions of surveillance targets) directly corroborates and extends BPA’s existing Law360 entry on vague search-reason abuse. RECOMMENDATION: treat this as a standing reference library for BPA’s ALPR work going forward — worth periodic re-fetch of the JSON feed to catch new entries, and several individual entries above merit their own dedicated BPA source-library records given their strength.