With the deadlines of the Minnesota Legislature coming fast, a specific bill that would require outside agencies to investigate fatal
officer-involved deaths may be on life support. It's known as the "Police and Community Confidence Act; a bill with bipartisan sponsorship
that will promote the cooperation and trust between officers and the
citizens they protect." as Senator Latz described the bill on his Facebook page. The bill is SF466 by Senator Ron Latz. The companion in the House is HF453 authored by Representative Cornish.
At this point Tony Cornish who is the Chair of the House Public Safety and Crime Prevention Policy and Finance is in a position to decide whether or not he wants to hear is own bill. It appears based on this week's schedule for hearings so far and discussion around the Capitol, the bill will die.
With the shooting death of a 19 year old in Madison, Wisconsin by a Madison Police officer last week and it being reported in the Twin Cities news market it brings to our attention the Wisconsin law which calls for an independent investigation, which the Minnesota proposal is based on.
The Cornish/Latz bill would oblige an outside agency to investigate officer involved deaths other than the law enforcement entity in which the officer or officers are employed with. For example, an officer of the Minneapolis Police Department (MPD) kills an individual in an officer-related shooting, the MPD would not due the investigation, possibly St Paul Police or even maybe the Bureau of Criminal Apprehension.
Several weeks ago there was a hearing on SF466 on February 19, 2015. Testimony opposing the bill was done by Minneapolis Police Union head John Delmonico, and Brian Rice, who represents the Minneapolis Police Federation. Mr. Delmonico right out of the box in public testimony stated he is there to "talk against the bill." It is very clear that the Minneapolis Police Federation opposes it.
On the other hand I am struck by the Minneapolis Police Federation position. In public data I obtained, Mr. Delmonico in discussion about the Bureau of Criminal Apprehension doing independent investigations in Minneapolis situations, a couple of years ago, stated in an email "in general, do not object to it."
Mr. Delmonico's email communication to Chief Harteau on September 16, 2013 was on a draft procedure titled "Use of the BCA to Investigate MPD Related Incidents" he stated:
"Thank you for providing me with a copy of "Use of the BCA to Investigate MPD Related Incidents" memorandum. I have had an opportunity to review it and in general, do not object to it."
It appears on one hand the main opposition against the independent investigations bill, Minneapolis Police Federation, publicly opposes independent investigations, but privately may have a different position from two years ago. Organizations do change their minds.
The bill is important to have a public hearing in the House and to be continued through the legislative process.
The bill is long overdue. In St Paul alone there have been 11 people killed by police use of deadly force since 2009 per the Star Tribune. To have an independent presence with an independent law enforcement agency investigating these kind of incidents as outlined in SF466/HF453 there comes integrity and believability to the process and that is what is needed.
Tuesday, March 17, 2015
Monday, March 9, 2015
Minn Legislature scrutinizing surveillance about you
The Legislature within several of its committees and soon on the floor are discussing proposals that will allow law enforcement to gather in mass hundreds of thousands, if not millions of license plate scans/reads on innocent people using automated license plate readers. (ALPR) What these scans collect on people as they drive around the streets are license plate number, time, data, and GPS location, but also photos like these:
License-plate reader images. Courtesy of Mike Katz-Lacabe
The collected data are matched against a database that the Minnesota Department of Public Safety operates. The database is known a "hotlist" or "watch list." It is formally known as the Minnesota License Plate Data File. Local law enforcement agencies may have their own watchlists, too.
In simple terms, data collected from a license plate reader is compared to a list of warrants, stolen cars, and a hodgepodge of other data bits in a database. A hit is produced, which then alerts law enforcement that there could be a wanted person in the vehicle.
"What's wrong with that?" law enforcement has asked me.
Nothing is wrong with hit data, and the ability to track down the bad guys. What's wrong is the wat that law enforcement has decided to use the technology for other purposes - without involving the public and policy makers in discussing the implications of the technology.
Most of what license plate readers capture is data on innocent people. We haven't been told about how that data is shared with others - including law enforcement agencies or private companies. Or why a database full of the whereabouts of innocents Minnesotans is necessary to keep for long periods of time. Or more importantly, how the collection of this type of data on innocent and law abiding people presumes everyone is guilty, and turns the presumption of innocence on its head.
The Legislature is currently sorting out the various interests involve in the use of license plate readers. There are two bills that have introduced, and they are at the center of the debate.
The two bills are HF155/SF31 and HF222/SF86. They have major differences in their approaches to LPR:
HF155/SF31 is the position that the Legislative Commission on Data Practices and Personal Data Privacy recommended. The bill permits license plate data that matches the hotlist/watchlist to be retained if it identifies the vehicle or plate as stolen, if there is a warrant for arrest of the owner, if the owner has a suspended/revoked license, or if the data is part of an active criminal investigation. There is no data kept on innocent and law-biding people.
That differs with HF222/SF86, which is the bill being pushed by law enforcement interests. There is a requirement in that bill that data such as location, license plate number, time, data, and GPS coordinates, and photos of all scanned vehicles be kept for 90 days. In other words, law enforcement is able to keep mass surveillance data on innocent Minnesotans.
By far, "non-hit" data is the biggest part of the data gathered by ALPR readers. In 2011, Minneapolis Police collected 3,750,877 license plate scans, but only 0.68 percent (25,543) were hits. Just recently, based on a data request, KSTP was provided with the following. One sees that the percentage is a half a percent of one percent that there are hits:
In both cases, most of the plates belong to innocent drivers. I've filed ALPR data requests since 2011 with law enforcement agencies such as Duluth and Maplewood. On average, less than one percent of plates paired up with a hotlist/watchlist, and even fewer led to an arrest, according to the data I received.
As it heads towards it's May adjournment, the legislature will have many discussions on the ALPR issue. As evidenced last week in a Senate Committee. (Law enforcement-backed license plate reader bill narrowly survives) Many questions still need to be answered. Some of them are: should there be a centralized repository and collection of ALPR data with location and photos of innocent Minnesotans? How deep and expansive should the law enforcement purpose be with the use of ALPRs? And how can First Amendment activities be protected from law enforcement monitoring?
If the Legislature decides to keep the kind of data as outlined at the beginning of this post, it will be setting the stage for collecting mass surveillance data on innocent Minnesotans for all other law enforcement technologies that are on the horizon, including facial recognition software.
Whatever the product of the Legislature will be, it must be one which achieves common aims of public safety, but also does not keep huge troves of data on innocent people to be used in integrated networks, shared with the Federal government, runs against our tradition of specific, targeted investigations, presumption of innocence, and our privacy and liberty traditions.
License-plate reader images. Courtesy of Mike Katz-Lacabe
The collected data are matched against a database that the Minnesota Department of Public Safety operates. The database is known a "hotlist" or "watch list." It is formally known as the Minnesota License Plate Data File. Local law enforcement agencies may have their own watchlists, too.
In simple terms, data collected from a license plate reader is compared to a list of warrants, stolen cars, and a hodgepodge of other data bits in a database. A hit is produced, which then alerts law enforcement that there could be a wanted person in the vehicle.
"What's wrong with that?" law enforcement has asked me.
Nothing is wrong with hit data, and the ability to track down the bad guys. What's wrong is the wat that law enforcement has decided to use the technology for other purposes - without involving the public and policy makers in discussing the implications of the technology.
Most of what license plate readers capture is data on innocent people. We haven't been told about how that data is shared with others - including law enforcement agencies or private companies. Or why a database full of the whereabouts of innocents Minnesotans is necessary to keep for long periods of time. Or more importantly, how the collection of this type of data on innocent and law abiding people presumes everyone is guilty, and turns the presumption of innocence on its head.
The Legislature is currently sorting out the various interests involve in the use of license plate readers. There are two bills that have introduced, and they are at the center of the debate.
The two bills are HF155/SF31 and HF222/SF86. They have major differences in their approaches to LPR:
HF155/SF31 is the position that the Legislative Commission on Data Practices and Personal Data Privacy recommended. The bill permits license plate data that matches the hotlist/watchlist to be retained if it identifies the vehicle or plate as stolen, if there is a warrant for arrest of the owner, if the owner has a suspended/revoked license, or if the data is part of an active criminal investigation. There is no data kept on innocent and law-biding people.
That differs with HF222/SF86, which is the bill being pushed by law enforcement interests. There is a requirement in that bill that data such as location, license plate number, time, data, and GPS coordinates, and photos of all scanned vehicles be kept for 90 days. In other words, law enforcement is able to keep mass surveillance data on innocent Minnesotans.
By far, "non-hit" data is the biggest part of the data gathered by ALPR readers. In 2011, Minneapolis Police collected 3,750,877 license plate scans, but only 0.68 percent (25,543) were hits. Just recently, based on a data request, KSTP was provided with the following. One sees that the percentage is a half a percent of one percent that there are hits:
In both cases, most of the plates belong to innocent drivers. I've filed ALPR data requests since 2011 with law enforcement agencies such as Duluth and Maplewood. On average, less than one percent of plates paired up with a hotlist/watchlist, and even fewer led to an arrest, according to the data I received.
As it heads towards it's May adjournment, the legislature will have many discussions on the ALPR issue. As evidenced last week in a Senate Committee. (Law enforcement-backed license plate reader bill narrowly survives) Many questions still need to be answered. Some of them are: should there be a centralized repository and collection of ALPR data with location and photos of innocent Minnesotans? How deep and expansive should the law enforcement purpose be with the use of ALPRs? And how can First Amendment activities be protected from law enforcement monitoring?
If the Legislature decides to keep the kind of data as outlined at the beginning of this post, it will be setting the stage for collecting mass surveillance data on innocent Minnesotans for all other law enforcement technologies that are on the horizon, including facial recognition software.
Whatever the product of the Legislature will be, it must be one which achieves common aims of public safety, but also does not keep huge troves of data on innocent people to be used in integrated networks, shared with the Federal government, runs against our tradition of specific, targeted investigations, presumption of innocence, and our privacy and liberty traditions.
Subscribe to:
Posts (Atom)