Skip to content

docs(guardrails): say how PII redaction works on streaming requests #1168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ninadphalak wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs(guardrails): say how PII redaction works on streaming requests #1168

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
74e78e8
docs(guardrails): say how PII redaction works on streaming requests
ninadphalak Nov 11, 2026
bb140fe
docs(guardrails): say how PII redaction works on streaming requests
ninadphalak Nov 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions aigw/product/guardrails/pii-redaction.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,12 @@ Once you've created your custom PII regex guardrail, add it to your AI Gateway c
You can add the same guardrail to both `before_request_hooks` (input guardrails) and `after_request_hooks` (output guardrails) to scan and redact PII in both user inputs and LLM responses.
</Note>

<Note>
On streaming requests (`stream: true`), output guardrails run on the full response after the stream ends. Redaction does not change the chunks the client has already received, and the result is informational only (see [Streaming Responses](/aigw/product/guardrails#streaming-responses)). To redact PII in LLM responses, send the request with `stream: false`.

Background on filtering streamed output: [OWASP AI Exchange, sensitive output handling](https://owaspai.org/go/sensitiveoutputhandling) and [Split-Boundary Leaks in Streaming Guardrails](https://doi.org/10.5281/zenodo.22909585).
</Note>

### Example Implementation


Expand Down
6 changes: 6 additions & 0 deletions product/guardrails/pii-redaction.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,12 @@ Once you've created your custom PII regex guardrail, add it to your Portkey conf
You can add the same guardrail to both `before_request_hooks` (input guardrails) and `after_request_hooks` (output guardrails) to scan and redact PII in both user inputs and LLM responses.
</Note>

<Note>
On streaming requests (`stream: true`), output guardrails run on the full response after the stream ends. Redaction does not change the chunks the client has already received, and the result is informational only (see [Streaming Responses](/product/guardrails#streaming-responses)). To redact PII in LLM responses, send the request with `stream: false`.

Background on filtering streamed output: [OWASP AI Exchange, sensitive output handling](https://owaspai.org/go/sensitiveoutputhandling) and [Split-Boundary Leaks in Streaming Guardrails](https://doi.org/10.5281/zenodo.22909585).
</Note>

### Example Implementation

<Tabs>
Expand Down