Skills Inventory De-Identification with anonym.plus

Strip the names from a skills database before it feeds workforce planning.

In simple terms, PII redaction is the on-device process of finding and masking personally identifiable information in a document before it is shared.

Skills inventory de-identification is the removal of identifiers from a workforce skills database so no one is named. A standing database is a processing activity you must record under UK GDPR Article 30, hold to the minimum under Article 5(1)(c), and delete on time under Article 5(1)(e). anonym.plus marks each name on your device, so the skill coverage stays clear while staff stay private.

When this applies

A planner models capacity from a skills database that has quietly grown for six years. You strip the names first, so the model runs on coverage rather than on a live staff directory.

How anonym.plus handles it

  1. Open the database extract in anonym.plus on your device.
  2. Built-in OCR reads a scanned skills matrix.
  3. The app marks names and contact fields.
  4. Confirm the markings and keep the skill tags.
  5. Swap each name for a steady code.
  6. Save the cleaned extract locally.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONHugo Bryant → EMP_22
ContactEMAIL_ADDRESSh.bryant@example.co.uk → [EMAIL]
ContactPHONE_NUMBER+44 20 7946 0918 → [PHONE]
OrgORGANIZATIONCloud Guild → [TEAM]
LocationLOCATIONBirmingham hub → [SITE]
DemographicNRPcontractor pool → [GROUP]

Compliance achieved

Anonymise skills inventories offline — see plans & start free →

Limitations & cautions

A rare skill held by one person breaks anonymity. The unique tag points back to that staffer even with no name. Bucket or suppress one-of-a-kind skills before sharing.

Frequently asked questions

Can a unique skill tag identify a person?

Yes. If one staffer holds a rare skill, the tag traces to them, which Recital 26 treats as non-anonymous. Bucket rare tags.

How long can we keep a skills database?

Only as long as you need it for the stated purpose. Article 5(1)(e) is the storage limitation principle, and Article 30 expects you to have written down what the database is for in the first place.

Does it keep the skill tags?

Yes. Only names and contacts are coded, so the coverage data stays intact for planning.

Is the extract uploaded?

No. The app is fully offline, so it stays on your device.