
Guideline 7 asks open data policies to protect privacy and security with narrow, clearly defined exemptions, and to release sensitive information in aggregate where individual records cannot be published.
Balancing openness and protection
Openness and privacy are not opposites, but they do have to be balanced. A good open data policy inherits the exemptions already in public records law and adds safeguards for risks specific to bulk online publication, where data sets can be combined in ways that expose individuals.
The guideline makes three practical points. Individual-level data about private persons deserves special scrutiny. Aggregation often lets a government release useful information without exposing anyone. And exemptions should be drawn as narrowly as possible, with a balancing test rather than a blanket refusal.
How policies typically phrase it
- A definition of "protected" or "restricted" data that cross-references existing law.
- A list of excluded categories, such as security-sensitive infrastructure plans or personal identifying information.
- A requirement that publication be reviewed for privacy before release.
- A preference for releasing aggregated or redacted versions when the raw data cannot be published.
Places whose policies adopted it
Charlotte's 2015 policy spells out excluded categories in detail, including federally defined sensitive security information and building plans for city infrastructure. New York City's 2012 Local Law 11 excludes data that agencies may withhold under state public officers law. Los Angeles's 2013 directive publishes data to the extent permitted by law and subject to valid privacy, confidentiality and security restrictions.
The guideline is tagged in most policies in this index, including Chicago, Philadelphia and South Bend.
Common pitfalls
- Overbroad exemptions that let departments withhold anything inconvenient.
- Ignoring re-identification, where separately harmless data sets combine to reveal individuals.
- No aggregation path, so sensitive data is simply withheld rather than summarized.
Practical safeguards before publication
Policies that handle this guideline well usually pair the legal exemptions with an operational review step. Common elements include:
- A named reviewer, often legal or privacy staff, who signs off before a new data set is published.
- A checklist covering direct identifiers, quasi-identifiers such as exact dates and addresses, and small-cell counts.
- Standard techniques such as aggregation by area or time, rounding, generalizing locations to blocks, and suppressing rare categories.
- A process for removing data quickly if a problem is found after release.
The checklist approach recognizes that privacy risk depends on context. A data set may be safe on its own but risky when joined to other public records, so reviewers consider what else is already available. Federal guidance on personally identifiable information, such as NIST SP 800-122, is a common reference point.
Why this matters for your business data
This is the guideline closest to how private data should be shared. Responsible data sales rest on the same principles: exclude what must be protected, aggregate or transform the rest, and check for re-identification risk before anything leaves the building.
Our guide to de-identified data explains the techniques, and open data policy to data value shows how public-sector safeguards translate to private operational data. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
What counts as sensitive information in an open data policy?
Typically personal identifying information, data protected by privacy statutes, security-sensitive infrastructure details, law enforcement records exempt from disclosure and anything confidential under state or federal law.
How can a government release data that contains personal details?
Often through aggregation or redaction: publishing counts, rates or summaries by area or time period instead of individual records, after reviewing whether the result could identify anyone.
What is re-identification risk?
The risk that data stripped of names can still be linked back to individuals, for example by combining it with other public data sets. Responsible publishers check for this before release.
Should exemptions be listed in the policy?
Most strong policies either list them or cross-reference existing law, and the guideline recommends keeping them as narrow as the law allows.
Policies in the index that reflect guideline 7
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Portland, OR | Sep 30, 2009 | Council resolution | 37810162230 |
| San Francisco, CA | Oct 29, 2010 | Ordinance | 47811182526 |
| Cook County, IL | May 4, 2011 | Ordinance | 12378131825 |
| New York, NY | Mar 7, 2012 | Local law (Local Law 11 of 2012) | 14578101118 |
| Philadelphia, PA | Apr 26, 2012 | Executive order (No. 1-12) | 34578182224 |
| Madison, WI | Aug 15, 2012 | Ordinance | 457810111318 |
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| Montgomery County, MD | Dec 17, 2012 | County legislation (Bill 23-12, Open Data Act) | 457811131822 |
| San Francisco, CA | Mar 28, 2013 | Ordinance | 34578101118 |
| South Bend, IN | Aug 22, 2013 | Executive order | 237810182528 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Louisville, KY | Oct 11, 2013 | Executive order (No. 1, Series 2013) | 1234781018 |
| Oakland, CA | Oct 15, 2013 | Council resolution (No. 84659) | 2345781011 |
| Honolulu, HI | Nov 27, 2013 | Ordinance | 237810111820 |
| Los Angeles, CA | Dec 18, 2013 | Executive directive (No. 3) | 37818222630 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Hartford, CT | Mar 26, 2014 | Executive order | 34789182224 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Chattanooga, TN | May 31, 2014 | Executive order | 123467810 |
| Phoenix, AZ | Jun 18, 2014 | Administrative policy | 13726 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| Houston, TX | Sep 18, 2014 | Administrative policy (AP 8-7) | 234567810 |
| Charlotte, NC | Jan 1, 2015 | IT policy | 2781924 |
| Denton, TX | Feb 9, 2015 | Administrative directive | 357811121618 |
| Boston, MA | Jul 30, 2015 | Administrative policy | 478132425 |
| Suffolk County, NY | Jul 31, 2015 | Administrative policy | 78131820222426 |
| Jackson, MS | Sep 1, 2015 | Executive order (No. 2015-06) | 12345678 |
| Cambridge, MA | Sep 21, 2015 | Ordinance | 12345678 |
| Durham, NC | Nov 23, 2015 | Administrative policy | 7818192430 |
| Seattle, WA | Feb 1, 2016 | Administrative policy (CTO policy) | 14678101112 |
| Seattle, WA | Feb 26, 2016 | Executive order | 17242627 |
| Baltimore, MD | Mar 7, 2016 | Ordinance | 1781113182426 |
| Las Vegas, NV | Apr 12, 2016 | Administrative policy (City Manager policy CM510) | 12345678 |
| Saint Paul, MN | Apr 27, 2016 | Council resolution | 12578101113 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| Bellevue, WA | Aug 1, 2016 | Management policy | 15678101118 |
| Naperville, IL | Nov 15, 2016 | Council resolution | 45789101112 |
| Fort Collins, CO | Feb 7, 2017 | Council resolution | 12345678 |
| Knoxville, TN | May 2, 2017 | Executive order | 14578111319 |
| Syracuse, NY | Jul 26, 2017 | Executive order | 1456781113 |
Sources
Updated December 31, 2024.