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

APPFOLIO, INC. — August 2025 breach

Clustered 12 filings across 12 jurisdictions · filing window Oct 6, 2025 → Oct 7, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

72,444

First → last filing

Oct 6, 2025 → Oct 7, 2025

Merge confidence

100%

incident inc_5abca642d2374dd9 · merged by deterministic · confidence 100%

Part of the SALESLOFT, INC. supply-chain incident (2025) — at least 3 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe hacking. Intrusion Aug 8, 2025–Aug 18, 2025, discovered Aug 22, 2025 — the first regulatory filing landed 45 days later. 72,444 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
45days

Discovered → first regulatory filing

Discovery variance
27days

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 clocksMaine⏱ ME AG >30d · 45dWashington⏱ WA AG >30dOregon✓ OR AG ≤45dIowa✓ IA AG ≤5 bdayMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 8, 2025breach begins
Aug 22, 2025discovered · members disagree
notification delay · 45 days
Oct 6, 2025first filing
Oct 7, 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. OCT 6MT AGMT AG noticefirst filing · 337 MT residentsday 0
  2. OCT 6OR AGOR AG noticestates nationwide total 72,444day 0
  3. OCT 6VT AGVT AG notice188 VT residentsday 0
  4. OCT 6IA AGIA AG notice799 IA residentsday 0
  5. OCT 6IN AGIN AG notice1,346 IN residentsday 0
  6. OCT 6MA AGMA AG notice932 MA residentsday 0
  7. OCT 6NE AGNE AG notice510 NE residentsday 0
  8. OCT 6ME AGME AG notice148 ME residentsday 0
  9. OCT 6WA AGWA AG notice2,882 WA residentsday 0
  10. OCT 6NH AGNH AG notice231 NH residentsday 0
  11. OCT 6CA AGCA AG noticestates nationwide total 188day 0
  12. OCT 7TX AGTX AG noticemost recent · states nationwide total 72,444+1d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 8, 2025 – Aug 18, 2025
OR AG
Discovered
Aug 22, 2025IA AG + NE AG + ME AG +2Sep 18, 2025OR AG + TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MT AG + VT AG + IA AG +7
Attack vector
Unauthorized Access
MT 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)

72,444

Sum of filed state slices

12,429· 17.2% of stated

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

US72,444
TX5,056
WA2,882
IN1,346
MA932
IA799
NE510
MT337
NH231
VT188
ME148

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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

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