Flock wanted to tap dashcams in rideshare vechicles to add to surveillance data

The proposal suggests a shift from static to dynamic surveillance coverage by leveraging existing dashcam hardware in rideshare fleets. This would allow Flock to expand its data collection without deploying additional fixed cameras, but it introduces dependencies on third-party vehicle operators and their camera systems. Engineers would need to design interfaces that can handle variable video quality, intermittent connectivity, and differing camera models across fleets.

Adopting this approach would require rideshare companies to expose their in-vehicle systems to external data pipelines, which may conflict with their own data policies or passenger agreements. The cost includes not only technical integration but also potential pushback from drivers or riders concerned about expanded monitoring. System reliability could suffer if rideshare operators modify or disable cameras without notice, breaking the data feed.

The proposal blurs the line between private vehicle recordings and public surveillance infrastructure. While it could improve incident response or traffic analysis, it also raises questions about consent, passengers may not expect their rides to contribute to a broader surveillance network. Engineers would need to address how to anonymize or filter data to comply with privacy regulations, which may limit the utility of the footage for real-time applications.