Redacting personal data before a document leaves the organisation

Before a case file, a support transcript or a claims bundle goes to a vendor, an opposing party or a training set, a detector marks names, phone numbers, account numbers and identifiers and an operator masks or substitutes them, with a named reviewer sampling the output before anything is released.

Effort
Weeks of work
Skill level
Some technical skill
Organisation size
Mid-market
Value
Risk reduced

Tools named for this

  • An open-source analyser with recognisers configured for your own identifier formats
  • A masking or surrogate-substitution step that leaves the document still usable
  • A sampling review with one named person accountable for each release

What to check before you ship it in India

  • Redaction is the control that makes onward sharing survivable, and section 8(5) puts the duty of reasonable security safeguards against a personal data breach on the fiduciary. A single missed identifier in a bundle that has already been sent is that breach, and no later fix retrieves it.
  • Direct identifiers are the easy half. Anonymisation research marks the spans that must be masked to conceal identity rather than only the standard entity categories, because a residual detail can still point at one person.

Sources

Every claim on this page traces to one of these, on the date it was read.