Redact Logs Before Sending Them to an AI Assistant

Worked example

Task context

A support log is useful for debugging, but it contains a customer email, an authorization value, a trace ID, and a callback URL with a token. Redact the sensitive parts while keeping the structure readable enough for debugging.

Open the related tool: Data Redactor

Input and output

{
  "email": "alex@example.test",
  "authorization": "Bearer demo-secret-token-1234567890",
  "trace_id": "8f14e45f-ea7d-4b32-a2fa-9f33f2bc4561",
  "callback": "https://example.com/callback?access_token=demo-token-12345"
}

{
  "email": "[EMAIL_REDACTED]",
  "authorization": "Bearer [TOKEN_REDACTED]",
  "trace_id": "[UUID_REDACTED]",
  "callback": "https://example.com/callback?access_token=[SENSITIVE_QUERY_REDACTED]"
}

Checks before copying

• Keep enough structure for the recipient to understand the problem.
• Do not rely on automatic redaction alone; review the result line by line.
• Preserve the original only in an approved internal system if it is needed for audit or debugging.
• Avoid pasting production secrets into any third-party system.

Lesson: Good redaction keeps the debugging shape while removing values that should not travel outside the trusted context.

Keep working