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

Apro, LLC — February 2025 breach

Clustered 11 filings across 7 jurisdictions · filed Dec 29, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

7

Affected · reported

11,987

First → last filing

Dec 29, 2025

Merge confidence

100%

incident inc_eeab3c585b9d4b36 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Feb 19, 2025–May 24, 2025, discovered Mar 22, 2025 — the first regulatory filing landed 282 days later (flagged late). 11,987 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
282days

Discovered → first regulatory filing

Discovery variance
63days

Range of discovered_at dates across filings

Filing span
0days

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 >45dCalifornia✗ CA 60-day late · 219dWashington✗ WA AG >90dMaine✗ ME AG >90d · 219dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 19, 2025breach begins
Mar 22, 2025discovered · members disagree
notification delay · 282 days
Dec 29, 2025first 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

  1. DEC 29NE AGNE AG noticefirst filing · no count statedday 0
  2. DEC 29OR AGOR AG noticestates nationwide total 11,986day 0
  3. DEC 29CA AGCA AG noticeno count statedday 0
  4. DEC 29MA AGMA AG notice1 MA residentsday 0
  5. DEC 29WA AGWA AG notice1,226 WA residentsday 0
  6. DEC 29WA AGWA AG notice621 WA residentsday 0
  7. DEC 29ME AGME AG noticestates nationwide total 11,987day 0
  8. DEC 29IN AGIN AG noticestates nationwide total 5,860day 0
  9. DEC 29IN AGIN AG noticestates nationwide total 11,987day 0
  10. DEC 29NE AGNE AG noticeno count statedday 0
  11. DEC 29CA AGCA AG noticemost recent · no count statedday 0
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 19, 2025 – Mar 2, 2025
NE AG
Discovered
Mar 22, 2025NE AG + WA AG + CA AGMay 24, 2025OR AG + CA AG + WA AG +2filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
NE AG + CA AG + WA AG +2
Attack vector
Unauthorized Access
NE 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)

11,987

Sum of filed state slices

1,234· 10.3% of stated

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

US11,987
WA1,226
IN6
MA1
ME1

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

0 days

Cadence

~1 / 0d

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.