First Logic Marketing LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-10-29. The breach occurred from 4/24/2020 to 6/7/2020. 9 Montana residents were affected.
Affected (this filing): 9
Clustered 2 filings across 2 jurisdictions · filing window Oct 29, 2020 → Nov 6, 2020. View entity profile → Other incidents for this victim →
incident inc_2e486211e5b840ab · merge_method human · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 24, 2020
When the intrusion reportedly occurred, per the linked filings
Jun 5, 2020
Reported by MAINE AG filing
First Logic Marketing LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-10-29. The breach occurred from 4/24/2020 to 6/7/2020. 9 Montana residents were affected.
Affected (this filing): 9
First Logic Marketing LLC reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred. The breach was discovered on June 5, 2020, and is listed as occurring on October 29, 2020. The incident affected 16 Maine residents. The compromised information included names or other personal identifiers in combination with financial account numbers or credit/debit card numbers, along with their security codes, access codes, passwords, or PINs. Written notifications were sent to the affected individuals on October 29, 2020. The company did not offer identity theft protection services.
Affected (this filing): 16
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.