DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed10 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcactushigh sensitivity
Merged incident · 10 filings

Parksite Inc. — December 2023 breach

Clustered 10 filings across 7 jurisdictions · filing window Jan 17, 2024 → Jul 8, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

6

Affected · reported

8,577

First → last filing

Jan 17, 2024 → Jul 8, 2024

Merge confidence

100%

incident inc_9a4a673475f5483a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Dec 25, 2023–Jan 16, 2024, discovered Dec 25, 2023 — the first regulatory filing landed 130 days later (flagged late). 8,577 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 173-day schedule across 9 filings beginning Jan 17, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
130days

Discovered → first regulatory filing

Discovery variance
22days

Range of discovered_at dates across filings

Leak precedence
107days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
173days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 143dVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 25, 2023breach begins
Dec 25, 2023discovered · members disagree
notification delay · 130 days
May 3, 2024first filing
Jul 8, 2024most 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. JAN 17Leak sitecactus postfirst filing · attacker claim · unverifiedday 0
  2. MAY 3VT AGVT AG noticeno count stated+107d
  3. JUN 1IL AGIL AG noticeno count stated+136d
  4. JUN 7ME AGME AG noticestates nationwide total 7,886+142d
  5. JUN 7MA AGMA AG notice255 MA residents+142d
  6. JUN 7IN AGIN AG noticestates nationwide total 8,577+142d
  7. JUN 10NH AGNH AG notice44 NH residents+145d
  8. JUL 2ME AGME AG noticestates nationwide total 8,577+167d
  9. JUL 2VT AGVT AG noticeno count stated+167d
  10. JUL 8NH AGNH AG noticemost recent · 8 NH residents+173d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 25, 2023 – Jan 16, 2024
ME AG
Discovered
Dec 25, 2023IL AGJan 16, 2024ME AG + NH AG + VT AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
VT AG + NH AG + ME AG +1
Attack vector
Unauthorized Access
ME 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)

8,577

Sum of filed state slices

344· 4.0% of stated

96% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US8,577
MA255
NH44
IN37
ME8

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

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
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

173 days

Cadence

~1 / 19.2d

vs. multi-state median

21.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.