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

SAINT ANDREW'S SCHOOL OF BOCA RATON, INC. — December 2024 breach

Clustered 5 filings across 5 jurisdictions · filing window Jul 8, 2025 → Jul 9, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

2,105

First → last filing

Jul 8, 2025 → Jul 9, 2025

Merge confidence

100%

incident inc_b8bc805af67249c8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Dec 27, 2024–Dec 29, 2024, discovered Dec 28, 2024 — the first regulatory filing landed 192 days later (flagged late). 2,105 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
192days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
1days

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 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 27, 2024breach begins
Dec 28, 2024discovered
notification delay · 192 days
Jul 8, 2025first filing
Jul 9, 2025most 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. JUL 8VT AGVT AG noticefirst filing · no count statedday 0
  2. JUL 8IN AGIN AG noticestates nationwide total 2,105day 0
  3. JUL 8NE AGNE AG noticeno count statedday 0
  4. JUL 9NH AGNH AG notice3 NH residents+1d
  5. JUL 9MA AGMA AG noticemost recent · 8 MA residents+1d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 27, 2024 – Dec 29, 2024
VT AG
Discovered
Dec 28, 2024· 1d undetected
VT AG + NE AG + NH AG
Data types
Identity (basic) · Government ID · PII
VT AG + NH AG + NE AG +1
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)

2,105

Sum of filed state slices

13· 0.6% of stated

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

US2,105
MA8
NH3
IN2

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

1 days

Cadence

~1 / 0.3d

vs. multi-state median

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