One linked filing — more sources may join as they report · filed Feb 5, 2025. View entity profile → Other incidents for this victim →
incident inc_03001aced7f7453d · merge_method deterministic
Discovered → first regulatory filing
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.
Identity (basic) · Government ID · Health (basic)
MD
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 20, 2024 → Dec 24, 2024
When the intrusion reportedly occurred, per the linked filings
Dec 24, 2024
Reported by MARYLAND AG filing
Aleto, Inc. notified the Maryland AG of a data event affecting 40 Maryland residents. Between Dec 20-24, 2024, an unauthorized actor accessed an employee device containing PII (names, SSNs, driver's licenses, passports) and health/financial info. Aleto secured the network, investigated, and offered 12 months of credit monitoring. Incident status is contained.
Affected (this filing): 40
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.