Third-Party Witness Statement Redaction under FRCP Rule 26: protect non-party identifiers – CCPA/HIPAA-compliant de-identification per FRCP Rule 26

Third-party witness statements collected during federal civil discovery under FRCP Rule 26 often contain personal data about bystanders, co-workers, and family members who are not parties; anonym.legal pseudonymizes those incidental identifiers before statements are shared with retained experts, co-counsel, or the client, minimizing unnecessary personal-data exposure at the analysis stage.

When this applies

Applies when litigation counsel has collected witness statements or interview memoranda during discovery and needs to circulate them internally or with experts without transmitting more personal data than is necessary for the litigation purpose.

  1. Upload witness statements or interview memoranda in PDF or DOCX format.
  2. Identify any witnesses whose names must remain in full for expert or counsel analysis — add them to the allow-list.
  3. anonym.legal pseudonymizes all other personal identifiers — bystander names, contact details, and incidental third-party references — throughout each statement.
  4. Factual narrative, event descriptions, and quoted testimony are preserved without alteration.
  5. A reversible mapping is stored in encrypted form for re-identification when the statement is used as a deposition exhibit or trial exhibit.
  6. Share the pseudonymized statements with experts or co-counsel; restore full names when using the statements in depositions or trial.

What you provide

  • Witness statements or interview memoranda (PDF or DOCX)
  • Allow-list of witnesses whose names must remain in full for the recipient's analytical purposes

Limitations & cautions

  • Work-product protection for interview memoranda is a legal question for counsel — pseudonymization does not create or expand work-product protection.
  • If witness statements will later be used as deposition exhibits, ensure re-identification before the deposition so the deponent can verify their own statement.
  • Witness contact information (addresses, phone numbers) that must be disclosed under Rule 26(a)(1)(A)(i) must appear in clear in the formal initial disclosure — not in the pseudonymized version.

FAQ

Are witness statements subject to automatic disclosure under Rule 26(a)?

Rule 26(a)(1)(A)(i) requires disclosure of the names and contact information of individuals likely to have discoverable information — but not necessarily their statements. Actual statements may be protected as attorney work product unless ordered produced.

Can I pseudonymize a recorded witness interview transcript?

Yes — upload the transcript in DOCX or PDF format. Audio or video files require transcription before upload; anonym.legal does not process audio or video directly.

What if a witness statement contains sensitive health information?

Health information about non-parties is treated as a personal identifier and pseudonymized. Ensure your data-sharing basis is appropriate before sharing even a pseudonymized version with third parties.

Civil Litigation

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.

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.