Care Before You Share

The 10-second screenshot check before you hit send

Most privacy leaks aren’t dramatic hacks. They’re ordinary screenshots — a chat, a booking, a bug report — shared a half-second before anyone noticed what else was in frame. Here’s a routine short enough to actually do every time.

Sweep the edges first

The subject of your screenshot is rarely the problem. The leak is usually in the margins:

• The status bar — location pins, unread notifications, other people’s names.
• Browser tabs and the address bar — session tokens, internal URLs, “gift-for-mum” tabs.
• The next message up — the reply you’re sharing often sits right below something private.
• Autocomplete and search history dropping down over the page.

The five-second questions

Before it leaves your device, ask:

1. Whose name is in here that hasn’t agreed to be shared?
2. Is there a number — phone, order, account, address — that identifies someone?
3. Would I be comfortable if this were forwarded one more hop than I’m planning?

If any answer gives you pause, that’s your cue to redact rather than crop-and-hope.

Cover it, don’t crop it

Cropping only helps when the sensitive part is at the very edge. For anything in the middle of the frame, open the shot in Redacted, drop a box over each detail, and download. It takes about as long as writing the message you’re attaching it to.

The habit matters more than any single tool. Ten seconds of looking is the cheapest privacy insurance there is — and unlike a recall, it works.