How to share a revenue screenshot without leaking data

You can post a revenue milestone without leaking anything, but a raw Stripe or dashboard screenshot almost always shows more than the one number you meant to show. The frame catches customer names and emails, a single customer's amount, your MRR or churn breakdown, and the last four digits of your payout bank account. The fix is not to blur those, because a blurred or pixelated name or number can be reconstructed. Crop the sensitive rows out of the frame, cover anything left with a solid block or a destructive scramble, export a brand-new file, then check it before you post. Do the whole thing on your Mac, because you are about to publish it to the world and a recoverable redaction is the entire risk.

Why a revenue screenshot is the risky one

Building in public runs on these shots. A green MRR curve or a Stripe payout does more for a launch than any amount of copy. The trouble is that the screen you are proud of is a working dashboard, and a working dashboard is dense with other people's data. Arvid Kahl, who built his own audience partly on public Stripe numbers, now argues the safe threshold for sharing them has collapsed toward zero, because a competitor can feed your public figures to an AI coding agent and clone the model in days. You do not have to go that far to see the smaller, concrete problem: the pixels around your headline number belong to your customers, and once a shot is on Twitter or LinkedIn it is copied, cached and out of your hands. This is a stricter case of whether it is safe to share a screenshot at all, because here you are publishing to everyone on purpose.

What actually leaks, where it hides, and the fix

Here is what a payments dashboard tends to reveal beyond the one figure you wanted to share, where each thing sits in the frame, and how to deal with it. The rule underneath the whole table: prefer cropping the sensitive region out of the shot entirely, and only cover what you cannot crop.

The customer data hiding in the frame

This is the leak people miss, because they are looking at the number, not the list under it. A Stripe payments view is a table of real charges, and each row can carry a customer's name, their email, the card brand and last four, and the exact amount they paid. A Customers tab is a directory of email addresses. A subscription page names one paying customer and shows what their plan costs them. None of that is yours to publish. Even one visible email is a person you have exposed to spam and scraping, and a name tied to an amount is a detail about their spending that they never agreed to make public. Crop so the list never enters the frame in the first place. If a row has to stay, cover it with a solid fill, and read the next section before you reach for a blur.

Figures you did not mean to reveal

The second leak is your own numbers. You wanted to post one headline, say the month's revenue, but the same screen usually shows the breakdown beside it: churn, refunds, active subscriber count, average revenue per user, the dip last quarter you were not planning to explain. A payout screen pairs the amount with the destination bank's last four digits, and on App Store Connect that sits right under the figure with your bank's name. Decide the one thing you are sharing, then make the shot show only that. Everything else on the screen is either a competitor's free intelligence or a detail you will have to answer questions about later. Crop to the single tile or line, do not photograph the whole dashboard and cover six things afterward.

The reversibility trap: do not blur a name or a number

The instinct is to blur or pixelate the names and amounts and post the shot. Do not. A blur or a mosaic hides the pixels, it does not remove them, and on short structured text it can be undone. In 2022 Dan Petro at 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, walking character by character. It builds on an earlier tool, Depix. Pixelation is deterministic and local, so there is a mapping to solve, and it is strongest on exactly the short, structured strings in a payments list, an amount, an order number, an account fragment, a name. A blur is the weaker cousin of the same problem, and a low-radius blur can be estimated back. Petro's advice was blunt: no pixelization, no blurring. For the fuller picture of what can and cannot be undone, I wrote a separate piece on whether you can reverse a blurred or pixelated image.

There is a second trap even if you do cover things properly. In 2023 a bug nicknamed aCropalypse (CVE-2023-21036) showed that Google's Pixel Markup editor and Microsoft's Snipping Tool left the cropped-out part of a PNG recoverable, because saving over the original wrote the smaller image without truncating the file, so the old bytes survived past the end. Card numbers and uncropped photos came back out of files people thought were clean. The lesson for a screenshot you are about to broadcast is simple: export a fresh file, never save over the original, and open that fresh file to check it.

The safe way to share one

This is the same discipline as how to redact a screenshot on a Mac, tuned for a revenue shot you are publishing on purpose.

1. Crop first, hard. Cut the browser and dashboard chrome, the account menu, and any customer list or breakdown you are not sharing. The best redaction is a region that was never in the frame.
2. Cover what is left with a solid, fully opaque block, or a destructive scramble that rewrites the pixels. Do not use blur or pixelate on a name or a number.
3. Cover generously. A block traced tightly around a figure still tells people how many digits it hides. Redact the whole line or a fixed-width bar rather than a shape that hugs the secret.
4. Export a brand-new flattened PNG. Do not save over the original, and do not trust an editor that keeps your cover on a separate layer.
5. Open the file you are about to post, not the one you were editing. Zoom all the way in on every covered area, push brightness and contrast to the extremes, and try to select text over the blocks. You should get nothing.

How ScrubShot handles it

The manual route works, but every step is easy to get half right, so I built ScrubShot to make the safe path the default for exactly this moment. Press Fn + Space and it captures the whole screen with ScreenCaptureKit and opens it in an editor. You crop afterward rather than fighting a drag selection, which is how you cut the customer list and the chrome out of the frame before anything else.

The Scrub tool is the part that matters here. 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 mosaic block is filled from a few pixels sampled at random from across the whole selected region, so the block pattern is decoupled from whatever sat underneath. It looks like a redaction and keeps the rough colors of the area, but there is no per-block relationship to the original name or amount to solve for. It reverses to nothing by design, and the scrub is baked straight into the image, so the covered pixels are gone, not hidden on a layer you can delete.

The whole point for a shot you are publishing: the capture, scrub and share flow makes no network connections, so a screenshot with a customer's email or your payout details in it never leaves your Mac before you have cleaned it. 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

Is it safe to share a revenue screenshot?

Yes, once you strip everything you did not mean to publish. A raw Stripe or payments-dashboard shot usually shows more than the one figure you want to share: customer names and emails, a specific customer's amount, an MRR or churn breakdown, and your payout bank's last four digits. Crop those out of the frame, cover anything left with a solid block, export a new file, and check it before you post.

What should I hide in a Stripe screenshot before posting it?

Any customer name or email, any single customer's amount, the card brand and last four digits, your MRR, ARR, churn and refund breakdowns if you only meant to show one headline number, and the destination bank's last four digits on a payout. The account email and any test-mode banner in the top chrome count too. When in doubt, crop tighter so the sensitive rows never enter the frame.

Can I just blur the customer names and amounts?

No. A blurred or pixelated name or number can be reconstructed. Bishop Fox's Unredacter tool, and Depix before it, recover pixelated characters by matching re-pixelated guesses in the same font, and they work best on short, structured text like amounts, order numbers and account digits, which is exactly what sits in a payments list. Cover the area with a solid block or a destructive scramble instead.

Does ScrubShot upload my screenshots?

No. The capture, scrub and share flow makes no network connections, so your screenshots never leave 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.