DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 2 filings

Outsource Orlando

Clustered 2 filings across 1 jurisdiction · filing window Sep 22, 2020 → Sep 28, 2020. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge92%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

4

First → last filing

Sep 22, 2020 → Sep 28, 2020

Merge confidence

92%

incident inc_f7cc55e04a5a4a80 · merged by deterministic · confidence 92%

Confirmed breach. One breach, 2 legal records. discovered Aug 24, 2020 — the first regulatory filing landed 29 days later. 4 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
29days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
6days

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.

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown
Aug 24, 2020discovered
notification delay · 29 days
Sep 22, 2020first filing
Sep 28, 2020most 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. SEP 22NH AGNH AG noticefirst filing · 4 NH residentsday 0
  2. SEP 28NH AGNH AG noticemost recent · 4 NH residents+6d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
Aug 24, 2020
NH AG
Data types
Identity (basic) · Government ID · Credentials
NH AG
Attack vector
Ransomware
NH AG
Response
Engaged a cybersecurity firm to assist us · Contacted law enforcement · Notified the Seminole County Sheriff’s Office
NH AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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 filing2 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
0.92 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (92% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

6 days

vs. multi-state median

1.2× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.