Clustered 3 filings across 2 jurisdictions · filing window Sep 15, 2023 → Nov 2, 2023. View entity profile → Other incidents for this victim →
incident inc_35a08262efc549ff · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA MT
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
May 23, 2023
When the intrusion reportedly occurred, per the linked filings
May 23, 2023
Reported by CALIFORNIA AG filings
San Francisco Jazz Organization reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-15. The breach occurred on 5/23/2023. 2 Montana residents were affected.
Affected (this filing): 2
San Francisco Jazz Organization experienced a ransomware attack on May 23, 2023, which encrypted critical systems including file servers and backups. Forensic investigation revealed potential access to employee personal information, including names, Social Security Numbers, driver's license numbers, and dates of birth. The organization engaged third-party experts, contained the incident, and implemented enhanced security measures including two-factor authentication and encryption. Affected individuals were offered 12 months of Experian IdentityWorks.
San Francisco Jazz Organization experienced a ransomware attack on May 23, 2023, encrypting critical systems. Forensic investigation revealed potential access to employee personal information, including names, SSNs, and driver's license numbers. The organization engaged third-party experts, contained the incident, and implemented enhanced security measures including MFA and encryption. Affected individuals were offered credit monitoring.
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.