DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

Indico Data — May 2026 breach

Clustered 6 filings across 4 jurisdictions · filing window Jul 16, 2026 → Sep 1, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

not comparable

First → last filing

Jul 16, 2026 → Sep 1, 2026

Merge confidence

100%

incident inc_513c7836b6f24d84 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filing describes unauthorized access. Intrusion May 5, 2026, discovered May 7, 2026 — the first regulatory filing landed 70 days later (flagged late). Data reported: Government ID, Identity (basic), PHI, and 2 more. Notifications rolled out on a 47-day schedule across 6 filings beginning Jul 16, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
70days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
47days

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.

Regulatory clocksTexas✗ TX AG >30dCalifornia✗ CA 30-day late · 112dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 5, 2026breach begins
May 7, 2026discovered
notification delay · 70 days
Jul 16, 2026first filing
Sep 1, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 16NE AGNE AG noticefirst filing · 4 NE residentsday 0
  2. AUG 10TX AGTX AG notice855 affected+25d
  3. AUG 27CA AGCA AG noticeno count stated+42d
  4. AUG 27NE AGNE AG notice58 NE residents+42d
  5. SEP 1TX AGTX AG notice2,128 affected+47d
  6. SEP 1MA AGMA AG noticemost recent · no count stated+47d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 5, 2026
CA AG
Discovered
May 7, 2026· 2d undetected
NE AG + TX AG + CA AG +1
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
NE AG + TX AG + CA AG +1
Attack vector
Unauthorized Access
NE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

47 days

Cadence

~1 / 9.4d

vs. multi-state median

5.9× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.