DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed13 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 13 filings

SelectBlinds — January 2024 breach

Clustered 13 filings across 12 jurisdictions · filing window Oct 29, 2024 → Nov 1, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

12

Affected · reported

206,238

First → last dated filing

Oct 29, 2024 → Nov 1, 2024

Merge confidence

100%

incident inc_53a297fc50d64950 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. Intrusion Jan 7, 2024–Sep 28, 2024, discovered Jan 7, 2024. 206,238 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Credentials, and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
265days

Range of discovered_at dates across filings

Filing span
3days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont⏱ VT AG >14 bdayWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 33dCalifornia✓ CA 60-day OK · 33dSouth Carolina✓ SC CRA notice dueOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Jan 7, 2024breach begins
Jan 7, 2024discovered · members disagree
Oct 29, 2024first dated filing
Nov 1, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. OCT 1IL AGIL AG noticefiling day not on record · no count stated—
  2. OCT 29VT AGVT AG noticefirst filing · no count statedday 0
  3. OCT 31DE AGDE AG noticeno count stated+2d
  4. OCT 31MT AGMT AG notice1,416 MT residents+2d
  5. OCT 31IN AGIN AG noticestates nationwide total 206,238+2d
  6. OCT 31NH AGNH AG notice1,206 NH residents+2d
  7. OCT 31CA AGCA AG noticeno count stated+2d
  8. OCT 31SC AGSC AG notice1,872 SC residents+2d
  9. OCT 31OR AGOR AG noticestates nationwide total 206,238+2d
  10. OCT 31WA AGWA AG notice7,530 WA residents+2d
  11. OCT 31ME AGME AG noticestates nationwide total 206,238+2d
  12. OCT 31VT AGVT AG noticeno count stated+2d
  13. NOV 1MA AGMA AG noticemost recent · 5,530 MA residents+3d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 7, 2024
VT AG
Discovered
Jan 7, 2024IL AGSep 28, 2024VT AG + DE AG + MT AG +6filings disagree on discovery
Data types
Authentication · Credentials · Financial account · Financial credentials · Identity (basic) · PCI · PII
VT AG + DE AG + MT AG +6
Attack vector
Misconfiguration
VT 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)

206,238

Sum of filed state slices

20,879· 10.1% of stated

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

US206,238
WA7,530
MA5,530
IN2,140
SC1,872
MT1,416
NH1,206
ME1,185

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing13 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 Oct 22, 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

3 days

Cadence

~1 / 0.3d

vs. multi-state median

2.0× faster

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.