Confirmed breach. discovered May 30, 2025 — the first regulatory filing landed 158 days later (flagged late). 1,000 individuals reported across the linked filings.
incident inc_4df40fdeaf6b455c · merge_method human · confidence 100%
Litigation Timing
Notification delay
158days
Discovered → first regulatory filing
Leak precedence
176days
Gap between first leak claim and first regulatory filing
Filing span
Regulatory clocksTexas✗ TX AG >30dFull clock table in Litigation Timeline
Leak SiteState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedworldleaks
176days
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)
1,000
Data types
—
Jurisdictions
2
TX
Linked filings
2
Leak Site · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
J-Kraft, Inc. is a manufacturing company based in Houston, Texas. They produce high-quality, custom-made doors and millwork for both residential and commercial applications. Since 1990, they've combined advanced technology with skilled artisanship to deliver superior products. They value customer satisfaction, quality craftsmanship, and attention to detail.
Breach discoveredAG web form
May 30, 2025
Reported by TEXAS AG filing
158 days
⭐Texas State AGMost recentLeaked → filing gap · 6 molinked via shared-victim match · 100%
J-Kraft, Inc based in Humble, Texas, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-05-30 and reported on 2025-11-04. 1,000 Texas residents were affected. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Other. Consumers were notified via U.S. Mail.
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.