All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 2 filings

SAN ANTONIO WINERY, INC. — November 2018 breach

Clustered 2 filings across 2 jurisdictions · filed Feb 26, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

First → last filing

Feb 26, 2019

Merge confidence

100%

incident inc_6694f3f11a0a4e3b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes a phishing attack. Intrusion Nov 13, 2018–Nov 15, 2018, discovered Dec 6, 2018 — the first regulatory filing landed 82 days later. 1 individual reported across the linked filings. Data reported: PII, Identity (basic), PCI, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

82days

Discovered → first regulatory filing

Filing span

0days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Incident timeline

Nov 13, 2018breach begins

Dec 6, 2018discovered

notification delay · 82 days

Feb 26, 2019first filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

FEB 26CA AGCA AG noticefirst filing · no count statedday 0
FEB 26MA AGMA AG noticemost recent · 1 MA residentsauto-linkedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Nov 13, 2018 – Nov 15, 2018
Discovered: Dec 6, 2018· 23d undetected
Data types: Financial account · Identity (basic) · PCI · PII
Attack vector: Phishing

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

0 days

vs. multi-state median

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