stopflock419
Chat with over 9000 of us on Discord!
Menu

Common Flock claims, answered.

Claim: These cameras are effective, accurate, and worth the cost.

“Flock makes us safer and solves crime.”

Flock can generate investigative leads, but the local record does not show a broad crime-prevention effect or whether a lead changed a case.

The Sylvania portal reviewed July 19, 2026, published reads, hot-list hits, and search sessions. Those are activity measures. It did not publish local false-alert totals, cases in which the system was indispensable, dispositions, relevant crime trends, or cost per validated outcome.

Independent ALPR evaluations are mixed: some found more stolen-vehicle recoveries or investigative activity, while randomized and quasi-randomized evaluations did not find a general deterrent effect or a reduction in auto theft from the ALPR treatment.

Local record

Sylvania’s 2023 police report called the city’s crime rate “very low,” while also reporting increases in some categories and warning that a few incidents can move percentages sharply.

Still unanswered

What defined local problem justified this system, and which published outcome would cause Council to expand, change, or end it?

“It costs less than one police officer.”

Even if the comparison is accurate, price does not prove need, effectiveness, or superiority to every other use of public money.

“Cameras or an officer” skips the prior question: what unmet need requires more of either? Other choices can include no expansion, targeted investigation, retaining current staff, lighting, traffic design, youth services, victim services, or returning the money.

A fair comparison also uses the same time horizon and includes subscriptions, installation, maintenance, renewals, administration, removal, and the full cost of alternatives.

Local record

Sylvania authorized $97,250 for 15 cameras and software in 2023. In 2025, Council separately authorized $90,000 for a 15-camera agreement. Those actions may overlap or replace earlier terms, so they should not simply be added together as a lifetime total.

Still unanswered

Show the need, every alternative considered, the five-year cost of each option, and the measurable result each option is expected to change.

“Human verification prevents false stops.”

Human review can catch some errors. It cannot correct a bad plate read, a bad hot-list entry, or a mistaken inference by itself.

Flock’s own policy warns that translated plate data can be incomplete or inaccurate and tells users to confirm the plate before taking action.

Even a correct plate read describes a vehicle observation; it does not identify the current driver or prove why anyone was there. A machine hit is a lead—not proof of identity or guilt.

Local record

Sylvania’s vendor-hosted portal, reviewed July 19, 2026, said hot-list hits require human verification. It did not publish how many alerts were rejected, corrected, or followed by no action.

Still unanswered

How many alerts were reviewed, rejected, corrected, and acted upon—and how many incorrect stops or complaints followed?

Claim: The data stays local, controlled, and short-lived.

“They’re just cameras—like a doorbell or traffic camera.”

They are cameras, but the important feature is what the system does after capture: structure, retain, search, alert on, and potentially share vehicle observations.

Flock describes a record containing a plate translation or vehicle characteristics together with the date, time, and location. The system can compare those observations with hot lists and support later searches.

Some private cameras are networked too. The distinction is not simply public versus private hardware; it is the scale, automation, retention, searchability, access, and purpose of the whole system.

Local record

The agreement approved by Lucas County on July 15, 2025 lists community, state, and nationwide lookup features alongside 25 readers. Commissioners rescinded the approval one week later.

Still unanswered

Publish a diagram showing what each camera records, where it goes, how long each record lasts, and every role that can search or export it.

“Only our local department can see the data.”

Local control cannot be assumed from the camera’s location. Access depends on the account configuration, network features, reciprocal relationships, and current rules.

The Lucas County agreement included community-network access plus state and nationwide plate lookups. The Sylvania portal reviewed July 19, 2026, listed local, out-of-state, and federally labeled organizations with access.

That list shows configured reach, not which organizations actually searched or used local data.

Still unanswered

Which organizations can access which local cameras today, through what access type, who approved each relationship, and what actual outside use occurred?

“The city owns the data, so the city controls it.”

Ownership matters. It does not by itself answer who hosts, administers, searches, exports, copies, preserves, or deletes the data.

Operational control also depends on account roles, encryption and hosting, vendor support access, sharing settings, recipient copies, integrations, logs, contract changes, and what happens when service ends.

The Sylvania portal reviewed July 19, 2026, said the department owns its data. A complete, signed set of terms shown to govern Sylvania today was not located in the public records reviewed through that date.

Still unanswered

Publish the operative signed contract and identify who holds every administrative role, encryption key, export right, deletion duty, and recipient copy.

“Flock never sells the data, so privacy is protected.”

A no-sale rule still allows other forms of access and disclosure. The public needs to know who can search, receive, export, keep, and demand the data.

Privacy depends on every material data flow: customer users, reciprocal or network lookups, downloaded evidence, service providers, legal demands, product support, and copies retained after a disclosure.

Flock’s current web policy, checked August 7, 2026, says customer data is not sold and also describes authorized-user access, support access, customer-controlled sharing, and disclosures required by law or policy. Those are different questions, not contradictions.

Still unanswered

After answering “Who can buy it?”, answer “Who can search it, receive it, export it, keep it, and require its disclosure?”

“Everything is deleted after 30 days.”

Thirty days is a stated ordinary-footage window in key records. “Everything” goes beyond what those records establish.

The Lucas County agreement lists 30-day retention, though commissioners rescinded its approval one week later. Sylvania’s vendor-hosted portal reported 30 days when reviewed July 19, 2026. Flock’s current web policy describes 30 days as a default that can vary with law or customer policy.

A footage-retention statement does not by itself explain exports, evidence preserved for a case, recipient copies, alert records, search and audit logs, backups, hot lists, or derived data.

Still unanswered

Which exact data classes are deleted after 30 days, which exceptions exist, who can extend them, and how can the public verify deletion?

Claim: Existing safeguards make serious privacy concerns unnecessary.

“Policies, search reasons, and audit logs prevent abuse.”

Policies state the rule. Logs record activity. Neither stops misuse unless officials review the records, investigate problems, and enforce consequences.

A policy is a rule. A required reason can add friction. A log can preserve evidence. A technical block can prevent an action. These are different layers and should not be described as interchangeable.

Meaningful oversight asks whether logs are complete and immutable, whether case identifiers are required, who reviews anomalies, how often review occurs, what findings are published, and what consequences follow.

Local record

Sylvania’s portal, reviewed July 19, 2026, said every access requires a valid reason and is stored indefinitely. It did not publish a local audit schedule, completed audit findings, or the number of improper searches found.

Still unanswered

Who audits every search, how often, against which case record, with what anomaly tests—and where can residents read the findings?

“There’s no facial recognition, so there’s no serious privacy issue.”

Flock says its fixed readers capture vehicles rather than faces. Its patent is broader: it describes facial recognition, people searches, and other objects across networked cameras.

A patent describes possible systems and claimed methods; it does not prove that a local roadside reader captures faces or that a local agency enabled facial recognition. Flock separately markets FreeForm people search for visible traits across enabled video while saying the feature is non-biometric and unavailable on its LPR cameras.

Privacy risk does not require a face. Combining searchable vehicle observations across locations and time can suggest routines involving medical care, worship, family, work, association, or political activity.

The same limit cuts both ways: a camera sees a vehicle, not the identity, intent, or guilt of its current occupant.

Still unanswered

What rules prevent searches for lawful sensitive activity, and what aggregate audit can show those rules are followed?

“License plates are public. People with nothing to hide shouldn’t care.”

The choice is not secrecy versus safety. It is one observation in public versus routine collection that can be retained, combined, and searched later.

An officer seeing one plate is not operationally equivalent to a network creating structured observations with a time and place, then making them available for alerts and historical searches.

Privacy protects ordinary lawful life, not just wrongdoing. The relevant questions are who may search, for which purposes, over what period, with which approval and review.

Still unanswered

Nothing to hide—from whom, under which rules, for which purpose, and for how long?

“If you oppose Flock, you’re anti-police.”

Supporting effective policing does not require supporting every tool, every deployment, or unlimited expansion.

A pro-accountability position can support targeted investigation while demanding a defined need, narrow purposes, current signed terms, controlled outside access, error reporting, independent audits, measurable outcomes, and a public renewal vote.

The question is not whether police should investigate crime. It is whether this system is proportionate, effective, governed, and removable if it fails its stated test.

Still unanswered

Will officials commit to enough policing to investigate crime—and enough limits to keep ordinary life from becoming the default search field?

Documented cases of access abuse

Sensitive-health investigation

Johnson County, Texas

83,345 cameras included in the larger documented search

A nationwide plate search was tied to an abortion investigation.

EFF published Flock search logs, a police incident report, and a lead detective’s sworn account. Two searches used the reason “had an abortion, search for female”; the larger reached 6,809 networks and 83,345 cameras. The same case number appeared on records describing a death investigation, and deputies consulted prosecutors about whether the woman could be charged.

A locally collected plate detection can become searchable evidence in another state’s investigation when an agency joins a broad sharing network.

Read EFF’s record-based reconstruction

Personal access abuse

Multiple U.S. jurisdictions

30 reported incidents listed by the Institute for Justice

Officers have repeatedly been accused of tracking romantic interests.

The Institute for Justice’s ongoing review of public records and reporting lists 30 incidents involving current or former partners, coworkers, or strangers. Its entries describe outcomes including arrests, criminal charges, firings, resignations, internal findings, and one no-contest plea. Most entries identify Flock; a few identify another or unspecified ALPR system.

An audit log can reveal abuse after the fact, but the tracker says only a few reviewed incidents were first found through internal investigations; many surfaced after a victim reported the conduct.

Review the Institute for Justice incident list

Indirect federal access

Nationwide requests through local agencies

4,000+ nationwide or statewide lookups identified in reviewed records

Local police access became a route for federal immigration searches.

404 Media analyzed Flock audit data obtained from Danville, Illinois and reported more than 4,000 nationwide or statewide lookups performed at federal request, as an informal favor to federal law enforcement, or with a potential immigration focus. Search reasons included “ICE,” “ICE+ERO,” “ICE WARRANT,” and “immigration.”

A federal agency does not need its own camera contract if a participating local agency is willing and able to run the search.

Read 404 Media’s investigation

Ask for an answer before the next purchase.

Bring one documented claim to the next public meeting and ask for an answer before another purchase or renewal.

Use the meeting statement Check the local record