Clustered 3 filings across 3 jurisdictions · filing window May 8, 2025 → Sep 26, 2025. View entity profile → Other incidents for this victim →
incident inc_bc58c48ea6634105 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA OR TX
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 29, 2025 → Mar 30, 2025
When the intrusion reportedly occurred, per the linked filings
Mar 29, 2025
Reported by CALIFORNIA AG, TEXAS AG filings
Mar 30, 2025
Reported by OREGON AG filing
Intelliloan, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2025-05-08. The breach occurred during 3/29/2025 - 3/30/2025. The breach was discovered on 3/30/2025. 250 individuals were affected. Notice was sent on 5/8/2025.
Affected (this filing): 250
Intelliloan, Inc., a mortgage lender, detected unauthorized activity on its network on March 29, 2025. The incident potentially compromised personal information of customers and employees, including names and other data elements. The company secured the compromise, engaged third-party experts, and collaborated with law enforcement. Affected individuals are offered complimentary credit monitoring and identity restoration services.
Intelliloan, Inc. based in Irvine, California, a financial services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-03-29 and reported on 2025-09-26. 389 Texas residents were affected. 6,071 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Medical Information;Date of Birth. Consumers were notified via U.S. Mail.
Affected (this filing): 389
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.