Image Redaction: Discover and Redact Sensitive PCI ,PII & PHI Data in Images
Image redaction removes PII, PCI, and PHI from screenshots, photos, and scans. Learn how it works and how Strac automates it across SaaS, browsers, and AI tools.
Image redaction is the permanent removal of sensitive data from an image. The card number, ID number, or patient detail is replaced with a solid mark, and the mark is saved into the file. Everything else in the image stays readable.
It differs from cropping a picture or drawing on top of it. Covering hides data from the viewer; redaction removes it from the copy you share.
Images are a blind spot for three reasons:
Manual review does not close the gap. A person can redact one image; a support queue receives them all day. Scanning text tells you part of the story. Reading images shows you the rest.

A screenshot captures whatever is on the screen, so almost any record can end up in an image.
Automated image redaction reads the image, finds the sensitive data, and covers only that data.
The method matters as much as the detection:
For scanned documents, see how to redact a PDF. For developers, the Strac Redaction API adds the same detection to your own apps.

A customer sends a photo of a card. Strac redacts the number before it sits in the conversation.
Sensitive images rarely arrive in apps you built. Strac connects to the apps your team already uses and checks images as they arrive, plus many already stored there.

Strac applies the same detectors to images, documents, and messages, so a card number gets the same treatment wherever it appears.
See DLP remediation for how each action works. All integrations connect in under 10 minutes.
Alt: A driver's license image with the license number, date of birth, and address covered by solid bars.
OCR is the difference between an image that looks clean and an image that is clean.
👉 Related reading:
A screenshot can carry the same card number as a database, and a text filter will never see it. Blurring hides data from a quick glance; redaction removes it from the image. Every other control fails eventually, so the data layer is the backstop: redact sensitive data the moment an image lands, and a leaked file holds nothing worth stealing.
Book a demo to see Strac redact images across your stack.

No. Blurring and pixelation keep traces of the original, and those traces can sometimes be recovered. Redaction replaces the sensitive pixels with a solid mark saved into the file, so nothing remains underneath in that copy.
Many DLP tools inspect text, and a screenshot holds pixels. Without OCR, a card number in a photo looks like any other image. Strac reads the text inside images and applies the same detectors it uses on messages and files.
No. Strac covers only the sensitive values, so agents still see the rest of the image. In Zendesk, you can also delay redaction until a ticket is closed, so agents finish the work first.
Not everything. Handwriting, very low-quality photos, and data types you never defined can slip past any OCR tool. Keep human review for legal disclosures, and redact at every entry point so what does get caught never spreads.
Yes. Browser DLP checks uploads and redacts or blocks sensitive data, and MCP DLP protects files that agents pull from connected apps. See AI data governance for the full picture.
.avif)
.avif)
.avif)
.avif)
.avif)

.gif)

