What the Secret Redactor does
The Secret Redactor finds private details in text you are about to share, such as a log file, config, error message or chat, and replaces them. It spots API keys from services like AWS, GitHub, Stripe, Slack, Google and OpenAI, private key blocks, JWTs, bearer tokens, passwords in URLs and in lines like password=..., email addresses, phone numbers, card numbers, Aadhaar and PAN numbers, and IP addresses.
How to use it
- Paste the text on the left. A sample is loaded to show how it works.
- Choose how to replace each item: a label like [EMAIL], dots, or dots that keep the last four characters.
- Open What to look for to switch types on or off.
- Copy or download the cleaned text, and read it through before sharing.
Example
In the sample, seven items are hidden: an email, a phone number, the login inside a database URL, a Stripe test key, an AWS access key, a JWT and an IP address. The line DATABASE_URL=postgres://app:S3cretPass!@db.internal becomes postgres://[LOGIN]@db.internal, so the host is still visible for debugging.
How it avoids false alarms
Card numbers are only hidden when they pass the Luhn check used by every card, and Aadhaar numbers when they pass the Verhoeff check digit, so ordinary long numbers such as order IDs are left alone. Labels like password: keep the label and hide only the value.
It is a safety net, not a guarantee. Unusual secret formats may be missed, so always look over the result.
Questions people ask
Is my text uploaded?
No. Everything is matched in your browser. Nothing is sent, saved or logged.
If a key was already shared, is redacting enough?
No. Once a secret has been posted or sent, revoke it and make a new one with the service that issued it.
Can I add my own patterns?
Not yet. For now, use Find and Replace for anything specific to your company.