Can You Actually Opt Out of Flock License Plate Readers?

As of August 25, 2026, there is no Flock Safety privacy setting that lets a resident opt a vehicle out of all Flock license plate reader cameras. The phrase “opt out” usually blurs three different questions: whether a camera captures a plate, how long the data is retained or used, and what oversight the camera owner accepts.

A resident cannot stop every Flock camera from capturing a plate when the vehicle passes a camera. A resident may be able to reduce how one residential community searches for that vehicle if that community has enabled Flock’s Safe List. And a resident, HOA member, or city voter may be able to push the camera owner toward shorter retention, restricted sharing, Evidence Mode, public transparency, or removal of cameras. Those are different levers. Treating them as one “privacy setting” is how people end up clicking through a maze and still having no answer.

If you are trying to understand what Flock collects and why it does not behave like a camera in your own smart-home app, NestGrid’s Flock Safety smart-home concerns backgrounder is the better place to start. This guide stays on the control question: what can you click, request, or demand today?

The Safe List is the only self-service-looking opt-out path, and it is community-limited

Flock’s Safe List is the setting most likely to be mistaken for a general opt-out. It is not one. Flock’s FAQ describes Safe List as a residential-customer feature: communities can choose to let residents add their vehicles to a list so those vehicles are not searchable within that community’s Flock system. Flock also says a vehicle on one community’s Safe List is still detected by other Flock cameras outside that community.[1]

The July 2026 Flock SafeList blog describes the resident path as an administrator-controlled process. A community administrator uses the Flock admin dashboard at admin.flocksafety.com to create or share the Safe List signup link, and residents use that link to submit vehicle information for that community’s list.[2] That detail matters more than the product name. If your HOA or neighborhood has not enabled Safe List or has not given you the link, there is no public Flock page where you can simply enter your plate and remove it from the network.

For a homeowner or tenant, the practical path is short:

1. Ask the HOA, property manager, neighborhood association, or community security administrator whether the community is a Flock residential customer and whether Safe List is enabled.
2. Ask for the Safe List signup link generated through the community’s Flock admin dashboard.
3. Submit only through that community-provided link, then ask what information is stored, who reviews submissions, and how updates or removals are handled.
4. Do not assume approval affects any camera outside that neighborhood or HOA boundary.

A useful HOA answer sounds operational: “Safe List is enabled; here is the signup link; these board members or managers can administer it; it applies only to our community cameras; and here is how residents can update or remove their vehicle.” A vague answer about “privacy by design” or “the vendor handles that” is not an opt-out path.

What to ask before you treat Safe List as protection

• Is Safe List enabled for this exact residential community?
• Who has administrator access to approve, edit, or remove Safe List entries?
• Does the community share data with law enforcement agencies or neighboring communities, and does Safe List change any of that sharing?
• What happens when a resident sells a vehicle, changes plates, moves out, or wants the entry deleted?
• Is there a written policy residents can read, or only an informal board practice?

The main mistake is thinking Safe List changes the camera’s ability to see. Based on Flock’s own FAQ, it changes searchability within one participating residential community; it does not make the vehicle invisible to the broader Flock network.[1]

The privacy-request form exists, but Flock says it cannot process requests for public-space LPR images

Flock also has a privacy-request route, including a OneTrust webform for submitting privacy requests.[3] This is where the interface becomes especially easy to misread. A form can feel like a control even when the policy behind it excludes the data you are trying to reach.

Flock’s Privacy Policy, dated Aug. 1, 2025, states that license plate recognition footage from public spaces does not contain Personal Information connecting an image to an identifiable individual. The same policy says Flock is unable to process data-subject requests related to such images.[4] That is Flock’s stated position; it should not be treated here as settled law for every jurisdiction or every future dispute. But it is the policy position a resident will run into when trying to use the form to delete plate reads.

So the answer is blunt: the OneTrust form is not a reliable way to remove your license plate footage from Flock’s public-space LPR records. It may be the correct channel for other privacy requests Flock recognizes under its policy, but the policy itself draws a wall around the very images most drivers are asking about.

If you still submit a request, keep the record. Save the date, the request type, the exact plate or vehicle information you provided, the response, and any denial language. That documentation may matter more in an HOA meeting, city council record, or agency appeal than it does inside the vendor form.

Retention controls reduce exposure, but Flock’s own pages do not give one clean number

After Safe List and the privacy form, the conversation shifts from opt-out to exposure management. Retention is the first setting to inspect because it controls how long a plate read remains useful for later search. This is also where Flock’s public materials need to be read by date and page, not blended into a single reassuring number.

The Aug. 1, 2025 Privacy Policy points to 30-day deletion language for LPR footage, subject to exceptions.[4] Flock’s Trust Center uses softer language, saying data is often deleted after 30 days and describing audit logging as part of its privacy and security posture.[5] Meanwhile, Flock’s FAQ and its Aug. 13, 2026 guardrails post refer to a 7-day retention default or recommendation, and the guardrails post also discusses Evidence Mode and more than 1,500 transparency portals.[1][6]

Those statements may reflect different products, contract settings, rollout stages, or policy pages. The resident-facing problem is that “auto-delete” does not answer the next question: auto-delete after how many days, for which customer, under which exceptions, and who can change it? Until the local agency or HOA supplies its actual setting or contract term, the safest reading is not one neat retention period. It is a menu of vendor statements that need local confirmation.

For a deeper claim-by-claim look at “auto-delete” and similar assurances, see NestGrid’s Flock Safety camera privacy claims guide.

Transparency portals and audit logs are oversight tools, not personal controls

A transparency portal can be useful. So can audit logs. But neither is the same thing as a privacy settings page in a consumer camera app. Flock’s Aug. 13, 2026 guardrails post says the company has more than 1,500 transparency portals and describes Evidence Mode as a way to require more justification for searches.[6] Flock’s Trust Center also points to audit logging.[5]

Those controls matter because they change who can search, what reason must be attached, and what the public or oversight body can later inspect. They do not stop a camera from capturing a vehicle. They also do not give a driver a private account where the driver can turn off collection. If your comparison point is a doorbell or home security camera with account-level retention and sharing settings, NestGrid’s Flock cameras vs. home security privacy explainer covers why the control model is different.

The practical use of a transparency portal is evidence gathering. Check whether your local police department, city, county, or HOA-facing agency appears. Look for retention language, sharing partners, hot list rules, search policies, and contact information. If the portal only proves that the system exists, it still gives you a starting point for a public-records request or public meeting question.

When individual opt-out is missing, the real levers are local policy and contracts

Civil-liberties groups have been direct about the weakness of individual control. The ACLU’s “Get the Flock Out” campaign says communities have almost no meaningful way to audit, challenge, or opt out of Flock’s system.[7] The Electronic Frontier Foundation has similarly criticized Flock’s reforms as insufficient and describes the absence of individual opt-out as a core problem.[8] StopFlock also frames opt-out as effectively unavailable for ordinary drivers.[9]

Those are advocacy positions, not vendor documentation. They become useful after the mechanics are clear: the critiques match what the resident interface shows. Safe List is narrow. The privacy form excludes the plate footage at issue under Flock’s stated policy. Retention and portals are governed by the customer, not the passing driver.

Local governments do have room to move. NPR reported in February 2026 that Flagstaff, Arizona, kept Flock cameras while adopting a 14-day retention period and restricted sharing, and also reported that more than 30 localities had canceled Flock contracts since early 2025 amid immigration-surveillance concerns.[10] That is the kind of middle path a resident can actually ask a council or agency to adopt: shorter retention, tighter sharing, clearer search rules, or cancellation.

The Hill reported in August 2026 on Flock’s privacy updates and quoted the ACLU calling them a “thinly veiled PR attempt.”[11] The quote is sharp, but the more important resident question is still operational: did the local customer change a setting, amend a contract, publish a policy, restrict sharing, or remove cameras?

What to ask your HOA, city, police department, or camera owner

If the system is in a private residential community, start with the HOA or property manager. If the cameras are on public roads or tied to a police agency, start with the agency, city council, mayor’s office, procurement office, or public-records process. The same vendor language can sit behind very different local rules.

• Safe List: Is it enabled for this community? Who controls the signup link? What does approval do, and what does it not do?
• Retention: Is the local setting 7 days, 14 days, 30 days, or something else? Is that in the contract, an admin setting, or only a vendor recommendation?
• Exceptions: What keeps a plate read longer than the standard retention period? Who can place data into evidence, export it, or preserve it?
• Evidence Mode: Is it enabled? Are searches required to include a case number, reason, or other justification?
• Sharing: Which agencies, neighboring communities, task forces, or outside entities can access the data? Can sharing be restricted by policy or contract?
• Audit logs: Who reviews searches, how often, and what happens when misuse is found?
• Transparency: Is there a public portal? Does it show retention, sharing partners, camera locations or general deployment areas, policy documents, and contact information?
• Exit: When does the contract renew, what is the cancellation process, and what happens to stored data when the contract ends?

For a residential board, the smallest meaningful improvement may be enabling Safe List and publishing a written resident policy. For a city, the stronger asks are shorter retention, restricted sharing, Evidence Mode, independent audit review, public transparency, and a contract vote instead of automatic renewal. For a resident trying to protect one vehicle today, those may feel indirect. They are still more real than hunting for a non-existent network-wide toggle.

This is also where Flock differs from consumer security products that expose account settings directly to the device owner. A Ring owner, for example, can evaluate account-level retention and sharing controls in a way a driver passing a Flock camera cannot. NestGrid’s Ring camera privacy and data-retention guide is a useful contrast because it shows what actual consumer-facing settings look like.

The honest answer

If your search was “flock safety license plate reader privacy settings how to opt out,” the answer is narrower than the search box suggests. There is no universal consumer opt-out setting in the cited Flock materials as of August 2026. Safe List can help only inside a residential or HOA community that enables it and supplies the signup link. Flock’s privacy-request process exists, but its Privacy Policy says public-space LPR footage is not handled as Personal Information connecting an image to an identifiable individual and that Flock is unable to process data-subject requests for those images.[1][2][3][4]

What remains is not nothing. Residents can ask for shorter retention, restricted sharing, Evidence Mode, audit access, transparency portals, Safe List enablement for residential communities, or cancellation. Those are privacy controls in the civic and administrative sense. They are not a setting that removes your vehicle from Flock’s network.

References

1. Flock FAQ — Flock Safety
2. How the Safe List Solves Privacy Concerns in a Neighborhood — Flock Safety, July 2026
3. Flock Safety Privacy Request Form — OneTrust
4. Flock Safety Privacy Policy — Flock Safety, Aug. 1, 2025
5. Data Privacy — Flock Safety Trust Center
6. Flock Guardrails Address LPR Privacy Concerns and Police Transparency — Flock Safety, Aug. 13, 2026
7. Get the Flock Out — ACLU, updated Aug. 20, 2026
8. Too Little, Too Late: Flock Admits Their Technology Needs Reforms — Electronic Frontier Foundation, August 2026
9. StopFlock
10. Flock contracts canceled over immigration surveillance concerns — NPR, Feb. 17, 2026
11. Flock cameras AI surveillance privacy updates — The Hill, August 2026