Kentucky license plate reader law

Kentucky — F

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

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: None: No state statute regulating automated license plate readers appears in the National Conference of State Legislatures survey of state ALPR statutes. Nothing caps how long a plate read may be kept in Kentucky. Source
Private cameras regulated: Yes: Kentucky 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: No state statute regulating automated license plate readers appears in the National Conference of State Legislatures survey of state ALPR statutes. No plate-reader statute grants a resident access to their own reads. Source
Sharing restricted: No: No state statute regulating automated license plate readers appears in the National Conference of State Legislatures survey of state ALPR statutes. Nothing restricts who these reads may be shared with. Source
Audits required: No: No state statute regulating automated license plate readers appears in the National Conference of State Legislatures survey of state ALPR statutes. No audit or report is required. Source

Graded on all five criteria. This state has no plate-reader statute to read. Its absence is established from the national survey of state statutes, and its privacy-law entry from the IAPP tracker.

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 Kentucky

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

Send exactly $1.000018 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 Kentucky, 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