Bates-Stamped Production Redaction under FRCP Rule 34: redact before stamping and producing – CCPA/HIPAA-compliant de-identification per FRCP Rule 34

Document productions in federal civil litigation under FRCP Rule 34 are standardly Bates-stamped before delivery to opposing counsel; anonym.legal applies Rule 5.2-compliant and proportionate third-party redactions to the production set before Bates stamps are applied, ensuring the stamped version is the final, redacted record — not a redacted copy of an already-stamped set that would disrupt page numbering.

When this applies

Applies when litigation counsel is preparing a formal document production in response to Rule 34 requests, the production will be Bates-stamped, and the documents contain Rule 5.2-covered identifiers or non-material third-party personal data warranting proportionate redaction.

  1. Upload the production-ready documents (pre-Bates-stamp) in PDF or DOCX format.
  2. Configure allow-list identifiers and select redaction categories: Rule 5.2 mandatory partial redactions and/or optional third-party pseudonymization.
  3. anonym.legal processes the full document set, applying redactions in the order: Rule 5.2 mandatory first, then proportionate third-party pseudonymization.
  4. The processed document set is returned ready for Bates stamping — apply stamps in your document-management or litigation-support platform.
  5. A redaction log mapping each document to identified and applied redactions is generated for the privilege and redaction log.
  6. Produce the Bates-stamped, redacted set with a cover letter or transmittal letter noting the redaction basis.

What you provide

  • Production-ready documents prior to Bates stamping (PDF or DOCX)
  • Allow-list of material identifiers to retain in full
  • Redaction scope configuration (Rule 5.2 only vs. full third-party pseudonymization)

Limitations & cautions

  • Bates stamping itself is performed in your document-management platform after anonym.legal processing — the tool does not apply Bates stamps.
  • The sequence matters: if Bates stamps are applied before redaction, page images may shift and invalidate the stamp-to-page correspondence. Always redact first.
  • The producing party bears responsibility for confirming that the redaction approach is consistent with any ESI protocol, protective order, or court order governing the production.

FAQ

What is the standard practice for indicating redactions in a Bates-stamped production?

Best practice is to apply a visible redaction placeholder (e.g., '[REDACTED — Rule 5.2]' or '[REDACTED — Non-Responsive Personal Data]') rather than a blank space, so opposing counsel can see that a redaction was applied and the asserted basis.

Can opposing counsel challenge a redaction in a Bates-stamped production?

Yes — opposing counsel may challenge any redaction as improper. Maintain a redaction log that documents each redaction, the basis (Rule 5.2, privilege, non-responsiveness), and the Bates number. Courts may conduct an in camera review of challenged redactions.

Does the redaction log need to be produced to opposing counsel?

Parties commonly agree to exchange redaction logs along with the production. Whether the log must be produced depends on the ESI protocol and any court order. Check your case management order and meet-and-confer agreements.

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.