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

SmartStart Employment Screening, Inc. — May 2020 breach

Clustered 9 filings across 9 jurisdictions · filing window Jan 1, 2021 → Aug 27, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

75,103

First → last filing

Jan 1, 2021 → Aug 27, 2021

Merge confidence

100%

incident inc_a81d7107b49a4e07 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion May 13, 2020, discovered Dec 18, 2020 — the first regulatory filing landed 14 days later (flagged late). 75,103 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 238-day schedule across 9 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
14days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
238days

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 clocksWashington✗ WA AG >90dMaine✗ ME AG >90d · 252dCalifornia✗ CA 60-day late · 249dSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 13, 2020breach begins
Dec 18, 2020discovered
notification delay · 14 days
Jan 1, 2021first filing
Aug 27, 2021most 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 1IL AGIL AG noticefirst filing · no count statedday 0
  2. AUG 24WA AGWA AG notice639 WA residents+235d
  3. AUG 24NH AGNH AG notice181 NH residents+235d
  4. AUG 24IN AGIN AG noticestates nationwide total 75,103+235d
  5. AUG 24MT AGMT AG notice81 MT residents+235d
  6. AUG 25SC AGSC AG notice4,465 SC residents+236d
  7. AUG 27ME AGME AG noticestates nationwide total 75,103+238d
  8. AUG 27CA AGCA AG noticeno count stated+238d
  9. AUG 27MA AGMA AG noticemost recent · 962 MA residents+238d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 13, 2020
IN AG
Discovered
Dec 18, 2020· 219d undetected
IL AG + WA AG + NH AG +4
Data types
Identity (basic) · Government ID · PII
WA AG + NH AG + MT AG +4
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)

75,103

Sum of filed state slices

7,979· 10.6% of stated

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

US75,103
SC4,465
IN1,528
MA962
WA639
NH181
ME123
MT81

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

238 days

Cadence

~1 / 29.8d

vs. multi-state median

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