Screenshot redaction for HR and recruiters
Short answer: HR and recruiting screens are wall-to-wall personal data about people who never see where the screenshot ends up, so before you share one, scrub every name, contact detail and salary figure that is not the point and annotate the thing you are actually asking about. The candidate or employee in the frame has no idea the image exists, which puts the bar higher than it is for your own data. Here is what your tooling tends to expose, the everyday moments these screenshots happen, and the loop that keeps the cleanup to a couple of drags.
HR tooling is personal data top to bottom
Most jobs put the occasional sensitive thing on screen. HR and recruiting put almost nothing else on screen. The applicant tracking system, the HRIS, the payroll view, the interview scorecards, every one of them is a wall of detail about real people, and a screenshot captures the whole frame whether you meant it to or not. The point you wanted to share arrives surrounded by everyone else.
- Candidate names, emails and phone numbers, sitting in lists ten or twenty rows deep.
- CVs and application answers, including addresses, dates and previous employers.
- Salary, band and offer data, the single most sensitive number in the building and the easiest to leave on screen.
- Interview feedback and scores, written for the hiring panel and nobody else.
- References, and right-to-work or identity documents attached to a record.
- Org charts with reporting lines, which quietly map who answers to whom.
None of that belongs in a chat thread, a help article or a vendor ticket. You grabbed the screenshot to ask one question or show one thing, but the answer to that question does not require the other nine candidates, their pay, or their feedback to come along for the ride.
The people in the frame never see where it goes
Here is the asymmetry that makes HR screenshots different from most. When I share a screenshot of my own account, I am the one taking the risk. When you share a candidate profile or a payroll record, the person in the frame has no idea the screenshot was taken, no say in where it lands, and no way to ask you to delete it. They handed you their data to apply for a job or get paid, not to feature in a screenshot in a chat channel.
That asymmetry is the whole reason the bar is higher here. You are not protecting yourself, you are protecting someone who is not in the room. The same instinct that covers names, emails and account numbers in other settings applies just as much to pay and personal detail, which is the territory of hiding bank details and personal information in screenshots. Salary and band data deserve exactly that level of care.
What leaks from a typical HR screen
The screens you screenshot most are the ones with the most on them. Here is what tends to be in frame, what leaks if you share it as-is, and what to cover before you do.
| Screen | What leaks | What to scrub |
|---|---|---|
| ATS pipeline | Every candidate in the list, their stage, score and contact details, not just the one you mean. | All rows except the one your question is about, including names, emails and ratings down the column. |
| Candidate profile | Full name, contact details, CV, application answers, interview feedback and references. | Everything that identifies the person, unless the identity is genuinely the point. Keep only the field you are pointing at. |
| HRIS record | Employee name, address, date of birth, role, manager and the reporting line around them. | Name and personal fields, plus the org-chart context if it lets someone work out who the record belongs to. |
| Payroll view | Salary, band, bonus and the name it is attached to, the most sensitive pairing on any HR screen. | Both the figure and the name. A pay number with the person still readable beside it is the leak. |
The moments these screenshots happen
Nobody sets out to leak candidate data. It happens in the small, ordinary moments where a screenshot is just the quickest way to ask or show something:
- Asking a colleague how to do something. You are stuck on a step in the HRIS and grab the screen to ask, and the whole employee record comes with it.
- Reporting a bug to the vendor. A screen is misbehaving, so you screenshot it for the support ticket with real names and salaries still on it.
- Sharing an ATS view in a hiring channel. You want a second opinion on one candidate and post the pipeline, which puts the other nine in front of the whole channel.
- Building training material. A how-to for the team, captured from a live record rather than a dummy one, so the example is somebody real.
The fix is the same in every case: keep the one thing you are asking about, scrub everyone and everything else. Recruiters and support teams run almost the identical check on their own queues, and the version framed for that work is redacting screenshots for customer support tickets, which is worth a look if you also handle inbound questions.
The loop: capture, scrub, annotate
The reason redaction gets skipped is never that people do not care. It is that saving a screenshot, opening a separate editor and re-exporting is a detour you will not take when you are mid-task. So the cleanup has to live in the same few seconds as the capture. With ScrubShot the loop is:
- Press the shortcut. It captures the screen you are looking at, the pipeline, the profile, the payroll view.
- Drag the Scrub tool over every name, contact detail and salary figure that is not the point. They are pixelated straight into the image as you go.
- Run your eye down the list and the corners for the ones that are easy to miss, the column of ratings, the menu showing your own login, and scrub those too.
- Use the Marker to circle the field you are actually asking about, or the Text tool to label it, so the reader looks exactly where you want.
- Copy it to the clipboard or let it save to your Pictures folder, then paste it into the channel, the ticket or the training doc.
Because the Scrub tool rewrites the underlying pixels, a scrubbed name or pay figure cannot be lifted off or recovered later, and none of the editing touches the network, so the only version that leaves your Mac is the cleaned one. That on-device part is the whole argument in the guide to redacting screenshots without uploading them, and it matters most when the data belongs to someone who never agreed to be in the picture.
FAQ
- What should I redact before sharing an ATS screenshot?
- Every candidate who is not the one your question is about. In a pipeline view that means the other names in the list, their emails and phone numbers, and any stage, score or rating attached to them. Keep the one row you are pointing at, scrub the rest. If the screenshot is about a feature or a bug rather than a person, scrub all of the names.
- Is it fine to share candidate details in an internal channel?
- A hiring channel is still a wider audience than the people working that one role, and the message stays in the history long after the conversation. So no, a channel full of colleagues does not need the other nine candidates in the list to answer a question about one of them. Scrub everyone who is not the point, the same as you would for an external share.
- What about screenshots for vendor support tickets?
- Treat a vendor ticket as fully external, because it is. The person debugging your HRIS or ATS does not need real employee or candidate data to see a broken screen. Scrub every name, contact detail and salary figure before you attach the image, leave the error and the layout, and the ticket still shows them exactly what is wrong.
- Can a scrubbed name or salary be recovered later?
- Not with ScrubShot. The Scrub tool pixelates the area straight into the image, and the blocks it draws are random color samples from the region rather than averages of the pixels underneath, so there is nothing for a depixelation tool to brute-force back. A scrubbed name or pay figure cannot be un-scrubbed or lifted off the saved file.
Try it
ScrubShot is a Mac app built for exactly this kind of work: press the shortcut, drag over the names, contact details and salary figures you are not pointing at to pixelate them into the image, annotate the one field you are, then copy or save. The cleaned screenshot is the only version that ever leaves your Mac. There is a free 7-day trial with no card required. After that it is $30 once.