Technology entity · ALPR

Automated license plate readers

Cameras that photograph every passing vehicle, read the plate with optical character recognition, and write a timestamped, geolocated record to a searchable database. The individual reading is mundane. The database is not — because a sufficient number of readers, retained long enough and networked widely enough, reconstructs where a person has been.

Straight answers

What is an automated license plate reader?

An automated license plate reader (ALPR) is a camera system that photographs passing vehicles, uses optical character recognition to read the license plate, and stores a record containing the plate number, a timestamp, and the camera's location. Most modern municipal systems upload these records to a networked database that can be searched later and, in many configurations, searched by other agencies.

Is an ALPR just a camera?

No. A camera records an image. An ALPR converts that image into a structured, searchable database record. The difference matters legally and practically: a photograph of a street requires a human to review it, while a database of plate reads can be queried in seconds for every place a specific vehicle has been seen.

Does an ALPR track people, or only cars?

Formally it records vehicles. In practice a vehicle is a strong proxy for the person who drives it, and a sequence of timestamped sightings is a movement history. Where that history shows a person parked — a place of worship, a clinic, a union hall, a lawyer's office, a partner's home — the inference about the person is immediate.

If I am in public, why does recording my plate raise a constitutional question?

Because the constitutional question has never been about a single observation. Anyone can see your car on a road. The issue is the aggregation: persistent, automated collection retained over time and made searchable produces something no human observer could assemble, and it does so for people suspected of nothing. Unsurveilled's position is that public life is not blanket consent to government tracking, and that the relevant limit is on what the government may build and retain, not on what may be glanced at.

Does a warrant requirement stop police from using ALPRs?

No, and that is the point of the ask. A warrant requirement of the kind Unsurveilled advocates targets access to historical, networked data about people who are not suspects. Real-time alerts on a stolen vehicle, an Amber Alert, or a plate connected to an active investigation are not what the requirement is aimed at. The distinction is between investigating a suspect and searching everyone's movement history to find one.

How long is license plate data kept?

It varies enormously by jurisdiction and by contract, from days to years, and in many places it has never been established publicly at all. Retention is the single field that most changes the privacy consequence of a system, which is why every jurisdiction dossier on this site carries it as an explicit field — including when the honest answer is "not established."

The mechanism

An ALPR does four things in sequence, and the privacy consequence is in the last one rather than the first:

  1. Photographs vehicles that pass within its field of view, without regard to suspicion.
  2. Reads the plate with optical character recognition.
  3. Records plate, timestamp, and camera location as a structured row.
  4. Retains and networks that row so it can be searched later — often by agencies other than the one that collected it.

Steps 1 through 3 describe an instrument. Step 4 describes an archive.

Where the constitutional argument actually sits

The weakest version of the case against ALPRs is “cameras are watching you in public.” That argument loses, and it should — a police officer may look at your car.

The stronger version is about what aggregation produces. One sighting is an observation. Ten thousand sightings across a metropolitan area, retained for a year and searchable by plate, is a movement history that no officer could have compiled by watching. It is generated automatically, about everyone, in advance of any suspicion — and it can be searched retroactively once someone becomes interesting.

This is the distinction Unsurveilled draws everywhere on this site:

Investigate suspects. Don’t surveil everyone.

Directed investigation of a person connected to suspected wrongdoing through lawful process is legitimate and useful. Building a searchable archive of everyone’s movements, and searching it later, is a different activity that happens to use the same hardware.

Reading a jurisdiction honestly

Four fields determine what a deployment actually means, and three of them are usually harder to obtain than the camera count everybody quotes:

FieldWhy it decides the outcome
RetentionThirty days is an operational tool. Two years is a movement archive. Same hardware.
SharingWhether a resident’s data leaves the jurisdiction, and who can search it without telling anyone locally.
Legal standardWhether a historical search needs individualized justification, or only a login.
AuditWhether misuse is ever discovered — and, as Chandler shows, how long that can take.

A city with 40 cameras, 30-day retention, sharing off by default, and a warrant requirement for historical search is in a substantially different position from a city with 12 cameras, two-year retention, and statewide sharing enabled. Camera counts alone tell you very little, which is why every dossier on this site carries all four fields — and says “not established” when that is the truth.

The honest case for the technology

Unsurveilled does not pretend the benefits are imaginary. Agencies do recover stolen vehicles with these systems, and they do generate leads in serious cases. Those claims are listed above as stated benefits because that is what they are: claims made by agencies and vendors, some well supported and some not.

What we ask is that the benefit be weighed against the actual configuration rather than the best-case description of it — and that a capability powerful enough to be worth buying be constrained by something more durable than the good intentions of whoever currently holds the login.

Stated benefits

Claims made by agencies and vendors. Listed fairly, not endorsed.

  • Locating stolen vehicles and vehicles associated with active investigations
  • Amber and Silver Alert response
  • Generating investigative leads in violent-crime cases
  • Identifying vehicles associated with outstanding warrants
  • Reducing the time officers spend manually checking plates

Documented harms

Outcomes on record, not hypotheticals.

  • Wrongful stops at gunpoint arising from misread plates or stale database entries
  • Officers querying the system for personal reasons unrelated to any investigation
  • Nationwide searches run from a single local agency's terminal
  • Retention of movement histories for people never suspected of any crime
  • Sharing configurations that expose local data to agencies a resident has never heard of

Recent Signal coverage

2d ago Arizona ALPR Public backlash

Arizona man arrested after bending Flock camera pole amid growing ALPR backlash

A Pinal County resident said he used his work truck to bend a license-plate reader pole so the camera pointed at the sky. He was arrested and faces a felony criminal-damage charge — in a state where two agencies have just walked away from their ALPR contracts.

Reported

Receipts

  • Research on the nationwide scale of automated license plate reader networksInstitute for JusticeUsed for context on the scale of ALPR deployment nationally. Cited for its own findings only; we do not restate its figures as Unsurveilled findings.NGO research
  • OpenStreetMap ALPR node data — nationwide extractOpenStreetMap contributors118,623 mapped camera coordinates retrieved via the Overpass API on 2026-08-15, queried per state across the 50 states and the District of Columbia, and committed as a snapshot. Community-contributed, licensed ODbL 1.0, attributed per record. These are volunteer observations, not Unsurveilled field verification — we have not personally confirmed any pole, and the Atlas labels them accordingly. Coverage is whatever mappers have recorded, so a place with no points has no OSM coverage rather than no cameras. Full extraction method, accepted tags, and known false-positive risks are documented at /atlas/methodology/. SUPERSEDES an earlier snapshot of 613 coordinates limited to the Phoenix East Valley; the ID is retained because published records cite it, and this note records the change rather than hiding it.NGO research

Verified as of