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

Syracuse Open Data Executive Order and Policy (2017)

Syracuse Open Data Executive Order and Policy (2017)

Syracuse's July 2017 open data policy, issued by executive order, set up a city open data program led by a Chief Data Officer, committing to proactive, license-free release of publishable data with metadata, historical archives and a published inventory.

What the policy does

The Syracuse policy creates an open data program meant to give the public, and city departments, faster access to information through an online portal. It expects to ease the load on staff who answer New York Freedom of Information Law (FOIL) requests, and it treats the protection of privacy, confidentiality and security as a top priority alongside transparency.

Key provisions

  • Clear definitions. Open data means online, open-format, free to download and free of legal encumbrances. Sensitive information is defined by weighing potential harm against public benefit.
  • Program commitments. Proactively release all publishable data; publish high-quality, documented data built to last; support free historical archives; measure effectiveness against city priorities.
  • Scope. Covers every city unit, including records that third-party contractors create for the city.
  • Prioritization. The Chief Data Officer sets release priorities with input from departments and the public, with final approval from corporation counsel and the mayor's office.
  • Governance. Departments name open data coordinators, build a published and regularly updated inventory, and follow a process for assessing the risk and benefit of releasing potentially sensitive data.

Which guidelines it reflects

Based on the text (the original annotators did not tag it): proactive release, lists of holdings, prioritization, outside services, sensitive information, archival material, permanent access and oversight authority.

Adoption context

Syracuse's policy belongs to the later wave of municipal open data policies adopted in 2016 and 2017, many of them using shared model language. Its risk-versus-benefit test for sensitive data reflects how practice had matured since the first policies in 2009.

Why this matters for your business data

Syracuse's test, which publishes data only when public benefit outweighs privacy or security risk, is a good model for any organization thinking about sharing operational data. The answer is rarely all or nothing; it depends on preparation. Our de-identified data guide shows how risky fields are removed, and you can request a bid once your data is ready.

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

Who runs the Syracuse open data program?

A Chief Data Officer, who reports to the mayor's chief of staff. The CDO works with department open data coordinators to build the dataset inventory, set release priorities and manage the review of potentially sensitive information.

Does the Syracuse policy cover contractors?

Yes. Its requirements reach records that third-party contractors create or acquire on behalf of a city agency, so outsourcing a service does not take the resulting data outside the open data program.

Guidelines this policy reflects

Other policies in NY

Sources

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

Updated December 31, 2024.