Calendar Icon White
November 17, 2026
Clock Icon
5
 min read

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: Discover and Redact Sensitive PCI ,PII & PHI Data in Images
ChatGPT
Perplexity
Grok
Google AI
Claude
Summarize and analyze this article with:

TL;DR

  • Image redaction removes sensitive data from screenshots, photos, and scans and leaves the rest of the image usable.
  • A single screenshot can expose a card number, a patient record, or an API key, and it can spread across tickets, chat, and AI tools in minutes.
  • Text-only filters miss this data because an image holds pixels, not characters.
  • Strac uses OCR to read images and redacts sensitive data across SaaS, cloud storage, Browser DLP, endpoint DLP, and MCP DLP.
  • This post covers images. For every file type and app, start with data redaction software.

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.

Why Images Slip Past Traditional DLP

Images are a blind spot for three reasons:

  • They hold pixels. A rule that searches text for a card number finds nothing in a screenshot of that number.
  • They travel fast. One screenshot can move from a Slack thread to a Jira ticket to ChatGPT in a few clicks.
  • They pile up. Old scans stay in Google Drive and SharePoint long after anyone remembers them.

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.

✨ What Sensitive Data Shows Up in Images?

__wf_reserved_inherit

A screenshot captures whatever is on the screen, so almost any record can end up in an image.

  • PII: names, home addresses, Social Security numbers, and passport or driver's license numbers. See the PII compliance checklist.
  • PCI data: card numbers and bank details in photos and payment screens. See redacting sensitive data for PCI compliance.
  • PHI: medical records, insurance cards, and treatment details. See the HIPAA data elements guide.
  • Secrets: passwords, API keys, and tokens in screenshots of terminals and admin panels.
  • Confidential business data: contracts, internal reports, and customer lists.

How Image Redaction Works

Automated image redaction reads the image, finds the sensitive data, and covers only that data.

  1. Read. OCR, or optical character recognition, turns the text in an image into machine-readable text and records where each word sits.
  2. Detect. Pattern matching, context, and machine learning models flag card numbers, ID numbers, and health details.
  3. Redact. A solid mark covers each match and is saved into a new copy of the image.
  4. Log. The finding and the action are recorded for audits.

The method matters as much as the detection:

  • Solid marks saved into the pixels leave nothing underneath in that copy.
  • Blurring and pixelation keep traces of the original, which can make them weak against recovery.
  • Editable layers can be removed by the next person who opens the file.
  • Metadata survives pixel edits, so remove location and device details separately.

For scanned documents, see how to redact a PDF. For developers, the Strac Redaction API adds the same detection to your own apps.

✨ Automatic Image Redaction Where Images Land

__wf_reserved_inherit

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: One Policy for Every Image

__wf_reserved_inherit

Strac applies the same detectors to images, documents, and messages, so a card number gets the same treatment wherever it appears.

  • Find it. The PII scanner and data discovery and classification read JPEG, PNG, screenshots, PDFs, Word files, and Excel files.
  • Set the rules. Use built-in detectors from the Strac catalog of sensitive data elements, or add your own.
  • Act on it. Choose what happens when Strac finds sensitive data:
    • Redact / mask. Removes part of an image or all of it in Slack, email, tickets, docs, Google Drive, SharePoint, and Box.
    • Block. Stops an image from reaching an AI tool, a personal upload site, or an agent.
    • Warn and coach. Tells the person what was found and where the file should go.
    • Revoke access. Removes public links and outside sharing from files that hold sensitive data.
  • Prove it. Findings and actions are logged as evidence for HIPAA, PCI DSS, SOC 2, and ISO 27001 audits.

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:

✨ The Bottom Line

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.

__wf_reserved_inherit

🌶️ Spicy FAQs on Image Redaction

Is image redaction the same as blurring an image?

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.

Why doesn't my existing DLP catch sensitive data in screenshots?

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.

Will image redaction slow down my support team?

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.

Can automated redaction catch everything in an image?

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.

Can I redact images before they reach ChatGPT or Claude?

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.

Customer story

“Don’t just alert on problems, fix them.”

Scott Roberts, Chief Information Security Officer, UiPath

  • UiPath
  • Crypto.com
  • Inmar Intelligence
  • thredUP
  • Paymentology
  • Enveda
  • Genesis Molecular AI
  • MeridianLink
More customer stories →
Discover & Protect Data on SaaS, AI, MCP, Endpoints & Cloud
Strac provides end-to-end data loss prevention for all SaaS and Cloud apps. Integrate in under 10 minutes and experience the benefits of live DLP scanning, live redaction, and a fortified SaaS environment.

Customers include

  • UiPath
  • Crypto.com
  • Inmar Intelligence
  • thredUP
  • Paymentology
  • Enveda
  • Genesis Molecular AI
  • MeridianLink
Trusted by enterprises
Data Security + Compliance Automation

Latest articles

Browse all

Get Your Datasheet

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Close Icon