Automated license plate readers are already part of Huntsville's public-safety network. Here is what the public record confirms—and what residents still cannot verify—about who owns them, who can search them, and where the data goes.
I have said publicly that I would not provide ALPR systems as a tool to law enforcement. Because the network is already in use, the immediate priority is accountability. Residents should be able to see the governing policy, understand who has access, and verify how searches, sharing, retention, and misuse are handled before the City considers any further expansion.
Here is the policy problem: Alabama Rule 265-X-6-.08 says a “capturing agency” must adopt and publicize a written LPR policy before capturing or using LPR data. That policy must address database comparisons, retention, sharing, and operator training. Yet I found no ALPR-specific policy in HPD's public library of 199 operating directives as reviewed on August 11, 2026, nor elsewhere in the City and HPD material reviewed for this page. The 2024 Flock packet specifies 30-day retention, but its order form incorporates terms from a “previously executed agreement” that are not included in the public six-page packet.
This does not prove HPD has no internal policy, and this page does not make a legal finding about compliance. It means a complete, Huntsville-specific policy covering permitted searches, prohibited uses, sharing, exports, audits, and consequences for misuse was not located in the public record reviewed. The public cannot evaluate a policy it cannot read.
FOX54 asked the District 3 candidates about Flock cameras. This is an embedded copy from FOX54 News Huntsville's official YouTube channel; the campaign has not downloaded or republished the station's video.
An automated license plate reader, or ALPR, photographs vehicles that pass a fixed or mobile camera. Software can identify a plate and record the time, location, vehicle image, and descriptive details such as make, model, and color. An authorized user can search recent reads for a plate connected to an investigation, and some systems can send an alert when a listed vehicle passes a camera.
That is different from issuing a speeding ticket. The value to police is that a plate sighting can help locate a vehicle or reconstruct movement. The privacy concern is that the same searchable history can reveal where an ordinary person traveled even when that person is not suspected of a crime. A camera hit should be treated as an investigative lead, not proof that a particular driver committed an offense.
The City had already acknowledged using strategically placed license plate readers in April 2021, but that official article did not name Flock, identify private owners, or disclose sharing terms. I found no earlier City or HPD announcement of the specific six-camera Flock arrangement. WAFF's February 2022 report is cited because it is the earliest public source located for that arrangement and attributes the details directly to HPD Investigator Mike Eichhorn. He said the cameras were privately owned, mostly at HOA properties and businesses, and HPD was not buying additional units at that time. This does not describe every camera operating today.
On September 12, 2024, the Council approved Resolution 24-697, authorizing the Mayor to contract with Flock Group for HPD. The official order form described two Falcon cameras, 30-day retention, a 24-month initial term, and a $13,300 total.
The item was approved with the New Business consent agenda. The minutes record no separate discussion or item-specific public comment. Minutes are summaries, so that does not prove no one ever mentioned the subject.
EFF's Atlas of Surveillance identifies Flock use by HPD, Huntsville Airport Police, and the Madison County Sheriff's Office. Within the fixed Huntsville-area boundary used for this review, the current DeFlock/OpenStreetMap dataset contains 101 community-mapped ALPRs from multiple manufacturers. That count changes with the boundary and community updates; it is not an official ownership inventory.
HPD's North Alabama Multi-Agency Crime Center predates the 2024 purchase. City descriptions say license plate readers are placed strategically and that the center supports intelligence sharing among agencies. More recent WAFF reporting says HPD users must provide a tag, case number, and search reason.
Within the review's fixed Huntsville-area boundary: 39 Flock Safety, 43 Motorola Solutions, 17 Avigilon, and two Genetec units.
Six Flock Safety cameras, two Motorola Solutions cameras, and one Avigilon camera fall inside the City's official District 3 boundary in the current community dataset.
The numbers describe different things. The 2024 City contract covered two HPD Flock cameras. The fixed community-map boundary used for this review contains 39 Flock-branded units and 101 ALPRs of all mapped brands. Nine mapped ALPRs fall inside District 3. Separately, 112 outside agency portals list Huntsville HPD as a data recipient. Camera hardware and data-sharing connections are not the same count.
The statewide rule is broader than city police departments, but it does not place the same duty on every camera owner. Its definitions and duties draw several important lines:
The chapter is directed to Alabama state, county, and municipal public agencies charged with enforcing laws whose officers or employees have arrest authority. That can include police departments, sheriffs, airport police, and other qualifying public agencies.
The rule defines this as the law-enforcement agency that operates an LPR and generates LPR data under its control. That agency must adopt and publicize the written policy described in Rule 265-X-6-.08.
It may not necessarily be the capturing agency. Even so, Rule 265-X-6-.04 says any law-enforcement agency that captures or uses LPR data must log the person accessing it, the date and time, and the purpose.
An ordinary business, HOA, or individual is not a “capturing agency” under this chapter merely because it owns a camera, and I found no policy-filing requirement for those private owners in the rule. A private vendor that maintains data for a capturing agency must agree to and submit an ALEA CJIS contractor/vendor security agreement.
Merely searching privately owned cameras may not make HPD the capturing agency for those cameras. It would still make HPD a law-enforcement agency using LPR data, with the access-log duty described above. For the City-contracted cameras, the public order form names HPD as the customer, but the complete operational and data-control terms were not included in the packet reviewed. The public record does not establish the legal classification of every camera or sharing arrangement, and this page does not attempt to make that legal finding.
The Huntsville Airport Police transparency portal reports two cameras and 30-day retention. It also publishes rolling 30-day counts for vehicle detections, searches, and hotlist hits; an acceptable-use policy; prohibited uses; a search-audit download; and a list of agencies granted access to Airport Police data. DeFlock's August 11 network snapshot showed 235 visible connections for the Airport Police portal.
HPD has no public Flock transparency portal and does not publish its sharing partners. DeFlock's network view finds 112 incoming, inferred connections because those outside agencies list Huntsville HPD in their own portals. DeFlock shows zero confirmed outgoing or mutual connections—not because it has proved HPD shares with no one, but because HPD publishes no portal from which that side of the relationship could be confirmed.
The real network may be larger. Agencies without a portal—or agencies that redact their sharing lists—cannot add a visible connection to this public count. The Airport Police portal proves that local disclosure is technically possible. Why Huntsville's primary police department does not provide comparable disclosure remains unanswered.
Examples of agencies whose published portals identify Huntsville HPD as a recipient:
Confirmed from the current community dataset: nine mapped ALPR cameras fall within District 3. That corrects the earlier impression that Southeast Huntsville had none. It still does not tell us who owns every camera or why those locations were selected.
Unanswered: No official document found in this review explains the distribution. The 2024 council packet did not identify installation sites or mark a council district. The earliest network followed participating private owners; police may prioritize travel corridors or investigative locations instead of equal district distribution; and a community map may be incomplete or outdated. Those are possibilities, not established reasons. The City should publish its placement criteria and a count by owner and council district while withholding only the precise details that would create a documented operational risk.
These cases do not establish misuse in Huntsville. They show foreseeable failure patterns that a local policy should address. “Charged” and “accused” do not mean convicted; employment actions are not criminal findings.
WBRC reported in July 2026 that a Moody employee was terminated and a Springville officer resigned after separate investigations found Flock-policy violations. Both matters were referred to ALEA. Public reporting provided limited detail.
WAFF reported that former Albertville officer Jeremy Hannah was arrested after allegedly searching ACJIS/LETS for information about an ex-spouse and a relative without a legitimate purpose. The reported searches were in ACJIS/LETS—not identified as Flock—so this is an example of the broader risk of personal access to law-enforcement databases, not a confirmed Flock case.
The Georgia Bureau of Investigation says five former officers were arrested in July 2026 after an internal audit found they had used retained Flock plate data for non-law-enforcement purposes. The cases were to be sent to the district attorney; the investigation remained active.
WTOC reported that Fayetteville fired three officers after an audit found searches outside their work—including plates belonging to themselves, friends, or family. The department asked the GBI to investigate. Separate reporting described arrests or employment actions involving personnel from other Georgia agencies.
Prosecutors said officer Josue Ayala used Flock 179 times for personal reasons to track a person he was dating and that person's former partner. He later pleaded guilty to attempted misconduct in public office and received 12 months of probation and a $500 fine.
WBTV reported that an officer was charged after allegedly querying an undercover officer's plate in Flock and another database, then providing the information to the target of a drug investigation. The allegation remains subject to the court process.
CBS Los Angeles reported that former officer Robert Jay Josett pleaded guilty to misdemeanor charges after using law-enforcement tools, including Flock readers, to track his wife, another woman, and romantic rivals.
InvestigateTV/WTOC reported that a security researcher found dozens of Flock Condor cameras streaming on the open internet without password protection. Flock attributed the exposure to a cellular-provider configuration error. This concerned video-camera feeds, not proof that the license-plate database itself was breached.
Other reporting has raised concerns about cross-state searches involving immigration enforcement, an abortion investigation, protest activity, and location-history searches without a warrant. Courts and state laws do not speak with one voice on every use. The policy lesson is narrower: purpose limits and sharing rules must be written, auditable, and enforceable before a controversial request arrives.
Each question stands on its own. The concern beneath it is not an accusation; it is what the missing public record leaves residents unable to rule out.
No ALPR-specific policy appeared in HPD's 199 published operating directives or the other City and HPD material reviewed for this page.
The answer determines where the statewide public-policy duty applies, but the public packet does not map the operational and data-control relationships across the mixed public/private network.
The rule requires the agreement when a vendor maintains a capturing agency's data. No public copy or filing confirmation was located in the materials reviewed.
Airport Police publishes one. Without an HPD explanation, residents cannot tell whether the absence is a delay, a policy choice, or resistance to disclosure.
The 112 visible incoming relationships answer only part of the question because HPD's side of the network is not public.
Zero publicly confirmed outgoing connections is not evidence of zero outgoing sharing when the agency has no portal.
Without a published role list and technical restrictions, residents cannot know how narrowly access is limited.
A policy field that accepts generic text is weaker than a system that verifies an active case.
The public needs written rules covering personal relationships, domestic disputes, protests, political activity, immigration-only requests, abortion-related investigations, and civil matters.
If only system users or their direct chain of command review the logs, misconduct may remain invisible until a victim complains.
Without regular reporting, Council cannot demonstrate that oversight is occurring.
Exports, screenshots, case files, alerts, and records received by partner agencies may outlive the vendor's automatic deletion window.
Residents need a correction process and a rule requiring independent verification before a stop or enforcement action.
A pole's location does not reveal whether the City, an agency, a business, or an HOA controls it or grants access.
Without placement criteria, the public cannot evaluate effectiveness, equity, duplication, or mission creep.
A search, alert, or camera hit is activity—not by itself proof of a solved crime or improved safety.
I would request and publish, with lawful redactions for active cases and genuine security needs:
Residents should not have to reverse-engineer a regional surveillance network from camera poles and scattered contracts. If a record cannot be released, the City should identify the legal basis and explain what can be disclosed instead.
The immediate responsibility is to make the existing network legible to the public. I would press for the contracts, incorporated terms, written policies, access controls, sharing relationships, retention rules, audit results, and substantiated misuse findings residents are entitled to evaluate.
This is compatible with supporting police work and protecting civil liberties. If the City asks residents to trust a powerful surveillance system, the City must show that its rules, controls, and results can withstand public scrutiny.
Send the policy, contract, audit, public record, or correction. This page will be updated when reliable evidence changes or clarifies the record.