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

Bay Village of Sarasota, Inc. — February 2025 breach

Clustered 4 filings across 4 jurisdictions · filed Apr 21, 2025. View entity profile → Other incidents for this victim →

✓ affected count, data types, discovery date agreeMerge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

1,405

First → last filing

Apr 21, 2025

Merge confidence

100%

incident inc_e39a33c24e414146 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Feb 7, 2025, discovered Feb 9, 2025 — the first regulatory filing landed 71 days later (flagged late). 1,405 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
71days

Discovered → first regulatory filing

Discovery variance
0days

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 bdayMaine⏱ ME AG >30d · 71dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 7, 2025breach begins
Feb 9, 2025discovered
notification delay · 71 days
Apr 21, 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. APR 21IN AGIN AG noticefirst filing · states nationwide total 1,405day 0
  2. APR 21ME AGME AG notice2 ME residentsday 0
  3. APR 21VT AGVT AG noticeno count statedday 0
  4. APR 21NE AGNE AG noticemost recent · 1 NE residentsday 0
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 7, 2025
IN AG
Discovered
Feb 9, 2025· 2d undetected
ME AG + VT AG + NE AG
Data types
Identity (basic) · Government ID
ME AG + VT AG + NE AG
Attack vector
Unauthorized Access
ME 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)

1,405

Sum of filed state slices

6· 0.4% of stated

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

US1,405
IN3
ME2
NE1

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

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.