City councils keep having the same argument about public-safety technology, and it is rarely about whether police should find wanted people. It is about method. Residents who come to the microphone tend to object to systems that record everyone who passes, keep it, and let someone search it later.

That objection can be answered in a contract. On 21 October, the Reno City Council approved a public-safety technology agreement with written conditions attached. They are worth reading closely, because they turn a heated public debate into terms a city can enforce.

What Reno put in writing

As reported by 2 News Nevada, the conditions include:

• Data not tied to an active, lawful investigation is deleted after 15 days.
• The city keeps control of its data, and sharing with an outside agency needs prior approval.
• Police audit access logs, retention, sharing and misuse at least quarterly.
• The police chief reports those findings to the council every three months.
• Any new surveillance technology, or any expansion beyond the current agreement, needs a council vote.
• The city can end the contract on 30 days’ written notice, with or without cause.

The council approved it 5 to 2. Police Chief Corey Solferino told members the tools do not establish probable cause on their own.

None of this is an endorsement of a product. It is a template: the questions a council can require answered before the vote instead of after the first complaint.

Five questions for the next vote

1. Who is in the searchable set? Everyone who passes a camera, or only people who already have a record created through a court or agency process?
2. How long does information about people who are not suspects exist, and who can search it in that time?
3. Can the vendor add cameras, sharing partners or features without another public vote?
4. Who reviews a result before an officer acts on it, and what are they trained to check?
5. Will the vendor publish its use policy in plain language, and will the city audit against it?

A vendor that answers the first two with “everyone” and “weeks” is asking a council to defend mass collection in public.

Starting from the record instead

There is another way to build identity technology for public safety. Instead of collecting everything and searching it later, it starts from records a court or agency has already created and asks a narrow question about a single moment: does this person match one of them?

That is the model Safience is built on.

Records first. Every comparison runs against UMbRA, the law-enforcement-sourced identity database. The live record count is on the UMbRA page. It draws on law-enforcement records, never social media, news photos or commercial data.

Nothing kept on anyone else. A sensor captures a single still image. If it does not match a relevant record, it is deleted at once. No template is stored, and there is no history of who walked past.

No video, no plates. Safience never receives, records or stores operational video, and it does not read license plates or follow vehicles. Authorized technicians have a limited view only during installation and troubleshooting.

A person before the alert. A trained analyst reviews every potential match before anyone is notified. A delivered alert is an informational lead. The receiving agency confirms current status and decides what to do.

Put that design through the five questions and the answers are short. Only people with an existing record. Non-matches deleted immediately. Alert scope set with local leaders. A trained reviewer on every match. A written policy anyone can read.

The short version

Public-safety tools lose votes when they collect too much. A council that writes retention, sharing, audit and expansion limits into the contract, paired with a system that starts from a verified record, gives residents something they can stand behind.

For how a single record-bound match works, see Identity intelligence starts with a record, not a face. For how biometric rules differ by state, see our state privacy policy pages. Agencies and councils can reach us through contact.

Sources

• 2 News Nevada, coverage of the Reno City Council vote, 21 Oct 2026. https://www.2news.com/news/local/reno-council-approves-axon-contract-despite-privacy-concerns/article_3286d8fe-1b5d-47e8-87c4-35209d4b3f6c.html

Featured photo by Michael D Beckwith on Unsplash.