DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Merged incident · 11 filings

Carnival Corporation Ltd. — August 2020 breach

Clustered 11 filings across 9 jurisdictions · filing window Oct 13, 2020 → Dec 4, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

37,500

First → last dated filing

Oct 13, 2020 → Dec 4, 2021

Merge confidence

100%

incident inc_d0b9664f569e4e6e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Aug 1, 2020–Aug 14, 2020, discovered Aug 15, 2020. 37,500 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 4 more. Notifications rolled out on a 417-day schedule across 10 dated filings beginning Oct 13, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
45days

Range of discovered_at dates across filings

Filing span
417days

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 clocksCalifornia✗ CA 60-day late · 118dMaine✓ ME AG ≤30d · 17dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Incident timeline

Aug 1, 2020breach begins
Aug 15, 2020discovered · members disagree
Oct 13, 2020first dated filing
Dec 4, 2021most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. 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

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. OCT 13DE AGDE AG noticefirst filing · no count statedday 0
  3. OCT 13CA AGCA AG noticeno count statedday 0
  4. OCT 13IN AGIN AG noticestates nationwide total 37,500day 0
  5. OCT 16ME AGME AG notice8 affected+3d
  6. OCT 16OR AGOR AG noticestates nationwide total 37,500+3d
  7. OCT 18MA AGMA AG notice145 MA residents+5d
  8. OCT 20SC AGSC AG notice5,801 SC residents+7d
  9. OCT 20NH AGNH AG notice17 NH residents+7d
  10. FEB 4CA AGCA AG noticeno count stated+114d
  11. DEC 4DE AGDE AG noticemost recent · no count stated+417d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 1, 2020 – Aug 14, 2020
DE AG
Discovered
Aug 15, 2020IL AG + DE AG + CA AG +2Sep 29, 2020ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · Health (basic) · PII · PHI · Financial account · PCI
DE AG + CA AG + SC AG +2
Attack vector
Unauthorized Access
DE 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)

37,500

Sum of filed state slices

8,465· 22.6% of stated

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

US37,500
SC5,801
IN2,494
MA145
NH17
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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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

417 days

Cadence

~1 / 46.3d

vs. multi-state median

69.5× 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.