The Flock Security Contract: A Case Study in Failed Oversight

The Core Issue: Coralville's police department signed a $36,000 annual contract with Flock Security for automated license plate recognition cameras—without City Council knowledge, public input, or proper privacy review.

What Happened

Flock Security is a Silicon Valley company that provides automated license plate recognition (ALPR) cameras to law enforcement. These cameras continuously photograph every vehicle passing by, uploading the data to Flock's cloud servers where it's processed, stored, and made searchable.

In 2024, Coralville's police department entered into a contract with Flock Security. The City Council learned about the contract only after concerned citizens filed public records requests and raised questions.

This represents a fundamental failure of governance:

Why This Matters

The Flock contract isn't just about cameras. It's about how decisions are made in our city government.

Privacy Concerns: Automated license plate readers create a comprehensive database of residents' movements. Every time you drive past a camera, your location is recorded, timestamped, and stored. Over time, this data reveals patterns—where you live, work, worship, seek medical care, and spend your free time.

Data Security: Flock's business model is built on data retention and sharing. They keep images and location data for 30 days (or longer under certain contracts), and the system is designed to allow data sharing between law enforcement agencies nationwide. Once your data enters Flock's cloud, you have no control over who accesses it or how it's used.

Facial Recognition Risk: While Flock claims not to use facial recognition currently, the cameras capture high-resolution images of drivers and passengers. The technology exists to add facial recognition capabilities to these existing camera networks—and Flock has explicitly acknowledged this potential in their marketing materials.

Economic Impact: $36,000 annually to a California corporation. Over a five-year contract, that's $180,000 leaving our community. This money could support local technology jobs, fund University of Iowa partnerships, or create apprenticeships for high school students learning to code.

The Broader Pattern: SaaS Lock-In

Flock Security exemplifies the Software-as-a-Service (SaaS) economy that extracts wealth from communities. Once locked into their system:

This creates a permanent revenue stream for Flock while giving Coralville zero equity, zero control, and zero local economic benefit.

The Municipal Technology Alternative

Instead of renting surveillance from Silicon Valley, Coralville could build municipal technology infrastructure that:

This approach costs more upfront but creates lasting value—jobs, skills, local expertise, and technology assets the city actually owns.

What Should Have Happened

Before any surveillance contract is signed, the City Council should:

  1. Hold public hearings - Allow residents to weigh in on privacy implications
  2. Review the technology - Understand what data is collected, how it's stored, who can access it
  3. Evaluate alternatives - Consider local solutions and less invasive approaches
  4. Assess necessity - Is this surveillance actually needed? What problem does it solve?
  5. Consider economics - Could this money create more value if invested locally?
  6. Establish policies - Set clear rules for data retention, access, and sharing
  7. Vote publicly - Make council members go on record supporting or opposing the contract

None of this happened with Flock. That's unacceptable.

My Commitment

If elected, I will:

The Flock contract represents everything wrong with how our city is currently governed. We can do better. We must do better.

Questions About This Issue?

I'm happy to discuss the Flock contract, surveillance policy, and municipal technology alternatives in detail.

Contact Marshall