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

City of Torrance — March 2020 breach

Clustered 8 filings across 7 jurisdictions · filing window Mar 1, 2020 → Oct 21, 2020. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

7,670

First → last filing

Mar 1, 2020 → Oct 21, 2020

Merge confidence

100%

incident inc_b4287f1c6b6447b3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. Intrusion Mar 1, 2020, discovered Mar 1, 2020 — the first regulatory filing landed 78 days later (flagged late). 7,670 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 234-day schedule across 7 filings beginning Mar 1, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
78days

Discovered → first regulatory filing

Discovery variance
51days

Range of discovered_at dates across filings

Leak precedence
78days 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
234days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✗ CA 60-day late · 75dLeak gap✗ Leak >180dMaine✗ ME AG >90d · 180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 1, 2020breach begins
Mar 1, 2020discovered · members disagree
notification delay · 78 days
May 18, 2020first filing
Oct 21, 2020most 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 1Leak sitedoppelpaymer postfirst filing · attacker claim · unverifiedday 0
  2. MAY 18CA AGCA AG noticeno count stated+78d
  3. MAY 20MA AGMA AG notice4 MA residents+80d
  4. OCT 13IN AGIN AG noticestates nationwide total 7,670+226d
  5. OCT 13MT AGMT AG notice8 MT residents+226d
  6. OCT 18CA AGCA AG noticeno count stated+231d
  7. OCT 18ME AGME AG noticestates nationwide total 7,670+231d
  8. OCT 21NH AGNH AG noticemost recent · 1 NH residents+234d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 1, 2020
CA AG
Discovered
Mar 1, 2020CA AG + MT AG + NH AGApr 21, 2020ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
CA AG + MT AG + ME AG +2
Attack vector
Unauthorized Access
MT 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)

7,670

Sum of filed state slices

17· 0.2% of stated

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

US7,670
MT8
MA4
IN3
ME1
NH1

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 filing7 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

234 days

Cadence

~1 / 33.4d

vs. multi-state median

26.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.