Preferred Parking Service, LLC
ent_0d7fa0ac55310743612f0529
Disclosures
4
State AG · 4 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
5,176
as filed · State AG SC
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Preferred Parking Service, LLC
- Normalized
- preferred parking service— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- preferredparkingsvcs.com
Disclosure history (4)newest first
- South Carolina State AGas victim2026-08-14
Preferred Parking Service, LLC notified consumers that an unauthorized actor accessed its database on June 7-8, 2026, and exfiltrated files containing names and credit card numbers. The company secured its network, conducted an investigation, and implemented additional IT security measures. No specific count of affected individuals was disclosed in the letter, though Rhode Island residents were specifically addressed.
- New Hampshire State AGas victim2026-08-14
Preferred Parking Service, LLC notified the NH Attorney General of unauthorized access to its database on June 7-8, 2026. An external actor accessed and exfiltrated files containing the names and credit card numbers of 26 New Hampshire residents. The company secured its network, investigated the incident, and sent notification letters on August 14, 2026. Additional security measures were implemented.
- Vermont State AGas victim2026-08-14
Preferred Parking Service, LLC reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-08-14. The reporting organization type is Other Commercial. 11 Vermont residents were affected. Categories of data breached: Financial Account Codes, Credit and Debit Account Info.
- Massachusetts State AGas victim2026-08-01
Preferred Parking Service, LLC notified Massachusetts residents of a data security incident involving their names and credit card numbers. The company stated it identified and addressed the incident and implemented additional IT security measures. No specific dates for discovery, occurrence, or notification were provided in the letter. The number of affected individuals was not disclosed.