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

Phoenix's 2014 Open Data Policy

Phoenix's 2014 Open Data Policy

Phoenix's June 2014 open data policy, recommended by the City Manager, makes city data open by default unless it is personally identifiable, confidential, sensitive or restricted by law. It also commits to community challenges to encourage reuse.

What the policy does

Phoenix's policy is short. It says that making non-confidential data freely available using open standards will make city government more efficient, effective and accountable, while keeping the public's trust in how the city handles personal and confidential information. Its main rule is "open by default."

Adoption context

The policy came from the City Manager's office. Council subcommittee records from spring 2014 show staff updates on an open data strategy and a draft policy before the June 2014 date. The original collection lists it as an administrative policy. Phoenix's open data site later published the policy text.

Key provisions

  • Data is open by default unless it is personally identifiable, confidential or sensitive, or release is barred by law or regulation.
  • Departments must use judgment before publishing data from existing systems.
  • The City Manager sets standards that support transparency and innovation through free web applications.
  • The city encourages engagement through competitions and challenges.
  • IT Services provides publishing procedures, and the Law Department decides what is appropriate to post.

Guidelines it reflects

The original annotators did not tag this document, so this index lists a conservative set: proactive release through open by default, goals and values, sensitive information through the PII and Law Department rules, and public participation through challenges.

What happened next

Phoenix began publishing city datasets online in late 2014 and later ran a dedicated open data portal. The policy is a good example of a short, principles-first approach in municipal open data policies. For a longer administrative model, see Houston's AP 8-7.

Why this matters for your business data

Phoenix's two-part test (open by default, but never personally identifiable or confidential) is also the right default for companies thinking about data partnerships. Strip the personal fields and the remaining operational patterns can still be very valuable. Learn more in the de-identified data guide and the valuation calculator. 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

Did the Phoenix City Council vote on this policy?

The available records show council subcommittee updates on a draft policy in spring 2014. The policy itself reads as a City Manager recommendation, and the original collection lists it as an administrative policy. This index found no record of a full council vote.

What data does Phoenix keep closed?

Personally identifiable information, confidential or sensitive information, and anything that law or regulation does not allow to be released. The Law Department decides whether data is appropriate for the portal.

Guidelines this policy reflects

Sources

  1. Phoenix Open Data: Open Data Policy
  2. KTAR: Phoenix to increase city data available to public online (2014)
  3. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.