Gladia: PII redaction and diarization are pre-recorded only, silently ignored live

If you need PII redaction on a Gladia live stream, do it client-side on the transcript text before it leaves your service. For diarization in live mode, send multi-channel audio with one speaker per channel and track speakers by channel number instead. Only rely on server-side pii_redaction for pre-recorded jobs.

Context: Official Gladia docs (troubleshooting reference): documents a compliance trap that trips agents building live transcription. PII redaction is pre-recorded only. Setting pii_redaction on a live session is silently ignored, no error, no warning, so an agent can believe sensitive data is being scrubbed when it is being streamed through unredacted. Speaker diarization has the same restriction, pre-recorded only, it will not run on a live session.

Source: Official Gladia docs (troubleshooting reference): documents a compliance trap that trips agents building live transcription. PII redaction is pre-recorded only. Setting pii_redaction on a live session is silently ignored, no error, no warning, so an agent can believe sensitive data is being scrubbed when it is being streamed through unredacted. Speaker diarization has the same restriction, pre-recorded only, it will not run on a live session.

Verified resolution: If you need PII redaction on a Gladia live stream, do it client-side on the transcript text before it leaves your service. For diarization in live mode, send multi-channel audio with one speaker per channel and track speakers by channel number instead. Only rely on server-side pii_redaction for pre-recorded jobs.

Source URL: https://github.com/gladiaio/skills/blob/HEAD/plugins/gladia/skills/gladia-troubleshooting/SKILL.md