By · Last updated 2026-02-23

Back to BlogLegal Tech

Courts Sanction Attorneys for Redaction

Highlighting text in Word isn't redaction. Courts are sanctioning attorneys for technical failures that expose privileged information.

February 23, 20266 minute read
legal redactione-discoverycourt sanctionsdocument security

The Highlight-to-PDF Trap

Every week, attorneys make the same mistake. They highlight text in black, convert to PDF, and call it done. That content is not hidden. Anyone can select it, copy it, and read it in seconds. It happens routinely. The error has real consequences.

Courts have noticed. Federal judges are not amused.

What Highlighting Actually Does

Highlighting places a colored layer over words. It does not remove anything beneath. The original data stays inside the file. It is searchable, copyable, and accessible to anyone.

Real document scrubbing is different. It removes the underlying data from the file entirely. The visual bar and the data removal are two distinct steps. Most attorneys only do the first one.

Courts Catching the Error

The "Technical Weakness" Warning

A magistrate judge recently demanded that counsel explain. The filing had a "technical weakness" in the redaction process. The attorney had used Word's highlight tool. Opposing counsel selected the covered passage and copied it out.

The Metadata Leak

An attorney produced files where names and dates appeared blacked out. Those same details were readable in the document properties. Metadata had not been stripped. Nothing had been removed from the file.

The Mass Recall

A paralegal found that covered passages could be copied from under black highlighting. The firm had already sent thousands of files in that format. Every document had to be recalled and re-produced. The cost and embarrassment were significant.

Federal Court Guidance

The federal judiciary is direct:

"Merely drawing black lines through text does not securely redact. The underlying text may still be searched, copied, or accessed."

The official guidance has four requirements. Use tools that remove data, not tools that cover it. Flatten PDF files after processing. Verify the output before filing. Strip metadata from every document.

What Proper Scrubbing Requires

These are the technical requirements.

Data deletion. The words must be removed from the file. A colored box over the words is not enough.

Metadata stripping. Document properties can expose the original content. Author name, timestamps, and revision history must all be cleaned.

Layer flattening. This prevents someone from lifting the black box off the passage.

Audit trail. Records what was removed and when. Essential for the privilege log. Courts may ask for this record.

The process has five steps. Review all content that must be removed. Use a tool that deletes the data. Verify the passage is gone from the saved file. Document what was removed and why. Then export the clean copy. Do not overwrite the original.

The Discovery Dilemma

E-discovery adds a complication. You must produce documents. But courts can later order original, un-covered production. Permanent removal creates a real bind.

A judge may order the original version produced. A client may need access to the source document. An auditor may request complete records. An appeal may require the original evidence.

Reversible encryption solves this. Instead of deleting a passage, you replace it with a token. The key stays with your firm. The file goes out clean. If a court orders disclosure, you decrypt with the key and produce the original.

How it works: Reversible Encryption for Legal Discovery.

Related reading: Word Add-in Redaction Costs at Law Firms.

Next Steps for Law Firms

The "technical weakness" excuse no longer works. Courts are more aware of these failures than before. Sanctions are more common now. The standard for attorneys is clear.

Three immediate actions:

  • Stop highlighting for any filing or production.
  • Add a copy-paste check. Paste the output into a plain text editor. Confirm the passage is absent.
  • Strip metadata before every production run.

anonym.legal's Office Add-in handles all three inside Microsoft Word. It removes data, flattens the output, and strips metadata. A full audit trail supports the privilege log.

Full use case: Legal Use Cases.

Sources

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.