In Open Data Policy
See also the Open Data Policy page for relevant clauses on privacy.
When records maintained electronically include items of information that would be available under this article, as well as items of information that may be withheld, an agency in designing its information retrieval methods, whenever practicable and reasonable, shall do so in a manner that permits the segregation and retrieval of available items in order to provide maximum public access.
Seattle’s Open Data Candidate Requirements and Risk Evaluation rubric covers some privacy considerations
Data submitted to data.gov requires the submitting agency to conduct a Privacy Impact Assessment - http://www.data.gov/datapolicy
Provenance & Accountability
Privacy coverage in the W3C guide on Putting Government Data Online:
A very common and important concern is the privacy of data which contains personally identifiable nformation. This article does not suggest that all data should be made public, nor does it discuss issues with anonymisation of data. Systems where PIP is an issue will probably not be an early choice when selecting those to put on the web. However, in cases in which these issues have already been resolved and the data is already public but not in the standard form, converting it to Linked Data is an excellent idea. In general, new government systems should be built to be aware of the provenance of the data they use, and of the appropriate use to which it may be put. But the design of these accountable systems is another topic we do not have space for here.
US Federal Policy
 Office of E-Government and IT & Office of Management and Budget, Data.gov Concept of Operations Version 1.0 at 22, 24 (n.d.), available at http://www.data.gov/documents/data_gov_conops_v1.0.pdf
 Data.gov, Data Policy, http://www.data.gov/datapolicy.