When you press the little button on a Ring doorbell, you expect a delivery alert or a “someone’s at the door” chime. As of mid-October 2025, another invisible chain of events quietly became easier: local police using Flock’s surveillance tools can now ask Ring users for footage through Ring’s Neighbors app, via Ring’s “Community Request” program. It’s a technical handshake that—on paper—keeps sharing voluntarily. In practice, privacy advocates and even a U.S. senator are warning that it could widen an already sprawling patchwork of public-private surveillance.

Ring says the integration ties its Community Request workflow to law-enforcement platforms that run on Flock’s Nova or FlockOS. That means when a local agency using Flock believes Ring footage in a neighborhood could help an investigation, it can submit a Community Request that appears in the Neighbors feed for users in the selected area. The request must include details about the alleged crime, a timeframe and location for the footage, and what Ring calls a “unique investigation code.” Participation is optional—users can ignore or opt out of Community Requests—and Ring says agencies cannot see who received or responded to a request. Ring expects to roll the Flock integration out in the coming months.

Ring’s Community Requests are not a brand-new idea: the company has been testing and revamping ways for public-safety agencies to request footage since the Neighbors app was created. In 2024, Ring shut down its older “Request for Assistance” feature after criticism, but the company continued exploring integrations that it says preserve user control—most notably an April 2025 tie-up with Axon (the Taser maker and digital-evidence company), which similarly allowed agencies to request footage through vetted channels. The Flock link is the latest example of Ring stitching its enormous installed base into police evidence ecosystems.

Flock is not just another vendor of pole-mounted cameras and license-plate readers; it runs a large, AI-driven network used by thousands of law enforcement agencies and municipalities. In recent days, a letter from Sen. Ron Wyden and investigative reporting have raised alarms that Flock had allowed access—at least historically—to federal entities, including the Secret Service, the Navy and Immigration and Customs Enforcement. Critics argue that linking Ring’s consumer cameras to platforms that already surface vehicle scans and other metadata could substantially expand law enforcement sightlines into ordinary neighborhoods.

The fear isn’t hypothetical: when private vendors build searchable databases (license plates, vehicle characteristics, timestamps), they change who can ask what of whose footage—and how often. Combine Flock’s vehicle-scan network with millions of Ring doorbells and you get a far bigger, more searchable ecosystem than either company has on its own. That prospect is exactly what Wyden’s office called out in its correspondence and why civil-liberties groups have been warning about “function creep.”

Ring emphasizes two big user protections: (1) Community Requests are optional and appear publicly in the Neighbors feed; and (2) law enforcement allegedly can’t see who receives or ignores requests. Ring also points users toward privacy controls—you can disable Community Requests in Neighbors feed settings, and the company offers an end-to-end encryption (E2EE) option for stored video that, if enabled, is intended to prevent Ring (and thus third parties) from accessing your unshared clips. But there are practical caveats: E2EE must be turned on by each user (and not every Ring device historically supported it), and once a user chooses to share footage with an agency, Ring’s docs note that the footage cannot be retracted or deleted. Those technical details matter.

Ring also still reserves narrow exceptions for sharing data without user consent—an “emergency” carve-out similar to what other consumer camera platforms have used—so the warrantless sharing question has not entirely disappeared despite past policy changes.

Law-and-order officials and Ring frame these integrations as “helpful” tools that let neighbors assist investigations without handing officials a warrant. Privacy advocates and some lawmakers see them as private companies operationalizing what used to be strictly government searches: creating avenues where agencies can ask—for many users at once—for voluntary uploads, and where voluntary sharing can be nudged by the design of apps and notifications. Senator Wyden’s letter explicitly warned that Flock’s architecture made “abuses … not only likely but inevitable,” urging communities to scrutinize vendor contracts and access rules.

What you, a Ring owner, can do right now

If this news makes you uncomfortable, there are concrete steps you can take today:

• Opt out of Community Requests notifications: In the Neighbors app, go to Neighborhood Settings → Feed Settings and uncheck Community Requests. That disables the in-app posts about requests. (If you use the main Ring app, similar controls exist in the Control Center → Neighbors.)
• Enable end-to-end encryption (E2EE) for eligible devices in the Ring app (Menu → Control Center → Video Encryption → End-to-End Encryption) so unshared recordings are protected from retrieval by Ring itself. Note: older or battery-powered models aren’t always eligible; read Ring’s E2EE notes before you rely on it. Save your passphrase safely—if you lose it, you may lose access to your own encrypted clips.
• Think before you share. If a Community Request appears and you voluntarily upload footage, Ring’s documentation says shared footage is transferred to the agency’s evidence system (Axon Evidence or the agency’s chosen platform) and cannot be retracted.

The bigger question: regulation, not just settings

The Ring–Flock tie-up is another reminder that surveillance in the U.S. increasingly looks like a hybrid between private tech stacks and public safety functions. Vendors build searchable data sets and let agencies query them; consumers buy devices that can be co-opted into those datasets; municipalities and police departments sign contracts that determine who can see what. That patchwork raises classic questions for lawmakers: who audits vendor access, what limits exist on federal agency queries, are there rules about retention and cross-jurisdictional searches, and how is accountability enforced when private companies hold the keys to vast troves of visual data?

Sen. Wyden’s letter to Flock and the renewed scrutiny of Ring’s public-safety programs show one route forward: legislative and contract safeguards that limit federal and out-of-state access, clearer rules about emergency exceptions, and stronger user control baked into default settings. For many privacy advocates, it’s not enough to say “you can opt out”; defaults and system design steer behavior at scale.

Ring’s new Flock integration stitches another layer onto an already dense surveillance quilt. The company insists sharing is voluntary and that users retain control; critics point to past vendor behavior and federal access to Flock data as reasons to be wary. Whether this feels like practical community policing or an expansion of private-company surveillance depends largely on your trust in the platforms involved—and on whether policymakers and local governments tighten the rules that govern those platforms. If you’re a Ring owner who’s unsettled by the idea of unsolicited investigatory requests, now is a good time to review your Neighbors settings and consider turning on end-to-end encryption where possible.