# PII redaction use cases

> Where to put a redaction call: LLM prompts, CSV exports, support tickets, logs, staging data, vendor sharing, HIPAA and DSAR.

Canonical: https://bitbanger.in/use-cases/
Last updated: 2026-10-27

- [Redact PII before sending text to an LLM](https://bitbanger.in/use-cases/before-llm) — Strip names, emails, card numbers, and 37 other entity types from prompts before they reach a third-party model. One HTTP call, no retention.
- [Redact PII from CSV exports](https://bitbanger.in/use-cases/csv-export) — Send a CSV and get a redacted CSV back. Per-cell redaction across every column, with headers and structure preserved.
- [Redact PII from support tickets](https://bitbanger.in/use-cases/support-tickets) — Clean customer conversations before they reach analytics, QA tooling, or a third-party summariser.
- [Mask PII in application logs](https://bitbanger.in/use-cases/logs) — Redact IPs, emails, tokens, and device identifiers from log lines before they are shipped to a log aggregator or pasted into a ticket.
- [Sanitise production data for staging](https://bitbanger.in/use-cases/test-data) — Turn a production dump into something safe to load into a non-production environment, without losing the shape of the data.
- [Redact data before sharing with vendors](https://bitbanger.in/use-cases/vendor-sharing) — Share a dataset with a contractor or vendor with the personal data removed, and keep an auditable record of what was stripped.
- [HIPAA de-identification workflows](https://bitbanger.in/use-cases/hipaa-deidentification) — Remove names, MRNs, health plan IDs, dates of birth, addresses, and the other HIPAA identifier categories from clinical text.
- [GDPR subject access requests](https://bitbanger.in/use-cases/gdpr-dsar) — When a subject access request covers a shared record, redact the other people in it before you send the response.