DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed10 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedeveresthigh sensitivity
Merged incident · 10 filings

Stiiizy Inc — October 2024 breach

Clustered 10 filings across 9 jurisdictions · filing window Nov 24, 2024 → Jan 28, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

380,000

First → last filing

Nov 24, 2024 → Jan 28, 2025

Merge confidence

100%

incident inc_4a135dfe0f664c8d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe a third-party compromise. Intrusion Oct 10, 2024–Nov 10, 2024, discovered Oct 10, 2024 — the first regulatory filing landed 71 days later (flagged late). 380,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 4 more. Notifications rolled out on a 64-day schedule across 9 filings beginning Nov 24, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
71days

Discovered → first regulatory filing

Discovery variance
41days

Range of discovered_at dates across filings

Leak precedence
25days before filing

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
64days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 50dWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 10, 2024breach begins
Oct 10, 2024discovered · members disagree
notification delay · 71 days
Dec 20, 2024first filing
Jan 28, 2025most recent filing

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

Member cascade — every filing about this breach

  1. NOV 24Leak siteeverest postfirst filing · attacker claim · unverifiedday 0
  2. DEC 20WA AGWA AG notice3,500 WA residents+25d
  3. DEC 31OR AGOR AG noticestates nationwide total 380,000+36d
  4. JAN 1IL AGIL AG noticeno count stated+37d
  5. JAN 8MT AGMT AG notice318 MT residents+44d
  6. JAN 8NE AGNE AG noticeno count stated+44d
  7. JAN 8CA AGCA AG noticeno count stated+44d
  8. JAN 9ME AGME AG noticestates nationwide total 380,000+45d
  9. JAN 9MA AGMA AG notice1,684 MA residents+45d
  10. JAN 28OR AGOR AG noticemost recent · states nationwide total 380,000+64d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 10, 2024 – Nov 10, 2024
WA AG
Discovered
Oct 10, 2024IL AGNov 20, 2024WA AG + OR AG + MT AG +3filings disagree on discovery
Data types
Behavior · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + MT AG + CA AG +2
Attack vector
Third-Party / Supply Chain
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)

380,000

Sum of filed state slices

5,714· 1.5% of stated

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

US380,000
WA3,500
MA1,684
MT318
ME212

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 filing9 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 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

64 days

Cadence

~1 / 7.1d

vs. multi-state median

8.0× 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.