Clustered 3 filings across 3 jurisdictions · filing window Oct 6, 2025 → Nov 12, 2025. View entity profile → Other incidents for this victim →
incident inc_c2e230190de34c04 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN ME VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 6, 2024
When the intrusion reportedly occurred, per the linked filings
Nov 13, 2024
Reported by MAINE AG filing
BT&CO PA reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-06 and was reported on 2025-10-06. 1 Indiana residents were affected. 789 individuals affected in total.
Affected (this filing): 789
BT&CO., P.A. reported a data breach that occurred on November 6, 2024, and was discovered on November 13, 2024. The breach affected one Maine resident. The company is offering 12 months of free credit fraud and identity theft monitoring from Haystack ID. The specific details of the breach and the types of data affected were not specified in the summary.
Affected (this filing): 1
State AG notice filed by BT&CO regarding a data breach. The source document is a portal page linking to a PDF consumer notice, but the attachment content is empty. No specific details regarding the incident nature, dates, data types, or affected individuals are available in the provided text.
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.