Anonymize legal-proceedings disclosures for disclosure-committee review – CCPA/HIPAA-compliant de-identification per 17 CFR §229.103

Reg S-K §229.103 requires registrants to describe material pending legal proceedings, naming parties, courts, and claimed damages in annual and quarterly reports. These disclosures identify litigation counterparties, government agencies, and individual plaintiffs. anonym.legal pseudonymizes those identifiers so legal and disclosure teams can review materiality and draft language without distributing named litigation details to non-essential personnel.

When this applies

Apply this workflow when draft Item 3 legal-proceedings sections or litigation summary schedules are circulated to disclosure committees, outside counsel, or D&O insurers for review where the named counterparty identities are not required by the reviewer.

  1. Upload draft §229.103 disclosure sections or internal litigation summary schedules in PDF or DOCX format.
  2. The engine identifies named plaintiffs, defendants, government agencies, and individual counterparties in each case description.
  3. Each named party is pseudonymized while the case description — court, jurisdiction, nature of claims, claimed damages, and current status — is retained as structural content.
  4. Case identifiers (docket numbers, case names as filed) are optionally pseudonymized if the disclosure committee requires full name suppression.
  5. Multiple proceedings in the schedule are processed in a single batch with consistent pseudonym assignments across all cases.
  6. The reversible mapping is stored encrypted for re-identification when finalized disclosure language is needed.
  7. The pseudonymized litigation schedule is exported for committee and insurer review.

What you provide

  • Draft §229.103 disclosure text or internal litigation summary schedules in PDF or DOCX format
  • Scope instruction identifying whether government-agency names should also be pseudonymized
  • Any prior-period disclosure text for cross-period consistency of pseudonym assignments

Limitations & cautions

  • anonym.legal does not assess whether a legal proceeding meets the materiality threshold for §229.103 disclosure; that determination requires securities counsel.
  • Court docket names and case-caption information may be publicly available and thus not fully protected by pseudonymization of the internal summary.
  • Government enforcement proceedings where the agency name is material to the disclosure may not be suitable for full pseudonymization.
  • The tool does not assess litigation privilege or work-product protection for any uploaded document.

FAQ

Yes. Both private-plaintiff case descriptions and government-enforcement summaries are processed in the same batch. You can configure whether government agency names are pseudonymized or retained based on your disclosure committee's needs.

Yes. Claimed damages, settlement ranges, and reserve estimates are structural financial content and are preserved in plain text; only named counterparties are pseudonymized.

Yes. D&O insurers reviewing litigation exposure typically require case summaries with nature of claims and damages data. Pseudonymizing plaintiff names while retaining claims descriptions allows renewal submissions to be prepared without disclosing counterparty identities to the insurer's underwriters.

Securities & Corporate Disclosure

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.