Tempe doesn't plan to turn Flock cameras back on even with guardrails

Our Take

Credit to KTAR News for flagging something a lot of cities won't say out loud: sometimes the answer to "how do we fix this surveillance tool" is just "we don't turn it back on." Tempe's decision suggests local officials looked at the proposed policy tweaks, audit trails, and access restrictions Flock Safety loves to tout, and decided they still don't outweigh the risk of a always-on network logging every car that passes by.

That matters because "guardrails" have become the industry's favorite deflection. Add a warrant requirement here, a retention limit there, and suddenly a mass-tracking system is supposed to look reasonable. Tempe pumping the brakes is a reminder that policy language on paper doesn't change what the hardware does: it still photographs your plate, timestamps your movements, and feeds a searchable database that outlives any single use case it was sold on.

Communities watching this debate should ask the same question Tempe apparently did — not "what rules would make this okay," but "do we want this infrastructure to exist here at all." Check our camera map to see what's already deployed near you, and visit take-action if you want tools to push your own city council toward Tempe's answer instead of Flock's.