Flock Safety / Ringdoorbell Camera Feed Partnership

Our Take

Credit to RTP Tech Tips for surfacing this one early. A Ring-to-Flock pipeline is exactly the kind of quiet infrastructure build we watch for: two massive private camera networks — one blanketing driveways and porches, the other blanketing roads and parking lots with ALPR and audio sensors — start talking to each other, and suddenly "neighborhood watch" starts to look a lot like a distributed, corporate-run surveillance grid with a law enforcement backdoor.

The video is right to flag the "owner consent" caveat, but consent regimes in this space have a bad habit of eroding. Terms of service change, defaults get flipped, acquisitions happen, and "opt-in today" quietly becomes "opt-out if you can find the setting" tomorrow. Once footage and plate data start flowing into shared systems — and especially once analytics platforms like Palantir are anywhere near the pipeline — the practical protections depend entirely on corporate policy, not law, and corporate policy can be rewritten overnight.

This is why tracking the physical footprint of these networks matters as much as tracking the partnerships. If you want to see how far Flock's camera network already reaches in your area, check our map, and if you want to push back on local ALPR deployments or doorbell-data sharing programs, our take action page has concrete next steps.