Disclosures Claims Reports Entities Incidents Pulse

Feed live

DisclosureLens

Structured extracts of public breach disclosures — regulator filings (SEC, HHS, state AGs, EU DPAs) alongside threat-actor leak-site claims and press reports. SEC and HHS filings render inline from the originating regulator’s public record under the fair report privilege; other sources link out to the source URL. AI-extracted with full per-record audit trail (model, prompt version, confidence).

ai_assisted: true · Article 50 disclosure on every record

Product

Disclosures feed
Pulse · analytics
Entities
Breach notifications by state

Methodology

How extraction works
Confidence & review
About the bot

Trust

Security
Self-disclosure commitment
API documentation
API keys

v0.1.0 · coverage growing weekly

T-Mobile USA/Experian data breach (2015) · DisclosureLens

All incidents View linkage analytics →

Merged incident · 2 filings

T-Mobile USA/Experian

Clustered 2 filings across 2 jurisdictions · filing window Oct 1, 2015 → Oct 30, 2015. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Confirmed breach. Intrusion Sep 15, 2015, discovered Sep 15, 2015 — the first regulatory filing landed 16 days later. 436,889 individuals reported across the linked filings.

incident inc_adfbc52f03ab42cf · merge_method deterministic · confidence 100%

Litigation Timing

Notification delay

16days

Discovered → first regulatory filing

Discovery variance

6days

Range of discovered_at dates across filings

Filing span

Regulatory clocksWashington✓ WA AG ≤30dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced

Affected (total reported)

436,889

Data types

—

Jurisdictions

OR WA

29days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Linked filings

all State AG

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

Breach window
Sep 15, 2015
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Sep 15, 2015
Reported by OREGON AG filing
Breach discoveredconflicts with Sep 15, 2015AG web form
Sep 21, 2015
Reported by WASHINGTON AG filing
🌲Washington State AGFirst filing
Filed Oct 1, 2015bd_4acd7ab8e9482cae
T-Mobile USA/Experian, a business sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2015-09-21 and filed notice on 2015-10-01. 328,889 Washington residents were affected. 10 days elapsed between awareness and notification. 6 days to identify the breach.
Affected (this filing): 328,889
WA AG ≤30d
🦫Oregon State AGMost recentlinked via multistate filing link · 95%
Filed Oct 30, 2015bd_9ec2e9674ac7b142
T-Mobile / Experian reported a data breach to the Oregon Attorney General. The breach was reported on 2015-10-30. The breach occurred during 9/15/2015. The breach was discovered on 9/15/2015. 108,000 individuals were affected. Notice was sent on 9/21/2015.
Affected (this filing): 108,000
OR AG ≤45d

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.