When Transparency Becomes a Crime: Why Precision in Minnesota’s Data Practices Law Matters
In recent months, a criminal case arising from a government data request in Kettle River has drawn attention across Carlton County. What began as a dispute over access to emails and text messages under Minnesota’s Government Data Practices Act ultimately resulted in a misdemeanor charge and a stay of adjudication for an elected city council member. Beyond the personalities involved, the case raises broader questions about how Minnesota’s transparency law is interpreted and enforced -- questions that affect every resident who relies on open government.
“A popular government without popular information, or the means of acquiring it, is but a prologue to a farce or a tragedy.”
-- James Madison (c. 1822)
In 2023, a member of the public submitted a handwritten request to the City of Kettle River seeking “all emails and text messages from all accounts” associated with an elected council member. The request was not made by the council member herself; it was (at best) a Minn. Stat. §13.03 public data request. The request was treated as triggering a ten-day compliance deadline. Concerns were raised about scope and classification, including whether private or confidential data might be included. The matter eventually escalated to criminal enforcement under Minn. Stat. §13.09. See Minn. Dist. Ct. Case No. 09-CR-23-1893. After contested litigation, the case concluded through a plea agreement involving a stay of adjudication.
In denying dismissal, the district court concluded that the law was “clear” that a ten-day deadline applied. In this instance, the Court was wrong. That conclusion illustrates how easily Minn. Stat. §§13.03 and 13.04 can be conflated. Section 13.04 expressly contains a ten-day deadline for data-subject requests -- requests made by individuals seeking access to data about themselves. Section 13.03 does not. It requires that public data be provided within a “reasonable time.” When a public request is analyzed under the data-subject provision, the statutory framework shifts. A flexible standard becomes a rigid mandate. When criminal liability turns on which statutory section governs, precision is essential.
This article does not revisit the plea; though importantly, both the Court and County Attorney got it wrong. Rather, it examines whether the statutory framework was applied in a manner consistent with the structure of Chapter 13 and asks a broader question: when statutory interpretation disputes are resolved in criminal court, what message does that send about how transparency laws function?
Minnesota’s Government Data Practices Act (MGDPA) is one of the most comprehensive transparency statutes in the country; legislation that Minnesotans should be proud of. It is the tool citizens use to obtain public records, the mechanism journalists rely on to investigate government conduct, and the statutory framework that governs how cities, counties, school districts, and state agencies handle public information. At its best, the MGDPA reflects a foundational democratic principle: informed citizens are essential to self-governance.
To understand the issue, it helps to begin with the scope of the statute itself. Under Minn. Stat. §13.02, a “government entity” includes cities, counties, townships, school districts, state agencies, boards, commissions, and other political subdivisions. In practical terms, Chapter 13 applies broadly across Minnesota. Whether interacting with a small-town council or a state department, the same statutory framework governs.
The statute also defines “government data” broadly. Government data includes all data collected, created, received, maintained, or disseminated by a government entity, regardless of its physical form or storage medium. An email discussing city business may qualify as government data. A text message about public policy may as well. A personal message unrelated to official duties does not. Classification matters. Not everything stored on a device is automatically government data, and Chapter 13 authorizes inspection of government data -- not unrestricted access to devices or accounts that may contain a mixture of public and protected information.
Many Americans are familiar with the federal Freedom of Information Act (FOIA), which governs access to records held by federal agencies. Like FOIA, Minnesota’s Government Data Practices Act is built on a presumption of public access and contains exemptions for protected categories of information. But the two statutes are not interchangeable. FOIA applies only to federal agencies. The MGDPA governs Minnesota’s state and local government entities. It also contains structural distinctions -- such as the difference between public data requests and data-subject requests -- that are unique to Minnesota law. Transparency statutes are creatures of statute. Their meaning comes from the text the Legislature enacted.
Every government entity must designate a “Responsible Authority.” Under Minn. Stat. §§13.02 and 13.05, that official is legally charged with establishing procedures for compliance, classifying data, safeguarding not public information, and responding to requests. This responsibility is assigned to ensure uniformity and legal consistency. It does not necessarily place primary compliance responsibility on each elected official individually. The structure exists precisely because government data may contain private personnel information, confidential material, protected health data, attorney-client communications, and other classifications that require careful review before disclosure. Proper classification is not optional; it is required by law.
At the center of many misunderstandings lies the distinction between §13.03 and §13.04. Section 13.03 governs requests made by members of the public for access to public government data. It requires that public data be provided within a “reasonable time,” recognizing that requests may involve large volumes of records or require thoughtful review and redaction. Section 13.04 governs access by a data subject -- someone requesting data about themselves -- and imposes a ten-day compliance deadline if immediate compliance is not possible. The difference is structural. Confusing the two collapses an important statutory safeguard.
Requests seeking “all emails and text messages from all accounts” raise legitimate classification questions. Chapter 13 provides access to government data, not to every communication an official has ever sent or stored. Not all emails are government data. Not all texts are government data. Not all accounts contain exclusively public information. The Responsible Authority must determine what qualifies as government data, what classification applies, and what redactions are required before inspection or copying occurs. If a request is overly broad or unclear, clarification is often necessary to ensure lawful compliance.
The MGDPA imposes penalties for failing to provide public data, but it also imposes liability for improperly releasing not public data. Minn. Stat. §13.08 provides civil remedies for unlawful disclosure, and §13.09 criminalizes willful violations. Officials therefore face dual statutory risks: disclose too much and risk unlawful release, or disclose too little and face allegations of noncompliance. In that context, seeking clarification is not obstruction; it is statutory caution.
Historically, criminal enforcement under §13.09 has been rare. Chapter 13 establishes an enforcement structure that includes advisory opinions from the Commissioner of Administration, civil remedies, and judicial clarification in civil proceedings. Criminal prosecution is generally reserved for clear, intentional misconduct -- such as knowingly releasing protected data or deliberately destroying records. When interpretive disputes over classification or timing are treated as crimes, the enforcement structure shifts in significant ways.
The MGDPA requires precision from requestors. A vague request may require clarification. A request directed to the wrong entity may be redirected. The same statutory precision expected of citizens should guide enforcement decisions by government officials and courts alike. When criminal liability is at issue, statutory interpretation must be exacting.
Transparency statutes exist to support democratic participation. They enable investigative reporting, public oversight, and accountable governance. Their legitimacy depends on consistent interpretation. If statutory ambiguities are resolved through criminal enforcement rather than advisory or civil mechanisms, a chilling effect may follow. Elected officials may hesitate to ask classification questions. Part-time public servants may fear personal liability. Citizens may become reluctant to serve. Precision in application protects both access and participation.
For residents who want to engage more directly with government transparency, Chapter 13 provides a clear starting point. Identify the government entity involved, locate its Data Practices Policy -- typically available on its website -- and direct requests to the designated Responsible Authority. Be specific about subject matter and time frame. Understand that classification and redaction may require review. Additional guidance on Minnesota’s Government Data Practices Act is available through the Minnesota Department of Administration’s Information Policy Analysis Division (IPAD). The statute belongs to the public. Its clarity benefits everyone.
Minnesota’s Government Data Practices Act is remedial in nature. It balances access with privacy, disclosure with protection. It was not designed to transform interpretive disputes into criminal matters absent clear, willful misconduct. Precision protects citizens seeking information, officials responding to requests, journalists relying on access, and courts applying the statute. It protects trust.
As communities across Minnesota continue to rely on Chapter 13 to ensure accountable government, careful and consistent interpretation is essential. Transparency depends on it. And so does democracy.