Bankruptcy Rule 9037 (FRBP 9037) Court Filing Redaction
Redact bankruptcy court filings per FRBP 9037 — last 4 of SSN/TIN/account, year-only of birthdates, minors' names to initials.
Redaction Policies
A community-curated library of Philter and Phileas policies covering HIPAA, PCI DSS, bankruptcy court filings, AI training prep, and more. Released under the permissive and business-friendly Apache license. Download as-is, fork, or contribute your own.
Redact bankruptcy court filings per FRBP 9037 — last 4 of SSN/TIN/account, year-only of birthdates, minors' names to initials.
De-identify clinical notes for research, ML training, or analytics — preserving temporal relationships via per-patient date shifting.
Strip cardholder data and PII from contact-center call transcripts — primarily PAN, CVV, SSN, account numbers — to reduce PCI DSS scope and meet QA privacy requirements.
Remove personally identifiable information from student educational records per FERPA (20 USC 1232g; 34 CFR Part 99).
Redact federal civil filings per FRCP 5.2 — last 4 of SSN/TIN/account, year-only birthdates, minor names to initials.
A balanced starting policy covering common PII types — names, contact info, government IDs, payment data — with no vertical-specific tuning.
Redact Nonpublic Personal Information (NPPI) from financial customer records under the Gramm-Leach-Bliley Act (15 USC 6801-6809).
Remove all 18 HIPAA Safe Harbor identifiers from clinical text per 45 CFR 164.514(b)(2).
Aggressive PII redaction for documents being fed into LLM training, fine-tuning, or RAG vector stores — preserves semantic structure with type tokens.
Redact PHI from user messages to a healthcare chatbot before they reach the LLM — preserves clinical meaning while removing identifiers.
Strip cardholder data (PAN, CVV, expiration) from logs, transcripts, and tickets to reduce PCI DSS scope per Requirement 3.4.
A starting policy for state-court PII redaction — covers the most-common state requirements; tune for your specific jurisdiction.
Every policy is a single JSON file. Download it, upload it to your Philter instance, and reference it by name from the redaction API.
# 1. Download the policy
curl -O https://raw.githubusercontent.com/philterd/pii-redaction-policies/main/policies/philterd/healthcare/hipaa-safe-harbor.json
# 2. Upload to your Philter instance
curl -X POST http://localhost:8080/api/policies \
-H "Content-Type: application/json" \
--data @hipaa-safe-harbor.json
# 3. Redact text using the policy
curl http://localhost:8080/api/filter?p=hipaa-safe-harbor \
--data "Patient John Smith was discharged on 2025-03-14." \
-H "Content-Type: text/plain"No Philter instance yet? Deploy one in 5 minutes →
The library lives at github.com/philterd/pii-redaction-policies. PRs welcome: bring your own vertical, your own custom identifiers, your own edge cases.
The library is more useful the more eyes are on it. Every policy you contribute saves another team (in healthcare, finance, legal, government, AI training) from rebuilding the same thing privately and often incorrectly. A rising tide lifts all boats.
author field and shows up on the policy’s page right here on philterd.ai. Durable attribution, not a buried changelog entry.Every contribution gets reviewed for: schema compliance, sidecar metadata completeness, and golden-file validation against a representative input. See CONTRIBUTING.md for the file layout, metadata schema, and review process.
Policies must conform to the Phileas redaction policy JSON schema.
If you have a specific compliance framework or vertical use case in mind, the Philterd team can build a custom policy and tune it against your real data.