H.R. 10691, introduced in the House on October 1, 2026, is not just another Flock Safety headline. The proposed Ban Flock Act would make automatic license plate reader use a funding and access question: who paid for the system, who can search the data, and whether a public agency can direct someone else to do what the agency could not do itself.
For private-property LPR buyers, the important part is not whether the bill becomes law in its current form. Most bills do not. The useful part is the contract test it exposes. If an HOA, university, parking operator, hospital, apartment owner or commercial garage is asked to host, share or subsidize plate data for a public agency, the buyer should be able to trace the money, data rights and search authority before the first camera goes up.
The Bill Treats ALPR Data As More Than A Camera Purchase
The introduced text of H.R. 10691 defines an automatic license plate reader broadly: cameras, sensors, software, databases or combinations that capture, record, analyze, store or compare plate information. It also defines captured plate data to include plate number, image, date, time, location, direction of travel, vehicle characteristics, confidence score and derived information.
That definition matters because it names sources that private buyers recognize: parking systems, private security networks, homeowners associations, commercial parking operators and data brokers. In other words, the proposed restriction is not framed only around police-owned roadside cameras. It follows the data and the access path.
The bill would prohibit federal agencies from acquiring, possessing, accessing or using ALPRs or captured plate data unless Congress later authorizes a specific use. It would also restrict certain federal funding to state and local governments that continue to use ALPR systems. The sponsors’ October 2 press release described the proposal as a response to nationwide plate-reader networks and AI-powered surveillance cameras; those claims are sponsor arguments, not proof that every deployment has the same architecture or risk.
The Operational Question Is Funding Chain First
A private LPR deployment can look private on a site map and still be tied to a public funding or access chain. The bill’s federal-funds language covers grants, subgrants, contracts, subcontracts, cooperative agreements, reimbursements, transfers, allocations and pass-through assistance. It also says recipients and subrecipients could not evade the prohibition by moving money between accounts, replacing non-federal funds, or directing another entity to conduct a prohibited activity on their behalf.
That does not mean every private parking camera or HOA entrance reader would be covered if the bill passed. Section 5(f) says the bill would not prohibit a state, political subdivision or other non-federal entity from using non-federal funds for otherwise lawful activity. The buyer problem is proving which bucket a deployment actually sits in.
Before a property signs an ALPR agreement connected to a city, police department, school district, grant-funded safety program or public-private partnership, ask for a written funding map. It should identify the purchaser, owner, installer, software subscriber, data controller, data processor, reimbursing entity, grant source and any pass-through recipient. If the answer is “the city pays for the camera but the property hosts it,” that is a different risk than “the property pays for a private parking system and does not share data with a public agency.”
Access Rights Matter As Much As Ownership
The second test is data access. The proposed bill is written around acquiring, possessing, accessing, searching, retaining, analyzing and disclosing plate data. A buyer therefore should not stop at camera ownership. A contract can create exposure through user accounts, hot-list integration, national lookup tools, investigative portals, API access, pooled databases, vendor support roles or data-sharing agreements.
Recent reporting shows why this issue is live. TechCrunch reported on October 2 that the bill would bar federal agencies from using ALPRs or tapping data collected by local police and private companies, while noting the proposal faces long odds. Separately, Semafor reported on October 2 that House Democrats questioned an FBI plan to acquire nationwide access to automatic license plate reader networks. Those are separate developments, but together they make one buyer question unavoidable: can an outside agency search the data, directly or indirectly?
For an HOA or apartment community, the practical answer should be documented in plain language: no shared law-enforcement network unless explicitly approved; no outside search without written legal process or board-approved emergency policy; named accounts only; redacted audit exports available to the property; and retention limits that match the approved property purpose. The broader public-safety ALPR versus private-property LPR distinction is only useful when the contract, user roles and audit logs support it.
The Tolling Exception Is Not A Parking Exception
One of the most important drafting details is the tolling exception. H.R. 10691 would allow ALPR use solely to assess, bill, collect, audit, dispute or enforce payment of a toll, subject to purpose, disclosure, retention, security and audit-log limits. It does not create a general parking-lot exception.
Parking operators should read that distinction carefully. A garage that uses LPR for monthly permits, QR payment, barrier entry, pay-on-exit billing or unpaid-session notices may have strong operational reasons for the technology. That does not make it a tolling system. The safer approach is to build a parking-specific evidence record: the facility purpose, customer notice, payment workflow, appeal path, retention schedule, support access and whether any public agency can search the data.
Placa.ai’s parking operator page currently describes QR payment, LPR entry and exit recognition, barrier control, permit management and white-label options. Those are private operational use cases. They should still be evaluated against the funding and access tests above whenever a public agency, grant-funded program or law-enforcement user is part of the project.
A Four-Part Review Before Signing
For buyers, the Ban Flock Act should prompt a short review rather than panic. First, map funding: private funds, public funds, federal funds, pass-through funds and reimbursements. Second, map data access: who can search, export, receive alerts, run support queries or request historical plate data. Third, map purpose: parking payment, gate access, school dismissal, towing documentation, public safety, tolling or a mixed use. Fourth, map exit: how accounts, stored reads, shared data, hardware and vendor backups are removed if the policy environment changes.
This review also helps compare vendors honestly. A switch from one ALPR brand to another does not necessarily change the funding source, access model or data-sharing obligations. Placa has a separate article on why changing the ALPR vendor does not end the surveillance network; the federal bill adds a related point: changing who writes the check may matter as much as changing the camera.
For a private property asked to host public cameras, the review should be even stricter. Require a hosting agreement that names the owner of the hardware, the operator of the software account, the agency with search authority, the retention period, the removal right, the public-notice plan and the process for responding to resident, tenant or driver questions. Placa’s private-property ALPR host consent guide covers that consent problem; the new federal bill gives buyers a reason to add funding-source and federal-access representations to the same packet.
What To Watch Next
The bill is only introduced legislation as of October 6, 2026. It may stall, change or become a bargaining marker for narrower ALPR rules. Buyers should not treat it as current law. They should treat it as a signal that ALPR procurement is moving from “which camera works” to “which institutions can access plate data, under what authority, with what money and for how long.”
That is a better buying question anyway. A property can operate a useful LPR workflow for access control, parking, towing documentation or school pickup only when the purpose is narrow enough to explain and the data controls are specific enough to audit. If the vendor, agency or reseller cannot draw that boundary in writing, the buyer does not yet have a deployable project.