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

Aqua-Aston Hospitality — August 2016 breach

Clustered 5 filings across 5 jurisdictions · filing window Jul 6, 2017 → Jul 14, 2017. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

1,149

First → last filing

Jul 6, 2017 → Jul 14, 2017

Merge confidence

100%

incident inc_699135bcfec54dcb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe hacking. Intrusion Aug 10, 2016–Mar 9, 2017, discovered Jun 8, 2017 — the first regulatory filing landed 28 days later. 1,149 individuals reported across the linked filings. Data reported: PCI, Financial account, PII, and 2 more. Notifications rolled out on a 8-day schedule across 5 filings beginning Jul 6, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
28days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

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.

Regulatory clocksHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Aug 10, 2016breach begins
Jun 8, 2017discovered
notification delay · 28 days
Jul 6, 2017first filing
Jul 14, 2017most 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. JUL 6MT AGMT AG noticefirst filing · 20 MT residentsday 0
  2. JUL 6NH AGNH AG notice10 NH residentsday 0
  3. JUL 7HI AGHI AG notice1,056 HI residents+1d
  4. JUL 10MA AGMA AG notice63 MA residents+4d
  5. JUL 14CA AGCA AG noticemost recent · no count stated+8d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 10, 2016 – Mar 9, 2017
MT AG
Discovered
Jun 8, 2017· 302d undetected
MT AG + NH AG + HI AG
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
MT AG + MA AG + NH AG +2
Attack vector
Unauthorized Access
MT AG

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

Affected residents by state

per-state reported counts

HI1,056
MA63
MT20
NH10

State AGs report only their own residents; teal bars show each state's reported slice.

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

8 days

Cadence

~1 / 2d

vs. multi-state median

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