Facility Parking Guide Practical Parking Solutions for Facility Managers

License Plate Recognition Privacy and Data Retention: What Facility Managers Should Put in Policy

A California appellate ruling treats a missing public LPR policy as actionable harm. Here is what a parking LPR privacy and retention policy should say, and how states differ.

License Plate Recognition Privacy and Data Retention: What Facility Managers Should Put in Policy

A license plate recognition system in a parking facility does not just check who may enter. Every read creates a record of a vehicle at a place and time, and once plates are linked to permits, payments or accounts, those records can describe a person’s routine. The legal risk has moved accordingly. In February 2026 a California appellate court held, in Bartholomew v. Parking Concepts, Inc., that a parking operator’s alleged failure to implement and publicly post the usage and privacy policy California requires was enough to plead harm. Review was denied in May, and law-firm commentary describes a wave of class actions following it. A July 2026 decision, Mata v. Digital Recognition Network, went the other way for an operator that did have a compliant policy, which is the point: having a real, posted policy is the difference.

This article covers what that policy should contain and how retention rules vary by state. It is operational guidance, not legal advice; confirm requirements for each state where you operate with counsel.

Why a written policy comes first

California’s ALPR statute (Civil Code section 1798.90.5 and following) applies to private operators, not only police. According to law-firm summaries of the statute, the operator’s policy must address authorized purposes for using the system, who may access it including training, any sale, sharing or transfer of the data, security measures, and retention. It must be conspicuously posted on the operator’s website. The statute provides a private right of action with $2,500 in statutory damages per violation, plus attorneys’ fees.

Even outside California, the same document does double duty. It tells the public what you do, and it gives your staff, vendor and insurer a single reference when something goes wrong. Drafting it also forces the inventory most facilities have never done: where plates are captured, where images and reads are stored, and who else can see them.

What the policy should say

Purpose limitation. List the specific uses: access control, permit enforcement, payment reconciliation, wayfinding or occupancy counting. Anything not on the list, such as marketing profiles or resale, should be expressly prohibited unless counsel has cleared it.

What is collected. Distinguish plate text, plate and vehicle images, timestamps and location, and any linkage to an account, permit or payment card. Linked data is more sensitive than anonymous reads, and the policy should say when linkage occurs.

Who has access. Name roles, not people: facility manager, enforcement staff, vendor support. State training requirements and keep an access log. California’s statute expects operators to log access, and it is good practice everywhere.

Sharing. State whether data is shared with law enforcement, enforcement contractors, collection agencies or other property owners, and under what process. A common rule is that law enforcement requests go to counsel or a named compliance contact and are documented. If you do not sell the data, say so plainly.

Security. Describe encryption in transit and at rest, access authentication and vendor responsibilities in general terms. Do not publish configuration details.

Retention and deletion. This is the section that most often fails in practice, so it deserves its own treatment.

Setting a retention period

There is no uniform national number. State rules differ, and many apply mainly to government users, so find out whether the law in your state reaches private facility operators before copying a figure. A 2026 state-by-state comparison and NCSL’s statute tracker show the range:

  • Arkansas sets a 60-day limit for private landowners, leaseholders and commercial businesses, and 150 days for other eligible entities, with an exception for data held in an active investigation. Per NCSL’s summary, private users must also compile statistics on scans and matches every six months. Verify against the current statute text.
  • Maine lists 21 days for non-investigative use, under a statute that restricts use of the technology by persons generally, with exceptions for listed government users.
  • California sets no fixed retention number for private operators; the operator’s own policy must state its retention and destruction practices, which means you will be held to what you publish.
  • Tennessee has a 90-day rule, but the comparison reports it applies only to government entities; private lot owners face signage requirements before enforcing with readers.
  • New Hampshire (three minutes for non-hit data) and Minnesota (60 days for non-investigative data) are framed around law enforcement use. They show how strict some legislatures get and the direction of travel, rather than binding your garage.

Because a comparison page can lag a legislature, treat every figure here as a lead to confirm, not a compliance threshold.

For the retention value itself, tie it to the shortest period that serves each stated purpose:

  1. Entry and exit matching for paid parking: keep reads until the transaction is closed and any dispute window has run, then delete.
  2. Permit enforcement: keep violation evidence for the appeal period; delete non-violation reads on a short cycle.
  3. Occupancy or analytics: aggregate the counts and discard plate-level data.
  4. Legal hold: a defined process to suspend deletion for specific records when there is an incident, claim or valid legal request.

Whatever you choose, the system should delete automatically. A retention period that depends on someone remembering to purge a database is a retention period you will miss.

Vendor contract terms that make the policy real

Your policy is only as accurate as your vendor’s behavior. Confirm in the contract that the vendor processes plate data only on your instructions, does not use it to build its own datasets or sell it, deletes on your schedule and certifies deletion, notifies you of a breach within a stated time, and returns or destroys data at termination. California treats ALPR data as personal information for purposes of its breach notification law, so a breach there carries notification duties. For the wider picture, see our guide to data privacy compliance for parking facilities and the vendor checks in access control cybersecurity and vendor risk.

Putting it into operation

Publish the policy on your website, and where a state or local rule requires it, post signage at entrances. Assign one owner who reviews it annually and whenever the system changes, such as adding a camera zone or a new data-sharing arrangement. Run a quarterly check that deletions actually occurred. And before any expansion, such as moving from LPR for access control to LPR for enforcement, update the policy first. The lawsuits now being filed are not about sophisticated misuse; they are about operators who captured plates every day and had nothing to show the public about what happened next.

Facility Parking Guide

A resource for facility managers navigating parking operations, maintenance, budgeting, and vendor selection. We provide practical, unbiased guides to help you manage parking assets effectively.