Minnesota license plate reader law

Minnesota — A

All states

Minnesota caps how long these records can be kept, in months rather than 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.

Limit on how long data is kept: Yes
Minn. Stat. § 13.824. Data not related to an active criminal investigation must be destroyed no later than 60 days from collection. Source
Private cameras regulated: Yes
Minnesota 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: Partial
Minn. Stat. § 13.824. No general right of access, but a participant in the Safe at Home programme may request destruction of data about them, and a person facing charges may request preservation. Source
Sharing restricted: Yes
Minn. Stat. § 13.824. Data not related to an active investigation may not be shared, disseminated, sold or traded unless the section or another law allows it. Source
Audits required: Yes
Minn. Stat. § 13.824. A public log is required, and an independent biennial audit of whether data is classified, how it is used, and whether it is destroyed as 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 Minnesota

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

Send exactly $1.000024 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 Minnesota, 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