Hailey Police | License plate readers
Three Flock Safety cameras at three Hailey intersections, approved by the City Council in September 2025 for $10,500 a year. The department's first audit came ten months later, and the chief told the Council there is no policy on sharing the data with other states.
At a glance
- Term
- Two years from September 2025, extendable [1]
- Who else can see it
- No list appears in any document we read. Asked on 27 July 2026 what policy governs sharing immigration information with other states, the chief told the Council there is no policy, that the department elected not to track immigration information, and that it can share information with any state at any time [4]
- A written policy
- We could not find one published by the department. The Council was told the retention period is set by the contract rather than by a policy [4]
How it happened
- Procurement
The chief asks for three cameras
An agenda item summary from the police department, printed in the council packet, asks for three plate readers and live cameras at an annual fee of $3,500 per camera, $10,500 in total, on a two year contract with installation waived. It cites Idaho Code 49-1432 as the authority and states that Flock Safety is already used by Sun Valley, Bellevue and the Blaine County Sheriff's Office, with eight cameras between them. [1]
- Decision
Four votes, and a question about the data license
The City Council adopts Resolution 2025-088, a master services agreement with Flock Group, Inc. The roll call is four to nothing. The minutes record a council member commenting on page 6 of the agreement, on customer data the vendor will not sell but holds under an irrevocable worldwide license, before voting yes. The chief tells the Council he has been looking at the software for three years, that the cameras read rear plates coming into town, and that intersection feeds are live for up to 30 days. [2]
- Procurement
The invoice
The city's claims register pays Flock Group, Inc. invoice INV-75503, described as VIDEO CAMERA/LPR, for $10,500.00. [3]
- Debate
Two residents ask for the cameras to be removed
In the open session for public concerns, one resident asks the Council to reconsider the cameras and remove them, raising the Fourth Amendment and asking the Council to investigate, take input, set guidelines and put the matter on a future agenda. A second speaks about privacy. A council member asks for a follow up and a community conversation to be put on the agenda. [5]
- Context
The first audit, and the answer about other states
The chief reports the department's first plate reader audit, completed in house by the assistant chief on 7 July 2026: five cases reviewed, all found to be legitimate searches by trained personnel, and six hot list items, with items removed if confirmed closed. He names the three camera locations. Asked what policy governs sharing immigration information with other states, he tells the Council there is no policy, that the department elected not to track immigration information, and that it can share information with any state at any time. Retention is 30 days because the contract limits it to 30 days. He says he will put the audit on the website. [4]
- Debate
A third meeting, a third objection
A resident tells the Council they disagree with the use of the cameras and want them removed. The same meeting's consent agenda carries a memorandum of understanding between the Hailey and Ketchum police departments for cooperative police services. [7]
- Debate
Two more speakers
Two residents speak against the cameras in the open session for public concerns, one reading from a prepared statement. [8]
Hailey is the county seat, and its three cameras are the smallest plate reader deployment in Blaine County that we can price. They cost $10,500 a year and they sit at three intersections on the way into town.
What the Council was told, and what it asked
The staff report that went to the Council on 22 September 2025 is a page long. It asks for three readers and live cameras at $3,500 each a year, on a two year term, with the $2,500 installation fee waived. It names the statute the department would work to. And it gives a count of what was already in the valley: Flock Safety “is currently utilized by the cities of sun valley and Bellevue and by the Blaine county Sheriff’s Office”, eight cameras between them.[1]
Hailey’s minutes are timestamped, so the discussion survives. At 7:34 in the evening a council member raised page 6 of the agreement: the vendor will not sell the city’s data, and holds it under an irrevocable worldwide license. At 7:47 the chief said he had been looking at the software for three years. At 7:50, asked whether the cameras take stills or video, he answered that the readers take rear plates coming into town and that the intersection feeds are live for up to 30 days. At 7:59 a council member said he was torn, that he had to trust the chief, and that he was happy with 30 days retention. At 8:03 the motion passed four to nothing.[2]
Three weeks later the city paid the invoice, $10,500, on a claims register line reading VIDEO CAMERA/LPR.[3]
The first audit
Idaho Code 49-1432 took effect on 1 July 2025, three months before Hailey voted. It requires every agency using plate readers to log each access with the user’s identity, the date, the time and the purpose, and to audit those logs twice a year.[6]
Hailey’s first audit was completed on 7 July 2026, a year after the statute and ten months after the cameras were bought. The assistant chief did it, looked at five cases, and found all five were legitimate searches by trained personnel. Six hot list items were reviewed, one for a wanted person not yet arrested, and items were removed where the case was confirmed closed.[4]
The same report answered a question the contract does not. Asked what policy governs sharing immigration information with other states, the chief told the Council there is no policy, that the department elected not to track immigration information, and that it can share information with any state at any time. Asked who audits, he said it is done in house for now and that the department is talking to other agencies about an external audit. Asked whether the 30 day retention is a policy, the city administrator answered that the Flock contract limits data to 30 days.[4]
What residents have said since
At the meeting of 13 July 2026, two residents used the open session to ask the Council to reconsider the cameras and remove them. A council member asked that a follow up and a community conversation be put on the agenda.[5] A resident asked for removal again on 24 August,[7] and two more spoke against the cameras on 14 September.[8]
As of the last packet we read, the Council had taken no vote on the question since the one that bought them.
On the map
The community has mapped 28 devices of this type in the county on OpenStreetMap. These are community reports: the vendor and operator of each point are unverified, and none is confirmed to belong to this system. See them on the map →
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
- Location road not yet identified license plate reader ↗
Street names from reverse geocoding — © OpenStreetMap contributors (ODbL).
What we do not know
- Which agencies can search Hailey's cameras, and whose cameras can Hailey search? No list appears in any document we read, and the chief told the Council the department can share with any state at any time.
- Does the department have a written plate reader policy? We could not find one published on the city website.
- Where is the audit the chief said he would publish? We could not find it on the city website.
- What is in the executed agreement? The Council adopted a master services agreement, and the packet prints the vendor's standard terms rather than a signed order form with a camera count.
What you can do
Show up
Systems like this one are approved by boards, councils and committees that meet in public. We have confirmed where each of them meets in Blaine County and how public comment works there.
How to show up in Blaine County →Protect yourself
Practical steps to shrink your personal data trail. Our guides publish at launch; until then, EFF's Surveillance Self-Defense is the best starting point.
Surveillance Self-Defense →Sources
- 1. City of Hailey City Council packet, 22 September 2025, carrying the plate reader agenda item summary and Resolution 2025-088 · Primary document · · accessed
- 2. Hailey City Council minutes, 22 September 2025 · Meeting record · · accessed
- 3. City of Hailey City Council packet, 14 October 2025, carrying the claims register · Primary document · · accessed
- 4. Hailey City Council minutes, 27 July 2026 · Meeting record · · accessed
- 5. Hailey City Council minutes, 13 July 2026 · Meeting record · · accessed
- 6.
- 7. City of Hailey City Council packet, 24 August 2026 · Primary document · · accessed
- 8. City of Hailey City Council packet, 14 September 2026 · Primary document · · accessed
Get the digest
A regular digest of what changed in the world of surveillance: the counties we published, the devices that appeared on the map, and the public meetings where these decisions get made. We send it when there is enough to report.
One click to unsubscribe. What we do with your address is on the newsletter page.