Confirmed breach. Intrusion Dec 25, 2025–Dec 26, 2025, discovered Dec 26, 2025 — the first regulatory filing landed 161 days later (flagged late). 76,781 individuals reported across the linked filings.
The LGBTQ Center OC was established as a volunteer organization in 1971 and incorporated in 1975 as a 501(c)(3) non-profit community-based organization.
The Center provides services to more than 20,000 individuals annually across a broad spectrum of culture, ethnicity, age, and economic background.
We will publish all the information next week.
128 days
🐻CALIFORNIAHHS OCRLeaked → filing gap · 4 molinked via same-victim cross-source · 100%
Gay & Lesbian Community Services Center of Orange County, Inc. (a California Healthcare Provider) reported a Hacking/IT Incident on 06/05/2026 affecting 75,532 individuals. The breach involved unauthorized access to a network server. No business associate was involved.
🌲Washington State AGLeaked → filing gap · 4 molinked via same-victim cross-source · 100%
Gay & Lesbian Community Services Center of Orange County Inc, a non-profit/charity sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-12-26 and filed notice on 2026-06-05. 1,249 Washington residents were affected. 161 days elapsed between awareness and notification. 1 days to identify the breach. 0 days to contain the breach.
Affected (this filing):
🐻California State AGMost recentLeaked → filing gap · 4 molinked via same-victim cross-source · 100%
Gay & Lesbian Community Services Center of Orange County, Inc. reported a data security breach occurring December 25-26, 2025. The incident involved unauthorized access to personal information, including names and government identifiers. The organization offered complimentary credit monitoring and established a toll-free response line for affected individuals.
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.