DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Merged incident · 2 filings

Pure Yoga LLC. — September 2016 breach

Clustered 2 filings across 1 jurisdiction · filing window Feb 1, 2017 → Feb 7, 2017. View entity profile → Other incidents for this victim →

✓ affected count, discovery date agreeMerge100%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

2,500

First → last filing

Feb 1, 2017 → Feb 7, 2017

Merge confidence

100%

incident inc_d7dbdd0cc9a94270 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. Intrusion Sep 6, 2016–Dec 18, 2016, discovered Jan 22, 2017 — the first regulatory filing landed 10 days later. 2,500 individuals reported across the linked filings. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
10days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
6days

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 6, 2016breach begins
Jan 22, 2017discovered
notification delay · 10 days
Feb 1, 2017first filing
Feb 7, 2017most 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. FEB 1OR AGOR AG noticefirst filing · states nationwide total 2,500day 0
  2. FEB 7OR AGOR AG noticemost recent · states nationwide total 2,500+6d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 6, 2016 – Dec 18, 2016
OR AG
Discovered
Jan 22, 2017· 138d undetected
OR AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

6 days

vs. multi-state median

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