Pond & Company reported a data breach to the Indiana Attorney General. The breach occurred on 2023-03-29 and was reported on 2024-02-15. 8 Indiana residents were affected. 1,495 individuals affected in total.
Affected (this filing): 1,495
Clustered 2 filings across 2 jurisdictions · filing window Feb 15, 2024 → Feb 19, 2024. View entity profile → Other incidents for this victim →
incident inc_2018b28749744c4c · 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.
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 29, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 24, 2023
Reported by MAINE AG filing
Pond & Company reported a data breach to the Indiana Attorney General. The breach occurred on 2023-03-29 and was reported on 2024-02-15. 8 Indiana residents were affected. 1,495 individuals affected in total.
Affected (this filing): 1,495
Pond & Company, a professional services firm based in Georgia, reported an external system breach (hacking) occurring between March 29, 2023, and April 5, 2023. The breach was discovered on December 24, 2023. The incident affected a total of 1,495 individuals, including 2 Maine residents. The attacker acquired names and personal identifiers in combination with driver's license numbers. Pond & Company sent written notifications on February 14, 2024, and offered 12 months of credit monitoring and identity theft protection services through Kroll.
Affected (this filing): 1,495
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.