DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedpysahigh sensitivity
Merged incident · 6 filings

Bosley, Inc. — August 2020 breach

Clustered 6 filings across 6 jurisdictions · filing window Jan 26, 2021 → Sep 9, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

100,855

First → last filing

Jan 26, 2021 → Sep 9, 2021

Merge confidence

100%

incident inc_10f05beb2f9b42ae · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe a ransomware attack. Intrusion Aug 17, 2020, discovered Aug 17, 2020 — the first regulatory filing landed 162 days later (flagged late). 100,855 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 226-day schedule across 5 filings beginning Jan 26, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
162days

Discovered → first regulatory filing

Discovery variance
146days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 226d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
226days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 17, 2020breach begins
Aug 17, 2020discovered · members disagree
notification delay · 162 days
Jan 26, 2021first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JAN 26OR AGOR AG noticefirst filing · states nationwide total 100,855day 0
  2. JAN 26IN AGIN AG noticestates nationwide total 100,855day 0
  3. JAN 26WA AGWA AG notice1,936 WA residentsday 0
  4. JAN 26CA AGCA AG noticeno count statedday 0
  5. JAN 26MT AGMT AG notice162 MT residentsday 0
  6. SEP 9Leak sitepysa postmost recent · attacker claim · unverified+226d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 17, 2020
OR AG
Discovered
Aug 17, 2020WA AG + CA AG + MT AGJan 10, 2021OR AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · Financial account
WA AG + CA AG + MT AG
Attack vector
Ransomware
WA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

100,855

Sum of filed state slices

3,101· 3.1% of stated

97% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US100,855
WA1,936
IN1,003
MT162

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 26, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

226 days

Cadence

~1 / 45.2d

vs. multi-state median

25.1× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.