DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed12 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakirahigh sensitivity
Merged incident · 12 filings

Precision Tax Relief — April 2025 breach

Clustered 12 filings across 11 jurisdictions · filing window Apr 1, 2025 → Jun 2, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

10

Affected · reported

7,381

First → last filing

Apr 1, 2025 → Jun 2, 2025

Merge confidence

100%

incident inc_e5960c2f0339494d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Apr 1, 2025–Apr 1, 2025, discovered Apr 1, 2025 — the first regulatory filing landed 59 days later. 7,381 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 62-day schedule across 10 filings beginning Apr 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
35days

Range of discovered_at dates across filings

Leak precedence
59days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
62days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap⏱ Leak >30dMaine✓ ME AG ≤30d · 24dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 1, 2025breach begins
Apr 1, 2025discovered · members disagree
notification delay · 59 days
May 30, 2025first filing
Jun 2, 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. APR 1Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. MAY 12Leak siteakira postattacker claim · unverified+41d
  3. MAY 30ME AGME AG notice18 ME residents+59d
  4. MAY 30CA AGCA AG noticeno count stated+59d
  5. MAY 30NH AGNH AG notice23 NH residents+59d
  6. MAY 30NE AGNE AG notice15 NE residents+59d
  7. MAY 30MT AGMT AG notice49 MT residents+59d
  8. MAY 30VT AGVT AG noticeno count stated+59d
  9. MAY 30OR AGOR AG noticestates nationwide total 7,381+59d
  10. MAY 30MA AGMA AG notice92 MA residents+59d
  11. MAY 30IN AGIN AG noticestates nationwide total 7,381+59d
  12. JUN 2TX AGTX AG noticemost recent · states nationwide total 7,381+62d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 1, 2025
ME AG
Discovered
Apr 1, 2025NE AG + MT AGMay 6, 2025ME AG + OR AG + TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
ME AG + CA AG + NH AG +5
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)

7,381

Sum of filed state slices

1,058· 14.3% of stated

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

US7,381
TX766
IN95
MA92
MT49
NH23
ME18
NE15

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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 Aug 23, 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

62 days

Cadence

~1 / 5.6d

vs. multi-state median

7.8× slower

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.