Verified Unsurveilled · Organizing

Make my city Unsurveilled

The badge is a target, not a trophy. Find where your community stands against the standard, and get the specific things that would move it.

Where almost every city currently stands

Of the 5 jurisdictions assessed so far, none meets the standard. That is not a scolding — it is the baseline. Most municipalities have never been asked these questions, so the first four criteria are usually unanswered rather than failed.

Usually unanswered

  • What surveillance technology exists at all
  • How long data is kept
  • Who else can search it
  • What an officer must show before a historical search

These are records requests, not political fights. One resident can resolve all four.

Usually requires a vote

  • A surveillance technology approval ordinance
  • A published inventory requirement
  • Retention limits with automatic deletion
  • Sharing defaults and the legal standard for access

These take a council. They are also the ones that survive a change of chief, mayor, or vendor.

The five asks that move a city furthest

All 12 criteria matter. These five are where a small group of residents realistically has leverage, in the order we would attempt them.

  1. 01

    A public surveillance technology inventory

    Nothing can be debated that is not listed. An inventory ordinance is usually the least controversial thing on this list and it unlocks every other conversation.

    Criterion in the standard →
  2. 02

    Council approval before new surveillance technology

    Advance public notice, a written impact and use policy, and a vote by the elected body. This is the criterion that governs technologies nobody has invented yet.

    Criterion in the standard →
  3. 03

    A defined retention limit with automatic deletion

    Retention is the single field that most changes what a system means. Thirty days is an operational tool; two years is a movement archive. Same hardware.

    Criterion in the standard →
  4. 04

    Outbound sharing off by default

    Sharing is usually configured once, at install, by someone who was not thinking about it. Ask what it is set to now — the answer is frequently the most alarming document in the file.

    Criterion in the standard →
  5. 05

    Language written against capability, not vendor

    Every ask above should describe what a system does, never what it is called. This is the difference between a policy and a press release.

    Criterion in the standard →

The tools

Why bother earning a badge from a small nonprofit?

Because the badge is not the point — the rubric is. A city that can satisfy all 12 criteria has, by construction, published what it operates, put new surveillance technology under a public vote, limited retention, controlled sharing, and written its rules against capabilities rather than product names.

Those protections hold whether or not anyone ever puts a seal on a municipal website. The designation exists to give that work a name, a public evidence trail, and something a council member can point at when somebody asks why they bothered.