Prosper Marketplace, Inc.

ent_adb38792d0ee9567e5cf55c9

Compliance scorecard →🔔 Follow entity

Disclosures

State AG · 4 jurisdictions

Incidents

filings grouped by incident

Max affected reported

13,076,476

as filed · State AG OR

Leak-site claims

none in sample

◈ All 4 filings merge into one incident.View incident →

Identity resolution

Canonical name: Prosper Marketplace, Inc.
Normalized: prosper marketplace— dedupe via name-norm; Microsoft / MSFT collapse to one row
GLEIF LEI: No match
SEC EDGAR CIK: None — not an SEC registrant
Domain: None on record

Disclosure history (4)newest first

⭐Texas State AGas victim2025-12-10
Prosper Marketplace, Inc based in San Francisco, California, a financial services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-09-01 and reported on 2025-12-10. 1,161,581 Texas residents were affected. 13,076,476 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Date of Birth. Consumers were notified via Posted at company website or special website;U.S. Mail;Email.
🌲Washington State AGas victim2025-12-09
Prosper Marketplace, Inc, a finance sector entity reported a other incident to the Washington Attorney General. The organization became aware of the incident on 2025-09-01 and filed notice on 2025-12-09. 249,848 Washington residents were affected. 99 days elapsed between awareness and notification. 125 days to identify the breach. 1 days to contain the breach.
🌽Iowa State AGas victim2025-12-09
Prosper Marketplace, Inc., a financial services sector entity reported a data breach to the Iowa Attorney General. The breach was reported on 2025-12-09.
🦫Oregon State AGas victim2025-12-09
Prosper Marketplace, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2025-12-09. The breach occurred during 4/29/2025 - 9/2/2025. The breach was discovered on 9/1/2025. 13,076,476 individuals were affected. Notice was sent on 12/9/2025.