Your HOA Is Installing Flock Cameras. Here's What to Do

The uncomfortable moment usually comes in an email, a board packet, or a neighbor’s text: the HOA is installing Flock cameras at the entrance. Maybe the board calls them “license plate readers,” “safety cameras,” or “gate security.” Either way, the practical question arrives fast: you may not have voted, but you may still pay through dues, and your vehicle data may become part of a system the association—not each individual homeowner—controls.

That is why Flock cameras in a neighborhood are not just a home security purchase. They are also a privacy, surveillance, contract, and governance decision. The New York Post reported on Aug. 19, 2026, that more than 200 homeowners associations nationwide had signed with Flock, often funded directly from resident dues and frequently without putting the decision to a vote; the same report described homebuyers canceling showings after checking surveillance maps and finding HOA camera systems that were not obvious in disclosure paperwork. [1]

Timing changes almost everything. Before a contract is signed, residents can press for a recorded vote, contract review, spending limits, data-sharing restrictions, retention terms, audit access, and state-law review. After installation, the tools are narrower: opt-out settings, transparency portals, maps, records requests where public agencies are involved, and pressure on the board to amend, pause, or terminate the contract.

The first issue is not the camera. It is who gets to be the “customer.”

Flock’s materials describe data as customer-owned and describe sharing as configurable. In an HOA setting, that phrasing needs to be translated into plain association governance: the “customer” is likely the association or community entity that signs the contract, not every homeowner whose dues fund it or whose plate is captured at the entrance. Flock’s own FAQ and trust materials describe customer-controlled data and resident self-registration tools, but they do not turn every resident into an individual data controller. [2][3]

That distinction is where many HOA disputes begin. A board member may think the association is buying a practical tool for package theft, gate damage, or suspicious vehicles. A resident may experience the same decision as a surveillance system added to daily life without a vote. Both can be true. The administrative question is whether the board has documented the spending authority, the data authority, the sharing settings, and the resident notice before committing the community.

Do not let the discussion stall at “no facial recognition” or “it only reads plates.” Those claims may matter, but they are not the whole decision. If you need the technical baseline, NestGrid has separate explainers on what Flock cameras record and retain and why Flock cameras are structurally different from ordinary home security cameras. For an HOA resident, the urgent issue is more concrete: who can search the data, who can share it, who audits the searches, and who can change those settings later.

Before signing: make the board price the whole obligation

Flock does not publish a universal public price list, so any HOA discussion should label pricing as reported, quoted, or contract-specific. Placa.ai’s pricing explainer describes commonly reported Flock Safety pricing around $2,500 per camera per year, plus roughly $250 to $350 in one-time installation costs, under a lease model in which the customer does not own the hardware; the same discussion flags auto-renewal and price-escalation language as terms to review rather than assume away. [4]

The annual structure matters. A board may present the system as a small safety upgrade because the entrance only needs a few cameras. Residents should ask for the math in the form they will actually bear it: total annual camera fees, installation charges, any cellular or service charges, taxes, insurance or indemnity obligations, renewal increases, cancellation costs, and the budget line that will pay for it. A one-time capital improvement debate is different from a recurring surveillance subscription paid out of dues.

The board should also say whether the cameras are being funded from operating funds, reserves, a special assessment, or a security budget already approved by the community. If the governing documents require owner approval above a spending threshold, for capital improvements, or for long-term contracts, residents should ask the board to identify the clause it is relying on before the contract is signed.

Documents to request while there is still leverage

• The full proposed contract, including exhibits, order forms, renewal terms, price-escalation language, cancellation rights, and indemnity provisions.
• The exact camera count, locations, annual cost per camera, installation charges, and total first-year and renewal-year cost.
• A written statement of whether the association leases or owns the equipment, and what happens to the hardware if the contract ends.
• The proposed retention period, who can change it, and whether any vendor-announced default is actually written into the HOA’s agreement or policy.
• A list of every law-enforcement agency, neighboring community, or private entity that can access or receive the data, plus who can approve new sharing later.
• Audit-log access: who reviews searches, how often, whether residents can inspect aggregate audit information, and what happens after a misuse complaint.
• Resident notice language, signage plans, guest and vendor notice, and whether camera use will appear in resale or disclosure packets.
• A state-law review from association counsel, especially if the community is in a state with ALPR-specific limits.

A board that will not circulate the contract before signing is asking residents to accept a privacy policy by invoice. That is backwards. The hard questions—retention, sharing, audit access, renewal, and resale disclosure—are easiest to answer before the association has already committed money and defended the decision in public.

Data-sharing terms should be voted on as terms, not left as settings

In many HOA conversations, “sharing with police” gets treated as a yes-or-no moral position. The contract question is more specific. Which agency? For what purposes? By default or only on request? Can officers search directly, or must the HOA approve access? Are hotlists used? Are searches audited? Can the board chair change settings without another board vote? Can a future board expand sharing after residents stop paying attention?

Because Flock describes sharing as customer-configurable, residents should not assume that one HOA’s settings match another’s. That cuts both ways. A board cannot defend a vague proposal by saying “Flock owns the data” if its own vendor materials describe customer control. Residents also cannot assume that every Flock installation automatically shares with every police agency. The association has to show its actual settings and its policy for changing them. [2][3]

If law enforcement access is part of the proposal, the board should put the access model in the minutes. A clean motion is better than a verbal assurance: approve or reject named sharing partners, require board approval for new partners, require periodic audit review, and require resident notice if sharing settings materially change. NestGrid’s separate guide to Flock law-enforcement audit controls covers the police-side audit concepts in more detail; the HOA version is simpler: do not approve a system unless someone is responsible for reading the logs and reporting what changed.

State law can change the answer

Some boards discuss license plate readers as if the vendor contract is the only rulebook. It is not. Washington’s SB 6002, effective March 30, 2026, imposed a 21-day default deletion period, restricted ALPR data sharing to judicial proceedings, and required a probable-cause warrant for ALPR data collected by private entities, according to the Municipal Research and Services Center. [5]

That does not mean Washington’s rules apply to every HOA elsewhere. It means residents should make the board answer a dated, jurisdiction-specific question before signing: what state or local ALPR law applies to this community today, and does the proposed contract comply with it? If the board cannot answer without asking counsel, that is a reason to pause the vote, not a reason to install first and research later.

If the cameras are already installed, start with the contract and the renewal date

Once the pole is up, residents often shift straight to “Can I opt out?” That is understandable, but the first practical document is still the contract. Ask for the signed agreement, invoices, board minutes approving the purchase, the current camera locations, the data-sharing settings, and the renewal or cancellation date. If the association refuses, use the inspection rights available under your HOA documents and state association law.

The renewal date is not housekeeping. It is leverage. A board that has already defended installation may be unwilling to reverse itself immediately, but renewal creates a natural point for a new motion: amend sharing settings, reduce retention, require notice, suspend expansion, bid alternatives, or decline renewal. If auto-renewal language exists, residents need to know the notice deadline before it quietly passes.

Safe List is useful, but it is not a universal opt-out

Flock’s Safe List or Authorized Access List can allow residents to self-register their plates so footage of their own vehicle is deleted within their own community. The limit is just as important as the feature: it does not stop other Flock cameras from capturing the same plate once the vehicle leaves that community. [2][3]

That makes Safe List a local deletion tool, not a network-wide privacy exit. Residents should still use it if they want the protection it offers, but they should not let a board describe it as a complete answer to neighborhood surveillance. For a closer walkthrough, see NestGrid’s guide to the Flock license plate reader opt-out.

Use portals, maps, and records requests to verify what was not disclosed

After installation, residents should separate three kinds of evidence. First, association records show what the HOA bought and approved. Second, Flock transparency materials may show participating agencies or deployments, depending on what is public for that location. Third, crowdsourced maps can help residents spot nearby readers, but their counts and placements should be treated as community-maintained indicators, not official inventories.

NPR reported in February 2026 that DeFlock, a crowdsourced map of license plate readers, showed more than 76,000 readers; that number is useful as a dated snapshot of mapping scale, not as a definitive count of every active camera in every neighborhood. [6]

Public-records requests can help when a city, police department, or other public agency has access to the HOA’s camera data or has a related agreement with Flock. The HOA itself may not be subject to public-records law in the same way a city is, so residents often need two tracks: inspect association records from the board, and request agency-side records from the public entity. Useful requests can include memoranda of understanding, data-sharing agreements, audit logs, policy documents, hotlist rules, and emails discussing the HOA installation.

Reversal is possible, but it is not automatic

Communities have reversed Flock decisions, but the record is uneven and local. The New York Post reported that Saranac Lake killed its Flock contract by a 4–1 vote after cameras had gone up. [1] NPR reported that Oshkosh approved and then revoked a Flock contract within one day, and that Flagstaff and Santa Cruz ended contracts amid surveillance and immigration-enforcement concerns. [6] ABC7 Chicago reported on debates and contract endings involving Chicago-area communities including Evanston and Oak Park. [7]

Those examples should not be read as a script that works everywhere. A village board, city council, and HOA board operate under different laws, political pressures, and contract terms. They do show something narrower and still important: once residents can point to a signed agreement, renewal clause, sharing setting, or public controversy, the debate becomes concrete. The board can no longer keep the issue in the soft language of “being proactive.”

What to put in writing after installation

• Ask the board to publish the signed contract, current annual cost, renewal deadline, and camera locations to all residents.
• Request a written data policy covering retention, sharing, audit review, Safe List availability, and who can change settings.
• Ask for a board vote before any new sharing partner, new camera location, retention extension, or renewal.
• Use Safe List if it fits your risk tolerance, while documenting its community-limited scope.
• Check public transparency portals and crowdsourced maps, but label each screenshot with the date because these tools change.
• File public-records requests with police or municipal agencies if they can access the data or helped arrange the deployment.
• Ask the association to add surveillance contracts to resale and disclosure packets so buyers are not discovering the system from a map before a showing.
• Organize around a specific remedy: amend sharing, shorten retention, require audits, pause expansion, disclose to buyers, or vote not to renew.

The resale issue is easy for boards to underestimate. If buyers are checking surveillance maps before tours and canceling showings, then the camera system is not only a privacy preference or a security expense. It can become part of how the property is perceived in the market. The New York Post’s reporting on canceled showings and thin disclosure practices should be enough to make any board treat resale notice as a governance item, not an afterthought. [1]

Treat new vendor guardrails as contract questions, not settled outcomes

On Aug. 13, 2026, Flock announced guardrail changes including a seven-day default retention period, Evidence Mode, mandatory Audit Assistance, case codes, and multi-factor authentication. Those are vendor-announced policy and product changes; residents should ask whether the HOA’s actual agreement, settings, and audit practices reflect them before relying on them. The ACLU’s same-day response argued that seven-day retention still exceeds its 48-hour recommendation. [8]

For an HOA, the right response is not to debate a press release in the abstract. Ask the board to show the current retention setting, the audit process, who reviews case codes, who receives Audit Assistance reports, and whether residents will be notified if the vendor or board changes defaults later. If a safeguard is real, it can be documented in the association’s policy and minutes.

The cleaner path is before the signature

A neighborhood may have a real security problem. Package theft, gate damage, and repeated vehicle break-ins are not imaginary just because residents care about privacy. But an HOA board should not treat a license plate reader contract like mulch, lighting, or a pool-service renewal. The system creates recurring financial obligations and data-governance consequences for people who may never have had a meaningful chance to object.

If the cameras are only proposed, residents should push the board into the open: documented vote, full contract, total annual cost, lease and renewal terms, retention period, law-enforcement sharing limits, audit access, resident notice, resale disclosure, and state-law review before signing. If the cameras are already installed, residents still have tools—Safe List, transparency checks, maps, records requests, contract inspection, and board pressure—but those tools mostly work around a decision already made.

References

1. “HOA surveillance cameras draw backlash — and kill home sales,” NY Post, Aug. 19, 2026.
2. “FAQ,” Flock Safety.
3. “Trust,” Flock Safety.
4. “Flock Safety Pricing Explained,” Placa.ai.
5. “New Restrictions on Flock Cameras and Other ALPR Technology,” Municipal Research and Services Center, April 2026.
6. “Flock contracts canceled over immigration surveillance concerns,” NPR, Feb. 17, 2026.
7. “Raging debate around use of license plate readers: Are Flock cameras advancing safety or violating privacy?,” ABC7 Chicago.
8. “Flock Guardrails Address LPR Privacy Concerns and Police Transparency,” Flock Safety, Aug. 13, 2026.