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

PCS Revenue Control Systems — May 2017 breach

Clustered 8 filings across 8 jurisdictions · filing window Mar 17, 2021 → Mar 24, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

867,209

First → last filing

Mar 17, 2021 → Mar 24, 2021

Merge confidence

100%

incident inc_e72a6d266afa4aaa · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion May 19, 2017–Dec 20, 2019, discovered Dec 19, 2019 — the first regulatory filing landed 454 days later (flagged late). 867,209 individuals reported across the linked filings. Data reported: Government ID, Minor, Education, and 2 more. Notifications rolled out on a 7-day schedule across 8 filings beginning Mar 17, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
454days

Discovered → first regulatory filing

Discovery variance
453days

Range of discovered_at dates across filings

Filing span
7days

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 clocksWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 2dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

May 19, 2017breach begins
Dec 19, 2019discovered · members disagree
notification delay · 454 days
Mar 17, 2021first filing
Mar 24, 2021most 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. MAR 17WA AGWA AG noticefirst filing · 11,807 WA residentsday 0
  2. MAR 18IN AGIN AG noticestates nationwide total 867,209+1d
  3. MAR 18MA AGMA AG notice256 MA residents+1d
  4. MAR 18ME AGME AG noticestates nationwide total 867,209+1d
  5. MAR 22CA AGCA AG noticeno count stated+5d
  6. MAR 24NH AGNH AG notice47 NH residents+7d
  7. MAR 24MT AGMT AG notice32 MT residents+7d
  8. MAR 24SC AGSC AG noticemost recent · 3,953 SC residents+7d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 19, 2019
WA AG
Discovered
Dec 19, 2019CA AG + NH AG + MT AG +1Dec 20, 2019WA AGMar 16, 2021ME AGfilings disagree on discovery
Data types
Education · Identity (basic) · Government ID · Minor · PII
WA AG + CA AG + ME AG +4
Attack vector
Phishing
WA 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)

867,209

Sum of filed state slices

25,606· 3.0% of stated

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

US867,209
WA11,807
IN9,450
SC3,953
MA256
ME61
NH47
MT32

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

7 days

Cadence

~1 / 1d

vs. multi-state median

1.1× 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.