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

Navvis & Company, LLC — July 2023 breach

Clustered 8 filings across 6 jurisdictions · filing window Dec 29, 2023 → Feb 13, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

874,506

First → last filing

Dec 29, 2023 → Feb 13, 2024

Merge confidence

100%

incident inc_b563a8de81004fd7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Jul 12, 2023–Jul 25, 2023, discovered Jul 25, 2023 — the first regulatory filing landed 157 days later (flagged late). 874,506 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 2 more. Notifications rolled out on a 46-day schedule across 8 filings beginning Dec 29, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
157days

Discovered → first regulatory filing

Discovery variance
135days

Range of discovered_at dates across filings

Filing span
46days

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 · 157dWashington✗ WA AG >90dOregon✓ OR AG ≤45dHawaii✓ HI CRA notice dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 12, 2023breach begins
Jul 25, 2023discovered · members disagree
notification delay · 157 days
Dec 29, 2023first filing
Feb 13, 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. DEC 29CA AGCA AG noticefirst filing · no count statedday 0
  2. DEC 29OR AGOR AG noticestates nationwide total 874,506day 0
  3. DEC 29WA AGWA AG notice6,783 WA residentsday 0
  4. JAN 9CA AGCA AG noticeno count stated+11d
  5. JAN 9HI AGHI AG notice765,370 HI residents+11d
  6. FEB 9CA AGCA AG noticeno count stated+42d
  7. FEB 9NH AGNH AG notice255 NH residents+42d
  8. FEB 13SC AGSC AG noticemost recent · 2,090 SC residents+46d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 12, 2023 – Jul 25, 2023
CA AG
Discovered
Jul 25, 2023CA AG + WA AG + NH AG +1Dec 7, 2023OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + WA AG + NH AG +1
Attack vector
Unauthorized Access
CA 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)

874,506

Sum of filed state slices

774,498· 88.6% of stated

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

US874,506
HI765,370
WA6,783
SC2,090
NH255

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

46 days

Cadence

~1 / 6.6d

vs. multi-state median

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