Employee Census De-Identification with anonym.plus

Clear staff identities, including sensitive fields, from the census data set.

Census de-identification is the removal of staff PII from a workforce data set. Health, union, and other special-category fields fall under GDPR Art. 9. Once the output is truly anonymous (Recital 26), it leaves scope. anonym.plus runs locally.

When this applies

A workforce census lists each employee with pay, role, and sometimes health or union data. A buyer needs the headcount math, not the people.

How anonym.plus handles it

  1. Point anonym.plus at the census file on your device.
  2. It scans ID columns and any free-text note fields.
  3. Special-category fields under Art. 9 get extra care.
  4. Swap staff for steady labels to keep joined rows.
  5. Save the clean data set on your device.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONemployee_name → [STAFF_n]
IdentifiersNATIONAL_IDsocial no. → [ID]
HealthMEDICAL_LICENSEleave reason → [SENSITIVE]
ContactEMAIL_ADDRESSwork email → [EMAIL]
DatesDATE_TIMEhire date → [DATE]
LocationLOCATIONhome address → [ADDRESS]

Compliance achieved

Anonymize employee census files offline — see plans & start free →

Limitations & cautions

Art. 9 fields like health or union status carry the highest risk. A rare role plus a small team can re-identify even after IDs go. Weigh the residual risk and keep no re-link key for true anonymity.

Frequently asked questions

Why is census data special under GDPR?

It can hold health, union, or other Art. 9 data, which needs strong safeguards. Making it anonymous drops that burden for headcount and cost work.

Can rows stay linkable after the swap?

Yes. A steady label map keeps each employee's rows joined while no real identity is left.

Does it handle both columns and free text?

Yes. Tidy ID columns and inline note fields are both checked on your device.