What publicly available datasets exist that link NCMEC CyberTips to law‑enforcement case outcomes?

Checked on January 28, 2026
Disclaimer: Factually can make mistakes. Please verify important information or breaking news. Learn more.

Executive summary

There is no publicly available dataset that directly links individual NCMEC CyberTipline reports to law‑enforcement case outcomes; NCMEC publishes aggregate CyberTipline statistics and metadata, and some platforms publish counts of tips they submitted, but outcome information after referral is not generally released [1] [2] [3]. The technical CyberTipline API and internal case‑management systems record law‑enforcement case identifiers and response metadata, but those fields are not exposed as public, outcome‑linked datasets [4] [3].

1. What NCMEC publishes publicly: aggregated CyberTipline statistics and jurisdictional snapshots

NCMEC issues annual CyberTipline reports and public pages that disclose aggregate totals (total reports, files, breakdowns by platform, incident type, and jurisdictional counts) intended to illuminate trends rather than case‑level outcomes [2] [5]. NCMEC’s public summaries include metrics such as total reports received in a year and counts by country and platform, and they highlight trends (for example, the 2024 report totals and trend notes) but do not tie a specific CyberTip to investigative disposition in a public dataset [6] [5] [2].

2. What technically exists inside NCMEC and its partners: fields for case IDs and responses

NCMEC’s CyberTipline Reporting API and associated case‑management tools document structured fields for law‑enforcement information — including investigator contact, law‑enforcement agency, and law‑enforcement case number — and elements for report responses and “report done” status that record operational outcomes internally [4]. NCMEC also shares reports with law enforcement through the Case Management Tool (CMT) to enable triage and case tracking across agencies; that system is designed for secure operational use, not public release [3].

3. Public datasets that approximate linkage: platform transparency and jurisdictional totals

Some Electronic Service Providers publish transparency data about the number and types of CyberTips they submit to NCMEC, providing another public signal about referrals (Meta’s transparency pages are an example) but those disclosures report counts and categories, not the downstream investigative results tied to individual tips [7]. Separately, third‑party aggregators and policy projects can combine NCMEC’s jurisdictional aggregates with other public data to create analytic views of reporting volume by locale, but those products still do not link single CyberTips to final law‑enforcement outcomes [2].

4. Why there is no public outcome‑linked dataset: legal, procedural, and operational limits

NCMEC explicitly notes that after a CyberTip is shared with law enforcement it does not always have access to subsequent steps or outcomes and therefore cannot provide that information in the public reporting stream [1]. Operational tools that could map tips to outcomes are internal and intended to protect victim privacy, investigative integrity, and interagency confidentiality — constraints repeatedly emphasized in NCMEC materials about how reports are shared with law enforcement via secure systems like CMT [3] [4].

5. Where researchers might look next and the limits they will face

Researchers seeking linkage must therefore rely on a patchwork: NCMEC’s public aggregates and API schema documentation showing which case fields exist (but not their public values), ESP transparency reports that enumerate tips they sent, and jurisdictional totals published by policy groups; none of these constitute a publicly accessible, case‑level dataset that ties a CyberTip to a documented law‑enforcement disposition [4] [7] [2]. Representative critiques and operational analyses note how CyberTip language and automated labeling can be misunderstood by investigators or courts, which further complicates any transparent mapping between tips and outcomes even if more data were available [8] [9].

6. Bottom line and realistic path forward

The existing public data ecosystem offers robust aggregate visibility into volume, trends, and reporting sources but not case‑level outcome linkage; fields and systems to record outcomes exist inside NCMEC and partner agencies, yet privacy, investigatory integrity, and explicit NCMEC policy about not always having downstream outcome info mean researchers cannot currently access a public dataset that maps CyberTips to law‑enforcement case outcomes [3] [4] [1]. Any effort to produce such linkages would require new, formal data‑sharing agreements, privacy safeguards, and likely legislative or policy changes to balance transparency with victim and investigatory protections [10] [3].

Want to dive deeper?
How can researchers request access to NCMEC operational datasets or aggregated jurisdictional CyberTip data?
What transparency data do major platforms publish about NCMEC CyberTip submissions and how do they differ by company?
What legal and privacy barriers prevent public release of law‑enforcement outcomes tied to child exploitation reports?