DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed1 filing · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Incident · single filing

Women's Care Florida

One linked filing — more sources may join as they report · filed Aug 14, 2026. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

1

Affected · reported

253

First → last filing

Aug 14, 2026

incident inc_bbba6ee4ede94dcc · merged by deterministic

Confirmed breach. Discovered Dec 18, 2025 — the first regulatory filing landed 239 days later (flagged late). 253 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 1 more.

What the filings say

TX AG

North Florida Women's Care based in Tallahassee, Florida, a healthcare – medical provider entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-12-18 and reported on 2026-08-14. 253 Texas residents were affected. 0 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Medical Information;Date of Birth. Consumers were notified via Posted at company website or special website;U.S. Mail.

AI-generated summary of the linked filing — not the filing's own words, and not independently verified.

Litigation Timing

Notification delay
239days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksTexas✗ TX AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown
Dec 18, 2025discovered
notification delay · 239 days
Aug 14, 2026first & only 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. AUG 14TX AGTX AG noticeonly filing · 253 affectedday 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
Dec 18, 2025
TX AG
Data types
Government ID · PHI · PII
TX AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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 filing1 member

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.

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.