DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed11 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

SVANACO, INC. — July 2022 breach

Clustered 11 filings across 10 jurisdictions · filing window Mar 29, 2023 → Apr 4, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

105,008

First → last filing

Mar 29, 2023 → Apr 4, 2023

Merge confidence

100%

incident inc_8a94771d2f9f43bb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Jul 13, 2022–Dec 9, 2022, discovered Nov 16, 2022 — the first regulatory filing landed 133 days later (flagged late). 105,008 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 2 more. Notifications rolled out on a 6-day schedule across 11 filings beginning Mar 29, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
133days

Discovered → first regulatory filing

Discovery variance
105days

Range of discovered_at dates across filings

Filing span
6days

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 clocksCalifornia✗ CA 60-day late · 133dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dMaine✓ ME AG ≤30d · 29dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Jul 13, 2022breach begins
Nov 16, 2022discovered · members disagree
notification delay · 133 days
Mar 29, 2023first filing
Apr 4, 2023most 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. MAR 29ID AGID AG noticefirst filing · 27 ID residentsday 0
  2. MAR 29CA AGCA AG noticeno count statedday 0
  3. MAR 29IN AGIN AG noticestates nationwide total 105,008day 0
  4. MAR 29MT AGMT AG notice437 MT residentsday 0
  5. MAR 29VT AGVT AG noticeno count statedday 0
  6. MAR 30SC AGSC AG notice103 SC residents+1d
  7. MAR 30ME AGME AG noticestates nationwide total 105,008+1d
  8. MAR 30WA AGWA AG notice1,475 WA residents+1d
  9. MAR 30OR AGOR AG noticeno count stated+1d
  10. MAR 30MA AGMA AG notice1,728 MA residents+1d
  11. APR 4OR AGOR AG noticemost recent · states nationwide total 105,008+6d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 13, 2022 – Dec 9, 2022
ID AG
Discovered
Nov 16, 2022ID AG + CA AG + MT AG +3Mar 1, 2023ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
ID AG + CA AG + MT AG +5
Attack vector
Unauthorized Access
ID 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)

105,008

Sum of filed state slices

5,981· 5.7% of stated

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

US105,008
IN1,748
MA1,728
WA1,475
ME463
MT437
SC103
ID27

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 filing11 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 Jun 12, 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

6 days

Cadence

~1 / 0.6d

vs. multi-state median

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