In 1989, actress Rebecca Schaeffer was tragically murdered by a stalker who found her home address via California motor-vehicle records. This incident highlighted the privacy and safety risks associated with the public availability of personal data managed by state motor-vehicle departments. In response, Congress enacted the Driver’s Privacy Protection Act in 1994. This legislation aimed to regulate the disclosure and resale of personal data in state motor-vehicle records, allowing exceptions only for valid purposes like law enforcement and public safety.
The Legislative Background
The intent was clear: government-held personal information about drivers should not be freely shared or sold. Ironically, Congress addressed a technological issue. At the time, technology had made motor-vehicle records easily accessible, and existing laws were outdated. Over three decades later, technology has advanced further. Companies such as Flock Safety can independently gather license-plate information without relying on state databases. Their system collects images, vehicle details, dates, times, and locations without accessing DMV databases.
New Technological Challenges
This distinction is pivotal. The Driver’s Privacy Protection Act covers personal information in state records, not every piece of data a private company can observe on public roads. This raises a broader question: what occurs when technology enables private firms to generate information for identification and tracking purposes without needing government records?
Imagine driving past an automated camera. It records your license plate, the time, and location. One observation might seem trivial, but multiple records create something more revealing—a detailed account of vehicle movements. Without government assistance, a company can establish a database based on license plates, possibly bypassing the Act’s restrictions. Yet, the privacy issues that motivated Congress remain.
The Balance Between Safety and Privacy
Automated license-plate readers have valid uses. Law enforcement can deploy them to track stolen vehicles, investigate crimes, and handle public safety threats. These are legitimate interests, and privacy measures should not hinder police work. Nonetheless, public safety must not justify unchecked surveillance.
The crucial questions are about post-recording actions. How long is the data kept? Who accesses it? Is it shared? Can it be repurposed later? Recently, Flock Safety addressed some of these issues. On August 13, the company declared its intention to lower the default data retention period from 30 days to seven days and introduced safeguards like misuse detection and accountability measures. This change is significant. Reducing data retention from 30 to seven days makes a difference, but seven days is a suggestion, not a fixed rule. The actual retention can vary by customer contract or local law. This nuance highlights why the discourse should not focus solely on safety versus privacy. Seeing a vehicle on the road is one thing. A searchable database with repeated observations is another.
The Need for Updated Privacy Laws
The Driver’s Privacy Protection Act did not declare an absolute right to road anonymity. It acknowledged that identifying and locating data is risky when mishandled. Modern technology offers another way to track movements. The government doesn’t need to provide records; cameras can create them. This does not imply that automated license-plate readers should be forbidden. Instead, privacy laws must reflect current technology, not 1994’s. Americans need not choose between safety and privacy if sensible rules can safeguard both. Laws like the Driver’s Privacy Protection Act must evolve to match the technology of today, and foresee the developments of 2026.
Shaun M. Simmons has over 20 years of experience in public safety across private, state, and federal sectors. He currently works as an independent security contractor and political organizer in Canyon County, Idaho.