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

JERRY'S ARTARAMA N.C. INC. — May 2016 breach

Clustered 3 filings across 3 jurisdictions · filing window Aug 30, 2016 → Sep 29, 2016. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

384

First → last filing

Aug 30, 2016 → Sep 29, 2016

Merge confidence

100%

incident inc_644aafe111df4b13 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe unauthorized access. Intrusion May 3, 2016–Jul 10, 2016, discovered Jul 6, 2016 — the first regulatory filing landed 55 days later (flagged late). 384 individuals reported across the linked filings. Data reported: Financial account, Identity (basic), and PII. Notifications rolled out on a 30-day schedule across 3 filings beginning Aug 30, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
55days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Filing span
30days

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

May 3, 2016breach begins
Jul 6, 2016discovered · members disagree
notification delay · 55 days
Aug 30, 2016first filing
Sep 29, 2016most 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 30CA AGCA AG noticefirst filing · no count statedday 0
  2. SEP 1SC AGSC AG notice384 SC residents+2d
  3. SEP 29OR AGOR AG noticemost recent · no count stated+30d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 3, 2016 – Jul 10, 2016
CA AG
Discovered
Jul 6, 2016CA AG + SC AGJul 7, 2016OR AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · PII
CA AG + SC AG
Attack vector
Unauthorized Access
CA 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 filing3 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

30 days

Cadence

~1 / 15d

vs. multi-state median

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