Security vs. Privacy; What’s The Right Balance?

I spoke recently at a conference on the topic of smart cities and security, and specifically on security-related projects implemented on a district scale. In preparing my remarks, I reflected back on my days working in emergency management for the City of New York and recalled the successes of programs like the Lower Manhattan Security Initiative. While I wasn’t personally involved with this public: private partnership, it is often touted as one of the earliest- and most successful -smart city initiatives in the world. However, it hasn’t been without its detractors and controversies, and it reflects the changing perceptions of privacy and security over the years since it was first implemented.

In New York City in the years following 9/11, increased security measures were widely accepted, even at the expense of some measure of personal privacy. I remembered gathering with personnel from the city’s emergency services agencies for a live disaster drill in 2011. New Yorkers from the neighborhood, after inquiring as to what we were doing, offered us coffee and opened their doors to us. A positive sentiment toward our efforts was something we had all grown accustomed to, even as the years passed after 9/11 and the overwhelming support citizens gave first responders in the aftermath faded. 10 years later, New Yorkers still seemed to accept that securing their city against a myriad of ever’changing threats involved giving up some measure of privacy.

A few years ago, I relocated to San Francisco and discovered very different cultural ideas about privacy versus security. Friends in the emergency management world described protesters at counter-terrorism drills decrying the “police state,” something that I found shocking after dedicating my career to these sorts of efforts with the intent of serving my community. My fiance, a native San Franciscan, tried to explain this phenomenon by describing widespread distrust of law enforcement, his mother’s experience with police harassment at Berkeley in the 1960s, and citizens’ exhaustion with marijuana-related stops and other minor offenses. So when I spoke about New York City’s security successes at that conference on the west coast, I was met with some “big brother” tweets accusing me of disregarding privacy. While this didn’t surprise me after learning more about these cultural differences, I took the opportunity to discuss the issue with peers and colleagues and gauge their feelings and concerns on the topic.

While technology has improved security and quality of life around the world, fears remain about the potential dark side of “smart city” technology. I came across an example of this years ago where a foreign government was using security technology, ostensibly rolled out to protect civilians, to also keep tabs on them. As a security professional with a career dedicated to making our cities safer, this was especially upsetting to me, and one of the reasons that I firmly believe in using aggregate rather than individual data. On the other end of the spectrum, I learned that a major west coast city recently elected to take its shot detection system offline in the face of privacy concerns.

Smart city security projects and other related technologies hold great promise. As we have seen, early rollouts have notched many successes and saved lives. But privacy considerations are a major concern for many people, and we at Armored Things are focused on these issues as we develop our products. For example, we do not employ the use of facial recognition technologies, for they are not core or necessary to our value proposition. At Armored Things, privacy is one of our main priorities. As we continue to explore these issues, we strive to maintain an open dialogue with partners, peers, and practitioners, and seek the balance that protects the public without violating privacy rights.

Employee Spotlight: Josh Hartley, Chief Architect

Josh Hartley, Chief Architect at Armored Things is a playful balance between fun and serious. Passionate about both programming and civil service, Josh has been a natural leader on Armored Things’ engineering team.

As a Chief Architect at Armored Things, Josh is responsible for collaborating with the rest of the engineering team to design and build Armored Things, physical security, and operations software.

“I tend to work as a hub for technical discussions, so I have a pretty deep insight on all of the individual projects,” he said. “In general, it’s really about communication and collaboration to ensure that we’re in sync and on track.”

Since he was a kid, Josh has always had an affinity for software development and enthusiasm for civil service – making him the perfect fit to lead Armored Thing’s mission-driven team.

“My skills lend me to software development, so I’ve always been searching for a way I can use my skills to help people solve real problems,” he said. “I think our solution is unique or I wouldn’t believe in it the same way.”

Before joining Armored Things, Josh worked at Carbon Black.

When asked how Armored Things has been different from his past experiences, he said, “I’ve never been in a situation in an early startup that has had quite the same business momentum. It is especially different that we have both some of the top business and technical minds.”

“Being able to see our team grow from only one person writing code to many people writing code has been my favorite thing about where we are as a company right now,” he continued.

For candidates looking to join Armored Things, Josh emphasizes the importance of demonstrating a willingness to learn and work hard. “I’m constantly learning and working on improving my skills, I think that is an essential quality in our team.”

When Josh isn’t at work, he is playing board games with his friends and fiance Audrey, cooking, and weightlifting.

If you want to learn more about internships and job opportunities at Armored Things, check out our careers page.