Hennepin County first-responder data leak: about 1,500 officers and infrastructure staff exposed in 2020

What happened

On July 10, 2020, the Minnesota Reformer reported that personal information for roughly 1,500 Minnesota first responders and critical infrastructure personnel had been published online. The leak came from a hack of a vendor that worked with the Minnesota Bureau of Criminal Apprehension and the Hennepin County Sheriff's Office. The exposed data included names, work locations, and other identifying information.

The leak hit during a period of intense focus on Minneapolis-area law enforcement after the killing of George Floyd in May 2020. Officers and their families were already facing elevated targeting; the leak added an additional vector.

How it started

The breach was traced to a vendor in the law enforcement supply chain, not to BCA or the Sheriff's Office directly. That detail matters. Officer data lives in many hands: training systems, accreditation bodies, payroll vendors, body-camera vendors, scheduling tools. Each is a potential source.

The Reformer's reporting noted the published data was distributed broadly online, making after-the-fact recovery effectively impossible. Once the data is in circulation, removal becomes about cutting off republication on broker pages rather than recovering the original leak.

What this means for you

Minnesota's Safe at Home program is one of the better address-confidentiality programs in the country and explicitly accommodates first responders for property-records protection (Minn. Stat. § 13.045). DMV confidentiality (Minn. Stat. § 171.12) covers your driver's license records.

Both stop the state from publishing your address. Neither stops Whitepages or Spokeo from republishing it. After a leak like this one, broker removal is the layer that actually stays current. We do that work and re-do it when the listings come back.

Editorial rules: Only public, already-reported incidents. Never name a non-public victim. Always end with the prevention takeaway tied to our service. Cite at minimum one public source per claim.