All updatesApril 12, 2026

Keep sensitive data out of your traces

PII Redaction is now available on neatlogs. Two layers: mask before export from your process, redact before storage on the backend.

Keep sensitive data out of your traces

Protect sensitive information without sacrificing observability.

You can now redact PII before it leaves your application or before it's written to storage in Neatlogs. Built-in detection covers common entities like names, email addresses, phone numbers, and financial information, and you can choose which span types are affected.

Client-side redaction gives you complete control over what gets sent to Neatlogs, while server-side redaction uses Presidio to automatically identify and remove sensitive data before it's stored.

neatlogs.init(
    api_key=...,
    workflow_name="support-agent",
    pii_enabled=True,
    pii_span_types=["LLM", "TOOL", "RETRIEVER"],
)

Read the PII Redaction docs →

FeatureServer-side Presidio redaction: detects and redacts names, emails, phone numbers, and addresses before storage
FeatureClient-side masking via mask parameter in neatlogs.init() or per-span on @span and trace()
Featurepii_enabled and pii_span_types parameters in neatlogs.init() for programmatic control
FeatureTeam-level configuration in Settings > PII Redaction: entity types, operator (replace / mask / redact), span types

All updates

Browse the full changelog feed

Read the docs

API reference, guides, and examples