The Privacy Filter Model — Enterprise Privacy & Governance
[ ABORT TO HUD ]
SEQ. 1
The Privacy Filter Model
Local PII Redaction (April 2026)
OpenAI released the Privacy Filter (April 22, 2026, Apache 2.0 license), an open-weight 1.5B-parameter sparse Mixture-of-Experts (MoE) model with only 50M active parameters per token and a 128K context window, engineered to detect and redact 8 core categories of Personally Identifiable Information (PII) and secrets locally before data leaves your infrastructure.
Enterprise Architecture
- User submits raw text containing sensitive data.
- Local Privacy Filter scans and replaces PII with tokens (e.g.,
[NAME_1],[CREDIT_CARD]). - Sanitized text is sent to the OpenAI API for processing.
- API returns results. Local system maps tokens back to original PII.
Data Retention Policies
| Plan | Data Used for Training? | Retention |
|---|---|---|
| API (default) | No | 30 days for abuse monitoring |
| API (zero retention) | No | 0 days - nothing stored |
| ChatGPT Free | Yes (opt-out available) | Varies |
| ChatGPT Enterprise | No | Configurable |
Compliance Certifications
- SOC 2 Type II: Enterprise security controls verified
- GDPR & Data Residency: EU/regional data processing agreements available (regional residency and FedRAMP endpoints carry a 10% uplift on models released on or after March 5, 2026)
- HIPAA: BAA available for healthcare customers
🔒 Zero-Trust Pattern: Privacy Filter + Zero Retention API = sensitive data never touches OpenAI's servers in readable form. This satisfies the strictest compliance requirements.
⌨ HANDS-ON LABAudit Enterprise Zero Data Retention (ZDR)
⭐ +150 XPEnterprise agreements support Zero Data Retention. Include organizational headers and verify data privacy compliance.
1POST to /v1/chat/completions including the OpenAI-Organization header.
OBJECTIVE 1 / 1 — type "hint" if stuck
SYNAPSE VERIFICATION
QUERY 1 // 3
Where is the Privacy Filter model deployed?
On OpenAI's servers
Locally on the enterprise's own infrastructure
In the browser
On a blockchain