Anonymize workforce reduction plans for ADEA disparate-impact analysis – CCPA/HIPAA-compliant de-identification per ADEA §623

Workforce reduction plans identifying employees selected for layoff carry ADEA §623 age-discrimination exposure when selection criteria correlate with age. anonym.legal pseudonymizes individual employee identifiers in reduction-in-force datasets so labor economists and outside counsel can perform ADEA disparate-impact analysis without the review team accessing unselected employees' personal data.

When this applies

Apply this workflow when RIF selection datasets must be shared with labor economists for ADEA statistical analysis, reviewed by outside litigation counsel, or provided to HR leadership for selection-criteria consistency review.

  1. Upload the RIF selection matrix, employee-population data, and selection-criteria scoring files to anonym.legal.
  2. The engine identifies employee names, employee IDs, manager names, and any direct demographic identifiers in the dataset.
  3. Each employee is pseudonymized consistently across the selection matrix and the underlying population dataset.
  4. Age, years of service, job title, performance rating, and selection-decision fields are retained as structural content for ADEA impact analysis.
  5. The pseudonymized dataset is exported for economist modeling or counsel review.
  6. A reversible mapping key is stored for re-identification of specific employees if individual notice or severance determinations are required.

What you provide

  • RIF selection matrix in CSV or XLSX format
  • Employee-population dataset with age, tenure, and job-classification fields
  • Selection-criteria scoring rubrics and decision documentation

Limitations & cautions

  • anonym.legal does not perform ADEA disparate-impact statistical analysis; that assessment must be conducted by a qualified labor economist or employment statistician.
  • The WARN Act (29 USC §2101) imposes advance-notice obligations for large RIFs; compliance with WARN Act requirements is a separate obligation not addressed by this workflow.
  • Small RIF populations with limited age-distribution variation may carry statistical re-identification risk even after name pseudonymization.
  • State mini-WARN statutes may impose different or broader notice obligations than federal law; this workflow covers federal ADEA requirements only.

FAQ

Can the tool process both the selected and non-selected employee populations together?

Yes. Processing the full affected-population dataset with consistent pseudonyms allows labor economists to compute adverse-impact ratios across age cohorts in the selected vs. retained groups without the analyst seeing individual employee names.

Will age and years-of-service fields be retained after pseudonymization?

Yes. Age and years-of-service are retained as structural content for ADEA analysis. Only direct identifiers — names, employee IDs, and SSNs — are pseudonymized.

Is this workflow appropriate for preparing the ADEA decisional unit analysis?

Yes. Pseudonymizing the RIF dataset by job classification or organizational unit allows counsel to define and analyze the appropriate ADEA decisional unit without the legal team accessing personal data for employees outside the unit under review.

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.