DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed5 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Park'N Fly — November 2013 breach

Clustered 5 filings across 4 jurisdictions · filing window Dec 30, 2014 → Jan 20, 2015. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

1,134

First → last filing

Dec 30, 2014 → Jan 20, 2015

Merge confidence

100%

incident inc_49d5c230a8e94e33 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Nov 27, 2013–Dec 24, 2014, discovered Sep 1, 2014 — the first regulatory filing landed 120 days later. 1,134 individuals reported across the linked filings. Data reported: Financial account, PII, Financial credentials, and 3 more. Notifications rolled out on a 21-day schedule across 5 filings beginning Dec 30, 2014. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
120days

Discovered → first regulatory filing

Discovery variance
134days

Range of discovered_at dates across filings

Filing span
21days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Sensitive data

financial_credentials

Incident timeline

Nov 27, 2013breach begins
Sep 1, 2014discovered · members disagree
notification delay · 120 days
Dec 30, 2014first filing
Jan 20, 2015most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. DEC 30NH AGNH AG noticefirst filing · no count statedday 0
  2. JAN 13CA AGCA AG noticeno count stated+14d
  3. JAN 20MA AGMA AG notice396 MA residents+21d
  4. JAN 20SC AGSC AG notice738 SC residents+21d
  5. JAN 20NH AGNH AG noticemost recent · no count stated+21d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 27, 2013 – Dec 24, 2014
SC AG
Discovered
Sep 1, 2014NH AGJan 13, 2015SC AGfilings disagree on discovery
Data types
Credentials · Financial account · Financial credentials · Identity (basic) · PCI · PII
NH AG + CA AG + MA AG +1
Attack vector
Unauthorized Access
NH AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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

21 days

Cadence

~1 / 5.3d

vs. multi-state median

2.6× slower

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.