Port Orford-Langlois SD 2CJ — December 2024 breach
One linked filing — more sources may join as they report · filed Apr 3, 2025. View entity profile → Other incidents for this victim →
incident inc_1f51503f33ae4355 · merged by deterministic
Litigation Timing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Sensitive data
identity_governmentIncident timeline
No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.
Member cascade — every filing about this breach
- APR 3VT AGVT AG noticeonly filing · no count statedday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Dec 21, 2024 VT AG
- Discovered
- —
- Data types
- Identity (basic) · Government ID · Financial account · Employment · PHI VT AG
- Response
- Began working with third-party specialists to investigate the activity · Notified the Federal Bureau of Investigation · Offering complimentary credit monitoring and identity theft protection services through IDX VT 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
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.