Log redactor
Mask emails, tokens, IPs, API keys, and Authorization headers before sharing logs.
Inputs stay in your browser. Rules mask common sensitive fragments and show counts, but manual review is still required before sharing.
Regex redaction can miss secrets; review before sharing.
How to use this tool
Mask emails, tokens, IPs, API keys, and Authorization headers before sharing logs.
Sanitize backend server logs before pasting them into public bug trackers, tickets, or Slack. Automatically redact emails, credit cards, IP addresses, JWT tokens, and API credentials with masked asterisks.
💡 3 Quick Steps to Get Started
Paste exception traces, terminal dumps, or system access logs into the editor.
Toggle redaction filters for emails, IPv4/IPv6 addresses, payment cards, and auth secrets.
Safely copy sanitized logs ready for vendor troubleshooting and public GitHub issues.
When it helps
Useful before support, issues, PRs, and AI collaboration.
How it works
Rules mask common sensitive fragments and show counts, but manual review is still required before sharing.
Worked example
Example: paste an error log and export a shareable version.
Limits and data handling
Rules cannot cover every secret format, so manual review is still required before sharing.
No. The Log redactor runs in the browser. Do not paste production secrets or unredacted personal data.
GDPR / PII Data Masking, Log Redaction & Privacy Handbook
1. PII Compliance Standards: GDPR, HIPAA & PCI-DSS
Global data privacy frameworks (GDPR Art. 4, HIPAA, California CCPA) classify direct and indirect identifiers—including emails, national identification numbers, payment card PANs, and IPv4/IPv6 addresses—as protected Personally Identifiable Information (PII). Ingesting un-redacted logs into third-party APM or LLM systems creates acute statutory breach liabilities.
2. Regex-Driven Automated Masking Heuristics
Redaction applies deterministic regex pattern matching conforming to PCI-DSS masking standards (preserving only first 6 BIN and last 4 digits on credit cards) and RFC 5322 email anonymization algorithms, substituting authentication tokens with immutable `[REDACTED]` markers.
3. Zero-Server Client-Side Sanitization
All text redaction streams process within client V8 memory, guaranteeing zero telemetry leakage prior to export.
Feedback
How can we improve this tool?
Send a suggestion or bug report for this tool.
FAQ
What input does the Log redactor accept?
Paste log text to sanitize, without intentionally adding production secrets.
How does the Log redactor produce its result?
Built-in rules mask common email, IP, token, API-key, and Authorization fragments and show counts.
What are the Log redactor limitations?
Rules cannot cover every secret format, so manual review is still required before sharing.
Does the Log redactor upload data?
No. The Log redactor runs in the browser. Do not paste production secrets or unredacted personal data.