If you are a council member, township trustee, mayor, manager, police leader, attorney or other local official reviewing an automated license plate reader contract, this page is for you.
You do not have to agree with DeFlock Metro Detroit.
But before voting to continue a network that records and searches vehicle-location information, residents should be able to expect one thing:
A fresh, informed decision.
Not automatic renewal.
Not “we already have it.”
Not “other cities use it.”
A real decision based on what the system does today, what it costs, what it has accomplished locally and what risks come with continuing it.
1. What exactly are we renewing?
Do not stop at Flock cameras.
Ask for the current product list.
Does the agreement include fixed license plate readers, mobile readers, video cameras, software subscriptions, vehicle-description search, natural-language search, analytical tools, alerting, integrations, shared camera access or other services?
Technology can change substantially while the roadside hardware looks exactly the same.
Know what you are actually approving.
2. How many cameras are currently operating?
Ask for the current inventory.
Distinguish between cameras approved, cameras installed and cameras currently active.
Ask whether cameras were added, removed, relocated, replaced or temporarily deployed since the last public approval.
3. What can our personnel search beyond our own cameras?
This may be more important than the local camera count.
Can personnel search data collected outside the municipality?
If yes, how broadly?
Neighboring departments? Countywide? Statewide? Multi-state? Other participating organizations? Private-camera networks?
Ask for something more concrete than “we participate in sharing.”
4. Who can search our local data?
Which outside agencies currently have access to information generated by our cameras?
Who approves those relationships?
How often are permissions reviewed?
Can the vendor change access or configuration?
Have sharing settings changed since the system was first approved?
5. How long is routine data retained?
Do not rely on a generic vendor answer.
Ask for the current local setting.
Then ask whether selected records can be preserved longer, what happens to exported information and whether other systems retain copies after the original record expires.
6. Who inside the department has access?
Ask:
- How many active users are authorized?
- What job roles can search the system?
- What permissions differ by role?
- Who approves new users?
- How quickly is access removed when someone changes jobs or leaves?
- How frequently are access lists reviewed?
7. What stops misuse before it happens?
Audit logs are useful, but they generally tell you what happened after a search.
Does every search require a reason?
Does any category of search require supervisor approval first?
Are sensitive queries treated differently?
Are alerts reviewed before action is taken?
What happens when policy is violated?
8. Who actually reviews the audit logs?
“We have audit logs” is not enough.
Who reviews them? How frequently? Is review automatic, random, complaint-driven or supervisory? When was the last review? What did it find?
A safeguard nobody checks is a much weaker safeguard.
9. Has our system ever been accessed in a way we did not intend?
Ask directly whether there have been unauthorized searches, incorrect permissions, unexpected external access, misconfigured sharing, vendor configuration errors, compromised accounts or policy violations.
If the answer is no, ask how that was verified.
10. What happens when the system is wrong?
ALPR technology can misread plates and databases can contain stale or incorrect information.
Ask what verification is required before officers act on an automated alert.
Is an ALPR hit treated as sufficient by itself? Are plate images manually checked? Are vehicle characteristics compared? How are officers trained to handle uncertain matches?
An automated result should be a lead, not a substitute for verification.
11. What problem did we originally buy this system to solve?
Go back to the original approval.
Was it justified by stolen vehicles, violent crime, retail theft, a specific crime trend, general investigative efficiency or something else?
Then ask:
Did it solve that problem?
12. What has it actually accomplished locally?
Ask for local evidence, not only national vendor case studies.
How many searches were performed? How many useful leads resulted? How many stolen vehicles were recovered? How many cases were materially advanced? How many alerts were incorrect?
Numbers need context, but officials should have something more substantial than “officers find it useful.”
13. Was ALPR information essential to those outcomes?
A case may be described as solved using Flock while also containing witnesses, security footage, a known suspect, phone records, physical evidence or other leads.
Ask whether the ALPR result materially changed the outcome.
14. What does the system cost now?
Ask for the full current cost, including camera subscriptions, software, video products, installation, maintenance, connectivity, integrations, services and renewal increases where relevant.
Then ask what it will cost over the next three to five years.
15. What else could we do with that money?
The comparison is not ALPR versus nothing.
Could the same resources support detectives, forensics, vehicle-theft prevention, crime analysts, targeted security measures, victim services, staffing or another local public-safety need?
16. Has the technology become more capable since we first approved it?
What could the system do when the municipality bought it?
What can it do now?
Which newer features are available?
Were those capabilities part of the original public discussion?
Renewal is an opportunity to evaluate the system as it exists today.
17. Can capabilities change without another public vote?
Can new software, search features, data integrations, sharing relationships or other functionality be added administratively under the existing agreement?
If so, who decides?
18. What are the current contract dates?
Ask for the effective date, current term, expiration date, automatic-renewal provision, nonrenewal notice deadline and early-termination rights.
Do not vote without knowing what legal commitment you are extending.
19. Does this renew automatically?
If yes, consider whether that is appropriate for surveillance technology.
A government should not drift into another year of mass data collection simply because nobody remembered to send a notice letter.
20. Why should renewal be automatic rather than publicly reconsidered?
Surveillance technology affects privacy, police authority, government spending, public trust and civil liberties.
Those are legitimate subjects for public discussion.
21. Have we considered nonrenewal?
Ask first:
What happens if we simply do not renew?
What capability would actually be lost? How often is it used? What alternatives already exist? What would removal cost? Could the department function without it?
A genuine review includes the option of ending the system.
22. What alternatives exist?
Do not accept a false choice between Flock and no investigations.
Ask what the department used previously and what targeted investigative work, security footage tied to actual incidents, warrants, public tips, forensics, open-source research, crime analysis and other proportionate tools can accomplish.
23. Have residents been meaningfully informed?
When was the system last publicly discussed?
Were sharing and search capabilities explained?
Were newer analytical features discussed?
Did residents have a real opportunity to comment?
A line buried in a consent agenda is technically public. That does not necessarily mean the community understands what is being renewed.
24. Do we know what residents actually think?
Do not assume nobody complained, therefore everybody supports it.
Many residents may not know the cameras exist or what happens to the data.
25. What would make us decide not to renew?
Ask:
What fact, failure, cost, risk or lack of effectiveness would cause us to stop using this system?
If the answer is nothing, then renewal is not really being evaluated.
Five questions if you only have five minutes
1. What exactly are we renewing?
Products, cameras, software and capabilities.
2. Who can search the data?
Locally and outside the jurisdiction.
3. What has the system actually accomplished here?
Local evidence, not sales material.
4. What does the contract cost and when can we stop it?
Current cost, expiration, renewal and notice.
5. Why is mass collection necessary compared with more targeted alternatives?
That gets to the heart of the decision.
Questions officials can ask the vendor directly
Consider asking:
- Can our personnel search cameras outside our jurisdiction?
- How broad could that access become under our configuration?
- Who can search information generated by our cameras?
- Can your company change a sharing configuration without local action?
- Which capabilities can be enabled through software after purchase?
- What features have been added to this product recently?
- Can vehicle associations or convoy patterns be identified?
- Can users search by natural-language vehicle descriptions?
- Can video feeds be searched for people based on visible characteristics?
- How are audit logs reviewed?
- What happens if your software incorrectly reads a plate?
- What independent evidence supports your effectiveness claims?
- What happens to our data when the contract ends?
- What does removing the system physically and technically require?
A company confident in its product should be able to answer precise questions.
Questions officials can ask their own police department
Ask:
- Which capability would you miss most if the system disappeared tomorrow?
- How often did you use that capability last year?
- Give us several local cases where it materially changed the outcome.
- What did you use before we had this system?
- What investigations would genuinely become impossible without it?
- What searches are allowed now that were not discussed when we first bought the system?
- How often are audit logs reviewed?
- What is the current sharing configuration?
- What is the false-alert or correction process?
- Have officers ever acted on an incorrect hit?
- What would you recommend if the council required a less surveillance-intensive alternative?
That is not hostility.
That is oversight.
Questions officials should ask themselves
Would I be comfortable explaining this system to residents in plain English?
Do I personally understand how broadly the data can be searched?
Do I know the renewal deadline?
Have I read the current agreement?
Am I relying primarily on the vendor to explain the risks?
Would I approve this system today if we did not already have it?
That last question may be the most useful one.
Existing infrastructure should not receive a lower standard.
Renewal often feels easier than purchase.
The hardware is already there. Staff already use it. The invoice is familiar.
That is exactly when scrutiny can weaken.
After years of operation, officials have more information than they had at the beginning. They can evaluate real cost, real use, real errors, real access, real technology and real alternatives.
Renewal should face a higher-quality decision, not a lower-quality one.
You can support public safety and still vote no.
A vote against renewal does not mean you oppose police, do not care about stolen cars, oppose technology or want investigators to fail.
It can simply mean:
I do not believe the demonstrated benefit justifies routinely recording and searching the movements of ordinary residents.
That is a legitimate public-policy judgment.
Our request to local officials
Before approving another year:
Read the current agreement.
Understand the current technology.
Know who can access the data.
Ask for local results.
Compare the cost with alternatives.
Listen to residents.
And seriously consider:
nonrenewal and removal.
Do not renew a mass-surveillance system simply because renewal is easier than reconsideration.
Contracts, Costs & Renewal Windows →
Do ALPRs Work? What the Evidence Actually Says →