Squire & Co. — January 2026 breach
One linked filing — more sources may join as they report · filed Mar 30, 2026. View entity profile → Other incidents for this victim →
incident inc_f54b395c3b3b4895 · 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.
Incident 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
- MAR 30ID AGID AG noticeonly filing · 3 ID residentsday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jan 1, 2026 ID AG
- Discovered
- —
- Data types
- Identity (basic) · Government ID ID AG
- Attack vector
- Misconfiguration ID AG
- Response
- Reviewed its mailing procedures to address the envelope alignment issue · Established a toll-free call center through IDX · Providing complimentary identity protection services to notified individuals ID 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.