Records / De-identification rules
The engine is measured on a public benchmark
We measure the engine on two public benchmarks and publish the result for the part of each we did not look at while building: the Text Anonymization Benchmark, court judgments in which legal annotators marked every identifier, with its strict metric; and PrivacyBench, company Slack, email and document exports in which people marked every identifier by hand, scored with its authors' own scorer beside the engines they published. The scripts that measure it ship with the engine, and so do its tests.
Dated 15 Oct 2026Source checked 15 Oct 2026Page out of reach at the last check, 16 Oct 2026Basis: our standard
“although the standard, mention-level recall seems relatively good at first sight (around 0.7), a closer look a the entity-level recall over direct identifiers ERdi shows a much poorer performance (around 0.45).”
Pilán et al., TAB, Table 7 discussion, checked 1 Jul 2022
NIST SP 800-188, section 5.2.1, checked Sep 2023
Pilán et al., TAB, Table 7 (test set, values), checked 1 Jul 2022
Tonic.ai, PrivacyBench dataset card (v2.5), checked 15 Oct 2026
Everything read from this source (1)Archived copy, 3 Oct 2026
- Several kinds of evidence, never one detector
- Every mention of a person, or the person is not protected
- Nothing identifying leaves your computer
- Stand-ins from a secret key you keep, never a plain hash
- A stand-in stays the same within a file, unless the use needs more
- A person reads records picked at random
Cited in this guide