Arizona License Plate Reader Laws

Status at a glance

No ALPR statute

We found no Arizona statute that regulates license plate readers. Arizona’s sources are narrow. One is a state supreme court decision whose broader reading of the Arizona Constitution is limited to home entries and doesn’t reach location data. The other is one city police department’s policy.

SB 1111 (2026), an ALPR regulation bill, reached a Senate engrossed version. News reports say it failed. We didn’t confirm its final status on the Legislature’s bill-status page. It isn’t law, so this page doesn’t describe what it would have required.

State v. Mixton: home entries only

Article 2, Section 8 of the Arizona Constitution, the Private Affairs Clause, is Arizona’s counterpart to the Fourth Amendment. In State v. Mixton (Jan. 11, 2021), the Arizona Supreme Court said the clause “provides broader protections to the home than the Fourth Amendment.”

In the same paragraph it set the limit: “Notably, we have yet to expand the Private Affairs Clause’s protections beyond the Fourth Amendment’s reach, except in cases involving warrantless home entries.” It also noted that the state exclusionary rule is “no broader than the federal rule.”

Mixton isn’t an ALPR case. It concerned IP addresses and internet subscriber information. The court held that “neither the federal nor the Arizona constitution requires a search warrant or court order for such information.”

So the broader Arizona reading is verified, but only for warrantless home entries. It does not extend to location surveillance, ALPR data or third-party records, and this page doesn’t suggest it does. ALPR questions in Arizona turn on federal law and agency policy. See is ALPR a search?

One agency’s policy: Buckeye

City of Buckeye Police Department Policy 460, on automated license plate readers, shows “Last Reviewed/Revised: August 14, 2026.” It is one city’s policy, not a statewide rule. Other Arizona agencies may follow different rules.

• Use. ALPR is authorized “only for legitimate law-enforcement investigations” or response to an imminent public-safety threat. It “shall not be used solely for Department administrative investigations or civil matters.”
• Searches. Every ALPR search must include a brief investigative reason or purpose.
• Alerts. “An ALPR alert is an investigative lead and, by itself,” doesn’t establish reasonable suspicion, probable cause or who is in the vehicle. Before enforcement, personnel should confirm the plate and vehicle description and verify the alert “through ALETS, NCIC, or another authoritative source when practical.”
• Retention. “Routine ALPR data and images stored or controlled by the Department shall be retained for 30 days.” Data from another agency’s system follows that system’s retention rules.
• Sharing. Personnel may share with another law enforcement agency after verifying the requestor and a legitimate investigative purpose, and must document the requesting agency, requestor, purpose and date of release.
• Audits. The ALPR Administrator must conduct “an ALPR system compliance audit at least monthly.”

What this can mean in an Arizona case

• Which agency’s cameras captured the data, and what does its written policy say about retention and sharing? See ALPR data retention and sharing.
• For Buckeye data, does each search record show an investigative reason, and do the monthly audits cover it? See audit logs and search records.
• For a stop on an alert, was the alert confirmed through ALETS, NCIC or another source? See ALPR alert traffic stops.
• Was the data drawn from another agency’s system, and whose retention rules applied?