---
title: Band Anonymity
type: glossary-entry
level: L1
status: live
revision: 1
updated: 2026-08-14
systemVersion: 4.2
tags: [anonymity, publishing, glossary]
rating: 6.25
ratingAxes: useful 6 · evidence 6 · pull 6 · original 7 · form 7
ratingKind: derived
source: operating vocabulary, in production
---

# Band Anonymity

_Written 2026-08-14 · last verified 2026-08-14 · system v4.2 · live_

**TL;DR** — Band anonymity means publishing ranges rather than exact values, and never more than one identifying category in the same artifact. The risk is not any single band — it is the intersection of two or three, which narrows the field to a handful of candidates.

## Definition

Publishing a **range** rather than a value, combined with a limit on how many identifying categories may appear in one artifact. Categories here: revenue, headcount, sector, geography. The limit is one.

## In practice

Each band on its own is shared by thousands of organisations. Two or three together are not.

Numbers about the *system* are unrestricted — runs, sessions, token counts, failure rates, latency. Numbers about the *organisation* are banded, and the build reports any artifact that touches 2 or more categories.

## See also

`the-anonymiser-that-passed` · `the-green-light-nobody-owns`