Growth Builders, LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2023-12-05 and was reported on 2024-07-15. 1 Indiana residents were affected. 466 individuals affected in total.
Affected (this filing): 466
Clustered 2 filings across 2 jurisdictions · filing window Jul 15, 2024 → Jul 18, 2024. View entity profile → Other incidents for this victim →
incident inc_c5a1a1086b7349a6 · 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.
PII · Identity (basic)
IN VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 5, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 5, 2023
Reported by VERMONT AG filing
Growth Builders, LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2023-12-05 and was reported on 2024-07-15. 1 Indiana residents were affected. 466 individuals affected in total.
Affected (this filing): 466
Growth Builders LLC notified consumers of a data breach involving its third-party IT provider, HRTec. Suspicious activity was identified on December 5, 2023. An unauthorized actor accessed network information. Data involved names and unspecified data elements. Growth engaged forensic specialists, secured its environment, and 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.