Preferred Parking Service, LLC — June 2026 breach
Clustered 5 filings across 5 jurisdictions · filed Aug 14, 2026 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_9cb997210a8449be · merged by deterministic · confidence 100%
Litigation Timing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing about this breach
- AUG 1MA AGMA AG noticefiling day not on record · 142 MA residentsauto-linked—
- AUG 14SC AGSC AG noticefirst filing · 5,176 SC residentsday 0
- AUG 14NH AGNH AG notice26 NH residentsauto-linkedday 0
- AUG 14VT AGVT AG notice11 VT residentsauto-linkedday 0
- AUG 14IN AGIN AG noticemost recent · states nationwide total 72,912auto-linkedday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jun 7, 2026 – Jun 8, 2026 SC AG
- Discovered
- —
- Data types
- Financial account · Identity (basic) · PCI MA AG + SC AG + NH AG +1
- Attack vector
- Unauthorized Access SC AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
72,912
Sum of filed state slices
5,447· 7.5% of stated
93% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
0 days
Cadence
~1 / 0d
vs. multi-state median
20.0× faster
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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.