STANDARD SALES COMPANY, L.P.
ent_019ebd3553e044932e7a5b06c3b1fa79
Disclosures
5
State AG · 4 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
4,321
nationwide · State AG TX
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- STANDARD SALES COMPANY, L.P.
- Normalized
- standard sales— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- 48LE3KK36KYT06NUYM15
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (5)newest first
- Texas State AGas victim2026-01-09
Standard Sales Company, LP based in Odessa, Texas, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-12-11 and reported on 2026-01-09. 1,877 Texas residents were affected. 4,321 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Driver’s License number. Consumers were notified via U.S. Mail.
- Indiana State AGas victim2026-01-08
Standard Sales Company LP reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-07 and was reported on 2026-01-08. 19 Indiana residents were affected. 4,321 individuals affected in total.
- Montana State AGas victim2026-01-08
Standard Sales Company, LP notified Montana residents of unauthorized access to systems between Oct 7-8, 2025. Personal information was accessed. The company secured systems, notified law enforcement, and offers credit monitoring via Epiq. Investigation determined personal info was present in affected files.
- Indiana State AGas victim2026-01-08
Standard Sales Company LP reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-07 and was reported on 2026-01-08. 19 Indiana residents were affected. 4,321 individuals affected in total.
- Nebraska State AGas victim2026-01-08
Standard Sales Company, LP reported unauthorized access to files containing names, SSNs, and driver's license numbers between Oct 7-8, 2025. The company discovered the breach on Oct 8, 2025, and began notifying 2 Nebraska residents on Jan 8, 2026. Response included law enforcement notification, credit monitoring via Epiq, and policy reviews.