Anonymize reasonable accommodation logs for ADA compliance auditing – CCPA/HIPAA-compliant de-identification per ADA §12112

Employer reasonable-accommodation logs maintained under ADA Title I §12112 consolidate disability-related requests, interactive-process timelines, and outcome decisions across the workforce in a single dataset. anonym.legal pseudonymizes employee and provider identifiers in accommodation logs so HR compliance teams and outside counsel can audit ADA process consistency without accessing individual disability disclosures.

When this applies

Apply this workflow before sharing accommodation log datasets with employment attorneys conducting ADA self-audits, HR analytics teams reviewing interactive-process timelines, or disability-management vendors benchmarking accommodation-decision patterns.

  1. Upload the accommodation log spreadsheet or HR-system accommodation module export to anonym.legal.
  2. The engine identifies employee name, employee ID, requesting manager name, and treating provider columns.
  3. Each employee and provider is assigned a consistent pseudonymous identifier across all log entries.
  4. Accommodation type, functional limitation category, decision outcome, and processing timeline fields are retained for compliance analysis.
  5. The pseudonymized log is exported in the original spreadsheet format for ADA audit or analytics use.
  6. A reversible mapping key is stored for re-identification if individual case follow-up is required.

What you provide

  • Accommodation log in CSV or XLSX format exported from the HR or disability-management system
  • Field mapping identifying employee-identifier columns vs. accommodation-data columns
  • Date range scope for the audit period

Limitations & cautions

  • anonym.legal does not assess whether the accommodation processes documented in the log satisfy ADA §12112 requirements; compliance determination requires attorney review.
  • Accommodation-type categories that are very rare may effectively re-identify an employee even after name pseudonymization in a small workforce.
  • Rehabilitation Act obligations for federal contractors and subcontractors are related but distinct from ADA Title I; this workflow is scoped to ADA private-employer obligations.
  • State disability accommodation statutes may cover smaller employers or provide broader protections than ADA Title I.

FAQ

Can the accommodation log be pseudonymized while retaining processing-time metrics for SLA auditing?

Yes. Request date, interactive-process meeting date, and decision date fields are treated as structural timeline data and are preserved. Processing-time metrics are directly calculable from the pseudonymized log.

Will the disability or medical condition field be retained in the pseudonymized log?

That depends on your configuration. By default, the engine retains functional-limitation categories (e.g., 'mobility impairment') for compliance analysis while pseudonymizing the employee's name. If you need to remove even the functional-limitation category, that field can be masked instead.

Is this workflow suitable for a multi-location employer with accommodation logs from multiple offices?

Yes. Batch processing consolidates accommodation logs from multiple locations into a single pseudonymized dataset, assigning consistent pseudonyms to employees who appear in more than one location's records.

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.