3 Key Tips for Surviving Flock Cameras

Our Take

Credit where it's due: AI Privacy & Business Counsel packs a decent starter kit into a short video — show up to council meetings and ask who approved the cameras, know where they physically sit before you plan a route, and dig into how long your plate data sits in a database and who gets to query it. Those three moves are exactly the playbook we push here, because Flock's pitch to city councils is almost always framed as "just catching bad guys," while the actual system quietly builds a location history on every driver who passes a reader, guilty of nothing more than existing.

The retention question deserves more attention than a lot of coverage gives it. Flock's default policies, audit access logs, and interagency data-sharing agreements vary wildly city to city, and most residents have no idea their local PD may be sharing reads with departments hundreds of miles away or with federal agencies. "Ask who approved it" is step one — the harder follow-up is getting the actual contract and audit trail on the record, which most councils won't volunteer unless pushed.

If you want the mapping piece done for you, check our camera map to see what's already logged near you, and if you're ready to push back at a council meeting, our take action page has the questions and templates to make that fight easier.