The label is not the privacy test
Synthetic records are intended to be artificial, but that label does not answer what someone could learn about the underlying people. NIST’s Collaborative Research Cycle evaluates deidentified data on privacy, fidelity and usefulness, and invites attempts to reconstruct information from synthetic samples. [1]
- Utility: retain useful patterns
- Privacy: test exposed information
- Scope: name the data and tests
Ask whether the data is useful
The SDNist tool produces a report with separate utility and privacy metrics. Its current README limits this version to specified American Community Survey excerpts. A benchmark report is evidence about the tested data and metrics, not a certificate for every dataset a generator could produce. [2]
Ask what an attacker can infer
Anonymeter tests attempts to isolate a person, connect records and infer an unknown attribute. Its evaluation compares attacks on original records with attacks on a separate control set and with a naive baseline. These comparisons help distinguish a privacy leak from an ordinary population pattern. [3]
Go a little deeper
Optional reading · about 1 more minute
A concrete distinction
Hypothetical example: A synthetic staff dataset may help test a dashboard because its columns and distributions look plausible. That usefulness does not settle whether a rare combination lets someone infer a real employee’s hidden attribute. The application test and privacy test answer different questions.
How to read a reassuring score
Our interpretation: Ask what information the test attacker had, which people and attributes were tested, and what the control comparison showed. Keep the answer tied to that experiment. This explainer does not certify a dataset as anonymous or determine whether sharing it is lawful.
Original sources
Attributed synthesis, not original reporting. Examples labeled hypothetical or illustrative are explanatory. Reviewing a source does not independently validate its findings.
- NIST: Collaborative Research Cycle ↗
Program introduction, evaluation metrics and red-team description read September 19, 2026. Page includes a March–June 2025 activity; not a new September announcement.
- NIST SDNist report tool ↗
README introduction and dataset scope read September 19, 2026. Current documentation, publication date not established; tool not executed.
- Anonymeter: original tool documentation ↗
README attack definitions and evaluation procedure read September 19, 2026. Developer documentation, not an independent endorsement or legal compliance assessment.
