New Hampshire license plate reader law

New Hampshire — A

All states

New Hampshire requires reads that match nothing to be destroyed almost immediately. 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: Strict
Non-hit reads must be purged within three minutes of capture, destroyed and unrecoverable. Source
Private cameras regulated: Yes
New Hampshire 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: Does not arise
N.H. Rev. Stat. Ann. § 261:75-b. A non-hit read is destroyed within three minutes, so there is nothing held about you to ask for. Source
Sharing restricted: Partial
Captured data obtained for the permitted purposes may not be used or shared for any other purpose. Source
Audits required: Does not arise
N.H. Rev. Stat. Ann. § 261:75-b. There is no store of reads to audit; the statute requires the data to be destroyed rather than watched over. Source

Graded on 3 of 5 criteria. The rest do not arise here, for the reason given against each. 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 New Hampshire

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

Send exactly $1.000031 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 New Hampshire, 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