Resources

Notes and guides.

Notes and guides on keeping sensitive detail out of screenshots you share, and on getting more out of ScrubShot. The why behind the app, how it compares to the alternatives, and the bits people ask about most.

• GDPR and screenshots: when a screenshot becomes personal data

  A screenshot of a name, an email or an account becomes personal data under UK GDPR, and an unredacted original sitting in chats and tickets is data you are storing. What controllers owe, and how to minimize it.

• Is sharing a screenshot a data breach?

  Sometimes yes. A screenshot that exposes someone else's personal data can be a breach under UK GDPR, and reportable to the ICO within 72 hours if it is likely to risk people. How to tell the difference, and what to do in order.

• Screenshot data leaks: the human error nobody plans for

  Human error is the leading cause of data leaks, and a screenshot is its most relatable shape. Why careful people leak, the four predictable failure points, and the workflow fix that removes the error instead of blaming the human.

• Microsoft Recall and the case for on-device screenshot control

  Microsoft Recall captures your screen in the background to make it searchable, and the privacy debate around it points to a clear principle: capture you choose, redact on-device, upload nothing.

• Should you redact a screenshot online? What actually happens when you upload

  To redact a screenshot online you upload the unredacted original first, so the sensitive version reaches a server before any scrubbing happens. What that means, and the on-device alternative.

• How to blur faces in screenshots on a Mac

  Meeting grids, strangers in frame, customers in admin views: how to cover faces in Mac screenshots so people cannot be identified, and why pixelating into the image beats a soft blur.

• What metadata do Mac screenshots actually contain?

  No GPS, but a timestamp in the file and the exact date and time in the filename. What a Mac screenshot really carries, how to check, and why the pixels are the bigger leak.

• Redact screenshots before posting them publicly

  A public post is scraped, archived and zoomable forever, and deleting it only removes your copy. What leaks in a typical post and how to clean a screenshot before it goes on X, Reddit or a blog.

• Redacting crypto and trading screenshots before you share them

  Seed phrases never get screenshotted at all. For everything else, balances, addresses and keys, here is how to share the chart and the win without doxxing your whole on-chain history.

• Screenshot redaction for HR and recruiters

  ATS pipelines, candidate profiles and payroll views are wall-to-wall personal data about people who never see where the screenshot goes. What to scrub before HR screens get shared.

• Screenshot redaction for accountants and finance teams

  Vendor tickets, client queries and training screens all carry client books, bank details and payroll figures. How finance teams share screenshots without leaking the rest of the ledger.

• Can pixelation be reversed? What depixelation tools actually recover

  Classic pixelation of screenshot text can be brute-forced back out, and AI unblurring invents detail rather than recovering it. What each attack really gets back, and the mosaic that gives it nothing.

• I shared a screenshot with sensitive info: what to do now

  Revoke what the screenshot unlocks first, then delete the post, then assume it was copied while it was up. The damage-control checklist for a leaked screenshot, in the order that matters.

• Does covering text in Preview actually redact it?

  An opaque shape flattened into a PNG genuinely hides the pixels. The trouble is the near-misses: translucent fills, highlighter redactions and PDF shapes that lift straight off. Where each one hides.

• Screenshot redaction for lawyers and legal teams

  On a legal screen the client list is the screen, and even the fact of a matter is confidential. What leaks from practice-management, email and billing views, and how to scrub it before sharing.

• Screenshot redaction for IT admins and MSPs

  Hostnames, internal IPs, usernames and version numbers turn a console screenshot into a map of the network. What to scrub before the image lands in a vendor ticket or a forum post.

• How to redact chat screenshots before you share them

  Names, avatars, numbers and group members identify everyone in a chat screenshot. How to anonymize a conversation so the words can travel without the people attached.

• Redacting email screenshots: headers leak more than the body

  The to and cc lines, the signature block, the sidebar of other subjects: an email screenshot leaks around the message, not just in it. What to scrub zone by zone before you share one.

• Blur and pixelate sensitive data in screenshots: a step-by-step guide

  Blur softens detail and can be reversed; pixelating into the image cannot. The real difference, and how to redact screenshots safely on a Mac in seconds.

• The fastest way to hide API keys and emails in Mac screenshots

  Pixelate API keys, tokens and emails straight into a Mac screenshot before sharing. The fast on-device workflow, a what-to-scrub checklist, and why redaction is not revocation.

• The best way to redact bank details and PII in screenshots

  What to cover, why irreversible pixelation beats a draggable box, and the exact steps to redact bank details and personal data in a screenshot on a Mac.

• Screenshot redaction vs cropping: why cropping isn't enough

  Cropping deletes pixels but only works at the edge of a frame. When to crop, when to pixelate the secret in place, and how to combine both on a Mac.

• Blur sensitive information in screenshots before you paste to Slack

  Chat is where screenshots leak most. Scrub the secret on your Mac, copy, then paste the cleaned image into Slack or Teams. Here is the exact loop and what hides in frame.

• Screenshot redaction for developers: secure bug reports in seconds

  Good bug reports capture exactly where secrets hide. Scrub tokens, keys and customer data inside the capture-to-share loop on your Mac, in one fast pass.

• Secure screenshot sharing for Jira, GitHub and Linear issues

  A screenshot on a GitHub, Jira or Linear issue is more public and permanent than it feels. Here is who really sees it, what leaks, and how to redact before you attach.

• How to redact screenshots for customer support tickets safely

  A support agent's guide to scrubbing screenshots before they leave your Mac: hide other customers, identifiers and internal notes in one fast capture-to-paste loop.

• How to anonymize client screenshots for case studies and demos

  Turn a real client screenshot into a safe case-study asset: what to anonymize, how to pixelate the values in place while keeping the UI believable, and the one step people skip.

• Mac screenshot redaction tools compared: built-in vs ScrubShot

  Built-in Mac tools handle capture, markup and cropping for free, but Markup has no pixelate. Here is the honest comparison with ScrubShot.

• Privacy-first screenshot workflows on Mac

  Build a privacy-first screenshot habit on Mac: edit on-device, redact inside the capture loop, clear out the unredacted originals, and prefer the clipboard.

• Why I built ScrubShot

  Every screenshot tool left the sensitive bits in, or wanted to upload them to redact them. So I built the one I wanted: capture, scrub out the private parts, share. Nothing leaves the Mac. The story behind a one-person app.