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

Richard Owen Nursery, Inc. — September 2017 breach

Clustered 4 filings across 4 jurisdictions · filing window Aug 29, 2018 → Sep 5, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

12,397

First → last filing

Aug 29, 2018 → Sep 5, 2018

Merge confidence

100%

incident inc_00d7294df9e74003 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. Intrusion Sep 20, 2017–Jul 31, 2018, discovered Aug 6, 2018 — the first regulatory filing landed 23 days later. 12,397 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, and PII. Notifications rolled out on a 7-day schedule across 4 filings beginning Aug 29, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
23days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
7days

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 clocksOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Incident timeline

Sep 20, 2017breach begins
Aug 6, 2018discovered
notification delay · 23 days
Aug 29, 2018first filing
Sep 5, 2018most 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. AUG 29CA AGCA AG noticefirst filing · no count statedday 0
  2. AUG 29OR AGOR AG noticestates nationwide total 12,397day 0
  3. AUG 30NH AGNH AG notice130 NH residents+1d
  4. SEP 5MT AGMT AG noticemost recent · 66 MT residents+7d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 29, 2017 – Jul 31, 2018
CA AG
Discovered
Aug 6, 2018· 311d undetected
CA AG + OR AG + NH AG +1
Data types
Financial account · Identity (basic) · PII
CA AG + NH AG + MT AG
Attack vector
Misconfiguration
NH 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)

12,397

Sum of filed state slices

196· 1.6% of stated

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

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

7 days

Cadence

~1 / 2.3d

vs. multi-state median

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