Automated License Plate Reader (ALPR) Laws Explained (2026)

Automated license plate readers turn plate images, times, and locations into searchable records. The legality of an ALPR program depends on the operator, jurisdiction, purpose, retention, access, and sharing rules. This guide explains those questions and links directly to a section for every state and the District of Columbia.

Information reviewed September 11, 2026.

Scope: This hub addresses US automated license plate reader laws through current examples from California, Maryland, and Montana, plus carefully limited federal case context. State rules differ and may change. Use the linked comparison section and current primary authority for the jurisdiction involved.

What is an automated license plate reader?

An automated license plate reader, usually called an ALPR or LPR, combines a camera with software that reads a vehicle plate and creates a searchable record. A record can include the plate characters, capture time, location, an image, and other vehicle details. California Civil Code §1798.90.5 defines an ALPR system in terms of cameras, algorithms, and the resulting searchable database, which helps show that the legal issue extends beyond the physical camera.

Different steps can create different legal questions. A city may approve installation at a public meeting, an operator may collect and store the records, an officer may conduct a query, a vendor may host the database, and another agency may request access. A rule that permits one step does not necessarily authorize the others.

ALPRs also differ from cameras dedicated to issuing red-light or speed citations. A plate-reader system may collect records from passing vehicles without issuing any citation. For traffic enforcement cameras, see the traffic camera ticket guide.

What controls whether an ALPR program is lawful?

The answer begins with the jurisdiction and the act being evaluated. State statutes may define who is an operator or end-user, require a written policy, restrict permissible purposes, set retention periods, regulate sharing, or require audits and access logs. Local ordinances, contracts, and agency policies can add operational limits, while constitutional rules apply to the government conduct challenged in a particular case.

The operator matters because public agencies, vendors, businesses, and neighborhood associations do not always have identical duties. California, for example, defines operators and end-users separately and gives the term “person” a broad meaning under Civil Code §1798.90.5. Its surrounding provisions assign specific duties to covered operators and public agencies rather than creating a single permission for every user of the technology.

The safest research method is to separate five questions: who owns or operates the system, what data it collects, why a record is searched, how long data remains available, and who can receive it. A complete answer may require a statute, the agency's current policy, a contract or amendment, and an access or audit record.

How do California, Maryland, and Montana regulate ALPRs?

These three states illustrate different statutory structures. They are examples rather than substitutes for the ALPR laws by state comparison, which identifies the source and scope for every state and DC. A provision from one state should not be carried into another state's analysis.

California

California Civil Code §1798.90.51 requires covered operators to maintain reasonable safeguards and a public written usage and privacy policy. Required topics include authorized purposes, users and training, monitoring, sharing, custody, accuracy, retention, and destruction. Section 1798.90.52 requires access records with the date and time, query information, user and affiliation, and purpose, and limits use to authorized purposes.

A public agency that operates or plans to operate an ALPR system must provide an opportunity for public comment before implementation under Civil Code §1798.90.55(a). Subsection (b) restricts a public agency's sale, sharing, or transfer of ALPR information to another public agency and only as otherwise permitted by law, with a clarification for data-hosting and towing services.

Maryland

Maryland Public Safety §3-509 requires a legitimate law-enforcement purpose for using captured plate data. Historical data belongs to the agency and cannot be sold. Vendor access requires the agency's express request and authorization, and the statute restricts uploads while expressly addressing the Maryland Coordination and Analysis Center database.

The same section requires operational procedures, an audit process, privacy safeguards, personnel screening and training, breach reporting, and annual reporting. It separately excludes ALPR information from disclosure under the Maryland Public Information Act. The section does not specify a numeric retention period.

Montana

MCA §46-5-117 starts with a public-highway restriction for state and local agencies, then provides enumerated exceptions, including a law-enforcement exception with conditions. Covered police use requires a public written policy, annual auditing, access records, and use for specified official purposes. A positive reader match alone does not establish reasonable suspicion; the statute requires independent suspicion or its specified visual and other confirmation.

MCA §46-5-118 generally limits covered police data to 90 days. It allows longer retention through a qualifying preservation request or specified warrant and defines information a preservation request must contain. Montana therefore should not be described either as a complete police ALPR ban or as unrestricted authorization.

How do Flock's retention statements affect a local system?

Flock's published materials distinguish a general policy, customer-specific agreements, and a later product update. Its August 12, 2026 Evidence Policy states a 30-day standard unless a customer agreement provides otherwise, and says data is irretrievable after the retention period expires. Those are company representations and do not replace a state statute or identify the configuration of a particular account.

On August 13, Flock announced an updated seven-day recommendation and default, together with a forthcoming Evidence Mode for selected investigative records. The announcement expressly states that existing customers will keep their approved retention periods. It therefore does not prove that every installed camera changed to seven days.

For a fuller explanation of vendor, account, state-law, and case distinctions, read Are Flock Cameras Legal?. For a named agency, check its current agreement, policy revision date, retention setting, and any legally authorized preservation procedure.

What do recent court decisions establish?

Court decisions must be limited to the system, record, claim, and procedural posture they actually address. In Schmidt v. City of Norfolk, the Eastern District of Virginia granted summary judgment to the defendants on January 27, 2026. The plaintiffs had standing to challenge collection and storage but lacked standing to challenge database queries on the record presented, and the merits analysis focused on the proved capabilities and observational gaps of Norfolk's network.

An opening brief filed April 13, 2026 identifies Fourth Circuit No. 26-1227. The district opinion also does not approve every ALPR network or every database query nationwide.

Chatrie v. United States, decided June 29, 2026, concerned Google's Location History rather than ALPR data. The Supreme Court held that acquiring the location history at issue was a Fourth Amendment search, vacated the judgment, and remanded warrant-validity questions. Chatrie supplies context for location-data analysis but does not create a universal ALPR warrant rule.

Compare ALPR law in every state and DC

The comparison page contains one linked section for each state and the District of Columbia. Each link below goes to that jurisdiction's heading on the comparison page. The directory does not claim that every state has a dedicated ALPR statute or that all 51 jurisdictions follow the same categories.

Use the jurisdiction section as an entry point. Read its classification and limitations, open the cited primary source, and check effective dates before applying the rule to a current program.

How can residents evaluate a local ALPR program?

Start with documents tied to the specific operator. Useful materials include the current usage and privacy policy, the governing body's agenda and meeting record, the contract and amendments, the stated retention setting, sharing-partner controls, annual reports, and access or audit logs. These documents answer different questions and may be subject to different disclosure rules.

Do not assume that a vendor statement about customer control authorizes every disclosure. California's transfer restriction and Maryland's historical-data and vendor provisions illustrate why the governing statute still matters. Do not assume that a system alert itself establishes legal grounds for a stop either; Montana has an express match-alone limitation.

This guide does not promise access to an individual's raw plate history. A records request, public meeting process, agency complaint, or legal claim has requirements set by the relevant jurisdiction.

Last updated: September 11, 2026. This is general legal information, not legal advice.