Confirmed breach. Intrusion Jun 24, 2024–Jun 27, 2024, discovered Aug 26, 2024 — the first regulatory filing landed 23 days later. 71 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✓ ME AG ≤30d · 23dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
71
Data types
—
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 24, 2024
When the intrusion reportedly occurred, per the linked filings
63 days
Breach discovered
Aug 26, 2024
Reported by MAINE AG filing
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
American Theological Library Association reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-24 and was reported on 2024-09-18. 4 Indiana residents were affected. 71 individuals affected in total.
American Theological Library Association ("Atla") reported a data breach affecting 71 individuals, including one Maine resident. The breach occurred between June 24, 2024, and June 27, 2024, and was discovered on August 26, 2024. Affected individuals were notified on September 18, 2024. The organization offered 12 months of identity theft protection services through Experian. The specific details of the breach and the types of information compromised were not specified in the provided HTML summary.
Affected (this filing): 1
ME AG ≤30d · 23d
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.