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

Inntopia — October 2021 breach

Clustered 12 filings across 5 jurisdictions · filing window Apr 5, 2022 → May 27, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

5

Affected · reported

68,635

First → last filing

Apr 5, 2022 → May 27, 2022

Merge confidence

100%

incident inc_8783df3eeae24e86 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Oct 9, 2021–Feb 18, 2022, discovered Feb 18, 2022 — the first regulatory filing landed 46 days later. 68,635 individuals reported across the linked filings. Data reported: PCI, Financial account, PII, and 4 more. Notifications rolled out on a 52-day schedule across 12 filings beginning Apr 5, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
46days

Discovered → first regulatory filing

Discovery variance
12days

Range of discovered_at dates across filings

Filing span
52days

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 clocksWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 34dCalifornia✓ CA 60-day OK · 46dFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Oct 9, 2021breach begins
Feb 18, 2022discovered · members disagree
notification delay · 46 days
Apr 5, 2022first filing
May 27, 2022most 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. APR 5MT AGMT AG noticefirst filing · 158 MT residentsday 0
  2. APR 5CA AGCA AG noticeno count statedday 0
  3. APR 5WA AGWA AG notice13,396 WA residentsday 0
  4. APR 5ME AGME AG noticestates nationwide total 18,884day 0
  5. APR 12ME AGME AG noticestates nationwide total 16,527+7d
  6. APR 15NH AGNH AG notice302 NH residents+10d
  7. APR 18NH AGNH AG notice279 NH residents+13d
  8. APR 21ME AGME AG noticestates nationwide total 17,952+16d
  9. APR 25NH AGNH AG notice708 NH residents+20d
  10. MAY 23CA AGCA AG noticeno count stated+48d
  11. MAY 23ME AGME AG noticestates nationwide total 68,635+48d
  12. MAY 27NH AGNH AG noticemost recent · 106 NH residents+52d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 9, 2021 – Feb 18, 2022
MT AG
Discovered
Feb 18, 2022MT AG + CA AG + WA AG +2Mar 2, 2022ME AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Financial credentials · Identity (basic) · PCI · PII
MT AG + CA 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.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

68,635

Sum of filed state slices

14,591· 21.3% of stated

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

US68,635
WA13,396
NH708
ME329
MT158

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 filing12 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

52 days

Cadence

~1 / 4.7d

vs. multi-state median

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