Clustered 2 filings across 2 jurisdictions · filing window May 1, 2026 → May 5, 2026. View entity profile → Other incidents for this victim →
incident inc_f8eaae9e0dd34c45 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
Government ID · Identity (basic)
MA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 25, 2025 → Feb 18, 2026
When the intrusion reportedly occurred, per the linked filings
Apr 16, 2026
Reported by MAINE AG filing
Radial Entertainment notified Massachusetts residents of a data breach involving names and Social Security numbers. The company arranged for 24 months of complimentary identity monitoring services through Epiq and enhanced security protocols. The incident involved unauthorized access to personal data.
Radial Entertainment reported a data breach to the Maine Attorney General. The incident was described as an external system breach (hacking) occurring between November 25, 2025 and February 18, 2026, discovered on April 16, 2026. A total of 182 persons were affected, including 2 Maine residents. Written notification was sent on May 5, 2026, and one year of credit monitoring and identity theft protection services through Epiq was offered. The specific data elements compromised were not disclosed in the Maine AG submission form.
Affected (this filing): 182
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.