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

The Gladney Center for Adoption — February 2025 breach

Clustered 8 filings across 7 jurisdictions · filing window Feb 3, 2026 → Feb 9, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

3,693

First → last filing

Feb 3, 2026 → Feb 9, 2026

Merge confidence

100%

incident inc_47b9adb4eb95498e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion Feb 1, 2025–Apr 30, 2025, discovered Feb 1, 2025 — the first regulatory filing landed 367 days later (flagged late). 3,693 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 6-day schedule across 8 filings beginning Feb 3, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
367days

Discovered → first regulatory filing

Discovery variance
367days

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 clocksMassachusetts✗ MA AG >90dVermont✓ VT AG ≤14 bdayTexas✓ TX AG ≤30dDate basis✓ Clock withheld · confirmation dateFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 1, 2025breach begins
Feb 1, 2025discovered · members disagree
notification delay · 367 days
Feb 3, 2026first filing
Feb 9, 2026most 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 3VT AGVT AG noticefirst filing · 640 affectedday 0
  2. FEB 3IN AGIN AG noticestates nationwide total 3,693day 0
  3. FEB 3IN AGIN AG noticestates nationwide total 3,693day 0
  4. FEB 3NE AGNE AG noticeno count statedday 0
  5. FEB 6TX AGTX AG noticestates nationwide total 3,693+3d
  6. FEB 6NH AGNH AG notice6 NH residents+3d
  7. FEB 6ME AGME AG noticestates nationwide total 3,693+3d
  8. FEB 9MA AGMA AG noticemost recent · no count stated+6d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 1, 2025
IN AG
Discovered
Feb 1, 2025MA AGJan 23, 2026TX AG + NH AG + ME AGFeb 3, 2026VT AG + NE AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + TX AG + NH AG +3
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)

3,693

Sum of filed state slices

2,691· 72.9% of stated

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

US3,693
TX2,008
VT640
IN23
ME14
NH6

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

Cadence

~1 / 0.9d

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.