License Plate Reader Records: Ask for the Program, Not the Plates
by Chaz Stevens, CLE Faculty
License Plate Reader Records: Ask for the Program, Not the Plates
License plate reader records worth requesting are the program’s paperwork: the contract, written access procedures, logs of use, audit reports, retention rules and data-sharing records. The plate data is another matter. Florida makes ALPR images and data containing personal identifying information confidential and exempt, while Minnesota requires a public log of use and public audit results.
Picture a hypothetical resident who spots a new camera on a pole at the edge of town and files a request for all of the town’s license plate reader data. That request asks for the part of the system the law guards most closely, and in Florida much of it runs into a statute that makes identifying images and data confidential and exempt. A request for the program points somewhere else: at the paper that shows how the cameras were bought, what rules govern them and whether anyone checks. Which of those papers the law requires depends on the state.
A license plate reader is a camera system that turns plates into searchable data; Florida’s s. 316.0777(1)(c) defines an automated license plate recognition system as “a system of one or more mobile or fixed high-speed cameras combined with computer algorithms to convert images of license plates into computer-readable data.”
The plate reads are the guarded part, so ask about the machine
Florida closes the identifying data by statute. Under section 316.0777(3) of the 2026 Florida Statutes, two kinds of information held by an agency are confidential and exempt from s. 119.07(1) and s. 24(a), Art. I of the State Constitution: “Images and data containing or providing personal identifying information obtained through the use of an automated license plate recognition system”, and personal identifying information of an individual in data generated from those images. Section 316.0777(4) allows two kinds of disclosure: by or to a criminal justice agency performing its official duties, and to an individual, for information relating to a license plate registered to that individual, unless it is active criminal intelligence or active criminal investigative information.
Minnesota starts from the same place. Under Minnesota Statutes section 13.824, subdivision 2(b), data collected by a reader are private data on individuals or nonpublic data unless they are public under listed parts of section 13.82 or are active criminal investigative data. A request built around other people’s plates also points at tracking individuals, which is a different project and not one this method serves. The program records point at the agency instead.
Minnesota writes the program records into the statute
Minnesota is one state that writes program records into its statute and makes several of them public. Its definition, in subdivision 1(b), says a reader “does not include a traffic safety camera system.” Under section 13.824, subdivision 5(a), a law enforcement agency that installs or uses a reader “must maintain a public log of its use, including but not limited to” the times of day the reader collected data, the aggregate number of vehicles or plates on which data were collected, and the state and federal databases the data were compared with, unless the existence of a database is not public. Subdivision 5(b) adds a list of current and previous locations of fixed readers, which must be accessible to the public unless the agency determines the data are security information, and that determination is subject to in-camera judicial review.
The checks on the program are public too. Subdivision 6 requires the agency to arrange “an independent, biennial audit” of its records, and says “The results of the audit are public.” Subdivision 7(b) requires written procedures limiting access to personnel authorized in writing, and subdivision 7(c) requires a data audit trail of queries, responses and every action in which data are entered, updated, accessed, shared or disseminated; that trail is public to the extent the data are not otherwise classified by law. Subdivision 8(b) has the Bureau of Criminal Apprehension keep a list of agencies using readers, accessible to the public and on the bureau’s website, except where an agency determines a specific location is security information.
Florida puts the retention rule on paper
Florida’s statute does less about logs but does name a records schedule. Under section 316.0778(2), the Department of State, in consultation with the Department of Law Enforcement, “shall establish a retention schedule” for records containing images and data generated through an automated license plate recognition system, and the schedule “must establish a maximum period that the records may be retained.” Section 316.0777(2)(d) adds that records containing images and data generated through the use of a system may not be retained longer than that maximum. Subsection (2), which governs readers installed along the State Highway System at a law enforcement agency’s request, also says such a reader “may not be used to issue a notice of violation for a traffic infraction or a uniform traffic citation.”
The surrounding paper is covered by Florida’s general definition. Under section 119.011(12), public records include documents and other material “made or received pursuant to law or ordinance or in connection with the transaction of official business by any agency”, and section 119.011(2) counts a private business “acting on behalf of any public agency” as an agency. Exemptions can still reach part of a record: Florida’s s. 119.011(13) defines “redact” as concealing “that portion of the record containing exempt or confidential information.”
| Record to request | Where a rule requires or shapes it |
|---|---|
| Contract and purchase records for the system | Florida: public records definition, s. 119.011(12). Elsewhere, your state’s records law. |
| Written procedures for access to the data | Minnesota: s. 13.824, subd. 7(b) requires them; it does not say they are public |
| Public log of use | Minnesota: s. 13.824, subd. 5(a) |
| List of fixed reader locations | Minnesota: s. 13.824, subd. 5(b), unless determined to be security information |
| Biennial audit results | Minnesota: s. 13.824, subd. 6 |
| Data audit trail | Minnesota: s. 13.824, subd. 7(c), to the extent not otherwise classified |
| Retention schedule | Florida: s. 316.0778(2). Minnesota: s. 13.824, subd. 3 |
| Records of when data were shared | Minnesota: the subd. 7(c) audit trail records actions in which data are shared or disseminated; subd. 4 limits sharing |
Write the request this week
The method is the one behind asking for the document instead of the topic: find the rule, then ask for the paper it produces.
- Confirm which law applies. The rules in this article come from state statutes, so start with your state’s records law; the guide to the difference between FOIA and state records law explains how to tell.
- Find the state’s ALPR statute, if it has one. Florida and Minnesota are examples; other states write their own rules or none.
- List the records by name. Use the table: contract, written access procedures, log, location list, audit results, audit trail, retention schedule. In Minnesota, cite the subdivision that requires each one.
- Ask for the retention rule separately. In Florida, ask for the retention schedule that s. 316.0778 requires the Department of State to establish. The guide to records retention schedules explains how to read one.
- Leave the plates out. Do not ask for reads, images or hits about any other person or vehicle.
In a state without a statute like Minnesota’s, a log or audit may not exist, and a “no responsive records” reply is a legitimate answer. If a denial cites an exemption, ask for the written reason; if the question becomes whether the denial is lawful, ask an attorney licensed in your state.
Ask for the paper that runs the cameras and leave the plates alone.
Where REVOLT fits in
REVOLT Training works both sides of the public records table: it teaches people who file requests and runs governance diagnostics for institutions. Its Must Exist method is to find the written rule an agency adopted for itself, work out what paper it produces, and ask for that paper by name, citing the rule. The FOIA Engineering Playbook is free. REVOLT will not draft requests for plate numbers, vehicle photographs, registered owner records, or any record sought to identify, locate, harass or surveil a private individual.
REVOLT does not provide legal representation or legal advice, and it does not promise that any agency will produce any particular record. If your question turns on a specific denial, an unfamiliar exemption or another state’s statute, book a call.
FAQ
Can I get license plate reader data about my own car in Florida?
Florida’s s. 316.0777(4)(b) says information relating to a license plate registered to an individual may be disclosed to that individual; the statute’s word is may, not must. The exception is active criminal intelligence or active criminal investigative information.
Are license plate reader audits public in Minnesota?
Yes. Minnesota’s s. 13.824, subdivision 6, requires an independent, biennial audit, and says the results of the audit are public.
How long can police keep license plate reader data?
The state’s statute and retention schedule decide. In Minnesota, s. 13.824, subdivision 3(a), says data not related to an active criminal investigation must be destroyed no later than 60 days from collection, except as otherwise provided in that subdivision. In Florida, s. 316.0778 has the Department of State set a schedule with a maximum retention period.
Can I find out where the cameras are?
In Minnesota, an agency’s list of current and previous fixed reader locations must be accessible to the public under s. 13.824, subdivision 5(b), unless the agency determines the data are security information. That determination is subject to in-camera judicial review.
Sources
- Florida Statutes s. 316.0777, Automated license plate recognition systems; public records exemption (The Florida Senate). Retrieved 2026-11-20.
- Florida Statutes s. 316.0778, Automated license plate recognition systems; records retention (The Florida Senate). Retrieved 2026-11-20.
- Minnesota Statutes s. 13.824, Automated License Plate Readers (Minnesota Office of the Revisor of Statutes). Retrieved 2026-11-20.
- Florida Statutes s. 119.011, Definitions (The Florida Senate). Retrieved 2026-11-20.
About REVOLT Training
By Chaz Stevens, founder of REVOLT Training.
REVOLT Training teaches public records practice: how to anchor a request to a rule an agency wrote for itself, and how to answer the stalls that follow. It also runs governance diagnostics for public institutions. REVOLT Training is operated by The Z Production Group, Inc.
This article explains how the law and public records work. It is not legal advice, and REVOLT Training is not a law firm. For advice on your situation, talk to a licensed attorney.

Learn more about him on Wikipedia.
Sedition Isn't Free.
Go ahead, speak your mind.
Recent Musings
Exposing Hypocrisy
One Story At A Time.




