Redact a screenshot before you share it — bug reports, order proofs, asking for help
Screenshots are a major source of accidental leaks. You meant to show one error or one chat line, but the same image often also carries: other messages in the top notification bar, browser tab titles, the email you're logged in as, and the real name and address on an order. Before posting to a forum, ticket, or group chat, black out or pixelate those regions locally.
What screenshots leak most often
Account identifiers: email, username, avatar, phone number — usually in page corners or a signed-in state.
Context leaks: other browser tab titles, notification previews, taskbar icons that together reveal what you're doing.
Order/receipt data: shipping address, real name, last digits of a card, and QR codes (which can encode links or ticket data themselves).
Use solid black or pixelate, not blur
For truly sensitive characters (numbers, addresses), use a solid black bar or pixelation — the mask is burned into the pixels and unrecoverable.
For sensitive text and numbers, prefer a sufficiently large solid fill and review the actual exported image. Blur and pixelation may retain information that can be inferred.
Screenshots can carry metadata too
Phone screenshots usually lack GPS but may carry device/time data; images re-exported from a gallery deserve extra care.
Strip image metadata as a habit before sharing.
Do it locally
The screenshot tool here processes images locally. For another product, check its own file-handling and privacy information.
This site's screenshot redaction lets you paste a screenshot with Ctrl/⌘+V, box and mask it locally in your browser, and export — the original never leaves your device.
Questions
Does shrinking or compressing the image remove sensitive info?
No. Resizing/compression only changes pixel quality; the text and faces in the photo stay readable. You must explicitly cover them.
Is mosaic (pixelation) safe?
For typical sensitive info, a large-enough pixel block is safe; for the rare enumerable content (like a short numeric code) there's a theoretical reversal risk, so use solid black for maximum safety.