Skip to content

Redact PII and API secrets before storing request traces

Automatically mask bearer tokens, emails, phone numbers, and credit-card patterns before writing observability traces or eval datasets.

Copy the prompt and paste it into the AI assistant you already use.

Checklist for privacy-safe AI trace logging

  1. 01

    Mask auth headers unconditionally

    Never persist Authorization, Cookie, or X-API-Key header values inside stored debug traces.

  2. 02

    Enable regex PII scrubbers

    Redact emails, phone numbers, and token formats such as sk_ or ghp_ prior to log persistence.

  3. 03

    Support zero-payload privacy mode

    Keep latency, error codes, and schema pass metrics on sensitive routes without storing raw text.

  4. 04

    Scrub before exporting eval sets

    Verify masked placeholders appear properly whenever production traces are copied into golden evals.

Common questions

Does log redaction break live endpoint execution?

No. Sensitive values are scrubbed exclusively from the observability log pipeline after or parallel to inference—never breaking legitimate inputs.

Can we keep metrics and status codes without storing user text?

Yes. Zero-payload logging mode records HTTP status, latency, and token metrics while dropping input and output bodies completely.

What custom secret formats can regex scrubbers catch?

Beyond standard emails and card patterns, you can register custom regex rules for internal account IDs or custom vendor keys.