Faulkner University reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-07. The breach occurred on 4/18/2022. 10 Montana residents were affected.
Affected (this filing): 10
Clustered 2 filings across 2 jurisdictions · filed Jun 7, 2022. View entity profile → Other incidents for this victim →
incident inc_e2449826909c4517 · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 18, 2022
When the intrusion reportedly occurred, per the linked filings
Apr 22, 2022
Reported by MAINE AG filing
Faulkner University reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-07. The breach occurred on 4/18/2022. 10 Montana residents were affected.
Affected (this filing): 10
Faulkner University reported a data breach affecting two individuals, both Maine residents. The breach, which occurred on April 18, 2022, and was discovered on April 22, 2022, was categorized as an external system breach or hacking incident. The compromised information included names in combination with Social Security Numbers. Affected individuals were notified in writing on June 6, 2022, and offered one year of identity theft protection services through Experian.
Affected (this filing): 2
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.