Privacy Localism
Module 1 · Regulatory Framework

Privacy Localism

Why a city council, not Congress or Olympia, ended up writing the rules for police AI and surveillance tech — and what that means for how fast and how locally those rules can change.

The Gap Seattle Is Filling

There is no comprehensive federal privacy law governing how a police department may acquire, deploy, or retain data from surveillance and AI tools. Washington State has moved further than most states — including a first-in-the-nation facial recognition law — but state law still leaves substantial gaps: it does not dictate procurement review, retention schedules, or public disclosure requirements at the department level.

Into that gap steps the city. Legal scholarship on this pattern — see Ira S. Rubinstein’s “Privacy Localism” — describes it precisely: in the absence of federal or state comprehensiveness, municipalities have become the primary regulators of surveillance technology, not because it’s the theoretically ideal level of government to do it, but because it’s the level of government that actually moved.

Seattle is one of the clearest examples of this pattern in the country.


Why Local Regulation, Specifically

Three characteristics of local regulation of personal data explain why cities — not states or the federal government — ended up as the primary regulators here:

  • Proximity to deployment. A city council votes on the actual budget line that buys a specific camera network or software license. That’s a concrete, fundable, votable decision in a way “regulate AI nationally” is not.
  • Faster iteration. A city ordinance can be amended in a single council session in response to a specific incident. Federal privacy legislation has been proposed and stalled for over a decade.
  • Direct accountability to the people under surveillance. The people a Seattle ordinance protects are also the people who elect the council that wrote it — a tighter accountability loop than a federal agency answering to a national constituency.

Values of Experimentation and Accountability

Local regulation carries a specific trade-off worth naming directly, because it shapes everything else in this course:

UpsideDownside
ExperimentationCities can pilot rules — disclosure requirements, impact assessments, sunset clauses — that would take years to test nationally. Seattle’s Surveillance Impact Report process (Module 1, Lesson 4) is itself this kind of local experiment.A rule tested in one city may not transfer. What works for Seattle’s council structure and consent-decree history may not fit a smaller department with no comparable oversight infrastructure.
AccountabilityLocal rules can be more specific and more enforceable — a named city department (Seattle IT’s Privacy Program) is responsible, not a diffuse federal agency.Local accountability is only as strong as local political will. A rule can be weakened by a subsequent council with different priorities, in a way a durable federal statute is harder to unwind.

This is the frame to hold through the rest of the course: everything you’ll study — the ordinances, the review boards, the 2025 AI policy — is a local experiment in accountability, not a settled national standard. It is instructive precisely because it is still being tested in real time.

⚠️ Common Pitfall: Don't Treat Seattle's Rules as a National Baseline

A department outside Seattle cannot assume state or federal law already covers what Seattle’s ordinance covers. Washington’s facial recognition law is unusually strong by national standards, and Seattle’s local ordinance goes further still. A department in a state with no comparable law is operating with a much smaller regulatory floor — which raises the stakes on getting local policy right, not lowers them.

🧠 Knowledge Check

A department in a different state is evaluating whether it needs its own local surveillance ordinance, on the theory that 'federal and state privacy law probably already covers this.' Based on the privacy localism framework, what is the strongest response?

Reveal Answer & Explanation

Check specifically what federal and state law does and doesn’t cover — for most jurisdictions, there is no comprehensive federal privacy statute governing police AI/surveillance procurement, and state coverage varies widely, so the assumption should not be taken on faith.

Privacy localism exists precisely because federal and state law have historically left this gap open. Washington State is actually one of the stronger state-level examples (its facial recognition law is frequently cited as a national model), and Seattle still found it necessary to layer a detailed local ordinance and AI policy on top. A department in a state with weaker baseline protection has even less reason to assume it’s covered — the correct move is to audit the actual statutory text, not infer coverage from the existence of some state privacy law.


Up Next

Privacy localism explains why Seattle regulates locally. The next lesson, Legislative Evolution, traces how that local regulation actually developed — from the first surveillance ordinance in 2013 through the AI-specific policy adopted in 2025.