Anonymize retaliation complaints for legal analysis and HR investigation – CCPA/HIPAA-compliant de-identification per Title VII §2000e-3

Retaliation complaints under Title VII §2000e-3 identify employees who engaged in protected activity — filing EEOC charges, participating in investigations, or opposing discriminatory practices — creating heightened privacy risk because disclosure of complainant identity can itself constitute further retaliation. anonym.legal pseudonymizes party identifiers so retaliation complaints can be evaluated by outside counsel and HR leadership without amplifying that risk.

When this applies

Apply this workflow before sharing retaliation complaints with outside employment counsel for legal assessment, reviewing patterns in retaliation reports across the organization, or using historical retaliation cases as training material for HR investigators.

  1. Upload retaliation complaint forms, related EEOC charge copies, and investigation correspondence to anonym.legal.
  2. The engine identifies and separately pseudonymizes the complainant, the accused retaliator, any named witnesses, and the HR or legal personnel who handled the prior protected activity.
  3. Consistent pseudonyms are applied across the complaint, any related EEOC charge documentation, and the retaliation investigation file.
  4. Protected-activity descriptions, adverse-action details, and temporal proximity data are retained as structural content for legal causation analysis.
  5. The pseudonymized file set is exported for outside counsel review or HR leadership assessment.
  6. A reversible mapping key is stored encrypted with restricted access for authorized personnel only.

What you provide

  • Retaliation complaint forms and related EEOC charge copies in PDF or DOCX format
  • Prior protected-activity records (original harassment complaint, EEOC charge, or opposition-activity documentation)
  • Adverse-action documentation (termination notice, demotion letter, schedule change records)

Limitations & cautions

  • anonym.legal does not assess whether the described conduct constitutes retaliation under Title VII §2000e-3 or any other anti-retaliation statute; that legal determination requires attorney review.
  • The engine pseudonymizes identifiers but does not redact incident narratives; circumstances described in sufficient detail may allow identification by individuals familiar with the workplace.
  • EEOC charge filings and related agency proceedings are public records subject to agency confidentiality rules that operate independently of this pseudonymization workflow.
  • Anti-retaliation provisions in other federal statutes (e.g., FLSA, FMLA, NLRA) are related but distinct; this workflow is framed around Title VII §2000e-3.

FAQ

Can the tool maintain the link between the original harassment complaint and the retaliation complaint for causation analysis?

Yes. When the original protected-activity file and the retaliation complaint are processed in the same batch, the engine applies the same complainant pseudonym across both documents, preserving the causal link while protecting the individual's identity.

Will adverse-action documentation retain its dates and decision-maker references after pseudonymization?

Dates are retained as structural content. Decision-maker names (supervisors, HR officers) are pseudonymized with consistent pseudonyms, so the temporal and organizational relationship between the protected activity and the adverse action remains analyzable.

Is this workflow appropriate for preparing a position statement for an EEOC retaliation charge?

Yes for internal preparation. The pseudonymized file set allows your litigation team to assess the strength of a retaliation claim and develop the EEOC position statement without the full team accessing personal data of uninvolved employees. The final position statement submitted to the EEOC must comply with agency requirements, which may require identified information.

Can retaliation complaint data be analyzed across departments to identify systemic patterns?

Yes. Batch pseudonymization of retaliation complaints across departments, with consistent pseudonyms for recurring individuals, allows HR leadership and counsel to identify systemic patterns — such as a department with disproportionate adverse actions following protected activity — without accessing individual employee identities.

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.