The most expensive redaction failure is the one that looks finished. A disclosure bundle full of neat black rectangles can still carry every redacted word underneath, and the recipient of a DSAR response has both the time and the motive to check. Before any bundle leaves the building, someone should try to break it. This page is the checklist for that person.
Why Redactions Fail
Almost every failure comes from one root cause: the redaction was drawn on top of the content instead of removing it. A black rectangle layered over live text in a PDF hides pixels, not data; the text layer underneath still contains the words, still copies, and still turns up in search. The same applies to shapes over spreadsheet cells, highlight-in-black formatting in word processors, and image crops that leave the original picture embedded. A second family of failures is subtler: content that was never visible in the first place, spreadsheet hidden rows and columns, tracked changes and comments, document properties and metadata, and the invisible OCR text layer under a scanned page, which can carry the very names the visible page had blacked out. True redaction removes data; anything else is decoration.
The Clean-View Test, Step by Step
Run these against the final export, the exact files you are about to send, not the working copies. Select all and copy: open each document, select everything, paste into a plain text editor, and read what arrives; redacted content appearing in the paste is a failed redaction. Search the file: use the viewer’s search for the redacted names and identifiers themselves; a hit under a black box is a fail. Extract the text layer: for PDFs, save as text or run any text extractor and read the output end to end; this catches OCR-layer leakage that copy and paste can miss. Open the awkward way: view spreadsheets with hidden rows, columns, and sheets unhidden, and documents with revisions and comments displayed. Check the properties: author, title, and comment metadata fields regularly carry names. And do it on a machine that has no access to the originals, because the test is what the recipient can recover, not what you can still see.
Who Should Run It
Not the person who did the redacting. The reviewer who spent three days applying redactions reads the bundle as finished; a colleague spending twenty minutes trying to defeat it reads it as a puzzle. In a small team the roles can simply swap bundles. What matters is that the check is a named step in the DSAR procedure with a named owner, because a verification that is nobody’s job is a verification that stops happening the first busy week.
The Stakes Are Now Statutory
A reversible redaction in a DSAR response is a disclosure of third-party personal data the moment anyone lifts it: an incident to assess and possibly report, on top of the original request. And from 19 June 2026, the affected parties have a formal route to raise it, since every controller must operate the section 164A complaints procedure and investigate on the record. The five-minute clean-view test is the cheapest control in the entire DSAR process relative to what it prevents.
How SafeRedact Approaches It
SafeRedact’s core redaction converts documents to images and burns redactions into the pixels, so the original text under a redaction is destroyed rather than covered and cannot be recovered by selection, search, or text extraction. On enterprise DSAR cases, every detection is human-reviewed before export and the output includes a processing summary and audit trail, which turns the verification step from an act of faith into a read of the record: what was detected, what was decided, and what was removed.
Files never leave your browser: documents are processed client-side, only extracted text is sent for AI detection, and no documents are stored on servers. Detection text is never used for training and is deleted within 30 days. A Data Processing Agreement is available, and enterprise cases are priced per case, with the price set with you and shown before you download. See the enterprise overview or the enterprise FAQ for how cases run end to end.
Send Bundles That Survive the Copy-Paste Test
Redactions burned into pixels, human review of every detection, and an audit trail of what was removed. Files never leave your browser.
Start Your EvaluationRelated Guides
Microsoft, Microsoft 365, Outlook, SharePoint, Exchange Online, OneDrive, Teams, and Purview are trademarks of Microsoft Corporation. SafeRedact is not affiliated with or endorsed by Microsoft. This page is informational, not legal advice.