PII & Secret Log Redactor / Masker

Client-SideOffline Ready

Scrub credentials, API keys, passwords, credit cards, emails, and PII from production logs and error stack traces 100% locally in your browser before sharing.

Load Sample:
Total Redactions7
API Keys & Secrets4
PII & Contacts1
Cards & Network2

Original Log Input

577 bytes • 7 lines

Sanitized Clean Output

7 Scrubbed

Detection Rules & Sensitive Pattern Filters

Toggle individual detector rules or entire categories on and off to match your scrubbing policy.

AWS Access & Secret Keys2 found

Detects AKIA access key IDs and paired AWS secret keys

OpenAI & AI API Keys1 found

Detects OpenAI sk- and sk-proj- credential strings

GitHub Tokens

Detects Personal Access Tokens (ghp_, gho_, ghs_) and fine-grained tokens

Stripe API Keys

Detects Stripe live and secret keys (sk_live_, rk_live_, pk_live_)

Slack Webhooks & Tokens

Detects Slack incoming webhook URLs and bot user tokens (xoxb-)

JSON Web Tokens (JWT)1 found

Detects signed or encoded Bearer JWT tokens (ey...)

Passwords & Auth Secrets

Detects key-value password assignments in configs and queries

Email Addresses1 found

Detects corporate and personal email addresses

Phone Numbers

Detects international and US telephone numbers

Social Security Numbers (SSN)

Detects 9-digit US SSN format (XXX-XX-XXXX)

Credit Card Numbers

Detects 13-19 digit cards with real-time Luhn algorithm validation

IPv4 Addresses2 found

Detects public and private IPv4 network addresses

MAC Addresses

Detects hardware network interface physical addresses

Embedded URL Credentials

Detects embedded passwords in URLs (http://user:pass@host)

Any matches matching these specific terms will be ignored and preserved exactly as typed.

100% Client-Side Privacy

Zero server uploads. Your production logs, error traces, and credentials are sanitized strictly in local browser memory using client-side regular expressions.

Multi-Category Detection

Automatically identifies API keys (AWS, GitHub, Stripe, OpenAI), JWT tokens, passwords, credit cards (Luhn-verified), emails, phones, SSNs, and IP addresses.

Custom Masking Strategies

Choose between descriptive placeholder tags ([REDACTED_API_KEY]), partial masking (j***@domain.com), fixed asterisks, or deterministic SHA-256 hashes.

Frequently Asked Questions

Why should I redact logs before sharing them with LLMs or public forums?
Production stack traces and application logs frequently leak sensitive authorization headers, customer PII (emails, phone numbers), cloud keys (AWS, Stripe, OpenAI), and internal network topology. Pasting raw logs into ChatGPT, Discord, or public GitHub issues poses severe data breach and credential theft risks.
How does the Credit Card verification work?
The redactor matches 13 to 19 digit card patterns (Visa, Mastercard, Amex, Discover) and runs the Luhn checksum algorithm in real-time. This eliminates false positives so timestamps and random 16-digit database IDs are not accidentally flagged as credit cards.
What is the "Deterministic Hash" masking mode?
Deterministic hashing replaces sensitive tokens (like a specific user email or IP address) with a consistent truncated SHA-256 hash (e.g., [HASH:a8f9c1...]). This allows you to track recurring user actions or debug session flows across multiple log lines without ever exposing the real identity.
Are my logs or sensitive files stored anywhere by AgentXAlpha?
No. The processing engine runs entirely within your browser client. No text, files, or parameters are transmitted to any backend server.
Recommended For You

More Security & Privacy Utilities

View all Security & Privacy tools