---
title: "What is PII? Personal data in LLM prompts and redaction"
description: "PII is information that can identify a person, alone or combined with other data. How NIST and the GDPR define it and how to redact it before an LLM API call."
url: https://broadrouter.com/glossary/pii/
lang: en
updated: 2026-11-15
publisher: BroadRouter (a BroadNet site); API by BroadNet Inference, https://inference.broadnet.ai
---

# PII (personally identifiable information)

Updated 2026-11-15

PII (personally identifiable information) is information that can be used to distinguish or trace a person's identity, such as a name, ID number or biometric record, plus other information linked or linkable to that person. The GDPR's broader term is personal data. In LLM work, PII redaction removes it from prompts before they leave your systems.

Also called: PII, personally identifiable information, PII redaction

The safest PII is the PII you never send. Most prompts that carry it don’t need it.

## How it works

NIST SP 800-122 (April 2010) uses a broad definition: PII is “any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual’s identity, such as name, social security number, date and place of birth, mother’s maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information.”

The GDPR’s term is personal data: “any information relating to an identified or identifiable natural person”, including “a name, an identification number, location data, an online identifier”. Saudi Arabia’s [PDPL](https://broadrouter.com/glossary/pdpl/) defines personal data in similar terms.

Redaction tools usually work in two steps. Microsoft Presidio’s analyzer handles “PII identification in text”, using patterns and [named-entity recognition](https://broadrouter.com/glossary/named-entity-recognition/). Its anonymizer then applies an operator to each match:

| Operator | Presidio’s description |
| --- | --- |
| replace | “Replace the PII with desired value” |
| redact | “Remove the PII completely from text” |
| mask | “Replace the PII with a given character” |
| hash | “Hashes the PII text using salted hashing for security” |
| encrypt | “Encrypt the PII using a given key” |

A placeholder pattern for a support ticket:

```text
Before: Ahmed Al-Harbi (+966 5x xxx xxxx) says order 4471 never arrived.
After:  <PERSON_1> (<PHONE_1>) says order 4471 never arrived.
```

You keep the mapping on your side and put the real values back into the model’s answer.

## Why it matters

-   **Every copy is a risk.** NIST advises organisations to “minimize the use, collection, and retention of PII to what is strictly necessary”. Prompts and logs are copies.
-   **Detection misses things.** Presidio says “there is no guarantee that Presidio will find all sensitive information”. Arabic names, Gulf phone formats and mixed-script text are where generic detectors often miss; test on your own data.
-   **Outputs can leak too.** Run the same checks on responses. [Guardrails](https://broadrouter.com/glossary/guardrails/) can block or flag them.

[Sending sensitive data to an LLM API](https://broadrouter.com/blog/llm-api-sensitive-data/) covers redaction, placeholders and logging in detail, and [usage logging with PII redacted](https://broadrouter.com/blog/llm-api-usage-logging/) covers your own logs.

## On BroadNet Inference

BroadNet’s privacy statement says it does not retain prompts, audio, images, answers or transcripts, and does not use inference data to train, fine-tune or evaluate models. That limits what is stored after the request. It does not redact for you: the PII still reaches the model during processing, so minimise first. See [zero data retention](https://broadrouter.com/glossary/zero-data-retention/).

BroadNet also publishes an open-source redaction proxy, the LLM Sensitive Data Firewall (LSDF), under Apache-2.0; the [sensitive data post](https://broadrouter.com/blog/llm-api-sensitive-data/) describes it and BroadNet’s own evaluation figures. This page is not legal advice.

## Questions

### Is PII the same as personal data under the GDPR?

They overlap but are not the same. NIST's PII definition comes from US federal guidance. The GDPR defines personal data as any information relating to an identified or identifiable person, which includes online identifiers and location data.

### Can a tool find all PII in a prompt automatically?

No. Presidio's own documentation says there is no guarantee it will find all sensitive information. Combine detection with sending only the fields the task needs, and test on your own data.

### Should I redact PII before calling an LLM API?

Where the model does not need it, yes. Replace names, phone numbers and IDs with placeholders and map them back after the response. It lowers exposure under any provider's terms.

## See also

-   [Guardrails](https://broadrouter.com/glossary/guardrails/) (term)
-   [Named entity recognition (NER)](https://broadrouter.com/glossary/named-entity-recognition/) (term)
-   [GDPR](https://broadrouter.com/glossary/gdpr/) (term)
-   [PDPL (Saudi and UAE data protection laws)](https://broadrouter.com/glossary/pdpl/) (term)
-   [Zero data retention](https://broadrouter.com/glossary/zero-data-retention/) (term)
-   [Prompt injection](https://broadrouter.com/glossary/prompt-injection/) (term)
-   [Sending sensitive data to an LLM API: redact, minimise, log less](https://broadrouter.com/blog/llm-api-sensitive-data/) (article)
-   [LLM API usage logging: cost per user and feature, PII redacted](https://broadrouter.com/blog/llm-api-usage-logging/) (article)
-   [GDPR and LLM APIs: 15 questions to ask your provider](https://broadrouter.com/blog/gdpr-llm-api-checklist/) (article)

Try it on your real workload. New accounts start with $5 of credit for Gemma and transcription. DeepSeek, GLM and Qwen3.8 need a top-up.

[Get started](https://inference.broadnet.ai/account/?utm_source=broadrouter&utm_medium=referral&utm_campaign=glossary-pii&utm_content=page-cta) ·

**Sources**

-   [NIST SP 800-122, Guide to Protecting the Confidentiality of PII, April 2010 (checked 2026-11-15)](https://csrc.nist.gov/pubs/sp/800/122/final)
-   [Regulation (EU) 2016/679 (GDPR), Article 4(1) personal data, official text (checked 2026-11-15)](https://eur-lex.europa.eu/eli/reg/2016/679/oj)
-   [Microsoft Presidio documentation, overview (checked 2026-11-15)](https://presidio.dataprivacystack.org/)
-   [Microsoft Presidio documentation, anonymizer operators (checked 2026-11-15)](https://presidio.dataprivacystack.org/anonymizer/)
-   [BroadNet Inference privacy statement (effective September 2026; checked 2026-11-15)](https://www.broadnet.ai/inference-privacy)
