Skip to main content
In addition to client-side redaction, AgentCat redacts sensitive values on our servers before events are stored, catching data that client-side filters may have missed.

​
What gets redacted

When redaction is enabled, the user intent, parameters, response, and error payloads of every incoming event are scanned, and matched values are replaced with placeholders:
  • Email addresses → <email>
  • IP addresses (IPv4 and IPv6) → <ip>
  • URLs and hostnames → <url>
  • Credentials — Bearer, Basic, Digest, Token, and API-key authorization values
  • Unique identifiers — UUIDs and trace IDs
  • Additional sensitive patterns, such as dates and long numeric identifiers

​
How it works

  1. Pattern-based detection: payload fields are scanned recursively — including nested objects and lists — against a curated set of patterns
  2. Applied before storage: redaction happens during event processing, so matched values are replaced before the event is written
  3. Best effort: pattern matching reduces the chance that sensitive data is stored, but it cannot guarantee catching everything. Keep sensitive data out of your events at the source where possible — see client-side redaction

​
Configuration

Server-side redaction is enabled by default for all projects. You can toggle this per project in Settings > Projects > Edit > “Redact sensitive strings”.
Toggling the setting only affects new events. Previously stored events are not modified.