How to blur customer data in a support screenshot

Do not blur it. A blur or a pixelate over a customer's name, email or order ID can be reconstructed, and those short, structured strings are the easiest kind to rebuild. Cover the region with a solid opaque block, or a tool that rewrites the pixels, then export a new flattened file and check it before you share. Do it on your own machine, because a support screenshot is personal data and a leaked one is a reportable breach.

What counts as customer data to hide

A ticket, a chat transcript, a CRM record or an admin panel is dense with things that identify a person or their account. Under GDPR and CCPA all of it is personal data, including an identifier like an order ID or account name that only points to someone indirectly. Here is the field-by-field call for a typical support view.

A leaked support screenshot is a reportable breach

This is the part support and CS teams underrate. GDPR defines a personal data breach as any unauthorized disclosure of personal data, and it does not require malice or a hacker. A ticket screenshot dropped into the wrong Slack channel, pasted into a public help article, or sent to a vendor you have no data agreement with is a disclosure. If it is likely to harm the customer, the clock starts: 72 hours to tell your supervisory authority, and the customer without undue delay.

The real cost is not theoretical. In May 2025 Coinbase confirmed an insider breach after threat actors posted screenshots of its internal support panel to Telegram. Overseas support agents at an outside vendor had been bribed for their access. The panel on screen exposed names, email addresses, phone numbers, dates of birth, KYC ID images, wallet balances and transactions for roughly 69,000 people. The attackers then demanded a $20 million ransom, which Coinbase refused, and the company put the total cost of the incident near $400 million. The lesson for everyone else is smaller and cheaper: the support view itself is a goldmine, so anything you capture from it has to be scrubbed before it travels anywhere.

Why blurring the data does not hide it

A blur or a pixelate does not remove the underlying pixels, it only smears them in a predictable way, so the original can be estimated back. In 2022 Bishop Fox released a tool called Unredacter that reconstructs pixelated text: it renders each candidate string in the same font, pixelates the guess with the same settings, and matches it against the redacted image, character by character. It builds on an earlier tool, Depix. Both work best on short, structured text in a known font, which is exactly what a support view is full of, an order ID, a phone number, a card last-4. That is the same reason it fails everywhere else, and the full mechanism is in how to redact a screenshot on a Mac and in reversing a blurred or pixelated image. For a customer's data, treat blur and pixelate as if they do nothing.

Do not paste a customer's details into a web blur tool

Searching for a quick way to blur a screenshot lands you on a browser tool where you upload the image and it hands one back. For a holiday snap that is fine. For a customer's data it is a second disclosure: you have just sent that person's name, email and account details to a third party you have no agreement with, on a server you cannot see. If your own policy says customer data stays inside your systems, an online blur tool breaks it in one drag-and-drop. Redact on your own machine with a local tool, so the data never leaves it.

The safe way to hide customer data before you share

The method is the same one that works for any secret: cover it solidly, flatten it, and check. You can do this in Preview with care.

1. Crop to just the part you need first. If the bug is one button, you do not need the whole customer record around it.
2. Open the shot in Preview, show the Markup toolbar, and choose the rectangle shape. Skip the blur and pixelate options.
3. Set the fill to solid black at 100 percent opacity and cover each field of customer data completely. A marker or highlighter applied below full opacity leaves the text readable when someone pushes brightness and contrast.
4. Flatten it. File, then Export, and save a fresh PNG. Do not save over the original, because save-over-original bugs like aCropalypse (CVE-2023-21036, 2023) left the hidden part of an image recoverable inside the file.
5. Open the exported file, the one you are about to send, and zoom in on every covered field to confirm nothing shows through.

Before you send it, scan the parts of the frame people forget. The browser address bar can hold a customer ID in the URL, a pinned tab can name another account, a desktop notification can slide in mid-capture, and the row above or below the one you meant to show is often a second customer. There is more on what hides in the frame in the guide to sharing a screenshot safely.

How ScrubShot handles it

The manual route works, but it is fiddly on every single ticket, so I built ScrubShot to make the safe path the default. Press Fn + Space and it captures the screen with ScreenCaptureKit and opens it in an editor, where you crop the support view down to what matters.

The Scrub tool is the part that suits customer data. A normal pixelate sets each block to the average of the pixels beneath it, which is the signal Depix and Unredacter exploit. ScrubShot does not do that. It uses what I think of as a content-independent scramble: each block is filled from a few pixels sampled at random across the whole selected region, so the pattern holds no relationship to whatever sat underneath. Drag it across a name, an email and an order ID and there is no per-field mapping left to solve. It reverses to nothing by design, and the scrub is baked into the image, so the original pixels are gone rather than hidden on a layer.

The capture, scrub and share flow makes no network connections, so the customer's data never leaves your Mac, and nothing is uploaded to a web tool. The app talks to a server only for the free-trial check, license activation and update checks, and that request carries a hashed machine identifier and your license key, never any image data. ScrubShot runs on macOS 14 and later, on both Apple Silicon and Intel, and it needs Screen Recording and Accessibility permission to capture the screen and to see the Fn shortcut.

FAQ

How do I blur out information on a screenshot?

For a customer's data, do not blur it. A blur and a pixelate can both be reconstructed, and the short, structured strings in a support view, an order ID, a phone number, a last-4, are exactly what reconstruction tools handle best. Cover the region with a solid opaque block or a tool that rewrites the pixels, then export a new flattened image and check it.

What customer data do I need to hide in a support screenshot?

Anything that identifies the person or their account: full name, email address, phone number, postal address, account or order ID, the last four digits of a card, IP address, and the contents of their messages. Under GDPR and CCPA all of these are personal data, including an order ID or account name that only indirectly points to someone. When in doubt, cover it.

Is sharing a screenshot of a customer's data a data breach?

It can be. GDPR defines a personal data breach as any unauthorized disclosure of personal data, so a ticket screenshot that reaches the wrong Slack channel, a public help doc, or a vendor without a data agreement counts, even if nobody acted in bad faith. In 2025 leaked screenshots of Coinbase's internal support panel exposed names, emails, phone numbers and more for tens of thousands of customers. A reportable breach can start with one shared image.

Is it safe to use an online blur tool for customer data?

No. Pasting a screenshot of a customer's details into a browser blur tool uploads that personal data to a third party you have no agreement with, which is its own disclosure and possibly its own breach. Redact on your own machine with a local tool so the customer's data never leaves it.

Does ScrubShot upload my screenshots?

No. The capture, scrub and share flow makes no network connections, so a support screenshot never leaves your Mac. The app contacts a server only for the trial check, license activation and update checks, and those requests carry a hashed machine identifier and your license key, never any image data.