California license plate reader law

California — D

All states

California sets no limit on how long a record of where your car was can be kept. Each agency decides for itself, and some decide years. A private company logging your trips here has to delete them if you ask. You have no clear right to see what has been collected about you.

Whether a resident can obtain their own plate history here is unsettled. A records request may be refused on that basis, and that refusal would not be unusual.

Limit on how long data is kept: None
No statewide cap on how long ALPR data may be kept. Each agency sets its own in its usage and privacy policy. Source
Private cameras regulated: Yes
Consumer privacy law reaches private operators, including a right to deletion. Source
You can see your own record: Unsettled
No statute grants a resident access to their own plate history. Whether the Public Records Act reaches it has not been settled. Source
Sharing restricted: Yes
Sharing with federal and out-of-state agencies is barred for local agencies. Source
Audits required: Partial
The statute requires a published usage and privacy policy and security safeguards, but no independent audit on a fixed schedule. Source

Graded on all five criteria. Read against the statute itself.

Write the deletion letter

Every state, compared

Where the vote stands

No votes yet. The first one decides the order.

Click a state to see how it does.

Retention counts double: how long a record of where your car was survives is the thing this tool is about.

Grades:ABCDF? Not examined

Vote for California

Reading a state properly is a day of work against its statutes, and the money pays for the tooling and some of the time. $1.00 of USDC is one vote for doing California next. It buys no promise about when.

Send exactly $1.000005 of USDC to

0x5AB284d85d6d5a2f702C732B2B1d6130fE3613F7
See what this address has received

Send that figure exactly. The last few millionths are how the chain records that the vote was for California, and they are worth a twentieth of a cent.

Send it on any of these, and it is the same address on all of them: Base, Arbitrum, OP Mainnet, Polygon PoS, Unichain, Linea, Avalanche, Celo, Ethereum.

It has to be real USDC, the one Circle issues. A bridged version — USDbC, USDC.e — is a different contract with the same ticker, and the count will not see it.

Every contract above was checked on its own chain on 2026-08-29: it reports the symbol USDC and six decimals, or it is not counted.

Molt sees none of this. The payment happens in your wallet and the record is public on the chain, which is also how the count is kept. Nothing stops the same person paying twice.

USDC contract, checked 2026-08-29