Tag Archives: Police Surveillance

New “Toolkit” from the ACLU & Oakland Privacy Can Help You Get A Surveillance Ordinance Passed

via Oakland Privacy

The ACLU has just announced a new Surveillance Ordinance Toolkit!

Two years in the making – and in collaboration with Oakland Privacy – this toolkit from the ACLU provides the critical information for part three of the Aaron Swartz Day Police Surveillance Project’s goals:  To help folks present the information to their own local city councils to help get a surveillance policy in place for how any surveillance equipment is allowed to be used on its citizens.

Since the November 2017 Aaron Swartz Day weekend, our police surveillance project has taught activists how to use our templates with muckrock to file public records requests – with a city’s police and sheriff departments (in the spirit of Aaron Swartz’ many FOIA requests via muckrock) so that they will have to give any relevant documentation when specific types of surveillance equipment have already been purchased.

The last, and most complicated of our project’s three goals involves figuring out what to do exactly once you have evidence of the surveillance equipment’s existence.  Ideally, once a piece of surveillance equipment has been identified, a city council can start working on  in the process of implementing a use policy, based on an ordinance, which regulates how that equipment is allowed to be used. But what’s the best way to present that evidence to a  city council for it to act upon?

Thanks to Tracy Rosenberg, we have provided some easy to use templates for obtaining information direct from a city’s own police and sheriff departments, so that the information could be taken to the City Council. Now, the ACLU & Oakland Privacy have created a toolkit for the process of taking that information to the City Council.

From the Oakland Privacy article:

Getting a surveillance transparency ordinance or a facial recognition ban passed in your town can seem like an overwhelming task. It’s not. You can do it!

Oakland Privacy and ACLU of Northern California sat down to write a step by step guide based on the dozen ordinances in place across the country, including 8 in the San Francisco Bay Area.

This free guide includes loads of advice on coalition-building, public education, strategy, research, messaging and advocacy and samples of useful documents.

Summer Update: The Aaron Swartz Day Police Surveillance Project

See Tracy Rosenberg, Daniel Rigmaiden & Lisa Rein discuss the Solar Survival Project – LIVE, on November 10, 2018 at the San Francisco Hackathon.

TICKETS HERE

We’ll be posting “Summer Updates” all week regarding our endless hackathon projects that we kept going from last year’s event.

The first is our new quick tutorial with templates for our Aaron Swartz Day Police Surveillance Project – or #ASDPSP.

These templates enable you to compel the Police and Sheriff Departments for a given City and County to hand over all documentation on all known surveillance equipment. (Including documentation and information regarding all software used and any data it collects and stores.)

If you’re wondering what the situation is exactly with all of the surveillance equipment (and the data about the public that is being collected via this equipment) – in most major cities across the country –  you’ll want to read my latest interview with Tracy Rosenberg of Oakland Privacy.org, entitled “The Aaron Swartz Day Police Surveillance Project #ASDPSP – Reports Back: Here’s #WhatWeFound In Sacramento.

Tracy created the templates, and explains even more about the different types of equipment our templates ask about.

Here are the first two detailed interviews with Tracy on this topic:

Interview with Oakland Privacy’s Tracy Rosenberg On The Aaron Swartz Day Police Surveillance Project

How a little “working group” stopped Oakland from becoming a mini-fusion center for the Department of Homeland Security.

The Aaron Swartz Day Police Surveillance Project  is all about developing a larger strategy for determining what types of surveillance equipment a city’s police and sheriff departments have already purchased and whether or not a surveillance policy is in place to monitor that equipment – regulating how that equipment is used against their citizens.

This project started during Aaron Swartz Day 2017’s Sunday hackathon. Before that event was even over, it was clear that it had been really successful and we were all very pumped and had decided to just keep going until next year.

The results of doing so are just starting to pour in, and I’m going to be doing my best to give you the full story – both here on the Aaron Swartz Day website, and over on Mondo 2000, over these next few months, leading straight into this year’s event.

We just added two new templates (Zip file of all templates in .PDF, Zip file of all templates in .DOC) to our tutorial – one for Police Departments (City) and one for Sheriff Departments (County) – that include the use of facial recognition software, since it came out recently that Amazon has been literally giving away its facial recognition software to law enforcement, in the hopes of getting a number of early implementations. Not a bad marketing strategy, and we’re not saying the software shouldn’t be used; just that there should be a surveillance policy framework in place that regulates how it can be used against citizens.

Special thanks to Muckrock, without which this project would not be possible.

 

 

Tracy Rosenberg Explains How to Compel Police & Sheriff Departments To Admit What Surveillance Equipment They Already Have

See Tracy Live at this year’s San Francisco Hackathon!

TICKETS HERE

Lisa Rein has written a pair of articles in Mondo 2000 with Tracy Rosenberg from OaklandPrivacy.org.

Tracy explains the importance of the Aaron Swartz Day Police Surveillance Project, and its mission of filing public records requests en masse, in order to retroactively determine what kinds of surveillance equipment and software a city’s Police and Sheriff Departments already have.

We will have a complete tutorial with templates and step-by-step instructions, so you to start doing this yourself, next week.

For now, please read these articles to get a better idea of why this project is so important, for all of us, right now.

How a little “working group” stopped Oakland from becoming a mini-fusion center for the Department of Homeland Security.

(How The Occupy Oakland Privacy Working Group became Oakland Privacy)

 

and

Interview with Oakland Privacy’s Tracy Rosenberg On The Aaron Swartz Day Police Surveillance Project