Montana license plate reader law

Montana — B

Montana 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.

Limit on how long data is kept: Yes: Mont. Code Ann. § 46-5-118. Data may not be preserved for more than 90 days, unless a preservation request or a warrant applies. Source
Private cameras regulated: Yes: Montana 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: Yes: Mont. Code Ann. § 46-5-118. The protection from disclosure applies \u201cexcept to the person to whom the license plate is registered\u201d. Montana is one of two states that says so. Source
Sharing restricted: Partial: Mont. Code Ann. § 46-5-118. The data is a public record protected from disclosure under Title 2, chapter 6. Source
Audits required: No: Mont. Code Ann. § 46-5-118. 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.

AKF MEC VTC NHA WAF IDF MTB NDF MNA ILF WIF MIF NYF MAF RIF ORF NVF WYF SDF IAF INF OHF PAF NJF CTF CAD UTD COF NEC MOF KYF WVF VAF MDD DEF AZF NMF KSF ARD TNC NCC SCF DCF OKF LAF MSF ALF GAF HIF TXF FLD

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 Montana

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

Send exactly $1.000027 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 Montana, 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