Confirmed breach. Intrusion Sep 3, 2024, discovered Oct 14, 2024 — the first regulatory filing landed 107 days later (flagged late). 4 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✗ ME AG >90d · 107dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
4
Data types
—
Jurisdictions
1
ME
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 3, 2024
When the intrusion reportedly occurred, per the linked filings
The City of Miami Beach reported an inadvertent data disclosure that occurred on September 3, 2024, and was discovered on October 14, 2024. The breach affected four Maine residents. Affected individuals were notified on November 13, 2024, and offered 12 months of credit and identity monitoring services through TransUnion.
Affected (this filing): 4
ME AG >90d · 107d
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.