Colorado license plate reader law

Colorado — F

All states

Colorado has a cap, but a long one. A limit measured in months or years is a record of everywhere you went in that time. 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.

This state exempts this data from public records. The records branch dead-ends here, and asking will not change that.

Limit on how long data is kept: Weak
Colo. Rev. Stat. § 24-72-113. Passive surveillance records must be destroyed after three years. The cap is general rather than plate-reader specific. Source
Private cameras regulated: Yes
Colorado has a comprehensive consumer privacy law in effect carrying a right to delete, which reaches a private operator. Source
You can see your own record: No
Colo. Rev. Stat. § 24-72-113. No right of access to your own record is given. Source
Sharing restricted: No
Colo. Rev. Stat. § 24-72-113. The section governs how long passive surveillance records may be kept and places no restriction on who they may be shared with. Source
Audits required: No
Colo. Rev. Stat. § 24-72-113. No audit or report is required. 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 Colorado

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 Colorado next. It buys no promise about when.

Send exactly $1.000006 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 Colorado, 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