Confirmed breach. Intrusion May 27, 2024, discovered May 28, 2024 — the first regulatory filing landed 108 days later (flagged late). 1 individuals reported across the linked filings.
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.
Regulatory clocksMaine✗ ME AG >90d · 108dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
1
Data types
1
Identity (basic)
Jurisdictions
1
ME
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 27, 2024
When the intrusion reportedly occurred, per the linked filings
Ortec, Inc. experienced an external system breach on May 27, 2024, which was discovered the following day. The breach affected 487 individuals in total, including one resident of Maine. The company began notifying affected consumers on September 13, 2024, and is offering 12 months of credit monitoring and identity protection services through IDX.
Affected (this filing): 1
ME AG >90d · 108dME resident >60d · 108d
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.