# Personally Identifiable Information

{% file src="/files/OXIhyBcTARpo4bLVaMJJ" %}

## Defining PII

#### [2 CFR § 200.79](https://www.law.cornell.edu/cfr/text/2/200.79)

> \[...] for example, first and last name, address, work telephone number, email address, home telephone number, and general educational credentials. The definition of PII is not anchored to any single category of information or technology. Rather, it requires a case-by-case assessment of the specific risk that an individual can be identified. Non-PII can become PII whenever additional information is made publicly available, in any medium and from any source, that, when combined with other available information, could be used to identify an individual.

This definition of public data is also supported in [HiQ Labs v. LinkedIn](https://en.wikipedia.org/wiki/HiQ_Labs_v._LinkedIn#cite_note-1).

## Goals

We want people to feel sound ethically and legally when they contribute to PDAP. To that end, these are our goals:

1. Draw a “[bright line](https://en.wikipedia.org/wiki/Bright-line_rule)” from our [Data Sources Database](broken://pages/nmpsayHbm28zgI94Cqdh) to the source material. We are not altering public records, we are helping people find them.
2. Avoid aggregating already-public PII in a way that would make it more usable (e.g. turning arrests from different jurisdictions into a unified database). [Citation](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2678420).
   * We don't want to become or facilitate a database of people impacted by the legal system.
3. Strive for completion, and not be accused of editorializing by omission. 
   * The board decided [submitting PII is allowed](broken://pages/-MYXSzQD2zS0CQR8q_P9).
   * We can track whether a given Data Source contains PII. 
   * PII collection is not required. If we aggregate data, we can choose to omit PII like `name` and `address` because those properties do not become statistically useful in aggregate, only dangerous.
4. Transparency in our published resources and information.
   * Our open-source tools are transparent in how they work.
   * Documentation about published data and tools should be clear about any properties which are collected—or left behind—and why the decision was made.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pdap.io/meta/operations/policy/pii-wip-discussion.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.