Clustered 2 filings across 2 jurisdictions · filed Nov 4, 2025. View entity profile → Other incidents for this victim →
incident inc_1ef9284bd6e6430a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
ME NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 5, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 5, 2025
Reported by MAINE AG, NEW HAMPSHIRE AG filings
Money Matters, a financial services company, reported a data breach that occurred and was discovered on July 5, 2025. The breach was an external system breach (hacking) and affected 2 Maine residents. The company provided 24 months of credit and CyberScan monitoring through IDX.
Affected (this filing): 2
Money Matters of Tampa reported a data breach discovered on July 5, 2025, where an unauthorized outside party accessed client data on a limited part of their server. Approximately 1,573 individuals were affected, including 2 New Hampshire residents. The compromised data included names, addresses, dates of birth, and a small number of Social Security numbers and driver's license numbers. Money Matters engaged forensic investigators, implemented additional security safeguards, and is offering 24 months of free identity theft protection services through IDX to affected individuals.
Affected (this filing): 1,573
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.