Documented controversies · Timeline

The record is not a rumor mill.

Ring’s trust problem is built from court filings, company blog posts, and investigative reporting—not anonymous screenshots. Here is the arc that still shapes why people refuse the next “just share the clip” ask.

Every soft pipeline leaves a paper trail.

Why a timeline

Product names change. RFA becomes Community Requests. A Flock deal appears, then vanishes. The underlying pattern stays: make it easy for law enforcement to ask; keep participation “voluntary”; move clips into systems built for evidence retention and sharing.

  1. Pre–2018 → mid-2010s growth

    Unrestricted internal video access

    According to the FTC complaint, Ring gave employees and Ukraine-based contractors broad access to customer videos stored unencrypted, with weak controls on download and sharing—setting the stage for later abuse findings.

  2. 2017–2018 (alleged conduct)

    Employee “spy” access to intimate spaces

    The FTC alleged that at least one employee viewed thousands of recordings from female users—including cameras covering bathrooms and bedrooms—over months before another employee flagged the misconduct. Ring’s monitoring failures meant the company could not fully determine how widespread improper access had been.

  3. Police portal era

    Law-enforcement request tooling

    Ring built and promoted pathways for police to request neighborhood footage through Neighbors—criticized by privacy advocates as a frictionless bridge between consumer cameras and investigations, often with limited public visibility until later policy changes.

  4. May 2023

    FTC action & ~$5.8M settlement

    The FTC charged Ring with compromising customer privacy: overbroad employee/contractor video access, security failures that enabled hackers to take control of accounts and cameras, and related deceptive practices. Ring agreed to pay $5.8 million for consumer refunds and accept stronger privacy/security mandates. See Sources for the FTC press release and order.

  5. January 2024

    Request for Assistance (RFA) sunset

    After years of criticism, Ring announced it was sunsetting the Neighbors Request for Assistance tool. Public-safety agencies could no longer use RFA inside the app to request and receive video. Agencies could still post tips—and could still ask residents by other means, or use warrants.

  6. 2025

    Community Requests (via Axon)

    Ring later launched Community Requests with Axon: verified local public-safety agencies using Axon Evidence can post geofenced, time-bound requests with an investigation code. Ring owners may voluntarily select clips; shared video goes into Axon Evidence. Ignoring a request is private, per Ring. The voluntary framing remains—but the destination is a professional LE evidence platform.

  7. October 2025

    Flock partnership announced

    Ring announced plans to expand Community Requests to Flock Safety—an ALPR/surveillance vendor whose network has been reported as used in immigration-related searches via local-agency cooperation. Backlash followed.

  8. February 12, 2026

    Ring–Flock integration canceled

    Ring and Flock jointly canceled the planned integration before launch. Ring stated no customer videos were ever sent to Flock. Axon’s Community Requests channel remained. The cancellation matters—and so does everything that made the deal radioactive in the first place.

FTC findings, in plain language

Employees and contractors accessed private videos they should not have. Security was weak enough that hackers compromised accounts and cameras. The settlement was about $5.8 million plus court-ordered reforms—not a slap on the wrist for a paperwork error. That history is why “trust us with your porch” lands differently in 2026.

What did not change