> It's practically impossible to build a system that "can't be abused"
For ALPRs? I’d make queries public with a short delay, including with a unique identifier for the cop initiating the query. Data automatically deleted within an interval.
And then you feel comfortable guaranteeing that it could never be abused?
The issue is being brought up by the state auditor. This article is literally what would happen anyway if your pet policy was enacted. The police would ignore your little policy, and the standard would have to write an article about the abuse. Hopefully that article would drive public opinion enough for change to happen.
As part of a Flock search, police have to provide a “reason” they are performing the lookup. In the “reason” field for searches of Danville’s cameras, officers from across the U.S. wrote “immigration,” “ICE,” “ICE+ERO,”
Well they didn't. The reason we just read the article we read was because they looked in the logs, and the logs included well written reasons that were illegal. So they wrote an article.
How does stopping them from writing "fuck you" in the field (which they provably didn't, considering they found the queries), or giving you access to it, help in any way in this situation? You're going to have to make an argument here for it to make any sense.
For ALPRs? I’d make queries public with a short delay, including with a unique identifier for the cop initiating the query. Data automatically deleted within an interval.