Soapy Joes Car Wash reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-06 and was reported on 2025-12-29. 1 Indiana residents were affected. 3,769 individuals affected in total.
Affected (this filing): 3,769
Clustered 2 filings across 2 jurisdictions · filed Dec 29, 2025. View entity profile → Other incidents for this victim →
incident inc_a013e5c087cf41a2 · 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
CA IN
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 6, 2025
When the intrusion reportedly occurred, per the linked filings
Oct 6, 2025
Reported by CALIFORNIA AG filing
Soapy Joes Car Wash reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-06 and was reported on 2025-12-29. 1 Indiana residents were affected. 3,769 individuals affected in total.
Affected (this filing): 3,769
Soapy Joe’s Car Wash reported a data security incident discovered on October 6, 2025, involving unusual activity on its corporate network. An unauthorized actor may have obtained data including names and other personal information. The company secured the network, launched an investigation, and implemented additional security measures. Affected individuals were offered complimentary identity protection services through Experian.
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.