Anonymize workplace harassment complaints for investigation and legal review – CCPA/HIPAA-compliant de-identification per Title VII §2000e-3

Workplace harassment complaints under Title VII §2000e-3 identify both complainants and alleged harassers by name, creating dual privacy exposure that can chill future reporting and complicate legal strategy. anonym.legal pseudonymizes all party identifiers so complaints can be assessed by outside counsel, reviewed for investigative consistency, or used as training material without revealing individual identities.

When this applies

Apply this workflow before sharing harassment complaints with external investigators, employment attorneys conducting privileged reviews, or HR training teams developing case-study materials from historical complaints.

  1. Upload harassment complaint documents, intake forms, or complaint-management system exports to anonym.legal.
  2. The engine identifies and separately pseudonymizes the complainant, respondent, and any named witnesses.
  3. Role labels (e.g., 'Complainant A,' 'Respondent B,' 'Witness 1') are applied consistently across all related documents so the complaint narrative remains coherent.
  4. Dates, incident locations, and procedural milestones (complaint date, investigation-open date, outcome date) are retained as structural content.
  5. Attached evidence references — email headers, document titles — are pseudonymized to prevent indirect identification from metadata.
  6. The reversible mapping is stored encrypted and accessible to authorized HR or legal personnel.
  7. The pseudonymized complaint set is exported for attorney review or investigative-consistency audit.

What you provide

  • Harassment complaint forms and intake documentation in PDF or DOCX format
  • Related witness statements and investigation correspondence
  • Complaint-management system exports (CSV or XLSX) for batch pattern analysis

Limitations & cautions

  • anonym.legal does not determine whether the described conduct constitutes harassment under Title VII or any related statute; that legal assessment requires attorney review.
  • The tool pseudonymizes identifiers but does not redact incident descriptions; a uniquely distinctive event in a small team may still be recognizable to those familiar with the circumstances.
  • EEOC charge filing procedures under 29 CFR §1601 remain the complainant's right regardless of any pseudonymization performed for internal review.
  • State anti-harassment laws may impose additional investigation and documentation requirements not addressed by this federal workflow.

FAQ

Does pseudonymizing a complaint affect the complainant's right to file an EEOC charge?

No. Pseudonymization is performed on copies used for internal review purposes only. The complainant's original complaint and their right to file an EEOC charge under 29 CFR §1601 are entirely unaffected.

Can the tool maintain consistent pseudonyms if the same individual appears in multiple complaint files?

Yes. When batch processing related complaint files, you can configure the engine to apply the same pseudonym to a given individual across all documents in the batch, preserving cross-complaint linkages for systemic analysis.

Is attorney-client privilege preserved when sharing pseudonymized complaints with outside counsel?

Pseudonymization does not affect privilege; it reduces the privacy risk of inadvertent disclosure but the underlying privilege analysis depends on the circumstances of the communication. Consult your attorney on privilege designation before sharing.

Employment Law

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.