Skip to content

One person, however they appear.

Link names, aliases, email addresses and identifiers across every document into single person records, with evidence for each link.

Try RedacticsTalk to us

The problem

One person appears as Dan, Daniel, D. Okafor, an email address and an employee number. Two different people share a surname. Document-level detection can tell you a name appears on page 12. It cannot tell you who the finding is about, which is the question that decides whether it is disclosed.

How Redactics handles it

Redactics links every mention across the whole case into person records. Confident links are made automatically with the evidence attached. Ambiguous matches are queued for a person to decide, with the conflicting evidence on screen. Merges and splits are recorded, so the person model can be explained and, if necessary, unpicked.

  • Aliases, initials, email addresses, phone numbers, employee and case identifiers
  • Role and relationship inference: line manager, clinician, family member, supplier
  • Ambiguous matches queued with the evidence for and against
  • Merge and split with full history

SAR-2026-0417/People

All people (23)Needs judgement (1)

  • Daniel Okafor

    Requester. Data subject

    98%

    Dan Okafor, D. Okafor, d.okafor@northgate-ht.example, Employee NG-40217

  • Priya Shah

    Line manager. Third party

    96%

    P. Shah, priya.shah@northgate-ht.example

  • Marcus Bell

    HR business partner. Third party

    95%

    M. Bell, marcus.bell@northgate-ht.example

  • Dr Helen Frost

    Occupational health adviser. Third party

    91%

    H. Frost, Dr Frost, OH adviser

  • D. Okafor (invoices, 2021)

    Possible second individual. Ambiguous

    54%

    D Okafor Deliveries, 07700 900 123

    Needs judgement: Appears only in supplier invoices. Different address and phone number from the requester.

  • Aisha Okafor

    Emergency contact. Third party

    89%

    A. Okafor

1,102 mentions resolved to 23 people. 1 ambiguous match queued.

Person resolution in the guided sample case. All data is synthetic.

For your team

Review by person, not by document
See everything held about the requester in one place, and everything about each third party in theirs.

For your risk

Identity decisions are explicit and recorded
When a reviewer confirms that two mentions are the same person, the decision and its basis are part of the case record.

For your security review

Case-scoped by design
Person records exist only within a case. Nothing is linked across cases or customers.
Security and trust

Works with

All capabilities

Make SARs manageable.

Try Redactics yourself or talk to us about your current process.

Try RedacticsTalk to us