Balancing Transparency and Privacy: The Fight Over Public Access to ALPR Surveillance Data

By ✦ min read

<p>Automated license plate readers (ALPRs) have become a contentious tool in law enforcement, enabling mass surveillance of vehicle movements. Public records laws, such as Freedom of Information Acts, have historically allowed journalists, advocates, and citizens to uncover how these systems are used—and often misused. However, a troubling trend is emerging: state legislatures are passing laws to shield ALPR data from public view, citing privacy concerns. Critics, including the Electronic Frontier Foundation (EFF), argue these moves block essential oversight. This Q&A explores the tension between transparency and privacy, the harms of ALPR surveillance, and what a balanced approach might look like.</p> <h2 id="q1">What are ALPRs and why are they controversial?</h2> <p>Automated license plate readers (ALPRs) are cameras that capture and record license plate numbers, often mounted on police cars, traffic lights, or bridges. They scan thousands of plates per hour, logging location, date, and time alongside the plate data. The controversy stems from their ability to create detailed movement profiles of individuals over time. <strong>Privacy advocates</strong> argue that this enables mass surveillance without a warrant, chilling First Amendment activities and revealing intimate details about a person's life—such as visits to clinics, political meetings, or places of worship. Moreover, <em>misuse</em> occurs when data is shared across agencies or retained indefinitely, leading to potential abuse. Reports have documented cases where ALPR data was used for non-law enforcement purposes, like tracking journalists or political rivals. The scale of collection, often lacking transparency, makes it difficult for the public to know how their movements are being monitored and stored. EFF and other groups have used public records to expose these abuses, but new laws threaten that oversight.</p><figure style="margin:20px 0"><img src="https://www.eff.org/files/banner_library/foia-og-1.png" alt="Balancing Transparency and Privacy: The Fight Over Public Access to ALPR Surveillance Data" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: www.eff.org</figcaption></figure> <h2 id="q2">How have public records laws been used to expose ALPR misuse?</h2> <p>Public records acts (PRAs) and Freedom of Information Acts (FOIAs) are powerful tools for holding government accountable. Reporters, community advocates, and organizations like EFF have leveraged these laws to demand records about ALPR programs. For example, they have obtained data revealing <strong>the extent of scanning</strong> in certain neighborhoods, the frequency of “hits” on wanted plates, and the rates of false matches. These disclosures have uncovered <em>disparate impacts on marginalized communities</em>, misuse of data for personal purposes, and a lack of clear policies on data retention and sharing. In some cases, public records showed that police departments exaggerated the effectiveness of ALPRs, overstating crime-solving benefits while hiding error rates. By shining a light on these practices, FOIA requests have spurred public debate and policy changes. However, the same transparency tools are now under attack by legislation designed to exempt ALPR data from disclosure.</p> <h2 id="q3">What recent legislative trends threaten public access to ALPR data?</h2> <p>Several states have recently enacted or proposed laws that broadly block the disclosure of ALPR-related information under public records laws. These measures go beyond protecting raw data; they can also restrict access to <strong>aggregate statistics</strong>, <em>operational policies</em>, and even images of a person’s own vehicle. For instance, bills in Arizona and Connecticut aim to prevent the public from obtaining records about how many plates were scanned, where scans occurred, and how many “hits” resulted. Lawmakers often justify these moves by citing privacy concerns for individuals whose data might be released. However, critics argue that such broad exemptions undermine the very purpose of FOIA: to allow public scrutiny of government actions. The trend is particularly alarming because it treats the entire category of ALPR information—including metadata that reveals no personal identity—as off-limits. This approach not only prevents oversight but also violates the spirit of open government. EFF has opposed these bills, noting that they cut off vital avenues for detecting and correcting abuses.</p> <h2 id="q4">Why does EFF oppose bills that block access to ALPR records?</h2> <p>The Electronic Frontier Foundation (EFF) strongly opposes legislation that completely closes off public access to ALPR data. Their opposition stems from the proven value of such records in revealing <strong>systemic harms</strong>. Through public records requests, EFF and others have documented cases of data being shared with federal agencies, retained for years beyond policy limits, and used to monitor protesters or journalists. Blocking access would prevent future oversight, allowing <em>unchecked surveillance</em> to continue without accountability. Additionally, these bills often fail to distinguish between sensitive raw data—which might include specific license plate scans of individuals—and non-sensitive operational data like auditing logs or redacted statistics. EFF argues for a nuanced approach that protects genuine privacy without sacrificing transparency. They note that the police themselves have access to vast amounts of ALPR data; the public should have the ability to verify that this power is not abused. Without FOIA, the only check on government misconduct would be internal, which history shows is insufficient.</p> <h2 id="q5">What types of ALPR information are at risk of being hidden from the public?</h2> <p>The proposed restrictions cover a wide range of information, not just raw license plate scans. <strong>Critical categories include:</strong></p><figure style="margin:20px 0"><img src="https://www.eff.org/files/privacy_s-defender-site-banner-desktop.png" alt="Balancing Transparency and Privacy: The Fight Over Public Access to ALPR Surveillance Data" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: www.eff.org</figcaption></figure> <ul> <li>General information about the extent of law enforcement use, such as how many cameras are deployed and their locations.</li> <li>Details on data sharing between different police agencies or with third parties like private companies.</li> <li>Statistics on the number of scans conducted, where and when they occurred, and how many “hits” (matches to watchlists) actually happened.</li> <li>Analyses of false matches or error rates, which are essential for evaluating system reliability.</li> <li>Images of vehicles captured by ALPRs, even those belonging to the requestor themselves.</li> </ul> <p>This is not an exhaustive list. Some bills are so broad that they could encompass any record that “derives from” ALPR data, including audits or after-action reports. By hiding this information, lawmakers prevent the public from understanding the true scale and impact of ALPR surveillance. <em>Transparency is the antidote to abuse</em>, and without access to these records, communities cannot advocate for appropriate limits or hold police accountable for overreach.</p> <h2 id="q6">How can privacy and transparency be balanced regarding ALPR data?</h2> <p>A balanced approach recognizes that wholesale release of raw ALPR data could indeed violate privacy—revealing where specific individuals go, thus exposing private activities. However, outright bans on disclosure are not the answer. EFF advocates for <strong>targeted redactions</strong> and aggregation techniques that protect individuals while preserving public oversight. For example, statistics can be released without identifying license plate numbers. Policies and protocols can be disclosed with names redacted. <em>Independent oversight boards</em> could review sensitive data and report findings. Additionally, sunset clauses and mandatory audits can ensure that laws are periodically reassessed. A model law would require that data be kept for only a limited time, shared only under strict agreements, and subject to periodic public reporting. The goal should be to maximize transparency about government practices while minimizing harm to individuals. This means avoiding the false choice between total secrecy and total disclosure. Instead, legislatures should work with privacy advocates to craft rules that serve both values.</p> <h2 id="q7">What is the better path forward according to EFF?</h2> <p>EFF recommends a framework that neither bans all public access nor releases raw data indiscriminately. <strong>Key elements include:</strong></p> <ol> <li><strong>Preserve FOIA rights</strong> for aggregate and operational data, such as deployment numbers and error rates.</li> <li><strong>Require routine publication</strong> of anonymized reports on ALPR use, including scans per capita and demographic impact analyses.</li> <li><strong>Establish strong data governance</strong> policies that limit retention and sharing, and mandate periodic audits.</li> <li><strong>Create an independent oversight body</strong> with power to review complaints and recommend improvements.</li> <li><strong>Include sunset provisions</strong> so that any new exemptions expire unless reauthorized based on demonstrated need.</li> </ol> <p>This approach acknowledges that <em>privacy and transparency are not enemies</em> but can reinforce each other. By setting clear rules, the public can trust that ALPR data is used responsibly, and the government can be held accountable when it isn't. Legislation currently being proposed in Arizona and Connecticut fails to strike this balance. Instead, it prioritizes secrecy over scrutiny, which history shows leads to more abuse. EFF continues to advocate for laws that protect both privacy and the public's right to know.</p>