Clustered 3 filings across 3 jurisdictions · filing window Aug 11, 2023 → Sep 20, 2023. View entity profile → Other incidents for this victim →
incident inc_08a1a968a4b542de · 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.
Identity (basic) · Government ID
ME MT NH
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Jan 30, 2023 → Feb 1, 2023
When the intrusion reportedly occurred, per the linked filings
Jun 6, 2023
Reported by MAINE AG filing
Georgetown Financial Group reported an email compromise incident occurring between Jan 30 and Feb 1, 2023, discovered on June 6, 2023. The breach affected 466 individuals, including 2 Maine residents, exposing names and Social Security Numbers. The company notified affected individuals in writing on Aug 11, 2023, and provided 12 months of credit monitoring and identity theft services via Experian.
Affected (this filing): 466
Georgetown Financial Group (GFG) issued a breach notification to one New Hampshire resident on September 20, 2023, following a phishing incident that compromised an email account. GFG secured the account, investigated the scope, and provided one year of complimentary Experian IdentityWorks monitoring and identity restoration services to the affected individual. The incident involved the potential exposure of personal and government-issued identification data.
Affected (this filing): 1
Georgetown Financial Group reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-20. The breach occurred from 1/30/2023 to 2/1/2023. 1 Montana residents were affected.
Affected (this filing): 1
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.