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

GC Services — September 2023 breach

Clustered 11 filings across 6 jurisdictions · filing window Jan 25, 2024 → Feb 22, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

6

Affected · reported

3,043

First → last filing

Jan 25, 2024 → Feb 22, 2024

Merge confidence

100%

incident inc_9716bd7b48264861 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Sep 11, 2023–Sep 20, 2023, discovered Dec 26, 2023 — the first regulatory filing landed 30 days later. 3,043 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 28-day schedule across 11 filings beginning Jan 25, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
30days

Discovered → first regulatory filing

Discovery variance
21days

Range of discovered_at dates across filings

Filing span
28days

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 · 36dMassachusetts✓ MA credit monitoring dueVermont✓ VT AG ≤14 bdayFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Sep 11, 2023breach begins
Dec 26, 2023discovered · members disagree
notification delay · 30 days
Jan 25, 2024first filing
Feb 22, 2024most 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. JAN 25MT AGMT AG noticefirst filing · 10 MT residentsday 0
  2. JAN 25MA AGMA AG notice11 MA residentsday 0
  3. JAN 25IN AGIN AG noticestates nationwide total 3,043day 0
  4. JAN 25ME AGME AG noticestates nationwide total 180day 0
  5. JAN 25NH AGNH AG notice1 NH residentsday 0
  6. JAN 30ME AGME AG noticestates nationwide total 2,824+5d
  7. JAN 30NH AGNH AG notice1 NH residents+5d
  8. JAN 30VT AGVT AG noticeno count stated+5d
  9. JAN 31MA AGMA AG notice42 MA residents+6d
  10. FEB 21ME AGME AG noticestates nationwide total 3,043+27d
  11. FEB 22MA AGMA AG noticemost recent · 59 MA residents+28d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 11, 2023 – Sep 20, 2023
MT AG
Discovered
Dec 26, 2023MT AG + ME AG + NH AGJan 16, 2024ME AG + NH AG + VT AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PII
MT AG + ME AG + NH 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)

3,043

Sum of filed state slices

113· 3.7% of stated

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

US3,043
MA59
IN30
ME13
MT10
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 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
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

28 days

Cadence

~1 / 2.8d

vs. multi-state median

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