DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed9 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcontihigh sensitivity
Merged incident · 9 filings

Spencer Gifts LLC — November 2021 breach

Clustered 9 filings across 7 jurisdictions · filing window Dec 5, 2021 → Jan 24, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

6

Affected · reported

10,024

First → last filing

Dec 5, 2021 → Jan 24, 2022

Merge confidence

100%

incident inc_76255d801e414d99 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Nov 24, 2021–Nov 26, 2021, discovered Nov 24, 2021 — the first regulatory filing landed 38 days later. 10,024 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 50-day schedule across 8 filings beginning Dec 5, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
38days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Leak precedence
27days 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
50days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 60dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Nov 24, 2021breach begins
Nov 24, 2021discovered · members disagree
notification delay · 38 days
Jan 1, 2022first filing
Jan 24, 2022most 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. DEC 5Leak siteconti postfirst filing · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticeno count stated+27d
  3. JAN 1IL AGIL AG noticeno count stated+27d
  4. JAN 1IL AGIL AG noticeno count stated+27d
  5. JAN 24CA AGCA AG noticeno count stated+50d
  6. JAN 24NH AGNH AG notice75 NH residents+50d
  7. JAN 24ME AGME AG noticestates nationwide total 10,024+50d
  8. JAN 24IN AGIN AG noticestates nationwide total 10,024+50d
  9. JAN 24MT AGMT AG noticemost recent · 50 MT residents+50d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 24, 2021 – Nov 26, 2021
CA AG
Discovered
Nov 24, 2021IL AGNov 25, 2021IL AG + CA AG + NH AG +2filings disagree on discovery
Data types
Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PII
CA AG + NH AG + ME AG +1
Attack vector
Unauthorized Access
NH 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)

10,024

Sum of filed state slices

308· 3.1% of stated

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

US10,024
IN152
NH75
MT50
ME31

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 filing8 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 9, 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

50 days

Cadence

~1 / 6.3d

vs. multi-state median

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