Greenfield Police | License plate readers

A perimeter, described as one

Most agencies describe plate readers in terms of what they help solve. Greenfield’s staff report describes where they go, and it is unusually direct:

To improve the city’s ability to monitor and deter criminal activity, staff are proposing an expansion of the city’s existing surveillance camera network. This initiative aims to cover high-traffic corridors and key locations that serve as entry and exit points to and from Greenfield. By capturing critical data on vehicles and individuals moving in and out of the city, the expanded system will significantly enhance investigative capabilities and response times.

And in the analysis section:

Placing Flock cameras at strategic locations along city boundaries and major access points will provide real-time data that can assist in identifying suspects, vehicles, and patterns of criminal activity.

City boundaries. Entry and exit points. Vehicles and individuals moving in and out. Those are the city’s words, in a public agenda packet, and they describe a ring rather than a set of cameras at crime hotspots.

Why it needed the County at all

Greenfield is small and the roads leading in and out of it mostly are not the city’s. To put cameras at the edges of town, the city needed poles on county land, which is what the agreement is for.

The arrangement it sets up is worth reading closely. The County provides access to the right of way and takes on nothing else. The city pays for and manages the Flock lease. And on the data:

The City agrees to be responsible for storage and retention schedules for any data or footage obtained through Flock Safety equipment / services including obligations that may arise from the collection of data such as license plates, photos/depictions of vehicles and/or areas surrounding photographed vehicles, and data documenting the date, time, and location of images captured. […] The parties agree that none of the data or documents collected are either County property or within the County’s possession, use, or control.

The County supplies the ground the cameras stand on and disclaims everything they collect.

The schedule that is assigned but not set

That paragraph makes the city responsible for a retention schedule. It does not say what the schedule is. There is no number anywhere in the section.

This is a pattern worth naming, because the same shape turns up in two counties on this site. A document that looks like it settles retention actually assigns it. Turlock’s plate reader policy in Stanislaus County refers its reader to a records retention schedule that the policy does not contain, name, date or cite. Greenfield’s agreement makes the city responsible for one without stating it. In both cases someone reading the governing document to find out how long their plate data is kept finds a pointer to another document that has not been published.

The agreement is precise elsewhere. It warrants that the city complies with SB 34 and is “solely responsible for such compliance”. It requires five days notice to the County before any installation or maintenance. It sets termination at 30 days notice and requires the city to remove the poles at its own cost. The retention question is the one left open.

The list that can move

One clause deserves attention on its own:

The parties agree that the locations set forth in Exhibit a may be added or modified be written agreement of the parties without a formal amendment of the MOU.

The camera locations are in Exhibit A. Exhibit A can be changed by written agreement between the city and the county, without amending the agreement the council approved.

Nothing about that is improper, and there are good administrative reasons for it: moving a pole should not need two governing bodies to meet. It does mean that the list of locations the council saw in March 2025 is a starting point rather than a boundary, and that later additions do not come back to a public agenda.

We have not read Exhibit A, so we cannot tell you the starting point either.

The item that had no number

The staff report records the fiscal impact as none:

Funds from the current city camera budget will be used to expand the Flock cameras, so there will be no impact on the budget. As future expansion continues, then at that time requests for budget modifications will be made.

Because the money was already there, the item reached the council as an agreement to authorise rather than a sum to approve. The report is straightforward that future expansion will need budget requests, so nothing here is hidden.

It is simply worth noticing what a budget line does that an authorisation does not. A number invites a comparison; it is the moment a council asks what else the money could do. An item with no fiscal impact skips that step, and a decision to ring a town with cameras arrives as a question about poles.