The North American Spine Society reported a data breach to the Montana Attorney General. The breach was reported on 2022-07-08. The breach occurred on 2/13/2022. 27 Montana residents were affected.
Affected (this filing): 27
Clustered 2 filings across 2 jurisdictions · filed Jul 8, 2022. View entity profile → Other incidents for this victim →
incident inc_5775e3c9e23d404b · 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
Feb 13, 2022
When the intrusion reportedly occurred, per the linked filings
Feb 13, 2022
Reported by MAINE AG filing
The North American Spine Society reported a data breach to the Montana Attorney General. The breach was reported on 2022-07-08. The breach occurred on 2/13/2022. 27 Montana residents were affected.
Affected (this filing): 27
North American Spine Society, an educational organization, experienced an external system breach that was discovered on February 13, 2022. The incident, which occurred on January 19, 2022, affected 17 Maine residents. The compromised information included names and financial account numbers or credit/debit card numbers along with their security codes or PINs. The company began notifying affected individuals on July 8, 2022, and offered identity theft protection services.
Affected (this filing): 17
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.