All incidents View linkage analytics →Get the evidence package — $79

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedlow sensitivity

Merged incident · 3 filings

Sullivan Environmental Services

Clustered 3 filings across 3 jurisdictions · filed Jul 31, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

First → last filing

Jul 31, 2026

Merge confidence

100%

incident inc_e3fa18636a1b40e9 · merged by deterministic · confidence 100%

Confirmed breach. One breach, 3 legal records. discovered Jul 28, 2026 — the first regulatory filing landed 3 days later. 8 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

3days

Discovered → first regulatory filing

Discovery variance

1days

Range of discovered_at dates across filings

Filing span

0days

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 clocksMassachusetts✓ MA AG ≤30dFull clock table in Litigation Timeline

Incident timeline

? — ?breach window unknown

Jul 28, 2026discovered · members disagree

notification delay · 3 days

Jul 31, 2026first filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

JUL 31NH AGNH AG noticefirst filing · 1 NH residentsauto-linkedday 0
JUL 31MA AGMA AG notice7 MA residentsday 0
JUL 31NE AGNE AG noticemost recent · 1 NE residentsauto-linkedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: —
Discovered: Jul 28, 2026MA AG + NE AGJul 29, 2026NH AGfilings disagree on discovery
Data types: Identity (basic)
Response: Engaged cybersecurity specialists to conduct a thorough review of the affected data · Notified the identified individual · Provided them with steps they can take to protect their personal information

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

Affected residents by state

per-state reported counts

MA7

NH1

NE1

State AGs report only their own residents; teal bars show each state's reported slice.

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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.