Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Dashboard ↗ JA
Home / Critical Brief / No. 036
No. 036 Critical Brief · Verifiable Origin

DataComp CommonPool: A public AI training dataset contained passports, résumés and faces (arXiv:2506.17185)

800+faces
Faces that escaped automatic blurring in a 0.1% sample; about 102 million estimated overall (the research team)
12.8billion pairs
Image-text pairs in DataComp CommonPool (released 2023), built on material Common Crawl collected in 2014–2022
0.1%
Share of the dataset the research team audited; thousands of valid ID documents and over 800 résumés and cover letters were found
CountryGlobal
Incident date2025-07-18
Published2026-06-08
AuthorsLemma Critical Team
Contents
  1. 01Summary
  2. 02What got through
  3. 03Pre-execution check
  4. 04What Lemma does
  5. 05Facts and timeline
  6. 06Sources

Summary

According to the research team’s audit, image-text pairs collected from the public web included real people’s ID documents, résumés and faces, and some faces had escaped the automatic blurring the curators applied. Filters for known PII strings such as email addresses were reportedly not applied. The scale is an estimate from a sample audit, not a full count. Even when material is public, unless the provenance and consent to use it for training are checked before ingestion, personal data that later filters cannot fully remove stays in the dataset.

Figure 1"Detection" versus a "pre-execution check"

A pre-execution check means checking, before material goes into a dataset, the provenance and consent to use it for training, and keeping a record. Detection means finding personal data mixed in after ingestion; here, the research team's sample audit did that.

Pre-execution check · not known from the disclosuresCheck each item's provenance and consent before ingestion
What the research team reportedUnblurred faces, IDs and résumés
remained in the data
Detection · the research audit workedAudit a 0.1% sample and estimate the whole
2014–22
Common Crawl collects the public web at scale
2023
Faces auto-blurred; the dataset is released
DOWNSTREAM
Circulates in a form anyone can train on
2025-07
The audit results are reported

What got through

What got through
Ingesting image-text pairs collected from the public web into a training dataset, and releasing it. After automatic face blurring, it was released as a dataset anyone could use for training (the research team’s audit; reporting by MIT Technology Review).
What the receiving side gets
In general, material collected from the web arrives with images and text, but not with provenance saying whose material it is, under what consent, and for what scope of use it was published. The ingesting side receives nothing on which to judge whether it may be used for training.
After-the-fact filters
Automatic face blurring was applied, but over 800 faces in the sample escaped detection. Filters for known PII strings such as emails and Social Security numbers were not applied, the research team reports.
Not disclosed
How much personal data actually reached downstream generative models and derivatives. The size of the problem across the whole dataset (estimated from a sample; not counted in full).

Pre-execution check

The condition that holds whatever the route is this: before material goes into a dataset, check that it has the provenance and consent to be used for training.

The core of this case
Even when material is public, unless the provenance and consent to use it for training are checked before ingestion, personal data that later filters cannot fully remove stays in the dataset.
Who approves
The owner of the material (the person pictured, or the owner of the document). Being public on the web does not stand in for permission to use it for training.
Where the check happens
Just before material is ingested into the dataset. Material whose provenance and consent cannot be checked is not ingested.
What remains
A record of which material went in under which provenance and consent, so that the relevant items can be traced when deletion or correction is requested.

The research team’s audit showed concretely what after-the-fact filters had failed to remove, but it found this after the dataset had been released. A case where being public and consent to train came apart is the Discord message scraping. The removable provenance mark on AI outputs echoes the SynthID watermark removal.

What Lemma does

Lemma builds the pre-execution check into the point just before material is ingested into a dataset. It does not search for personal data after the fact; it checks, before ingestion, that the material has the provenance and consent to be used for training.

Industries and operations to watch

IndustryAI
Organizations that train models on material collected from the web, or that publish or provide training datasets.
OperationDisclosure & data release
Publishing or providing collected data as a dataset.

Current controls vs Lemma

Column 1 is ingesting material into the dataset and column 2 is removing personal data from ingested material; in this case, both were passed.

Control Ingesting material (provenance and consent) Removing personal data from ingested material
Automatic face blurring Not relevant Partial
Known PII string filter Not relevant Partial
Lemma (pre-execution check) Effective Not relevant

According to the research team, automatic face blurring was applied, but over 800 faces escaped detection in the sample alone, and filters for known PII strings were not applied. Both search ingested material for personal data and remove it; neither decides whether the material may be used for training. Lemma checks each item’s provenance and consent before ingestion. It does not find personal data inside ingested material, and it does not delete data.

Note: Lemma’s check works only when it is built in just before ingestion and each item’s provenance and consent are issued and managed separately from the collector. Material that has provenance and consent passes this check. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions.

CheckChecklist

Three items to confirm when ingesting data for training or analysis

  • Do you select material by a criterion other than whether it is public?
  • Do you record which material went into the dataset under which provenance and consent?
  • When deletion or correction is requested, can you trace the relevant items within the dataset?

Facts and timeline

Target
DataComp CommonPool, a training dataset of 12.8 billion image-text pairs released in 2023. It is built on material Common Crawl collected from the web in 2014–2022, and is the successor to LAION-5B.
Disclosure
The research team published its audit paper (arXiv:2506.17185), and MIT Technology Review reported it on 2025-07-18.
What was found
In an audit of 0.1% of the dataset, thousands of valid ID documents (credit cards, driver’s licences, passports, birth certificates) and over 800 résumés and cover letters (real people confirmed via LinkedIn) were found, the research team reports.
Estimate
The research team estimates that personal images number in the hundreds of millions across the whole dataset.
Privacy measures
The curators applied automatic face blurring, but over 800 faces in the sample escaped detection, with about 102 million faces estimated to have been missed overall. Filters for known PII strings such as emails and Social Security numbers were not applied.
Impact
CommonPool is the successor to LAION-5B and sits in the training lineage of Stable Diffusion, Midjourney and others. The research team and reporting point to the risk of personal data reaching downstream generative models and derivatives.

Glossary
DataComp CommonPool — An AI training dataset of image-text pairs released in 2023; the successor to LAION-5B.
Common Crawl — An effort that collects the public web at scale. CommonPool is built on material it collected in 2014–2022.
PII string filter — A filter that searches text for personal data with a fixed format, such as email addresses or Social Security numbers, and removes it.

Timeline

  • Common Crawl collects images and text from the public web at scale.
  • DataComp CommonPool is released at 12.8 billion pairs, with measures such as automatic face blurring applied.
  • The research team’s paper is published on arXiv (arXiv:2506.17185).
  • MIT Technology Review reports the ID documents, résumés and unblurred faces found, and the overall estimates.

Proper names are based on primary sources (research institutions, etc.). This is a 0.1% sample audit and overall estimate by the research team; estimates are not treated as confirmed totals, and the scale is not exaggerated. This is not an attack but a case that brought the handling of provenance and consent in training data into view. This Brief does not blame any particular organization. What has not been disclosed does not mean no measures were in place.

Response after disclosure

The research team and reporting
Estimated the whole from a sample audit, and pointed out the faces missed by blurring and the absence of PII string filtering. As the successor to LAION-5B, they flagged the risk of downstream spread.
Filter improvements
Improvements to automatic face blurring and PII detection filters are under way.
Industry discussion
For training data built on large-scale web collection, after-the-fact filters alone cannot fully remove personal data, and a composition that can trace which material went in with which provenance is increasingly demanded by both personal-data protection (such as the right to be forgotten) and the model supply chain. A dataset without provenance makes deletion and correction hard to honour.

Sources

References: “The last layer left for cyber defense in the age of AI”

The same method elsewhereSee all 15 "Disclosure & data release" cases

This Brief sets out, from disclosed facts, what organisations in a similar position can check. It is not guidance on individual losses or procedures.

This material is a structured analysis of public information; it is not an audit, diagnosis, or recommendation for any specific organization.

Cite this Brief

Lemma Critical Team. (2026).
"DataComp CommonPool: A public AI training dataset contained passports, résumés and faces (arXiv:2506.17185)".
Lemma Critical Brief No.036. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/036-commonpool-training-data-pii/
Read nextNext
All Briefs →
Lemma

If it can't be verified,
it doesn't enter your operation.

Lemma is a pre-execution check: logins, payments, records and publishing that look genuine are checked before they run, with cryptographic proofs the receiving side verifies without asking the issuer. Detection stays; the check sits in front of it.