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

PeopleGuru Holdings, Inc. — July 2025 breach

Clustered 9 filings across 9 jurisdictions · filed Oct 16, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

80,146

First → last dated filing

Oct 16, 2025

Merge confidence

100%

incident inc_aa7718d02b764315 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Jul 6, 2025–Jul 9, 2025, discovered Jul 9, 2025 — the first regulatory filing landed 99 days later (flagged late). 80,146 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
99days

Discovered → first regulatory filing

Discovery variance
68days

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 clocksVermont✗ VT AG >45 bdayIowa✗ IA AG >5 bdayWashington✗ WA AG >90dMaine⏱ ME AG >30d · 99dDate basis✓ Clock withheld · confirmation dateFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 6, 2025breach begins
Jul 9, 2025discovered · members disagree
notification delay · 99 days
Oct 16, 2025first dated filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. OCT 16VT AGVT AG noticefirst filing · no count statedday 0
  2. OCT 16NH AGNH AG notice240 NH residentsday 0
  3. OCT 16OR AGOR AG noticestates nationwide total 80,146day 0
  4. OCT 16IA AGIA AG notice1,053 IA residentsday 0
  5. OCT 16MT AGMT AG notice19 MT residentsday 0
  6. OCT 16NE AGNE AG noticefiling day not on record · 523 NE residents—
  7. OCT 16WA AGWA AG notice1,861 WA residentsday 0
  8. OCT 16ME AGME AG notice756 ME residentsday 0
  9. OCT 16CA AGCA AG noticemost recent · no count statedday 0
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 6, 2025 – Jul 9, 2025
VT AG
Discovered
Jul 9, 2025VT AG + NH AG + IA AG +5Sep 15, 2025OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + NH AG + IA AG +5
Attack vector
Unauthorized Access
VT 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)

80,146

Sum of filed state slices

4,452· 5.6% of stated

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

US80,146
WA1,861
IA1,053
ME756
NE523
NH240
MT19

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