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

Creative Services, Inc. — November 2021 breach

Clustered 15 filings across 9 jurisdictions · filing window Feb 1, 2022 → May 6, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

9

Affected · reported

165,226

First → last filing

Feb 1, 2022 → May 6, 2022

Merge confidence

100%

incident inc_4bcee096b84c45e9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. The filings describe unauthorized access. Intrusion Nov 23, 2021, discovered Nov 26, 2021 — the first regulatory filing landed 67 days later. 165,226 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 94-day schedule across 15 filings beginning Feb 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
67days

Discovered → first regulatory filing

Discovery variance
60days

Range of discovered_at dates across filings

Filing span
94days

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 clocksMaine⏱ ME AG >30d · 83dWashington⏱ WA AG >30dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Nov 23, 2021breach begins
Nov 26, 2021discovered · members disagree
notification delay · 67 days
Feb 1, 2022first filing
May 6, 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. FEB 1IN AGIN AG noticefirst filing · states nationwide total 164,673day 0
  2. FEB 1ME AGME AG noticestates nationwide total 456day 0
  3. FEB 7NH AGNH AG notice3 NH residents+6d
  4. FEB 23CA AGCA AG noticeno count stated+22d
  5. FEB 23OR AGOR AG noticestates nationwide total 164,673+22d
  6. FEB 23MA AGMA AG notice79,943 MA residents+22d
  7. FEB 23MT AGMT AG notice53 MT residents+22d
  8. FEB 23WA AGWA AG notice1,311 WA residents+22d
  9. FEB 23ME AGME AG noticestates nationwide total 164,673+22d
  10. FEB 24SC AGSC AG notice1,246 SC residents+23d
  11. FEB 28NH AGNH AG notice5,891 NH residents+27d
  12. APR 18CA AGCA AG noticeno count stated+76d
  13. APR 18ME AGME AG noticestates nationwide total 165,226+76d
  14. APR 22NH AGNH AG notice5,900 NH residents+80d
  15. MAY 6NH AGNH AG noticemost recent · 18 NH residents+94d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 23, 2021
IN AG
Discovered
Nov 26, 2021NH AG + CA AG + MT AG +2Jan 21, 2022ME AGJan 25, 2022OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PII
ME AG + NH AG + CA AG +4
Attack vector
Unauthorized Access
ME 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)

165,226

Sum of filed state slices

91,299· 55.3% of stated

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

US165,226
MA79,943
NH5,900
ME2,062
WA1,311
SC1,246
IN784
MT53

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

94 days

Cadence

~1 / 6.7d

vs. multi-state median

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