Personal data & PII scanner

Before you paste a log into a ticket, commit a config file, or share a snippet in chat, it is worth checking whether it contains anything sensitive. This scanner reads text you provide and flags likely personally identifiable information and secrets: credit card numbers (validated with the Luhn checksum to cut false positives), Social Security numbers, AWS access keys, JSON Web Tokens, and private keys. It can then redact what it finds so you can share a safe version.

The whole scan runs in your browser. The text you paste is never uploaded, which matters precisely because the material you would want to check — production logs, credentials, customer data — is the material you least want to send to a third-party server. Pattern matching plus checksum validation catches the common formats reliably, though no automated scanner is a substitute for a careful read of anything truly high-stakes.

Typical uses are cleaning logs before attaching them to a bug report, scrubbing example data before publishing documentation, and catching an API key that slipped into code before it reaches a public repository. Treat a clean result as a strong signal, not a guarantee, and always confirm redaction visually before you share the output.