Confirmed breach. Intrusion Apr 7, 2023–Apr 8, 2023, discovered Apr 8, 2023 — the first regulatory filing landed 109 days later (flagged late). 3 individuals reported across the linked filings.
incident inc_6120743328774738 · merge_method human · confidence 100%
Litigation Timing
Notification delay
109days
Discovered → first regulatory filing
Leak precedence
109days
Gap between first leak claim and first regulatory filing
Filing span
Regulatory clocksCalifornia✗ CA 60-day late · 109dFull clock table in Litigation Timeline
Leak SiteState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3
109days
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Affected (total reported)
3
Data types
—
Jurisdictions
2
CA
Linked filings
2
Leak Site · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 7, 2023 → Apr 8, 2023
When the intrusion reportedly occurred, per the linked filings
Bayside started in 1984 as a Northern California family owned and operated business, offering services in Southern California since 2006. Nearly 40 years later, we have proudly grown to serve customers across the nation and around the globe. Headquar...
109 days
🐻California State AGMost recentLeaked → filing gap · 4 molinked via operator-confirmed · 100%
Bayside Interiors, Inc. reported a network security incident discovered on April 8, 2023. Unauthorized access or acquisition of files containing full names and Social Security numbers occurred between April 7 and April 8, 2023. The incident affected 3 Rhode Island residents. The company engaged external cybersecurity professionals and is providing credit monitoring and fraud assistance services.
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.