Skip to main content
PII redaction automatically detects and removes personally identifiable information from your AI agent traces at the edge, before any data is persisted. This ensures sensitive data never reaches your stored logs, search indexes, or analytics.

​
How it works

When PII redaction is enabled for your organization, every incoming trace is scanned during ingestion. Detected sensitive values are replaced with category-specific placeholders before the data is written to storage. The redaction runs on all text fields across your traces:
  • Runs - user prompts, full prompts, responses, status messages, attributes, and metadata
  • Steps - prompts, responses, status messages, and attributes
  • Tool calls - arguments, results, status messages, and attributes
Nested objects and arrays within attributes and metadata are also scanned recursively.

​
What gets redacted

Credit card detection uses the Luhn algorithm to avoid false positives on arbitrary number sequences. Phone number detection requires formatting characters (parentheses, plus sign, or dash) and a valid digit count to reduce false matches.

​
Availability

PII redaction is available on the Enterprise plan. Contact us at support@thecontextcompany.com to enable it for your organization.

​
Things to keep in mind

  • Redaction is irreversible - original values are never stored and cannot be recovered.
  • Redaction is idempotent - applying it multiple times produces the same result, so placeholder tokens like [EMAIL] are not double-redacted.
  • Redaction happens before data reaches storage, search indexes, and pattern detection. Downstream features like insight search and monitoring operate on the redacted text.