Bartlesville City Council approves flock camera regulations with key amendments
The short version: Bartlesville added guardrails to its Flock network — geographic limits and restrictions on federal data sharing — proof local pressure can shape ALPR policy, as Tulsa's News Pulse reports.
Our Take
Credit to Tulsa's News Pulse for covering a story that too often flies under the radar: a city council actually setting limits on Flock Safety cameras instead of rubber-stamping the vendor's pitch. Councilor Aaron Kirkpatrick's push to cap installations within 500 feet of Bartlesville's city limits, restrict automatic data sharing, and rein in federal agency access to the footage is exactly the kind of granular policy fight that determines whether a surveillance network becomes a permanent fixture of daily life or stays on a short leash.
These details matter because ALPR systems live and die by their default settings. "No automatic sharing" and boundaries on federal access sound like modest tweaks, but they're the difference between a local tool for local investigations and a node in a nationwide tracking web that ICE, the DEA, or out-of-state agencies can query without anyone in Bartlesville ever voting on it. Flock's own network effect depends on cities not asking these questions — so when a council does, it's worth documenting.
Every city considering Flock cameras should be having this exact debate before the vote, not after the cameras go up. If you want to see whether your town already has them — and where — check our camera map, and if you want to push your own council toward real limits, our take-action page has a place to start.
This is DeFlock The USA’s original commentary. The video above is the work of Tulsa's News Pulse, published on YouTube — full credit to the creator.