Airway Oxygen, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2017-06-06. The breach occurred on 4/17/2017. 23 Montana residents were affected.
Affected (this filing): 23
Clustered 3 filings across 3 jurisdictions · filing window Jun 6, 2017 → Jun 16, 2017. View entity profile → Other incidents for this victim →
incident inc_62b8ec3da01f4dbc · 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.
MI MT OR
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 17, 2017
When the intrusion reportedly occurred, per the linked filings
Apr 18, 2017
Reported by OREGON AG filing
Airway Oxygen, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2017-06-06. The breach occurred on 4/17/2017. 23 Montana residents were affected.
Affected (this filing): 23
Airway Oxygen, Inc. reported to HHS on 2017-06-16 a Hacking/IT Incident affecting 500000 individuals. Breached information located on Network Server. The incident involved a ransomware attack encrypting PHI including names, addresses, DOB, SSNs, and treatment info. The entity provided credit monitoring and implemented safeguards.
Affected (this filing): 500,000
Airway Oxygen Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-06-16. The breach occurred during 4/18/2017. The breach was discovered on 4/18/2017. Notice was sent on 6/1/2017.
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.