DisclosureLens
State AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

SMITH GAMBRELL & RUSSELL LLP — July 2021 breach

Clustered 6 filings across 5 jurisdictions · filing window Jun 28, 2022 Mar 1, 2023. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

19,322

First → last filing

Jun 28, 2022 Mar 1, 2023

Merge confidence

100%

incident inc_6a2d7ffe0aec469c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Jul 19, 2021–Aug 9, 2021, discovered Aug 9, 2021 — the first regulatory filing landed 323 days later (flagged late). 19,322 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 246-day schedule across 6 filings beginning Jun 28, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
323days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
246days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >90d · 323dWashington WA AG >90dVermont VT AG >45 bdayCalifornia CA 60-day late · 491dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 19, 2021breach begins
Aug 9, 2021discovered
notification delay · 323 days
Jun 28, 2022first filing
Mar 1, 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. JUN 28ME AGME AG noticefirst filing · states nationwide total 6,515day 0
  2. JUN 28MT AGMT AG notice21 MT residentsday 0
  3. AUG 8ME AGME AG noticestates nationwide total 19,322+41d
  4. DEC 13WA AGWA AG notice516 WA residents+168d
  5. JAN 27VT AGVT AG noticeno count stated+213d
  6. MAR 1CA AGCA AG noticemost recent · no count stated+246d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 9, 2021
ME AG
Discovered
Aug 9, 2021
ME AG + MT AG + WA AG +2
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + MT AG + WA AG +2
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)

19,322

Sum of filed state slices

545· 2.8% of stated

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

US19,322
WA516
MT21
ME8

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

246 days

Cadence

~1 / 49.2d

vs. multi-state median

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