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

City of Saco, Maine — March 2026 breach

Clustered 2 filings across 2 jurisdictions · filing window Jul 7, 2026 → Jul 15, 2026. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge95%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

23

First → last filing

Jul 7, 2026 → Jul 15, 2026

Merge confidence

95%

incident inc_f573323c88144b01 · merged by deterministic · confidence 95%

Confirmed breach. One breach, 2 legal records. Intrusion Mar 16, 2026–Mar 31, 2026, discovered Apr 30, 2026 — the first regulatory filing landed 68 days later. 23 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
68days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

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

Mar 16, 2026breach begins
Apr 30, 2026discovered
notification delay · 68 days
Jul 7, 2026first filing
Jul 15, 2026most 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. JUL 7NE AGNE AG noticefirst filing · 1 NE residentsday 0
  2. JUL 15NH AGNH AG noticemost recent · 22 NH residents+8d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 16, 2026 – Mar 31, 2026
NE AG
Discovered
Apr 30, 2026· 45d undetected
NE AG + NH AG
Data types
Identity (basic) · Government ID
NE AG + NH AG
Attack vector
Misconfiguration
NE AG
Response
Removed the dispatch logs from its website · Began an investigation · Notified potentially impacted individuals
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.95 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (95% is the strongest edge).

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

Filing velocity

Spread

8 days

vs. multi-state median

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