Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Policy index / Open data policy index
Open data policy index

Seattle Open Data Policy OD-1 (2016)

Seattle Open Data Policy OD-1 (2016)

Seattle's Open Data Policy OD-1, version 1.0 of February 1, 2016, made City data open by preference, required department data catalogs and Open Data Champions, and set rules for metadata, unique row identifiers, open licensing and citations.

What the policy does

Policy OD-1 sets the principles for Seattle's Open Data Program and what each department must do. The program's goals are to improve public understanding of city operations, create economic opportunity, help city staff work more effectively and support new technology that improves quality of life.

The policy took effect through a mayoral executive order signed later that month, which ordered every department to follow it.

Key provisions

  • Open by preference. City data, including data held by contractors on the city's behalf, is proactively published on data.seattle.gov, subject to privacy, security and other limits.
  • No barriers. Portal datasets require no registration or license, although publishers of derived apps may be asked to name the source and version used.
  • Risk review. Departments use program tools to assess privacy and safety risks, especially for bulk releases, and the city's Chief Privacy Officer resolves privacy questions.
  • Accountability. Each department names an Open Data Champion, sets annual publication goals and ties them to director performance reviews.
  • Catalogs. Departments catalog and prioritize their holdings, combined into a public master catalog.
  • Data quality. Data and metadata are published in machine-readable form, each row has a unique identifier, datasets carry an open license, and a citation format is provided for each one.

Which guidelines it reflects

OD-1 is one of the few policies that addresses citations and unique identifiers directly, alongside proactive release, lists of holdings, sensitive information and metadata. The original annotators did not tag this document; this mapping is a reading of the text.

Why this matters for your business data

Seattle's unique-identifier rule lets users check that records stay consistent over time. Data buyers prize that same property in private datasets, because it lets them join, deduplicate and track change without guessing. If your systems already assign stable IDs, your data is easier to value. See de-identified data for how IDs are handled without exposing people, then get a bid.

We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Our compliance promise: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Frequently asked questions

What does open by preference mean in Seattle's policy?

Departments should assume the data they create, collect or maintain, including through contractors, will be made public unless open data, privacy, security, retention or disclosure policies say otherwise. Release still follows a risk assessment, particularly for data that could cause harm when combined or released in bulk.

Who is an Open Data Champion?

Each Seattle department designates one. The Champion is the department's point of contact and coordinator for publishing open data, working with data owners and the central Open Data Team to meet the department's annual publishing goals.

Guidelines this policy reflects

Other policies in WA

Sources

  1. Original policy document (historical; may no longer resolve)
  2. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.