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

AssuranceAmerica Managing General Agency, LLC — March 2026 breach

Clustered 14 filings across 14 jurisdictions · filing window Jun 1, 2026 → Jul 15, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

14 filings

States

14

Affected · reported

6,998,886

First → last filing

Jun 1, 2026 → Jul 15, 2026

Merge confidence

100%

incident inc_2f8989688b5b41f3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. Intrusion Mar 16, 2026–Mar 17, 2026, discovered Mar 17, 2026 — the first regulatory filing landed 76 days later (flagged late). 6,998,886 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 44-day schedule across 14 filings beginning Jun 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
76days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
44days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dMassachusetts✗ MA AG >90dTexas✗ TX AG >30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 16, 2026breach begins
Mar 17, 2026discovered
notification delay · 76 days
Jun 1, 2026first filing
Jul 15, 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. JUN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 15DE AGDE AG noticeno count stated+14d
  3. JUN 17CA AGCA AG noticeno count stated+16d
  4. JUN 17WA AGWA AG notice8,950 WA residents+16d
  5. JUN 18SC AGSC AG notice611,046 SC residents+17d
  6. JUN 18OR AGOR AG noticestates nationwide total 6,998,886+17d
  7. JUN 23VT AGVT AG notice272 VT residents+22d
  8. JUN 23IA AGIA AG notice1,839 IA residents+22d
  9. JUN 23MA AGMA AG notice3,569 MA residents+22d
  10. JUN 23NH AGNH AG notice463 NH residents+22d
  11. JUN 24RI AGRI AG notice633 RI residents+23d
  12. JUN 26TX AGTX AG noticestates nationwide total 6,998,886+25d
  13. JUL 10IN AGIN AG noticestates nationwide total 6,998,886+39d
  14. JUL 15NE AGNE AG noticemost recent · no count stated+44d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 16, 2026
DE AG
Discovered
Mar 17, 2026· 1d undetected
IL AG + DE AG + CA AG +9
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PII
IL AG + DE AG + CA AG +9
Attack vector
Phishing
DE AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

6,998,886

Sum of filed state slices

1,364,900· 19.5% of stated

80% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US6,998,886
SC611,046
TX500,987
IN237,141
WA8,950
MA3,569
IA1,839
RI633
NH463
VT272

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing14 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

44 days

Cadence

~1 / 3.4d

vs. multi-state median

5.5× 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.