Juniata College reported a data breach to the Montana Attorney General. The breach was reported on 2019-11-01. The breach occurred on 4/12/2019. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filing window Nov 1, 2019 → Nov 5, 2019. View entity profile → Other incidents for this victim →
incident inc_fc6d8021f49147b4 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 12, 2019
Reported by NEW HAMPSHIRE AG filing
Apr 12, 2019
When the intrusion reportedly occurred, per the linked filings
Juniata College reported a data breach to the Montana Attorney General. The breach was reported on 2019-11-01. The breach occurred on 4/12/2019. 2 Montana residents were affected.
Affected (this filing): 2
Juniata College notified the New Hampshire Attorney General of a data event involving approximately 6 NH residents. The incident involved suspicious email activity discovered in March 2019, leading to potential unauthorized access to employee email accounts. Affected data included names, Social Security numbers, financial account numbers, and medical information. The college engaged forensic investigators, reset passwords, and offered one year of credit monitoring.
Affected (this filing): 6
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.