12 min read

People investigations

How Viokit looks a natural person up: the purpose gate in front of it, what each jurisdiction lets anyone see, how the Person tab assembles a dossier, and how a dataset you hold plugs into the same profile. Legal wording here is a summary as of 2026-11-14, not advice: you are the controller.

The purpose gate

Looking up a named individual is processing their personal data. Before any transform that looks a person up runs, the case records why and on what lawful basis:

  • Purpose: due diligence; journalism; a legal claim; fraud or financial crime investigation; safeguarding; regulatory; academic research; other (in your words).
  • Lawful basis (UK GDPR Art. 6(1)): legitimate interests (f), legal obligation (c), public task (e), consent (a), vital interests (d), contract (b).
  • Special-purposes exemption (optional): journalism, academic, artistic or literary work, with a view to publication you reasonably believe is in the public interest (DPA 2018 Sch. 2 Part 5 para 26). It is not a general licence to hold data.
  • Reference (optional): a matter, instruction or ticket number.

The declaration is recorded with who made it and when, and cites itself as evidence. The latest declaration stands; a later one replaces it; a withdrawal closes the gate again. Every declaration and withdrawal is also kept in an audit log.

Every lookup that takes a person is gated, and so is every search of records about individuals by name. Until a purpose stands, the investigation tree skips them with the reason “This case has no recorded purpose for looking up individuals”, shown in the summary and on the seed record like any other skip, and in the console's Not yet checked and History. Running one by hand fails with the same reason.

Company lookups, domain lookups and plate lookups are not gated: they look up a company, a domain or a vehicle, not a person. Officers found on a company record appear in the graph as before; what is gated is looking a person up in their own right (their other appointments, disqualifications, sanctions screening, donations, gazette notices, leaked offshore records).

The case report prints the declaration in its handling note. In the console, the case header carries a chip (“Purpose: Due diligence · legitimate interests”, or “No purpose recorded for looking up people”); seeding a person or opening the Person tab asks once with the Before you look up people… panel.

What is lawful where

The “people” record type in the coverage map lists, per jurisdiction, the automated lookups and the manual sources for person-centred records, with the legal limits in the note. It is distinct from “officers and owners”: that answers who runs or owns a company from the company's side; “people” answers what lawful public records name an individual.

Jurisdiction Public Not public, or restricted
United Kingdom Directors and PSCs with a service address, month and year of birth, nationality, country of residence (Companies House); disqualified directors; the Individual Insolvency Register; The Gazette; FCA approved persons; Electoral Commission donations; MPs' interests; Find Case Law. The open (edited) electoral register, which councils sell. Directors' home addresses since 1 October 2009 (Companies Act 2006 ss.240-246); the full electoral register (RPR 2001 reg. 114); DVLA keeper details (reasonable cause only, through DVLA: Viokit never asks).
United States FEC itemised contributions (not for solicitation or commercial use, 52 U.S.C. 30111(a)(4)); PACER and state court records; county recorders; state voter files in many states, with use restrictions. A report used for credit, employment, insurance or tenancy decisions is a consumer report under the FCRA and needs a permissible purpose.
Russia EGRUL founders and directors with INN (use the OpenSanctions mirror); Fedresurs bankruptcies; FSSP enforcement proceedings. 152-FZ restricts onward processing; Rosreestr owner data is closed.
Netherlands KvK directors on a paid extract; the central insolvency register; pseudonymised judgments. Natural persons' home addresses at KvK since 2022; the UBO register since November 2022.
Ireland CRO directors with a service address; Iris Oifigiúil; ISI; court judgments. The RBO (legitimate interest only since 2023); the electoral register outside electoral purposes.
Offshore set (CY, VG, AE, JE, GG, IM, LU, MT) Officers where the registry publishes them; ICIJ Offshore Leaks officers (leaked, historical, not evidence of wrongdoing). Beneficial-ownership registers, closed to the public since CJEU C-37/20 (22 November 2022); BVI BOSS.

The Person tab

For a person in the case, the Selection panel's Person profile, the palette, or the Panels menu opens the Person tab. It is assembled from the merged graph, the step log and the run records, so it says nothing the case does not:

  • Header: name; month and year of birth (never a day); nationality; countries of residence and placement; how many records the case resolved as this one person.
  • Roles and control: director, secretary, officer, employee, member, trustee, approved person and person with significant control, with the organisation, dates, source and grade chip; current first.
  • Address timeline: every address linked to the person, or used by an organisation they hold a role in, deduplicated on the shared address (the same country and postcode), with the country named, ordered by first and last seen, with source and grade. An address that is a linked company's registered office says so and names the companies. For UK directors it says that home addresses are not public and a service address is shown.
  • Associates: co-officers and co-PSCs at the same companies, people at the same personal address, and stated relationships.
  • Flags: sanctions candidates (name matches, said so), ICIJ Offshore Leaks officer records, disqualified-director records, insolvency and court records, political donations and declared interests.
  • Vehicles: only plates you add with Add a plate you hold, looked up on DVLA and DVSA's public vehicle records. The run is recorded, so the history says which person you added it for. No keeper lookup exists in Viokit, and the tab says so.
  • Not yet checked: lookups that could not run (the purpose gate, a missing key) and, for each of the person's countries, the people sources no run used, with the manual sources to consult.

Wanted-list screening

Viokit screens a seeded person's name against public law-enforcement wanted lists the way the sanctions packs screen against sanctions lists: the FBI Wanted list and the National Crime Agency most-wanted page. It is behind the purpose gate and runs only on a name the analyst seeded, because the name is sent to the agency's site.

  • A hit is a proposal with a score, never an identification: the listed person is a separate entry on the agency's watchlist, and a proposed match links it to the person asked about with the name, score and band (“possible” from 0.80, “probable” from 0.95; the likelihood is “likely” at most on a name alone).
  • Add a date of birth or nationality to the person and a listing that agrees scores higher and one that contradicts it drops out. The NCA page gives no date of birth, so its hits rest on the name.
  • A namesake on a wanted list is a serious false positive. Check the poster against what you know, and corroborate with a date of birth, photograph or place before treating two people as one. A listing is a statement that an agency seeks the person, not a finding of guilt, and the notice summary is the agency's allegation, not a fact.
  • The FBI's list also holds missing persons, kidnapping victims, unidentified cases and people it only seeks information from. Those are never screened against.
  • Interpol and Europol are not covered.

Resolution across sources and jurisdictions

A UK PSC, an ICIJ officer and an OpenCorporates officer are only proposed as one person on evidence beyond a name:

  • the same Wikidata item: almost certain;
  • the same name and the same month and year of birth, from any source: likely, a proposal;
  • the same name and the same shared address (same country and postcode): likely, a proposal;
  • a shared name and nothing else: listed as possibly the same person, never proposed;
  • two different full dates of birth or two Wikidata items: a conflict, never proposed.

Addresses carry their country, so a Dutch flat and a UK office never collide, and an address recorded by one source meets the same address recorded by another. Nationality is shown and compared by the analyst; it is not a merge basis on its own, since sources spell it differently and people hold more than one.

Datasets you supply

An owner-supplied people or contact dataset (a client's KYC file, a licensed list, a journalist's own records) is registered as an offline dataset marked sensitive, with the principals allowed to use it. Looking a person up in it is behind the purpose gate as well as the dataset's own gate; every lookup is audited beside the purpose declarations; its evidence is withheld from exports and agents unless included. What it provides (people with month and year of birth, nationality and addresses) feeds the same Person tab and the same resolution rules as public sources.

Retention, erasure and restriction

UK GDPR expects storage limitation, erasure and restriction where they apply, and accountability for both. Viokit's case history is append-only, so none of these is a rewrite of history: each is a further record, and everything that reads the case honours it.

Retention. The purpose declaration also says how long the case keeps personal data before review: 6 months, 1 year, 2 years, until a date, or indefinitely with a justification. The review date runs from the declaration in force, so recording the purpose again is how a review is recorded. The console puts the review date and days left on the header chip and raises a Review due alert 30 days before and once past it. A list of every case you may open that is past or near review is also available.

Erasure. In the console: Person tab, Data protection → Erase this person…. It erases a person from the open case. Only the case owner may, and a basis (erasure request, no longer necessary, purpose ended, objection, unlawful processing, legal obligation) and a reason are required. The console always shows the plan first: exactly what would go.

  • What is withheld: the person, every record merged with them (an applied or accepted merge), and records known only through them: an address or phone whose every link is to the person and whose every source is one that also spoke about the person. Then every relation and event touching those, every merge proposal or decision about them, and every note on them or on one of those relations.
  • How: an erasure record names the withheld items only as SHA-256 digests (so the record does not say who was erased), with who, when, basis, reason, the count of steps withheld, and the hashes of evidence whose bytes were removed. Everything that reads the case leaves out what the digests cover, so the graph, the map, the timeline, reports, exports, notes, the cross-case index, and later matching never see them. A later lookup that returns the same person stays withheld too: in this case, erasure holds.
  • Evidence: bytes no remaining step in the case, no other case and no fork cites are deleted from the evidence store. Bytes shared with other facts stay, because they are those facts' evidence too, but are redacted, so they never leave in an export.
  • Accountability: the audit log records each erasure without the person's name. A list shows when, by whom, why, how much, never who.

Phone, device, financial and table-import data. A call, message, position, payment or imported row involves several parties, and only one may be erased. So erasure works per party:

  • What goes with a person: the numbers, email addresses, handsets, SIMs, accounts and bank accounts linked to them (any link, either direction) and to no other person or organisation. One that is also linked to someone else is shared: the dry run names it and it stays. Erasing a number, handset or account on its own erases only that thing (its SIM or handset is its own entity: erase it too).
  • A record with a party who stays (a message to someone else, a payment to a counterparty, a table row naming two people) keeps its time, direction, duration, amount and currency, record id and the other party. Everything else on it (message text and length, handset and SIM ids, position, payment reference, description and balance, a row's note) is withheld at read time and replaced by "content withheld (erasure)". An event whose parties are all erased (a position only the erased handset reported) goes entirely.
  • Files: an imported file is shared by many people, so its bytes are never deleted for one. The file stays in the evidence store as the case's exhibit, but is redacted so it never leaves in an export or bundle. The stored erasure record lists, per file, the record ids (message, row or payment numbers) withheld, so a recipient of a redacted copy can see which rows were taken out. The original exhibit is retained under the case's lawful basis (for example, to prove what was seized); erasing from the case is not erasing the exhibit, and a lawful-basis decision about the exhibit itself is the controller's.
Erased with the person Stays
The person, merged records, notes on them Withheld from every reader The erasure record: when, by whom, basis, reason, ids as digests only
Their number, email, handset, SIM, bank account Withheld, with every link to them Anything shared with another person or organisation
A message, call or payment with another party Text, reference, description, handset and SIM ids Time, direction, duration, amount, currency, record id, the other party, a "content withheld" marker
A position (location point) only their device reported The whole event Positions of other devices
An imported row naming two people The erased person's entity, their personal properties, the row's note The other person, the event with its date
Imported file bytes (CDR, extraction report, statement, table) Never deleted for one person (only bytes no remaining fact cites) The file in the store, redacted from every export; the record ids withheld are listed
Cross-case search Hidden in this case Other cases (erase each in its own right), forks made earlier
Free text naming them in another's note or a row's note column Not found automatically Read the dry run and edit it

What erasure does not reach: other cases (each is erased in its own right), forks made before the erasure, the source cache, and free text that names the person in a case-level note or another entity's record. Read the dry run.

Restriction. In the console: Restrict processing…. It marks a person, and the records merged with them, as restricted in the open case. Their facts stay and are shown, but no new lookup runs on them: the tree does not expand them (the summary says how many were held back) and a lookup whose input names them (or a number, handset or account they hold) fails with “processing restricted”. The phone and financial analyses leave out the person, what they hold and the calls, messages, positions and payments they took part in, and say so (a number asked for by name is refused with the same message). Table import does not match or write about them. The case report's handling note says who is restricted and since when, and a list of restricted people is available.

Subject access. In the console: Export everything held. It returns everything the case holds about a person, merged records included: their identifiers, connections, events, analyst notes about them, the devices, SIMs, numbers and accounts linked to them (shared ones marked), the calls, messages, positions, payments and imported rows they took part in (what each says, its record id in its file, who else took part), and every artifact behind each statement (when and how it was acquired, from which source) with the chain-of-custody records of the imported files. It comes as data (JSON) and a readable summary (HTML) to send, and the audit log records that an export was made.

Docs

↑↓ to moveEnter to openEsc to close