Anonymize equal-pay audit data for compensation-equity analysis – CCPA/HIPAA-compliant de-identification per Title VII §2000e-2

Pay-equity audits conducted to identify potential violations of Title VII §2000e-2 require linking individual employee compensation figures to protected-class characteristics. anonym.legal pseudonymizes employee identifiers in compensation datasets so external equity analysts and outside counsel can perform regression modeling and pay-disparity analysis without unnecessary access to individually identified salary records.

When this applies

Apply this workflow before sharing compensation datasets with pay-equity consultants, econometricians conducting regression analysis, or outside counsel evaluating equal-pay exposure under Title VII.

  1. Upload compensation data exports from your HR or payroll system to anonym.legal.
  2. The engine identifies and pseudonymizes employee names, employee IDs, and manager identifiers in the dataset.
  3. Protected-class fields — gender, race, ethnicity — are retained in their original coded form for regression analysis.
  4. Compensation fields — base pay, bonus, total remuneration — and job-level fields are retained for equity modeling.
  5. The pseudonymized dataset is exported in the original format for consultant or counsel use.
  6. A reversible mapping key is stored for re-identification of individuals identified as potential pay-disparity outliers requiring remediation.

What you provide

  • Compensation data exports from HR or payroll systems in CSV or XLSX format
  • Job-level and job-family classification structure
  • Protected-class field definitions and coding scheme

Limitations & cautions

  • anonym.legal does not perform pay-equity regression analysis; statistical modeling must be conducted by a qualified compensation analyst or economist.
  • Retaining protected-class fields alongside compensation figures carries inherent re-identification risk that pseudonymization of names alone cannot fully eliminate in small demographic cells.
  • The Equal Pay Act (29 USC §206(d)) and state equal-pay statutes may impose overlapping but distinct obligations; this workflow is framed around Title VII §2000e-2 and does not constitute EPA-specific guidance.
  • Pay-equity analysis results may be attorney-client privileged or attorney-work-product; privilege designation must be managed separately from this pseudonymization workflow.

FAQ

Can this workflow accommodate multiple job-family structures across different business units?

Yes. The pseudonymization applies to all rows in the dataset regardless of job family or business unit. Job-family and business-unit codes are treated as structural fields and are retained for cross-unit equity analysis.

Will the pseudonymization affect the statistical validity of a pay-equity regression model?

No. Removing names and employee IDs does not affect the numeric compensation values or the protected-class and job-level variables that drive regression results. The pseudonymized dataset is statistically equivalent to the original for modeling purposes.

Is this workflow suitable for preparing data for an OFCCP compliance evaluation?

Pseudonymization is an internal preparation tool; actual OFCCP submissions must include identified employee records as required by the agency. Use this workflow for internal pre-submission analysis and attorney review, not for the submission itself.

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.