What it finds
| Kind | Examples |
|---|---|
| Emails | alex@example.com |
| Phone numbers | 8 to 15 digits, with or without a country code; dates are left alone |
| Card numbers | Checked with the Luhn test, so ordinary long numbers aren’t blurred |
| Bank accounts | IBANs |
| API keys and tokens | Keys starting sk- (Stripe, OpenAI, Anthropic style), GitHub, Slack, AWS and Google keys, JWTs, and long random tokens |
How to redact a screenshot
- Capture the area you want to share.
- Choose Auto-redact on the toolbar. Every match is blurred, and the toast says what was found.
- Look it over. Each blur is an ordinary mark: move it, resize it, delete it, or add more with the Blur tool.
- Copy, save or send it to your AI app.
Why it matters with AI
Screenshots of terminals, dashboards and settings pages often carry keys, customer emails and account numbers. Pasting them into a chat, a ticket or an AI app copies those secrets to someone else’s servers. Redacting first, on your own computer, keeps them out.
Questions
Is my screenshot uploaded to find the secrets?
No. The text is read on your computer and matched against patterns on your computer. Nothing is sent anywhere.
Can it miss something?
Yes. It finds things by their shape, like an email address or a key prefix, so a name, an address or a secret in an unusual format can slip through. Look over the capture before you share it, and blur anything else with the Blur tool.
How many times can I use it for free?
As often as you like. Auto-redact and the Blur tool are free with no daily limit.