|
Developer Utilities 100% Client-Side · 0 Bytes Sent to Server Instant In-Memory Execution

Sensitive Data Scrubber & Reversible Masker

Protect your privacy before pasting logs or documents into ChatGPT and Claude. Automatically detects and redacts Indian and global sensitive entities (Aadhaar with Verhoeff validation, PAN, GSTIN, IFSC, UPI, credit cards with Luhn check, API keys) into reversible tokens, and lets you swap them back from AI replies locally.

Active Scrubber & Masking Filters
Verified with Luhn & Verhoeff Checksums
Note: Names cannot be detected by regex alone without an AI model. Add specific names above to mask them cleanly.
Masked 9 sensitive entities into secure reversible tokens
API_KEY: 1GSTIN: 1PAN: 1IFSC: 1UPI_ID: 2PHONE: 1IP: 1CUSTOM: 1
1. Original Prompt / Document
2. Masked Prompt (Safe to Paste in AI)

3. Reverse & Restore AI Output (Local Token Swap)

Paste the reply you got from ChatGPT or Claude below. It will swap all tokens (`[AADHAAR_1]`, `[PAN_1]`, `[EMAIL_1]`) back into your original real data locally on your computer!

100% Client-Side Privacy: Your documents and token maps never leave your device. Zero cloud logging.

Step-by-Step Instructions

1

Paste Unsanitized Data or Logs

Paste application server logs, SQL query dumps, error stack traces, or customer datasets.

2

Configure Scrubbing Profiles

Select detection categories: Passwords, API Keys / Tokens (AWS, GitHub, Stripe, OpenAI), Credit Cards, SSNs, IP Addresses, and Emails.

3

Choose Replacement Mask

Select masking format: Generic placeholders (`[SECRET_REDACTED]`), hashed identifiers, or partial character masks (`sk-live-***`).

4

Copy Scrubbed Data

Copy the sanitized logs ready for sharing with third-party vendors, bug tracking systems (Jira, GitHub Issues), or public logs.

Key Features & Capabilities

  • High-entropy secret key detection identifying AWS Access Keys (`AKIA...`), GitHub Tokens (`ghp_...`), Stripe Keys (`sk_live_...`), and OpenAI Keys (`sk-...`)
  • Password and authentication credential pattern scrubber for database connection strings (`postgres://user:pass@host`)
  • Payment Card Industry (PCI) and HIPAA compliance data sanitization engine
  • Client-side processing guaranteeing zero external leakage of sensitive corporate secrets

Frequently Asked Questions

Why is data scrubbing critical before sharing logs on GitHub or Jira?

Application logs and error stack traces frequently contain accidental secrets (Bearer tokens, database credentials in connection strings, authorization headers, customer PII). Automated bot scrapers continuously monitor public GitHub repositories and Jira boards for leaked API keys to compromise cloud infrastructure within minutes.

How does the scrubber identify API keys from services like AWS, Stripe, and GitHub?

The scrubber uses specialized regex signatures and entropy analysis: **AWS Keys** match `AKIA[0-9A-Z]{16}`; **GitHub Tokens** match `ghp_[a-zA-Z0-9]{36}`; **Stripe Keys** match `sk_live_[0-9a-zA-Z]{24}`; **OpenAI Keys** match `sk-[a-zA-Z0-9]{48}`.

How are database connection strings sanitized?

Connection URIs like `mongodb+srv://admin:[email protected]/prod` are parsed, replacing the password segment with `mongodb+srv://admin:[REDACTED]@cluster0.mongodb.net/prod` while keeping the host structure intact for debugging.

Is data scrubbing executed client-side?

Yes. All regex pattern matching and token scrubbing run entirely in local browser memory. Zero bytes of sensitive data or credentials are ever sent to an external server.

Discover complementary online tools in the same workflow.