A 30-Month ALPR Data Retention Question

Our Take

Credit to Buntai for zeroing in on the number that almost never gets debated in public: retention. Everyone argues about whether ALPRs should exist at all, but the real policy lever is how long your travel history sits in a database waiting to be queried, subpoenaed, hacked, or quietly shared with another agency. A 30-month window isn't a technical necessity — it's a choice, and it's usually made by a vendor's default settings rather than a city council vote.

Here's the uncomfortable math: Flock Safety and similar systems market themselves as solving car break-ins and stolen vehicles, crimes where investigators typically need days or weeks of data, not years. When retention stretches well past that, the system stops functioning as an investigative tool and starts functioning as a permanent, searchable map of everywhere your car has ever been. That distinction matters enormously once you consider who else can query that history — ICE, out-of-state prosecutors chasing abortion or trans-care cases, a jealous ex with a badge. Longer retention just means more exposure windows for abuse that has already been documented in jurisdiction after jurisdiction.

If your town hasn't published its retention policy, or if the number quietly crept up from 30 days to 30 months without a public vote, that's worth raising at the next council meeting. Check our camera map to see what's already deployed near you, and use our take-action guide to push for retention limits, audit logs, and real public oversight before the data piles up any higher.