Share logs and messages without the personal bits
Support requests, error logs and screenshots of text often carry more than the problem: email addresses, phone numbers, IP addresses, card numbers and, surprisingly often, passwords and API keys. Paste the text, check what was found, and copy a version that's safe to send.
What it looks for
- Contact details: email addresses and phone numbers in most international formats.
- Network details: IPv4 and IPv6 addresses, device (MAC) addresses.
- Money: card numbers (checked with the Luhn test, so random numbers aren't flagged) and IBANs.
- Secrets: private keys, JWTs, bearer tokens, AWS, GitHub, Slack, Stripe, Google and AI service keys, passwords inside URLs, and values after words like
password=orapi_key:. - Your own words: names, company or project names you add.
Three ways to replace
Labels turn each value into a placeholder such as [EMAIL-1]. The same value always gets the same label, so the text still makes sense. Mask keeps a few characters, like r•••@e•••.com. [REDACTED] hides everything.
Questions
Is my text sent anywhere?
No. It's checked in your browser.
Does it find names and street addresses?
Not automatically, because they're hard to tell apart from ordinary words. Add them in the "Also hide these words" box, and always read the result before you share it.
I pasted a real password or key. What now?
Nothing left your device here, but if it was already shared anywhere else, change it. Keys that end up in tickets or chat logs should be treated as exposed.