Skip to content
The Taxonomy

A shared vocabulary for describing technology.

Each category is a question people ask about a technology, and its elements are the answers. Choose a category, then an element, to see its icon and what it means. New to the terms? Read the concepts.

Purpose

What is the purpose of this system?

Why this system exists — the outcome it’s designed to achieve.

Accountable

Who is accountable for this system?

The organization responsible for deploying and operating this system.

Context: Role

How this organization participates in the deployment of the system.

VendorThe organization that builds, supplies, or licenses the system.
DeployerThe organization that deploys and operates the system in this place.

People affected

Who is this system used on?

The people this system is used on, or whose lives its decisions affect — including those who never chose to interact with it.

Context: Relationship

How this system touches this person or group.

Decided aboutThe system produces an output about this person that affects them directly — a score, a match, an eligibility call.
Caught incidentallySwept into the system’s data even though it isn’t making a decision about them — a face in the background of a camera aimed elsewhere.
Wider communityA place or group affected collectively, beyond the individuals the system processes — a neighbourhood under watch, a ranked workforce.

What it does

What is this system doing?

This system's actions, said as everyday verbs — it senses, predicts, decides, creates, moves. Naming the verbs makes it easier to reason about what the system touches and what could go wrong.

Context: Human involvement

Who completes the loop — a quick, system-level signal of how much runs without a person, shown on the verb it colors. A general characterization of the deployment, not a technical audit.

A person decidesThis system suggests or informs; a person makes the call before anything takes effect. Example: a triage tool ranks cases for a clinician who chooses which to see first.
A person oversees or carries it outThis system works out the result on its own; people supervise it, can step in, or carry out the result themselves. Example: an optimizer plans the day's collection routes, and drivers run them.
Runs on its ownThis system decides and takes effect without a person reviewing each result. Example: a road toll that reprices and charges automatically as traffic changes.

Risks & Mitigation

What are the risks and how are they mitigated?

The risks this system could create and how they’re being addressed.

Rights

What are your rights?

What you can do in relation to this system — how to access, contest, or opt out.

Collection Technology

What captures the data this system uses?

The devices and channels that capture this system's input data — cameras, sensors, microphones, forms, or feeds from other systems. The instrument that collects the data, distinct from the algorithm that processes it.

Input Data

What input data does this system process?

The input data this deployed system processes when it operates.

Context: Personal Information

How identifiable the data is when this system processes it. The element name says what the data is about; this colour says how directly it identifies a person.

Anonymized dataData about people with the link to who is broken. Stripped of identifiers, blurred, aggregated, or noised so this system can’t reasonably tie a record back to an individual.
Pseudonymous dataEach person’s data is tied to a token (hash, ID, template) that lets this system recognise the same person across events, but the token itself doesn’t reveal a name. Reidentification is possible with extra information.
Identifiable dataThe data either contains a direct identifier (name, address, account name, recognisable face or voice, plate number) or carries a token this system uses to look up legal identity during processing.

Algorithm or Model

What algorithm or model processes the data?

What processes the input — the algorithm family, model class, or technique used to turn inputs into outputs.

Output Data

What does this system produce?

The output data this deployed system produces when it operates — decisions, content, and actions.

Context: Personal Information

How identifiable the data is when this system produces it. The element name says what the output is about; this colour says how directly it identifies a person.

Anonymized dataOutput about people with the link to who is broken. Stripped of identifiers, blurred, aggregated, or noised so the result can’t reasonably be tied back to an individual.
Pseudonymous dataThe output is labelled with a token (hash, ID, template) that lets this system tie the result to the same person across events without revealing a name. Reidentification is possible with extra information.
Identifiable dataThe output names a person directly (name, address, account, recognisable face or voice, plate) or carries a token this system resolves to legal identity in the same step.

Manifestation

How do people encounter what this system produces?

The form this system's output takes when it reaches the world — a screen or sign, a price, a notification, a gate opening, a spoken reply. How people meet the output, distinct from the output data itself.

Data Access

Who has access to the data?

Who can see or use the data this system collects or produces.

Data Retention

How long is the data kept?

How long the data this system collects or produces is kept.

Data Storage

Where is the data stored?

Where the data this system collects or produces is kept.