• Text Size
• Print
• Email

  From:
  

  To:
  

  Hey! Check out this news page: https://www.thebackgroundinvestigator.com/Articles/The-MN-BCA-Breach-Why-“Public”-Doesn’t-Always-Mean-“Fair-Game”/3215/index.php.

  SendCancel

National News

The MN BCA Breach: Why “Public” Doesn’t Always Mean “Fair Game”

March 31, 2026 posted by Steve Brownstein

For background investigators, the recent data leak at the Minnesota Bureau of Criminal Apprehension (BCA) is more than just a headline—it’s a high-stakes warning about the reliability of "official" sources.

In early 2026, a technical glitch within the Minnesota Criminal History System (CHS) caused the records of 595 individuals to remain public on the state’s website, even though those records had been legally ordered sealed or made private by the courts.

For an investigator, this raises a terrifying question: If the primary source is wrong, how do you stay compliant?

The Anatomy of the Glitch

The error occurred during the synchronization process between the BCA’s internal database and its public-facing search portal.

• The Failure: The system failed to recognize specific "restrictive" court actions.

• The Result: Records that should have been suppressed—due to Minnesota’s 15-year public disclosure limit or new "Clean Slate" expungement laws—remained visible to anyone with a name and a date of birth.

• The Timeline: The breach persisted for several weeks before being patched in late February.

The Compliance Trap for Investigators

Under the Fair Credit Reporting Act (FCRA), background screening firms are required to follow "reasonable procedures to assure maximum possible accuracy." This leak creates a unique liability trap:

1. The Snapshot Problem: If you or your vendor "scraped" the MN BCA portal during that window, you may have captured data that is now legally non-existent.

2. Reporting Sealed Records: Reporting a record that has been expunged or sealed is a Tier-1 compliance violation. Even if you "found it on the state site," the burden of accuracy often falls on the reporter.

3. The Dispute Wave: With 600 people affected, the likelihood of a "Notice of Dispute" hitting your desk is high. If your internal database hasn't been purged of this specific "glitch data," you are at risk.

Action Steps for the Field

• Audit your Minnesota Hits: If your team pulled records from the BCA portal between January and March 2026, those files should be flagged for a manual re-verification.

• Check the "15-Year" Logic: Minnesota law is unique; conviction data is public for only 15 years after the sentence is completed. Ensure your researchers are calculating dates based on sentence completion, not just the conviction date.

• Scraper Caution: If you use automated tools to gather Minnesota data, ensure they are doing "live" lookups rather than relying on cached results from the early 2026 period.

The Bottom Line

This incident proves that "Public Access" is not a synonym for "Accurate." As more states adopt automatic expungement and "Clean Slate" policies, the window for what is legally reportable is shrinking.

As investigators, we are the last line of defense between a "glitch" and a person’s livelihood. Don’t let a state’s technical error become your legal liability.