DisclosureLens
State AGConfirmed7 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

Trusted Tours & Attractions, LLC — March 2019 breach

Clustered 7 filings across 7 jurisdictions · filing window Jul 29, 2019 Jul 30, 2019. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

50,743

First → last filing

Jul 29, 2019 Jul 30, 2019

Merge confidence

100%

incident inc_31e5f7b94bcc458a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe hacking. Intrusion Mar 24, 2019–Jun 27, 2019, discovered Jun 25, 2019 — the first regulatory filing landed 34 days later. 50,743 individuals reported across the linked filings. Data reported: PII, Identity (basic), Financial account, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
34days

Discovered → first regulatory filing

Discovery variance
7days

Range of discovered_at dates across filings

Filing span
1days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon OR AG ≤45dSouth Carolina SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Mar 24, 2019breach begins
Jun 25, 2019discovered · members disagree
notification delay · 34 days
Jul 29, 2019first filing
Jul 30, 2019most 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 29MT AGMT AG noticefirst filing · 79 MT residentsday 0
  2. JUL 29WA AGWA AG notice706 WA residentsday 0
  3. JUL 29CA AGCA AG noticeno count statedday 0
  4. JUL 29MA AGMA AG notice1,394 MA residentsday 0
  5. JUL 29OR AGOR AG noticestates nationwide total 50,743day 0
  6. JUL 30SC AGSC AG notice1,080 SC residents+1d
  7. JUL 30NH AGNH AG noticemost recent · 285 NH residents+1d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 24, 2019Jun 27, 2019
MT AG
Discovered
Jun 25, 2019MT AG + WA AG + CA AG +2Jul 2, 2019OR AGfilings disagree on discovery
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · PCI · PII
MT AG + WA AG + CA AG +3
Attack vector
Unauthorized Access
MT 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)

50,743

Sum of filed state slices

3,544· 7.0% of stated

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

US50,743
MA1,394
SC1,080
WA706
NH285
MT79

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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 Jun 12, 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

1 days

Cadence

~1 / 0.2d

vs. multi-state median

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