Confirmed breach. Intrusion Aug 1, 2018–Mar 30, 2019, discovered Mar 20, 2019 — the first regulatory filing landed 75 days later (flagged late). 7,659,293 individuals reported across the linked filings.
incident inc_98e8749f6b8c43a5 · merge_method human · confidence 100%
Litigation Timing
Notification delay
75days
Discovered → first regulatory filing
Filing span
2days
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.
Regulatory clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
7,659,293
Data types
—
Jurisdictions
2
MT OR
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 1, 2018
When the intrusion reportedly occurred, per the linked filings
Retrieval-Masters Creditors Bureau, Inc (d/b/a American Medical Collection Agency) reported a data breach to the Montana Attorney General. The breach was reported on 2019-06-03. The breach occurred from 8/1/2018 to 5/30/2019. 7,898 Montana residents were affected.
Affected (this filing): 7,898
🦫Oregon State AGMost recentlinked via operator-confirmed · 100%
Retrieval-Masters Creditors Bureau, Inc. (d/b/a/ American Medical Collection Agency) reported a data breach to the Oregon Attorney General. The breach was reported on 2019-06-05. The breach occurred during 8/1/2018 - 3/30/2019. The breach was discovered on 3/20/2019. 7,651,395 individuals were affected. Notice was sent on 6/5/2019.
Affected (this filing): 7,651,395
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.