The Redaction Flow
Your payload enters with PII.
It leaves without it.
01
Raw Payload
Live data from your upstream service — unfiltered, with PII intact.
"customer_id": "cust_8821",
"full_name": "Sofia Mendez",
"ssn": "429-31-8821",
"dob": "1987-03-14",
"passport": "US29847321",
"kyc_status": "approved",
"risk_score": 0.12
"full_name": "Sofia Mendez",
"ssn": "429-31-8821",
"dob": "1987-03-14",
"passport": "US29847321",
"kyc_status": "approved",
"risk_score": 0.12
Intercept
at runtime
02
Active · Redacting
Treza Redaction Layer
Strips PII fields before they reach your models or downstream services. Every action is logged and vaulted — never silently discarded.
Runtime field stripping — zero latency impact
Stripped fields encrypted + vaulted (KMS + TEE)
You declare what to retain — Treza removes the rest
Immutable audit record per request
GDPR erasure on demand
Forward
clean payload
03
Your Downstream Services
Receive a clean, compliant payload. PII is gone. Models only see what they need.
ChatGPT
Claude
Application Logs
Telemetry / APM
Third-party APIs
Databases / Storage