The post In search of privacy advocacy from underrepresented communities appeared first on Seattle Privacy Coalition.
]]>Below is an email sent to a Seattle Police Department program manager regarding the the Muslim, Sikh and Arab Advisory Council to the Seattle Police Department on November 19th, 2014. The program manager, Maggie Olsen, promptly replied stating that my email had been forwarded to the Commander of the Community Outreach Section, Captain John Hayes. Jan and I have not yet received a reply.
Hello Maggie, My name is Christopher Sheats, a concerned citizen of Seattle and a volunteer for the Seattle Privacy Coalition (SPC) (seattleprivacy.org). My colleague Jan is CC'd, she is the SPC director. I'm writing with regard to the Muslim, Sikh and Arab (MSA) Advisory Council to the Seattle Police Department. This email may be better directed to Detective Yanal Vwich, or possibly Chief Kathleen O'Toole. I attended my first MSA meeting on October 2nd, 2014. I advertised that the Citizens Technology and Telecommunications Advisory Board (CTTAB) was planning a privacy symposium to focus on the privacy impact to vulnerable populations in Seattle. The privacy symposium is supposed to happen next year, but I am not yet sure about details. I also want Detective Yanal Vwich and the MSA to be aware that the City of Seattle is establishing a special, and likely permanent, privacy advisory board for the city. For more information about the new privacy board: CITY OF SEATTLE LAUNCHES DIGITAL PRIVACY INITIATIVE http://murray.seattle.gov/city-of-seattle-launches-digital-privacy-initiative/ Seattle Takes the Lead in Nationwide Surveillance vs. Privacy Debate https://www.seattleprivacy.org/press-release-response-to-seattle-privacy-initiative/ Composition of City’s Privacy Advisory Board (written by Jan) https://www.seattleprivacy.org/composition-of-citys-privacy-advisory-board/ I have several questions, please help where possible. Q1- It appears that MSA and the East African Advisory Council's have been combined and that their meeting schedule has been severely reduced. Why is that? Q2- Given the privacy and trust implications of these vulnerable populations, I was surprised to learn that these meetings were being held at a government facility. I know that this has a negative impact on attendance. Why can't it be changed to a community center, with more access to bus routes? NSA Surveillance Chilling Effects: HRW and ACLU Gather More Evidence https://www.eff.org/deeplinks/2014/07/nsa-surveillance-chilling-effects Q3- Would't it be prudent to have a member of the Muslim community to be directly involved with the Seattle Privacy Advisory Board? Latest Snowden Leaks: FBI Targeted Muslim-American Lawyers http://www.wired.com/2014/07/snowden-leaks/ One of the attendees bluntly accused that the FBI was spying on people in his community. The FBI attendee blatantly lied in response--given the Snowden revelations that go into specific proof that says otherwise. The Seattle City Council, the Seattle Police Department, local FBI offices, and the City's IT Dept all share the responsibility in gaining trust though cooperation and privacy enhancements. Having gone to just one MSA meeting, I was almost overwhelmed with the amount of distrust between attending members of vulnerable populations and the various US Gov attendees. As an empathetic white male, it was uncomfortable. On behalf of the Seattle Privacy Coalition, I would like to assist wherever possible to help bridge this divide, regarding trust through privacy. Please share the following information to the respective Advisory Councils where appropriate. It would also be great to get members of MSA involved with our citizen group (Seattle Privacy Coalition) for greater diversity: Send an empty email to the following address to be put on our announce list: [email protected] Seattle Privacy Coalition can be contacted directly: [email protected] I can be contacted directly, and I have a public PGP key available: [email protected] 7DFF 4EE5 1C63 9060 C9C9 A48A BEAF 1420 523A EB46 If any of you would like help setting up your own PGP key-pair so that people can securely contact you, or an alternative secure chat application, please let me know. Lastly, with your permission, I'd like to publish any or all responses to our blog, SeattlePrivacy.org, so that the public can be further educated about these ongoing issues. Cheers Christopher Sheats citizen
The post In search of privacy advocacy from underrepresented communities appeared first on Seattle Privacy Coalition.
]]>The post “If not for Seattle, this history would be different” appeared first on Seattle Privacy Coalition.
]]>A few days before the Seattle City Council announced its precedent-setting privacy initiative, the year’s most anticipated documentary, Citizenfour, opened at the Uptown SIFF Cinema. Laura Poitras’s third film about the post-9/11 American security state tells the story of Edward Snowden, the NSA whistle-blower who made “dragnet surveillance” a household term.
Seattle’s step toward privacy and accountability was well-covered in the local press and also made the leap to a couple of governance trade journals. Seattle Privacy made sure that Laura Poitras herself knew what had happened here at the same time that her film was drawing capacity crowds. She sent us congratulations:
It is fitting that Seattle is first to respond – it is the home of NSA
PRISM partners such as Microsoft, as well a strong community of people
building alternatives to dragnet surveillance. These alternatives, as
well as informing and engaging with the people of Seattle, are a step
toward regaining meaningful democratic oversight relating to security
and privacy in our country.
If not for Seattle, this history would be different.
When the Seattle Privacy Coalition came together in early 2013, the city’s political establishment issued us the tin-foil hats reserved for people who worry about government surveillance. The disgraced, federally supervised Seattle Police Department was so used to getting its way in technology matters that it shrugged off negative public reaction to the “port security” camera network. In talks with city officials, we provoked eye-rolls and knowing smirks by suggesting that the city should pass up federal grant money that paid for boondoggles such as police drones. [Note: See the update at the end of this post. It ain’t over.]
After Snowden, the complacency was gone. Little has changed at the national or state levels — the security agencies still run Congress and the White House, Boeing still dictates to Olympia. But locally, there is movement. DHS-funded spying and cops in tanks have become issues with names: Oakland, Ferguson. The city establishment’s dread of controversy now works in favor of privacy advocates. The security lobby will have a hard time influencing every petty municipality the way it influences the federal government.
An evolving model for political action emerges from Citizenfour. In a world where democracy and the press have ceased to function at the highest levels, we watch lone individuals making fateful choices grounded in their private experience. These precise moments of integrity contrast with farcically mediated global contexts: archival footage of NSA Director Keith Alexander and National Security Director James Clapper telling extravagant lies to Congress; a frantic scrum of boom-bearing reporters around Glenn Greenwald and his partner (and taking care to edit themselves out of the film they will broadcast); or the recurring apparition of Wolf Blitzer playing Wolf Blitzer. Always there is a strong implicit case for what it real and what is not, and where personal agency lies.
Poitras, not Snowden, is the first example of this in Citizenfour. Out of the blue, Snowden sends her an encrypted email message, an event recreated on-screen as white text unspooling in the black void of a Linux computer terminal. Disembodied in this weirdly intimate environment, an as yet anonymous Snowden tells her he is a spy, that he has classified disclosures to make, that there is great danger, and that their joint government adversary can attempt one trillion password cracks per second. Her private decision to accept this mysterious challenge leads to the events of the movie. When she later asks “Citizenfour” why he had chosen her, He tells her, “You chose yourself.”
Poitras next tells the story of NSA veteran William Binney. After the end of the Cold War, he developed systems to automate the collection and analysis of telecommunications metadata. Originally, the targets were foreign, but shortly after 9/11, NSA turned Binney’s work into the basis of its new program of blanket domestic surveillance. His internal protests against NSA’s lawless, ineffective, and wasteful policies went nowhere, and he soon left the agency. After being raided at gun-point in 2007 during an FBI leak investigation (in which he was later cleared), Binney gained prominence as one of the most outspoken NSA whistle-blowers prior to Snowden.
The misguided raid on Binney was provoked in part by the revelations of Mark Klein, who is not actually in the movie, though we do see a hearing from one the lawsuits that resulted. Klein was a technician for AT&T who discovered that Room 641a at 611 Folsom Street in San Francisco was an NSA diversion site for all of AT&T’s Internet and telephone traffic. Appalled by what amounted to a tap on the entire Internet, Klein took his story to the Los Angeles Times, which refused (under government pressure) to print it. He next took it to the New York Times, which also bowed to government pressure for a year before finally publishing it in 2005.
Seattle Privacy’s co-founder Jacob Appelbaum turns up twice in the film, once before and once after his NSA reporting forced him into Berlin exile. In one segment, he presses an Occupy Wall Street audience to consider whether they have been personally under surveillance, and lists ways it could have happened — not just by means of telephones, email, and the Web, but also credit cards, travel passes, etc. He calls them canaries in a coal mine who are experiencing what everybody will experience in the near future. (As Jacob likes to say, “My present is your future,” though he now thinks the future has pretty much arrived for everyone.) The personal experience entails the universal problem, and is the key to fighting it.
We also meet Ladar Levison, the [former] proprietor of the secure email service Lavabit. Its most famous customer: Edward Snowden. Levison built an encrypted mail service that collected no information on its users, and thus had nothing to give law enforcement even when subpoenaed. Unable to identify Snowden’s correspondents in the usual way by seizing metadata, the FBI told Levison to give up Lavabit’s master SSL encryption keys, which would allow them to uncloak the entire Lavabit customer base secretly in real time. Levison instead shut down his business rather than betray his customers’ privacy. Try to imagine that in a corporatized setting where profit is paramount and ethical concerns are actionable in civil court.
In bare outline, Snowden’s own story is that he gave up his prior life and risked life imprisonment (or worse) to expose the actions of NSA and its partners. Most will remember his principled if fatalistic rationale from the original June 2013 interview. In Citizenfour, Snowden’s anxiety and regret become palpable. He masters his fear and steps through the hotel room door into what may be the waiting arms of a hostile government. Though Snowden repeatedly downplays his role in leaking the documents — “I’m not the story” — his choice is the story.
At Seattle Privacy, we hope to change how citizens are treated by their local government and by the police. The recent good news notwithstanding, we will continue to push the City Council to follow through on its stated intentions. We don’t want the promised oversight structure to end up a dead letter like Ordinance 124142, another privacy “first” that was passed 18 months ago and never enforced. At stake is a role for Seattle as a national model of awakened democratic government. It took bold individuals to expose the corrupt surveillance state, and it will take a bold community to prove Laura Poitras right: “If not for Seattle, this history would be different.”
Even as I wrote and published this, the City Council threatened to reverted business-as-usual by planning a budget hearing for a ShotSpotter-type system. For information about the city’s past flirtation with outdoor audio surveillance (and some sleazy video of Seattle politics at its worst) see our ShotSpotter fact sheet. Rest assured we will communicate to our leaders what we think of their renewed interest in ShotSpotter.
The post “If not for Seattle, this history would be different” appeared first on Seattle Privacy Coalition.
]]>The post Seattle Takes the Lead in Nationwide Surveillance vs. Privacy Debate appeared first on Seattle Privacy Coalition.
]]>This morning, Mayor Ed Murray and Seattle City Council members Mike O’Brien and Bruce Harrell boldly announced a new initiative[1] to begin to address the erosion of privacy in our society. Seattle is the first city in the nation to take such a proactive and farsighted step. The initiative will begin with a systematic review of the potential effects on personal privacy of all city programs and policies.
“This move will save Seattle taxpayers money by limiting spending on ideas like surveillance cameras or drones that later need to be scrapped.” -Adam Shostack
The Seattle privacy initiative comes two years after disclosures about Seattle Police Department’s acquisition of surveillance drones[2] and installation of a public surveillance camera network[3] drew public concern and protest. This debate merged with concerns about spying on political activists, unchecked use of facial-recognition technology, locational surveillance via automated license plate readers, and data sharing with private entities along with state and federal agencies.
The Seattle Privacy Coalition applauds Seattle’s leaders and legislators for their bold move to grapple with the difficult and vexing issue of protecting privacy while embracing technological innovation, and for their commitment to expanding civic involvement and bringing more voices to the table.[4]
“We hope that this effort will serve as a model for other municipal governments, and give heart to grassroots privacy advocates everywhere,” said Jan Bultmann, co-founder of SPC. “This development shows that even if our federal government is too paralyzed and beholden to corporate interests to act, we don’t have to sit back and watch our right to privacy evaporate. We can work with local governments who can still hear and respond to our voices.”
“This move by our city’s leadership is exciting,” said Christopher Sheats, Seattle resident and political activist. “It demonstrates that they’re listening to those whom they represent, and that community input is valued here in Seattle. The proposal to further implant privacy-strengthening processes in our city’s government is a refreshing reminder that civil liberties can be protected regardless of advancements in technology.”
“I am happy to see Seattle recognizing the importance of privacy to our citizens and residents,” said Adam Shostack, Seattle resident and author of Threat Modeling: Designing for Security. This move will save Seattle taxpayers money by limiting spending on ideas like surveillance cameras or drones that later need to be scrapped.”
“Meaningful transparency and accountability requires regular people’s fully informed civic involvement. I’m glad to see that the city of Seattle has heard the call and is committing itself to democratic action. This moment in Seattle is made possible because of the sacrifice and courage of the whistleblower Edward Snowden. It is exactly these kinds of changes all across America that he worked to create,” said Jacob Appelbaum, privacy journalist and co-founder of of Seattle Privacy Coalition.
THE PLAN IN BRIEF
2014
2015
Seattle Privacy Coalition is a group of current and former Seattle residents that formed in April 2013 over a shared interest in transparency, accountability, and accuracy about the current state of privacy, security, and related issues. Our first project was to explore, document, and provide oversight relating to the Seattle Police Department’s surveillance camera network. Our mission is to urge and empower the City of Seattle to take advantage of Seattle’s leadership in technology and commitment to civil rights to lead the United States to restore and protect all people’s right to privacy.
[1] http://clerk.seattle.gov/~public/meetingrecords/2014/cbriefing20141103_3a.pdf
[2] http://westseattleblog.com/category/seattle-police-surveillance-cameras/
[3] http://westseattleblog.com/category/seattle-police-surveillance-cameras/
[4] https://www.seattleprivacy.org/mission/
The post Seattle Takes the Lead in Nationwide Surveillance vs. Privacy Debate appeared first on Seattle Privacy Coalition.
]]>The post We get excellent coverage in the Seattle Times appeared first on Seattle Privacy Coalition.
]]>The post We get excellent coverage in the Seattle Times appeared first on Seattle Privacy Coalition.
]]>The post The sort of thing we are curious about… appeared first on Seattle Privacy Coalition.
]]>In bland technical language, we learn that the network has the following capabilities.
However, these details raise questions that still have not been answered by the Seattle Police Department or any other city office.
These are questions that should have been asked and publicly debated at early stages of the planning process. They also quickly become issues of general policy: If data is collected, it will be used by any legal or illegal branch of government whose agents can pick up a phone. To protect privacy, don’t collect sensitive information in the first place.
Below is a link to the source documents, courtesy of Tacoma-based Infowars reporter Mikael Thalen, who discovered them on the Seattle.gov Web site:
Or download the document.
The post The sort of thing we are curious about… appeared first on Seattle Privacy Coalition.
]]>The post How police culture works against effective police reform appeared first on Seattle Privacy Coalition.
]]>
I have a long history of reading the internal and inter-agency emails of police intelligence units, mostly thanks to the Public Records laws of the State of Washington. I’ve also been known to avail myself of the opportunity to dumpster-dive for records discarded by police and have even gone so far as to reconstruct the shreds of police reports which were found in trash bags. I’ve had a long time to think about police culture as an outsider investigator, police reform activist, and protester over the course of about twenty years.
Formal vs. informal power
Police, like any other group of people, are not simple or monolithic in their viewpoints or attitudes. Despite this, I have been able to see some general trends in the outlooks and attitudes of the police I study, especially in the police intelligence units and drug task forces I have tended to focus upon. These are a few of the things I have learned.
Police memoirs and agency histories agree that there is a cultural divide between patrol officers and police administrators, a distinction often seen in movie and TV dramas when conflict arises between the “desk cop” and the “street cop.” There is a grain of truth here, a difference in style and outlook necessary for the police officers who manage other police officers and interact with higher authorities such as police commissioners or sheriffs or city council members. The focus for any manager is always on where authority lies, who answers to whom, and what the organization chart looks like. Nowhere is this focus sharper than when the persons being managed are armed and authorized to make regular use of physical violence.
On the other side of that coin, street cops are of course jealous of their power and alert to any attempt to modify or control it by those outsiders who “just can’t understand” and “don’t risk their lives” as they do. The culture of the street cop can best be exemplified in the “guild rep,” and is expressed in police guild contracts with police management, which explicitly forbid questioning a patrol officer about the use of deadly force for at least three, and often five, working days after the event.
It is this guild-based center of power (often left off of the official organization chart) which most persistently resists personal body-worn cameras, in-car cameras, and other tools of accountability because the first and best users of these technologies will always be police managers. In an especially bad guild-run police agency, police who have been fired come back to work (with back pay) and public records requests have to pass inspection by a guild rep. When the US Department of Justice steps into an agency and tries to reform it by selecting or replacing its managers and its processes, its success in effecting lasting change is often limited by its failure to recognize and confront the actual power of the organized street cops, whether organized in the guild or expressed in “blue flu” epidemics or selective non-patrols of key city council districts. Informal power networks often have as much power as formal ones, especially if they are free from interference because they are covert.
What the police are for
A similar failure of outsider-led police reform often arises from the misunderstanding of how police agencies infringe on protester rights. The police as an institution are constructed to manage social disruption and strikes, keeping the private ownership of enterprises from being forcibly ejected by the working persons who daily occupy the enterprises. Police see protest as the crack from which such events would flow, and are institutionally opposed to protests unless they are organized by police, for guild purposes. Police intelligence units are the ultimate expression of this distrust of protest. This culture of distrust bridges the street-cop/desk-cop divide. It can flow from management directives down to patrol level or arise independently from patrol officers reacting to unexpected, spontaneous protests. In either case, activists cannot trust either side of the police agency to actually protect their rights to protest. Fundamentally this is NOT what police agencies are made to protect, despite all propaganda to the contrary.
Yet City Council members and activists (often relying on the official organization chart) focus their efforts on management or policy when called on to address police agency interference in legitimate protest movements. Thus the activist often hears the police manager’s response that the police have arrived “to protect everyone’s rights” and that they will only intervene “if there is violence.” I cannot relate to you how many times I have heard these words spoken by a man dressed in padded armor, while standing in front of an entire array of men similarly equipped, all of them armed and trained how to use those arms. Oddly enough this statement has never made me feel secure in the use of my rights.
Co-opting the politicians (or worse)
Police managers run interference with the elected (transient) layer of government, while conditioning them through continuity of government (COG) arrangements and private threat assessments and executive session briefings to accept the permanent security state, and to distrust protesters and their motives. You might not realize it, but there is a specific Washington State Patrol officer assigned to find and secure each state-level elected official in case of an emergency. Each official has a WSP “buddy” or “COG Officer” with that official’s personal contact info and addresses.
I can’t emphasize enough the potential for psychological buy-in which this arrangement supports and engenders. Because they depend upon the police intelligence and security apparatus for their personal safety, in a manner which is annually reinforced and practiced in drills, the elected official can come to identify with the stated assumptions implicit in the police intelligence institutions beyond the level which would be expected from simply reading briefings and accepting them as true reflections of reality.
I also can’t emphasize enough the implications of such an arrangement if the security state were ever to lose confidence in the system of electoral politics. Is “continuity of government” a deliberate plan to have a ready-made coup in place if it is ever needed? Perhaps it was intended to be so; it would certainly hang well on that frame as long as most of the COG officers either believed the emergency situation were dire enough, or that the elected officials they “serve” were beneath their contempt. But it certainly doesn’t depend on being explicitly thought of as a coup to function effectively that way in a crisis.
The military mindset
From my readings, the types of folks who enjoy making lists of activists and their planning meetings and passing those lists around as “threat assessments” are former military (often former military intelligence) and they do this either as contractor intel analysts or as police employees of various types. I’ve seen everything from IT support personnel doing it, to police detectives doing it, to US Army Reserve intelligence managers doing it as Washington State Fusion Center contractors paid under WSP/DHS grants. They all share common assumptions in their reporting and analysis which stem from who they are as people.
The common link is that they are mostly or all rule-followers. Their thinking is not “rights based” but rather “permission based.” Explaining that you have to respect the rights of protesters to these folks just gets a blank stare. They literally have no idea what you might mean by that. They walk out into the world with a notion of duty and service, they accept that what they were told by higher command is what is important, and if you contradict these orders then you’re a traitor or a terrorist.
If you tell them they are doing terrible things they will not believe it for a minute – they are keeping America safe from all the things that they can imagine some brain-damaged protester might do, if not properly supervised. This is the type who tells you that you can’t take pictures of (This Or That) because (My Boss Said So). It is this type who tells you that “I am the Law.”
Meanwhile, their managers are the types who know that when an elected official asks whether rights are being violated, they had better hand that official a nice organization chart to explain (A) that the system is VERY VERY COMPLEX and (B) Fully Audited To Make Sure They Follow Rules. These are great things until you realize that it doesn’t matter how you write those rules if the rules tell the practicing intelligence analyst to respect fundamental rights (apply a general principle to various situations) rather than evaluate whether a protest group followed the orders they were given, whether by the law or by the sergeant or lieutenant in charge of making the rules clear to the protest group. Making the evaluation is objectively possible while applying a principle is not for a rules-based individual whose sense of order is violated or insulted by the protester’s ideology. How could a criminal have a “right” to block a car in traffic on a road, after all?
The person who knows that the First Amendment protects your right to protest knows that this right is more fundamental than the privilege to drive a car, which must be licensed and approved as to its fitness to be on the road. There is no government “fitness test,” meanwhile, for public political speech – it must only not harm others or call for imminent harm. The officer who hears his sergeant shout at the protesters to get out of the road hears that they have been given an order (an order HE would have to follow), so naturally he sees no problem applying discipline to the protesters (unruly children!). And of course this application of force to clear a road is seen in dozens of cases, even to the point of using a Taser or a baton to harm protesters and in rare instances kill them, all in order to protect the “right” to drive a car to the grocery store or the hospital. Even though the supposed reason to remove the protesters would be “for their safety.” Again, unruly children do not get to decide for themselves what risks they adopt.
Assessing the protester threat
To illustrate this point, let me pull out two quotes from the 2013 threat assessments around May Day 2013, the first from the Washington State Fusion Center’s April 5th May Day threat assessment:
While the WSFC does not track First Amendment protected activities of groups or individuals, May Day events have been plagued by significant criminal conduct carried out by a small group of people who commit criminal acts (vandalism, property damage, graffiti, etc.).1
Now imagine saying that same sentence with the event “May Day” replaced with the word “Seafair,” or “football game” and it becomes obvious that this “threat assessment” contains some serious political animus toward the political importance of May Day for Anarchists, Socialists, and other counter cultures rather than an objective concern over “vandalism, property damage, graffiti, etc.”
A further quote from a smaller police intelligence unit, the Regional Intelligence Group 5 (Pierce County) shows how police intelligence relies on cut-and-paste lip service for rights, while contradicting the spirit of those words with the actual content of the quote:
While the SSRIG does not track First Amendment protected activities of groups or individuals, May Day events have been plagued by significant criminal conduct carried out by a small group of people who commit criminal acts (vandalism, property damage, graffiti, etc.)….
LE officers need to be aware those who are involved and planning this event have been involved in aggressive Port Military Resistance Protests at the Port of Tacoma, to include Police Brutality protests in Tacoma in the recent past.2
If the SSRIG / RIG5 “does not track First Amendment Protected activities” (such as association) then how, exactly, would they know that “those who are involved and planning this event have been involved in aggressive Port Military Resistance Protests at the Port of Tacoma, to include Police Brutality protests in Tacoma in the recent past.”? And why would protesting police brutality be a police intelligence issue, anyway?
Any attempt to re-write the rules and procedures to protect protester rights will fail because of how the people who organize police intelligence think about the world. The problem is that people who believe in rights and the application of principles to situations are not the types who go into managing or distributing police intelligence. Built on that foundation, the little individual lies each officer tells about their “study subjects” can compound quickly into a domestic terrorism dossier for a simple protest organizer. Until 2009, the Washington State Patrol actually ran an informal database-sharing effort in a series of “Domestic Terror Conferences” which apparently profiled activists and protesters as long as they had been accused of violence during one of their arrests, without apparent regard for whether they had actually been convicted of a violent crime.3
WSP ended its sponsorship of the DT conferences and they were taken up by the Portland Department of Justice in 2010 and 2011. The WSP explanation for ending their sponsorship of the “DT Book” database in the last year they hosted the associated conference is telling:
Perhaps some clarification is due on the reason for discontinuing the “book”. The reasons are myriad and we hope that this will help you have a better understanding of our decision.
- Intelligence information must be vetted through a supervisor and the Section Commander for inclusion into the database (to comply with LEIU standards and 28CFR part 23).
- No Intelligence data should be kept in separate files/locations.
- The information for the book is derived from multiple sources and there is no verification that it been vetted for accuracy and completeness nor the reliability of the source and the content.
- In reference to the purge requirements, the information is not WSP’s information thus we have not established the retention period and at time of purge we would have to verify the information has not been updated prior to that purge creating more work than necessary for WSP.
- We do not know how the information was collected. Each state, as well as federal agencies, has different collection and retention standards that could be in conflict with WSP requirements. That could easily open all of us to extensive scrutiny and outside audits.
- Finally, WSP OCIU [Organized Crime Intelligence Unit] has limited ability to continue to devote such intense levels of time and resources toward putting together this information, maintaining it, and distributing it to these other agencies.
We welcome discussion on submitting information or intelligence into another database, such as the RISS Network nodes (WSIN, RMIN, etc), which would enhance the aspects of the original concept of the “book.”4
Even more telling is that I and activists associated with me had caught US Army spy John Towery about five months before this email was written, and a top-down review of Washington State Police intelligence was underway at the time.5
Conclusion
In light of my research and experience studying law enforcement professionals, I call on elected officials and specifically the DOJ monitor assigned to review the progress of reform in SPD, to recognize that there are institutional and attitudinal barriers to change that need to be confronted. It really is not the business of any police agency to decide which potential protest events will be met with force, and which protest organizers will be interfered with, arrested, followed, watched, and lied to by undercover officers and their informants. By starting down that road, these police agencies have abandoned their Constitutional oaths in favor of their convenience and their corporate patrons. It is time to return to the rule of law, if you’ll hear that from an Anarchist like me.
The post How police culture works against effective police reform appeared first on Seattle Privacy Coalition.
]]>The post Seattle Privacy expands mission to include state, federal issues appeared first on Seattle Privacy Coalition.
]]>Then, Edward Snowden surfaced in Hong Kong, with revelations about the NSA’s illegal dragnet surveillance programs and what has fairly been called the militarization of the Internet.
At first we tried to stay focused on what we could do right here in Seattle. We dreamed of presenting Seattle to the world as a model of legislative success in curtailing surveillance. We still do
Over time, however, all of our members have been drawn into other efforts as well. This week we’re talking to US Senator Maria Cantwell, next week we’ll be lobbying state elected officials in Olympia. It’s time for us to acknowledge that we are no longer a municipally focused organization. We’re working with Washington State ACLU and the national organization Free Press to identify legislators to contact and legislation to promote.
We seek the protection of privacy for all people, where ever they live, whatever their citizenship, against increasingly totalitarian government surveillance programs and intrusive and cynical corporate data collection. Our focus remains on policymaking, but we are happy to publicize other approaches, including direct action, protests, petitions, training and educational efforts, and more.
Be seeing you!
The post Seattle Privacy expands mission to include state, federal issues appeared first on Seattle Privacy Coalition.
]]>The post How Seattle City Council can fix broken Seattle Police oversight appeared first on Seattle Privacy Coalition.
]]>We, your constituents, respectfully request that you change your oversight strategy toward the Seattle Police Department in response to the events of 2013, as described below.
Traditionally, the record suggests, Council has treated SPD requests for funding and for entrance into partnerships with other governmental bodies and private companies as innocuous, as business as usual, as more of the same.
This seems an inadequate approach, particularly given the following:
In light of these developments, we ask that you, our elected representatives, step up the level of scrutiny that you bring to all SPD initiatives.
We hope that you will send to SPD a message similar to the following:
Our constituents no longer have the trust in your organization that many of them once had. We have watched with surprise and dismay as your staff are repeatedly found to have acted with disregard for individual privacy and with resistance to institutional transparency. Those days are over. We now intend to oversee your department’s actions with even greater rigor than that with which we oversee other city departments. We will not treat reviews of audits as perfunctory. We will insist on systems that prevent inappropriate use by design, not simply by policy. We will not authorize the acceptance of federal grants that allow you to operate outside of our oversight. We will look upon every proposal for new SPD policies or equipment with skepticism. Our constituents demand it.
The post How Seattle City Council can fix broken Seattle Police oversight appeared first on Seattle Privacy Coalition.
]]>The post Why we & the federal monitor agree: don’t trust SPD on surveillance tech appeared first on Seattle Privacy Coalition.
]]>As reported in the Seattle Times, a draft report on the Seattle Police Department’s performance has been released by the federally appointed monitor, Merrick Bob, and it is not pretty. Say what you like about the federal government’s own violations of constitutional and human rights, the Department of Justice has served Seattle well by placing SPD under court review and holding it to an objective standard of policing. The excessive force — the unnecessary deaths, beatings, profilings, and daily humiliations — that compelled the DOJ to get involved must stop, and the SPD must fulfill its mission to serve and protect the people of Seattle.
As the city’s privacy-lovers already know, excessive force is not the only problem at SPD. It was grant-chasing SPD leaders, particularly in the Information Technology division, who accepted money from the Department of Homeland Security and deployed a city-wide surveillance of security cameras and radio links without public review or debate. In response to community apprehension (especially in West Seattle, where the first cameras went up), SPD’s leadership promised to manage the collected data responsibly and to allow public scrutiny of the images being captured. Additionally, Ordinance 124142, passed in March 2013, required SPD to submit a use policy within 30 days and gain council approval before turning on the system.
Eight months have passed since March, and no use policy has appeared. After people recently noticed that the system was turned on anyway, SPD promised to turn it off again. A legitimate question at this point would be: Who is running this circus?
The federal monitor’s report makes clear that SPD’s Information Technology division is a big part of the problem. There is not only lack of leadership from the City and inside SPD, there is, front and center, a simple lack of competence in IT.
The following excerpts from the report highlight IT’s inability to oversee large projects, plan new ones, manage its data, keep its machines working, and on and on. Remember, these are the people who sneaked in a public surveillance net, and then promised to manage its data in the public interest. In fact, they can’t even produce reliable data for Merrick Bobb. The failure of IT to manage (or even locate) its data plays directly into the SPD leadership’s conspiratorial, closed-door management style. Got a Freedom of Information Act request? Sorry, that information was lost. Got a federal consent decree? Sorry, we can’t really tell you what we are doing, because we don’t know, and we don’t want to know.
The Department’s Information Technology (“IT”) leadership has given incorrect or incomplete information to the Monitor and Monitoring Team and has proven itself unable to tackle the management of projects of import or complexity relating to use of force and other areas encompassed by the Settlement Agreement. SPD’s existing capacities to track, analyze, and use data are, at best, weak. The data produced by the IT Department has been error-ridden and inadequate: The SPD simply does not have the data required to implement the Consent Decree, to manage the risk of unconstitutional conduct, to respond to the Monitoring Team’s requests for data in order to measure progress, to enable the Court to assess the speed and good faith of implementation, or to respond to routine inquiries by
City Council for data needed for legislative purposes. (1)
Modern policing is, in short, a scientific and data~driven enterprise…. The Settlement Agreement repeatedly stresses the need for the SPD to gather accurate data by which to manage the risk of unconstitutional policing and measure compliance. The SPD has nonetheless found it difficult to embrace these new technologies. Current data and analytical capabilities are nowhere near adequate. The SPD generates frequently erroneous and incomplete factual information about itself and officer performance. (6)
A business intelligence system, properly conceived and developed, is pivotal to SPD’s ability to hold itself accountable for constitutional policing…. During the last year, the SPD has spent substantial time and money–possibly hundreds of thousands of the business intelligence project because some within the Department firmly insisted that they could develop a system on their own, without input from outside experts or from those who will be the users of the system. A proposed “vendor” solution that would link the Department’s existing, jerry-built silos of erroneous and incomplete data to each other, with a weak interconnection, fell well short of what is needed: a modern, sophisticated, and dynamic tool that SPD can use to pragmatically and rigorously assess its performance. (7)
Despite the Monitoring Team repeatedly advising SPD to tum to outside experts and consider alternative solutions for collecting more reliable data, this advice was slow to gain internal support. SPD’s IT leadership consistently told the Monitoring Team that some interim solutions were not technologically feasib1e–even though they were later shown to be easy to accomplish. (7)
Notwithstanding the SPD’s resistance to change and suspicion of innovation in some quarters, the Monitor emphasizes that there are many talented individuals within the SPD dealing with data and information technology who are working in good faith and taking justifiable pride in their accomplishments. The problem appears Qt to be the lack of a talented and dedicated staff but, instead, a failure by some members of senior IT leadership to fully accept the requirements of the Settlement Agreement…. (7-8)
The Monitoring Team’s third troubling discovery was that, for two consecutive years, the demographic figures for Asian and Caucasian subjects in use of force incidents were notably inconsistent with subsequent years. After confirming the accuracy of its analysis, the Monitoring Team brought this inconsistency to the attention of the Compliance Coordinator’s office. After an inquiry, the SPD explained that, for two years, “Asian” was incorrectly recorded in AIM as “Caucasian,” and vice–versa. Thus, although the Monitoring Team collected use of force data across only seven basic categories, it discovered a critical systematic error. The Monitoring Team understands that no effort is currently being made to audit or otherwise correct these errors. It underscores DOJ’s view that the SPD 1acked–and the Monitoring Team thinks the SPD still lacks–the basic tools necessary to manage the risk of unconstitutional policing. (11)
As this report details elsewhere, video and audio are missing far too frequently for incidents reviewed by the Use of Force Review Board and Firearms Review Board These omissions compromise the integrity and quality of investigations. When ICV [in-car video] is missing, the Department regularly and without additional inquiry accepts the explanation that the officer’s equipment was not properly functioning or that the officer did not know how to operate it. The days of technical issues being an immediately accepted excuse for the absence of video must come to an end so that officers can be fairly held accountable if they inappropriately fail to activate ICV or cause their on-body microphone to be muted during an incident. (13)
The post Why we & the federal monitor agree: don’t trust SPD on surveillance tech appeared first on Seattle Privacy Coalition.
]]>The post Protocols for surveillance data under development in Seattle appeared first on Seattle Privacy Coalition.
]]>Dear Councilmember Harrell,
Thanks so much for all the work you’re doing to address police accountability, the gender pay gap issue, and equitable access to broadband in the city, among so many other issues.
Quick question: In March of this year, Council passed ordinance 124142, which called for the creation of written protocols for City-owned surveillance equipment. The legislation required programs running previously deployed surveillance equipment — specifically, the Alki “Port Security Cameras” — to provide written protocols for their use within 30 days of the passage of the ordinance.
I searched the Council site and the Committee for Public Safety, Civil Rights, and Technology’s recent agendas, but I didn’t see any mention of these protocols under discussion, and was just wondering if you could provide an update about their progress and when the public might hope to have a peek at them.
Thanks very much,
Jan Bultmann
Seattle Resident
Member, Seattle Privacy
Today I got a very encouraging response from a member of CM Harrell’s staff, who wrote that the committee is working with SPD and ACLU on draft protocols for the Wireless Mesh Network cameras. The staff person said, “The document is still subject to further changes and will go before the Public Safety Committee for public discussion. The most recent meeting with ACLU and SPD was on Wednesday, 7/17.”
I’m very glad to hear about this, and we’ll be keeping an eye out for the protocols on the Public Safety Committee agendas for when the draft comes out for public review.
Meanwhile, we’ve updated our map (see right) of the mesh network to include the nodes along third and fourth avenues, and we’re planning to get the latest batch to go up in along Rainier Avenue on the map as soon as we can.
As co-founder Phil Mocek has reported, the government-owned cameras are a fairly small slice of the overall camera pie: There’s also a program in Seattle called Seattle Shield, in which Seattle PD exchanges information with more than 100 private entities. You can read more about Seattle Shield here: http://investor.abm.com/common/mobile/iphone/releasedetail.cfm?ReleaseID=550581&CompanyID=ABM&mobileid=
Phil’s efforts to discover who all is in Seattle Shield through FOIA requests here: https://www.muckrock.com/foi/seattle-69/seattle-shield-mailing-list-2012-2971/.
Or, see a video of a federal officer harassing Phil on the sidewalk yesterday here: http://archive.org/details/20130725FederalProtectiveServiceHarassment.
If you zoom in on our map at right you can see the exact location where this took place: the federal building.
The post Protocols for surveillance data under development in Seattle appeared first on Seattle Privacy Coalition.
]]>