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

Open Access: Open Data Policy Guideline 10

Open Access: Open Data Policy Guideline 10

Guideline 10 asks open data policies to remove barriers such as registration, fees and usage limits, so anyone can access public data at any time without identifying themselves or explaining why.

What open access requires

Even data in perfect formats can be closed off by friction: mandatory accounts, access fees, rate limits, restrictive terms of use. Guideline 10 asks policies to address these barriers directly, whether they were imposed deliberately or emerged by accident from a software choice.

The goal is broad, non-discriminatory, free access. Anyone should be able to download public data anonymously and at any time, without providing a reason.

How policies typically phrase it

  • A requirement that public data sets be available without registration or fees.
  • Terms of use drafted to maximize, not restrict, reuse.
  • Requirements that data be reachable by external search engines and automated tools.
  • Notice mechanisms that tell users when data is updated.

Places whose policies adopted it

New York City's 2012 Local Law 11 requires that public data sets be available without registration, license requirements or restrictions on use, while allowing the city to ask redistributors to identify the source. Chicago's 2012 order requires formats that permit automated processing and accessibility to external search. San Francisco's 2013 ordinance takes a softer line, allowing "reasonable, user-friendly" registration requirements under standards adopted by the city.

Other tagged examples include Louisville, Oakland, Madison and Saint Paul.

Common pitfalls

  • Registration walls justified as usage tracking.
  • API keys with low limits that block bulk reuse.
  • Terms of use that quietly reintroduce restrictions the policy removed.

Writing open terms of use

Terms of use are where open access is often won or lost. Terms consistent with this guideline tend to share several traits:

  • They disclaim warranties and liability rather than restricting use.
  • They do not require registration, payment or justification for access.
  • They allow commercial and non-commercial reuse alike.
  • They may ask users to cite the source, but do not make citation a condition of use.
  • They avoid clauses that let the publisher revoke access to particular users.

Technical choices matter as well. If an API is the only access route and it imposes low rate limits, heavy users are effectively shut out; offering bulk downloads alongside APIs solves that. Making portals crawlable by search engines also helps the public find data without knowing where to look.

Why this matters for your business data

Public open data is free by design. Private operational data is different: it is proprietary, and access to it is what a buyer pays for. Understanding why governments give their data away, and why companies building AI still need more, explains why private data commands a price.

Our pillar on open data policy to data value explores that contrast, and how to value my data shows what drives price. 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

Can a government require registration to download open data?

The guideline recommends against it. Some policies allow light registration, but strong policies require that public data be accessible anonymously, without fees or justification.

Are API rate limits a barrier to open access?

They can be, if they prevent bulk or automated reuse. Offering bulk downloads alongside APIs is a common way to avoid that problem.

How do terms of use affect open access?

Terms of use can undo an open policy by restricting reuse or imposing conditions. The guideline asks that terms maximize accessibility and reuse.

Policies in the index that reflect guideline 10

PlaceAdoptedInstrumentGuidelines
Portland, ORSep 30, 2009Council resolution37810162230
New York, NYMar 7, 2012Local law (Local Law 11 of 2012)14578101118
Madison, WIAug 15, 2012Ordinance457810111318
Chicago, ILDec 10, 2012Executive order34678101113
San Francisco, CAMar 28, 2013Ordinance34578101118
South Bend, INAug 22, 2013Executive order237810182528
Austin, TXAug 26, 2013Administrative memo123457810
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Oakland, CAOct 15, 2013Council resolution (No. 84659)2345781011
Honolulu, HINov 27, 2013Ordinance237810111820
Pittsburgh, PAMar 19, 2014Ordinance12345678
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Cincinnati, OHMay 29, 2014Administrative regulation8101122242629
Chattanooga, TNMay 31, 2014Executive order123467810
Kansas City, MOJun 19, 2014Ordinance (No. 140443)81018242713
Washington, DCJul 21, 2014Executive directive (Mayor's Order 2014-170)12356789
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Tulsa, OKDec 21, 2015Executive order123458910
Seattle, WAFeb 1, 2016Administrative policy (CTO policy)14678101112
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
Saint Paul, MNApr 27, 2016Council resolution12578101113
Milwaukee, WIJul 14, 2016Council resolution12356789
Bellevue, WAAug 1, 2016Management policy15678101118
Naperville, ILNov 15, 2016Council resolution45789101112
Fort Collins, COFeb 7, 2017Council resolution12345678

Sources

  1. Sunlight Foundation, Open Data Policy Guidelines (historical reference)
  2. openFDA terms of service (example of open terms)

Updated December 31, 2024.