Key Takeaways
- Your socio-economic status often dictates your stance on public safety tech, with affluent individuals prioritizing privacy and less privileged communities prioritizing safety.
- Residents of secure neighborhoods, like Park Heights, with access to private security, generally push back more against surveillance tools like Flock Safety's license plate readers.
- Communities experiencing higher crime, lacking private guards or gates, are typically the strongest advocates for technology that promises increased security.
- Jason Calacanis draws a line at data retention, accepting license plate data for 2 to 30 days, but firmly rejecting facial recognition or a national government database.
- Garret Langley, Flock Safety's CEO, notes that those who “don't have any other way to protect themselves” are the ones who "want this" technology.
The Unseen Divide: Privilege and Public Safety
When Flock Safety CEO Garret Langley sits down with Jason Calacanis on the All-In Podcast, the conversation quickly turns to a raw truth: your neighborhood often dictates your view on crime-fighting technology. It's a truth many overlook, especially founders building products meant to serve broad markets.
Calacanis didn't mince words, advising listeners, “you have to be extremely aware of your own privilege” when talking about crime. His point? If you don't personally deal with crime, your perception of security needs is likely skewed. He referenced historical measures, like New York's “stop, frisk, and ask” policies in the 70s and 80s, which, while arguably a “violation of the fourth amendment,” arose from a desperate need to combat a city "dangerous as hell."
This isn't an abstract point. Calacanis highlighted a direct correlation: “people who experience crime are in favor of it.” Conversely, “People who live in Pack Heights, they don't need to worry about this, man. something goes down in Pack Heights, there's 20 cops and 50 private security guards.” His observation cuts to the core: if you're surrounded by security, both public and private, the idea of more surveillance feels intrusive. If you're not, it feels like a lifeline.
Why Your Security 'Need' Isn't Universal
Langley echoed this sentiment from his vantage point at Flock Safety, a company deploying license plate readers and drone technology. He pointed out the disparity directly: it's “typically people who don't have any other way to protect themselves, who need this, right? who want this.” He contrasted this with those who already possess “a gate and have a guard and have cameras and have a security system and they have Jaime's incredible doorbell camera.” For these privileged groups, more technology often feels unnecessary, a step too far into privacy infringement. They ask, “Why does why does anyone need to feel any safer?” because their baseline of safety is already so high.
Calacanis drew his own line in the sand, showing where even he, a proponent of some data collection for safety, hits his limit. “I don't want the government to have like a national flock database. I don't want the government to do facial recognition. I find that like a bridge too far.” His compromise: “The license plates for two weeks or 30 days. I kind of feel okay with it.” This shows the individual balancing act, but also how personal context shapes where that line gets drawn. The less immediate the threat, the shorter the acceptable data retention period, and the fewer the types of data collected.
What to Do With This
For any founder building products with real-world impact, especially in areas touching public services or sensitive data, this conversation is a wake-up call. Don't assume your personal views on privacy or security represent your entire user base. Tomorrow, pull your user persona documents. For each persona, add a new dimension: "Security Context." Map out whether they live in a high-crime area, have access to private security, or depend solely on public resources. Then, revisit your product's privacy settings, data retention policies, and feature priorities through each of those lenses. What feels like an optional 'nice-to-have' for one group might be a non-negotiable lifeline for another, and understanding this gap is key to building a product that truly serves all your users.