In 2018, Oakland enacted an innovative law giving citizens a voice in police use of surveillance technology. The Electronic Frontier Foundation called it “the new gold standard in community control of police surveillance.” Since then, about 20 other cities have adopted similar laws.
Now, Brian Hofer, one of the architects of Oakland’s law, says it’s not working. Earlier this month, Hofer filed suit against the city and the police department, saying they had repeatedly violated the law.
“We ignored human nature,” Hofer says in an interview. “Police don’t like to be transparent. Surveillance technology use is by design secretive, and no self-interested party is going to voluntarily highlight anything negative about their own proposal.” A spokesperson for the Oakland Police Department says it doesn’t comment on ongoing legal matters.
Even in Oakland, however, the law has given critics of police surveillance a platform. Indeed, Hofer sued under a provision of the law that allows citizens to take the city to court. He hopes it leads to the appointment of an independent counsel to review the police department’s data and assessment of surveillance tech.
“Like any law, [the surveillance ordinance] needs to be enforced,” says Matt Cagle, a staff attorney for the Technology and Civil Liberties Program at the ACLU of Northern California. “Which is why it’s so great to see people in Oakland and San Francisco use it to take the police to court.”
A national review of the laws—dubbed CCOPS, for Community Control of Police Surveillance—suggests other small successes. In Nashville, opposition from a community group created by such a law stopped—at least temporarily—a proposal for the city to buy automated license plate readers.
“We ignored human nature.”
Brian Hofer, chair, Oakland Privacy Advisory Commission
The laws vary in their specifics. Some require regular meetings between police and community members, annual audits for effectiveness and potential bias, greater transparency of vendors and the cost to taxpayers of any new tech, and a period of public comment before purchasing new tech such as body cameras or ShotSpotter, which uses microphones to detect gunfire.
In a student white paper released earlier this year, the Samuelson Law, Technology & Public Policy Clinic at the Berkeley School of Law said many of the ordinances are weaker than Oakland’s. New York City and Grand Rapids don’t empower citizens to file suit, as Oakland does. In six jurisdictions, including Cambridge, Massachusetts, and Palo Alto, California, police are exempt from the rules. So while a library or school would have to allow for public comment for new surveillance tools, police are exempt from restrictions if they’re executing a warrant or responding to a crisis.
Most of the cities give police broad latitude to use surveillance tech during “exigent circumstances.” Students Tyler Takemoto and Ari Chivukula, authors of the white paper, say this can create loopholes in citizen oversight.
“We know that different local governments considered, for example, racial justice uprisings last summer to fall within that category of extenuating exigent circumstances,” Takemoto says.
Acknowledging that there’s no perfect combination of rules, the authors suggest such ordinances empower citizens to sue and create independent bodies to oversee police and provide support. “Maybe the most important thing is the outside advice … a local nonprofit or community group that’s going to stay engaged,” Chivukula says. “If you don’t have public engagement, then there’s no pressure.”
The movement in Oakland toward reining in police surveillance began in 2014, when groups including the ACLU and EFF protested a proposed “Domain Awareness Center,” a fusion center combining microphones, CCTV, and surveillance data.
First created for port security, the city was moving toward approving a citywide expansion. The advocacy groups successfully campaigned to cancel the expansion and create a temporary privacy committee that would write policies for the city’s use of technology. This became an early iteration of the CCOPS model.