Confirmed breach. Intrusion Jun 18, 2025–Jun 21, 2025, discovered Aug 6, 2025 — the first regulatory filing landed 9 days later. 2,163 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✓ ME AG ≤30d · 9dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
2,163
Data types
—
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 18, 2025 → Jun 21, 2025
When the intrusion reportedly occurred, per the linked filings
Ojo Caliente Holdings, Inc. reported an external system breach that occurred from June 18, 2025, to June 21, 2025. The breach was discovered on August 6, 2025. Two Maine residents were affected. Notification letters were sent to affected individuals on August 15, 2025, and 12 months of identity theft protection services were offered.
Affected (this filing): 2
ME AG ≤30d · 9d
🏎️Indiana State AGMost recentlinked via multistate filing link · 100%
Ojo Caliente Holding Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-06-18 and was reported on 2025-08-15. 1 Indiana residents were affected. 2,163 individuals affected in total.
Affected (this filing): 2,163
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.