Clustered 2 filings across 2 jurisdictions · filing window Sep 5, 2023 → Sep 6, 2023. View entity profile → Other incidents for this victim →
incident inc_9c206a2f754c489c · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME OR
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
Feb 28, 2023 → Jul 2, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 21, 2023
Reported by OREGON AG, MAINE AG filings
Vivendi Ticketing US LLC d/b/a See Tickets reported a data breach to the Oregon Attorney General. The breach was reported on 2023-09-05. The breach occurred during 2/28/2023 - 7/2/2023. The breach was discovered on 7/21/2023. 323,498 individuals were affected. Notice was sent on 9/5/2023.
Affected (this filing): 323,498
Vivendi Ticketing US LLC, operating as See Tickets, reported an external system breach that occurred on February 28, 2023, and was discovered on July 21, 2023. The breach resulted in the compromise of names and financial account or card numbers along with their security codes or PINs. A total of 323,498 individuals were affected, including 559 Maine residents. Affected individuals were notified on September 5, 2023, and offered 12 months of credit monitoring and identity theft protection services from Kroll.
Affected (this filing): 559
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.