AI Tools · August 12, 2026 · Box of Prompts

Before You Sign With Flock, Read the Contract First

By Flock Safety's own count, more homeowners associations and businesses host its cameras than police departments do: over 6,000 HOAs and 1,000 businesses, against just over 5,000 law enforcement agencies. We've written elsewhere about what these networks do and who ends up querying them. This post is narrower and duller on purpose: what the thing costs, what the contract actually says, and what to ask before your board votes.

What you're actually paying

Flock doesn't publish a price list, which is the first thing worth knowing. Every public figure below comes from a security integrator, a competing vendor, or a city contract that became a public record. Treat all of it as a working range rather than a quote, and note that most of the people publishing Flock's prices sell something else.

With that caveat: the figure that recurs is roughly $2,500–$3,000 per camera, per year, leased rather than owned, plus a one-time installation fee of about $250 to $350 for a standard mount. Sites needing a new pole, trenching, or solar run higher. A community putting cameras on two entrances should expect roughly $5,000 to $6,000 a year, every year, plus install in year one. That is the number to carry into a board meeting, not the per-camera figure, and not a first-year total that quietly drops the recurring part.

What you're actually signing

The pricing is the visible half. The contract terms are the half that surprises people later.

You never own anything. The hardware belongs to Flock and stays Flock's property. Cancel, and the cameras come off the poles. There is no year in which the equipment is paid off and your cost drops, which is the ordinary arc when a community buys cameras outright. Contracts run annually, with multi-year commitments used to earn better per-camera pricing, so the cheaper quote is usually the one that locks you in longer.

That structure is not hidden and it isn't unusual for the category. It just means the decision you're making is a permanent operating expense, not a capital purchase that ages off the books.

Whether the contract holds

A contract is only worth what it constrains, and two municipal customers have now reported that theirs constrained less than they believed.

In Mountain View, California, the city disabled all thirty of its Flock cameras in February after discovering a “national lookup” setting had been switched on for one camera without the city's authorization, exposing it to out-of-state agencies. Reporting on the incident noted the setting could violate California's SB 34, which bars state and local agencies from sharing plate-reader data with out-of-state or federal entities. Flock kept no records from that period, so nobody can determine what actually left the system.

Cambridge, Massachusetts stopped using its cameras over related data-sharing concerns. Vice Mayor Marc McGovern:

“We sort of thought we had a solid contract with Flock, that we would be able to protect the information… We've come to learn that it's not quite as solid as maybe we had thought it was.”

Cambridge Vice Mayor Marc McGovern, via CBS News Boston

Both are municipal cases. We could not find a named, dated dispute at the HOA level to match them, and we are not implying one exists. But a board signing this contract is relying on the same class of assurance those cities relied on, and it is fair to ask what happens if it turns out to be wrong.

Does hosting a camera make you an AI “deployer”?

Several 2026 state AI laws create obligations for “deployers” of automated systems, Colorado's automated-decision-making law being the most developed. We looked for a clean answer on whether hosting a Flock camera puts a business inside that definition and did not find one. Colorado's law is built around systems that materially influence a consequential decision like employment or housing, which a parking-lot camera network does not obviously do.

So the honest answer is that we don't have one. If a case ever tests it, this post gets updated. Until then, don't assume the compliance question is settled because the security question is.

Four things worth asking before you sign

None of these questions require distrust of the technology itself. They require the same diligence you'd apply to any vendor contract that runs on autopilot once it's signed.

Where we sit on this

Box of Prompts doesn't sell or install camera networks. We're writing this because reading a contract carefully, before signing, before the automatic renewal, is exactly the kind of diligence we think every purchasing decision deserves, AI-powered or not.

Sources

Tags mark who published each source and what interest they have.

← Back to all notes