Sensitive Data Scrubber

Paste logs, emails or documents and automatically redact sensitive information like emails, phone numbers, IP addresses and credit cards before sharing.

runs locally on your browser. Your data never leaves your device.
Scrubbed Output
Safe
Scrubbed output will appear here…

Common Use Cases

Sanitise server logs or stack traces before pasting them into a GitHub issue or Stack Overflow question
Scrub customer email addresses and phone numbers from a support ticket thread before forwarding internally
Remove credit card numbers and SSNs from a sample dataset before sharing it with an external contractor
Strip API keys and JWT tokens from configuration dumps or debug output before posting in a team Slack channel

About Sensitive Data Scrubber

Personally Identifiable Information (PII) is any data that could be used to identify a specific individual: names, email addresses, phone numbers, Social Security numbers, credit card numbers, IP addresses, and API credentials all qualify. Sharing PII carelessly in logs, bug reports, support tickets, or public forums can violate privacy regulations like GDPR, CCPA, and HIPAA, and can expose individuals to identity theft, phishing, and account takeover.

Developers routinely paste stack traces, server logs, and API responses into Slack channels, GitHub issues, and Stack Overflow questions without realising those snippets contain customer email addresses, authentication tokens, or internal IP addresses. Support agents forward email threads that include credit card numbers and phone numbers. Data analysts share sample datasets that contain Social Security numbers. In every case the intent is benign; the sensitive data is simply overlooked.

This tool solves the problem by scanning any text you paste and automatically replacing detected PII with clearly labelled placeholders like [EMAIL], [PHONE], [IP_ADDRESS], [CREDIT_CARD], [SSN], [API_KEY], and [JWT_TOKEN]. The scrubbing happens entirely in your browser using native JavaScript regular expressions, so no data is transmitted to any server, no copies are stored, and no third-party libraries are involved. You can toggle each PII category on or off independently, customise the placeholder text, and even add your own regex patterns for project-specific identifiers.

Whether you are sanitising logs before pasting them into a public issue tracker, preparing a dataset for sharing with a contractor, or simply double-checking an email draft for accidental PII leakage, this tool gives you a fast, private, and transparent way to scrub sensitive data before it leaves your machine.

Frequently Asked Questions

What types of sensitive data does this tool detect?
The tool detects seven categories of PII out of the box: email addresses, phone numbers (US, EU, and international formats), IPv4 and IPv6 addresses, credit card numbers (16-digit patterns with optional separators), US Social Security Numbers (XXX-XX-XXXX format), API keys (alphanumeric strings of 32 or more characters), and JWT tokens (three Base64-encoded segments separated by dots). You can also add your own custom regex patterns.
Is my data sent to a server?
No. All scrubbing happens entirely in your browser using JavaScript regular expressions. Nothing you paste is ever transmitted to any server, stored in any database, or logged anywhere. The tool works fully offline once the page has loaded. Closing the tab discards all data.
Can I customise what replaces detected PII?
Yes. Each PII type has a default placeholder like [EMAIL] or [PHONE], but you can change it to anything you prefer, for example '******', 'REDACTED', or '<removed>'. The custom placeholder applies only to that specific PII type, so you can use different replacement styles for different categories.
What if I need to detect a pattern not covered by the defaults?
The tool includes a custom regex field where you can enter any JavaScript-compatible regular expression along with a label. Your custom pattern is applied alongside the built-in detectors, so you can catch project-specific identifiers like internal employee IDs, order numbers, or proprietary token formats.
Does this tool guarantee 100% PII detection?
No automated tool can guarantee perfect detection. Regex-based scanning catches well-formatted PII reliably, but it cannot detect PII in unusual formats, misspelled names, or contextual references like 'my neighbour John'. This tool is a strong first pass, so always review the output manually before sharing sensitive documents in high-stakes contexts.