Public case informationLast updated

SitusAMC Data Breach Settlement

SitusAMC · Data security and protection of personal information · Settlement Reached

About this case

A class action filed in the U.S. District Court for the Southern District of New York alleged that SitusAMC failed to adequately protect personal information exposed in a November 2025 data breach, potentially including names, taxpayer identification numbers, and financial account information. SitusAMC agreed to a $5.3 million settlement while denying wrongdoing; claims are due November 6, 2026.

Case overview

Defendant company
SitusAMC
Product or service
Data security and protection of personal information
Court case number
1:25-cv-9748
Case status
Settlement Reached
Lawsuit type
Privacy
Reported harm
Data Breach

Important dates

SitusAMC Data Breach Settlement Claim

Participation information

SitusAMC Data Breach Settlement Claim

U.S. residents who were sent notice that their personal information was involved in the SitusAMC data incident occurring on or about November 12, 2025, are generally included. Exclusions include SitusAMC's executive leadership team, the assigned judge, the judge's immediate family and court staff, and people who validly opt out.

Submit a claim by November 6, 2026. Documented out-of-pocket losses require supporting documentation such as bank statements or receipts; a $75 payment is available without proof according to the settlement terms.

Type
Settlement Claim
Status
Open
Total settlement amount
$5,300,000
Amount per claim
$75
Payout
Eligible class members may receive one year of credit monitoring automatically. Claimants may seek reimbursement of documented, unreimbursed out-of-pocket losses up to $5,000.00 with third-party documentation, or elect a flat cash payment estimated at $75.00 that may be higher or lower depending on the number of valid claims. California residents who lived in California from 2025-11-12 through 2025-11-22 may also elect a $50.00 statutory payment, subject to possible pro rata reduction.
Reported proof requirement
Unclear

Sources