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

Indigo data breach (2017) · DisclosureLens

All incidents View linkage analytics →

Merged incident · 2 filings

Indigo

Clustered 2 filings across 2 jurisdictions · filed May 12, 2017. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge100%

Confirmed breach. Intrusion Nov 14, 2016–Apr 17, 2017, discovered Apr 17, 2017 — the first regulatory filing landed 25 days later. 501 individuals reported across the linked filings.

incident inc_f3791077abff4c0e · merge_method deterministic · confidence 100%

Litigation Timing

Notification delay

25days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

Regulatory clocksOregon✓ OR AG ≤45dWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced

Affected (total reported)

501

Data types

—

Jurisdictions

OR WA

0days

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
Nov 14, 2016 → Apr 17, 2017
When the intrusion reportedly occurred, per the linked filings
154 days
Breach discoveredAG web form
Apr 17, 2017
Reported by OREGON AG, WASHINGTON AG filings
🦫Oregon State AGFirst filing
Filed May 12, 2017bd_17c8cdde05d621c9
Indigo Wild reported a data breach to the Oregon Attorney General. The breach was reported on 2017-05-12. The breach occurred during 11/14/2016 - 4/17/2017. The breach was discovered on 4/17/2017. Notice was sent on 5/12/2017.
OR AG ≤45d
🌲Washington State AGMost recentlinked via multistate filing link · 100%
Filed May 12, 2017bd_33162c0539929f6c
Indigo Wild, a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2017-04-17 and filed notice on 2017-05-12. 501 Washington residents were affected. 25 days elapsed between awareness and notification. 154 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 501

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.

WA AG ≤30d