That Tech Pod
Welcome to That Tech Pod, a podcast co-hosted by Laura Milstein, Gabi Schulte and Kevin Albert. Each Tuesday, That Tech Pod will feature in depth discussions about data privacy, cybersecurity, eDiscovery, and tech innovations with heavy hitters in the industry. Subscribe so you don't miss an episode! Visit thattechpod.com for more information.
That Tech Pod
An Optimistic Data Privacy Future With Uber’s Nishant Bhajaria
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Today on That Tech Pod, Laura and Gabi speak with Nishant Bhajaria. Nishant is an executive leader and industry-expert in the privacy and security space and currently serves as the Head of Privacy Engineering and Governance at Uber.
He is the author of Data Privacy, a guide for engineers on how to implement strong data privacy practices which is available now! Nishant also serves on the Advisory Board of Data Protocol, an education and training platform for developers whose job it is to protect consumer data.
Nishant believes it is important to ensure developers and engineers have the tools and training to implement smart, effective data privacy measures.
Follow That Tech Pod: Twitter-@thattechpodLinkedIn: LinkedIn.com/thattechpod website: thattechpod.com
Hello and welcome to that tech pod where we discuss all things e-discovery, data privacy, cybersecurity, and tech innovations. I'm Laura Milstein, and I have just this insatiable quench for tech knowledge.
SPEAKER_01And I'm Gabby Schulte, and my tech knowledge thirst isn't as intense as Laura's, but you know, it's up there.
SPEAKER_02That's why each week we're talking to experts in the industry to help us break down these topics. And Gabby, today, who are we talking to?
SPEAKER_01Today we're talking to Nishant Bajaria. Nishant is an executive leader and industry expert in the privacy and security space. And currently he serves as the head of privacy engineering and governance at Uber. He is the author of Data Privacy, a guide for engineers on how to implement strong data privacy practices. And he serves on the board, uh, the advisory board of Data Protocol, which is an education and training platform for developers whose job it is to protect consumer data. Nishant, welcome to the show.
SPEAKER_00Thank you so much for having me here.
SPEAKER_01Yeah, so you have this amazing background. When we talk about we bring on experts, you are 100% uh that type of person. So we want to know like what is your journey of getting into this industry? Normally we find people have really interesting stories. So let us know like how how you got interested and sort of how you came up to be, you know, uh head of governance and kind of on the advisory board of data protocol. It's all really impressive.
SPEAKER_00Uh thank you so much. Yeah. So I began my career as an engineer at Intel back in the day, once I finished graduate school. And even in the early days of my career, I was the engineer that always liked to ask questions. I never just took somebody's instructions. I heard generally it's been hard to mind my own business. I would ask, why are we doing it this way versus that way? And when I went from Intel to WebMD, this was late 2009, early 2010. We were in the throes of a healthcare debate. We were passing the Affordable Care Act, known as Obamacare. And I was the back-end engineer that routinely got files with sensitive healthcare data that was then used to process gift cards for employees of our customers. And I was the guy asking inconvenient questions like why is this file not encrypted? Why do we have this employee's data? We don't need this data to give them their gift card. And I asked those questions enough times for me to be able to get close enough to the attorney who was handling privacy for us at the time. And beyond that, I found a bunch of files that had data that was risky, and I would routinely write code to clean up those files. That's how I got into privacy. It was kind of a side job amid a side job. And then as the decade unfolded, Facebook and Google became public companies, global IDs, global internet, mobile platforms. It meant that the risk that emerges from data created the space for engineers that were decent at coding, which I'm not the best engineer in town, but I had my chops in place. But beyond that, somebody who could work with engineers, with attorneys, with policy folks, with enterprise customers, somebody who could write well. And in my college days, I was an engineer, but I also was part of the debate team. I used to write for the college paper. So the last decade has created this space for people like me who may not fit into one of these silos that we put engineers into, but an engineer that can travel across multiple platforms. So finally, I love protecting customer data. I like to think of customers as like my dad, for example. The only thing my dad does on the internet is he uses the Uber app to order cars to go from point A to point B. And he sends me fake news on WhatsApp. So how do we protect customers who are not experts? How do we make sure that we balance engagement with trust? So that's how I got into this space. And then of course, the last seven or eight years have been amazing. Netflix, Google, and now Uber and Nike before that. So it was a mix of sort of the time we live in and sort of my somewhat unique skill combination.
SPEAKER_01Love the description of your dad. I feel like it's such a dad.
SPEAKER_02That's exactly what I wanted to say. I was like, I'm into your dad right here. Like what he's doing is so relatable.
unknownThank you.
SPEAKER_02Um, so just to jump in for our audience, can you tell them, like, can you define what privacy is for our audience? Before we get too deep into it, why don't we start with that? And then I'll follow up with a question based on how you answer that.
SPEAKER_00Perfect. So I'm going to defer to somebody I hired a couple of weeks ago. She is an amazingly smart engineer. She'll be starting in my team fairly soon. I asked her the same question. How do you define privacy? She said privacy is the combination of tools and processes and judgment that begin once security has done its job. And I love the example because you have invested as a company to protect bad things from happening, sorry, protecting customers from bad things when it comes to outside bad actors. That is, how do you protect the customers from hackers, from people who would steal their data? How do you apply those same protections to the same customer when it comes to the insiders in your company? How do you protect them from bad access by other engineers, but from insider threat, from inappropriate retention of data? So that's kind of what privacy means. How do you make sure that your customers are protected from bad actors on the inside and the outside? The second definition I would say that's also pretty important is how do you make sure that the customer has control over their data? How do you make sure that they can look at what we have, how we use it, how long we use it for? So, how do you create this combination of protection and transparency? For me, that's what privacy is all about.
SPEAKER_02Yeah, that's interesting. So, based on that, my next question, and then we're gonna dive more into your book and your background and other things, but just staying on that for privacy. How do you think privacy is involving in the sharing economy and with consumers wanting to put more information out there for conveniences?
SPEAKER_00Yeah, and I think that's a great question. It's something that I think should have been discussed a lot more in the last five years. So I'm gonna go back to the last 10 years since you asked about my background initially. When I was an engineer, IT and the top-down management process was the way we did business. IT decided what laptop I could get, what phone I could get, what data I could collect, and my managers' OKRs or responsibilities became my responsibilities. It was very, very top-down. That gave us a more orderly disciplined engineering process, but it also made things very slow to get to the market. Remember how long it took Microsoft to compete with Google. And by which time they lost the productivity market to Google and they lost the mobile device management market to Apple. What has happened in the last seven years is that the engineering culture has become a lot more bottoms up, which means engineers make a lot of decisions. Sometimes I joke that being an engineering executive like me is like being the security person at a funeral home. Like there's a lot of people under you, but nobody really listens. The power is bottom-up now. So this means that the equation has fundamentally changed. We have gone from consumers give us data and we give them products to understand to having a conversation about is big tech too powerful? Are customers being taken for a ride? And I feel like that's where we're at right now, where people genuinely are wondering like Steve Bannon on one side, Bernie Sanders on the other side both agree big tech is bad. Now, I agree with neither assessment, but when you unify people into thinking that big tech is not being straight with customers, for me, that's a problem. And I feel like the book, the courses I teach, this conversation I'm trying to force open is to make sure that the tech community, the regulatory community, and the customer base at large speak with the same vocabulary. That's what's missing right now, the connecting tissue and the bridge amongst these three islands.
SPEAKER_01No, that's so interesting. And I think that is a lot. The the message of you know, big tech bad is kind of getting out there a lot. Um, I know a lot of people are getting more sus more and more suspicious of these big companies like Facebook slash meta or Google or whatever. Like what are people doing with our data?
SPEAKER_02And so I wonder your whole background, all of the companies you've ever worked with.
SPEAKER_01Well, and but that's that kind of brings me to your book. So um you recently came out with a book, Data Privacy. Um, so first of all, congrats. It's really exciting. Um and so tell us a little bit about kind of where that came from, um, where the inspiration came from and what you hope people get out of it, because that's that's an interesting point to me. Um, because we are hearing a lot about there's a lot of worry, there's a lot of stress when it comes to big tech um and and data sharing. So bring up bring us some hope or try some.
SPEAKER_00And there is a lot of hope uh to be had here. So the inspiration for this book was a specific moment uh in February 2020, right before the COVID thing happened. There was a before time as well. So we have not always been in this before times, even though it's hard to remember, but yes. Totally. So I was on a panel with um, it was a four-person panel, me and another privacy engineer, somebody I really respect in the industry, and then two other folks who come from the government regulatory side of the house. One of those two said that the reason we need all these privacy laws is because there are no good actors in Silicon Valley. And I again I fundamentally disagree with that, but of course, the way we have conducted ourselves in the tech industry in the last five years makes it hard to make the argument. So the problem is when the policy folks pass laws that are not very practical, not very detailed, it creates a lot of confusion. It makes it a compliance exercise with the big companies that have all the attorneys and the engineers, and these big companies tend to not suffer, whereas the small companies tend to get very stifled because they don't even know where to start. And I like to call it the Nishan Job Security Act because the more ambiguous these laws are, the more I get to write my books, the more I get jobs at companies without even like trying something different. So when I argue for better privacy laws, I'm essentially arguing against economic self-interest, but I still think those laws are required because that's what my dad needs at the end of the day. My mom doesn't need the laws because she's very tech savvy. She reads on the fine print, she uninstalls the app, she turns off location forecasting, all that stuff. But I'm trying to protect my dad here. So but the book does two things. First up, if you I think of this as two different books. The first two chapters and the last chapter talk about how do you scale privacy and security? How do you measure success? How do you judge yourself based on the capability maturity model? How do you make decisions around build v buy? How do you communicate to your executives at the C level? How do you convince the board to invest in privacy and security? These are not things that academic institutions teach our engineers. It's very hard, even to this day, hire to hire engineers who can talk outside of their silo. So the book addresses that problem heads-on. But in the middle part of the book is very, very engineering-focused content that teaches your existing engineers, not people outside the company, but your existing engineers, how to build tooling, how to buy tooling that protects customer data and privacy and security. So this is a book aimed at engineers on the one side and executives, folks in the media, folks in the regulatory space on the other side. Usually, when people write books, they address one of the two audiences. I'm trying to address both at the same time because privacy and security are by their very definition interdisciplinary areas. You cannot just think of your silos. So that's one thing that gives me hope. And the response to the book has been great. If you look at the Amazon listing, Neil Hunt, who was my sponsor and mentor at Netflix, he was the chief product officer, one of the biggest names in the industry, is one of the champions. Other people with strong reputations have weighed in pretty strongly, and the sales numbers are great, which means there is a need for resources like this one. And the problem is that we have created this fear culture where people feel if they ask questions, they will be seen as lacking knowledge and they will open themselves up to scrutiny. So I'm going to give people a safe space to ask questions by reading this book. And that's that was one of the inspirations. But what gives me real hope is that the book that I have written and the certification that I'm going to release with a company called Data Protocol, as you mentioned, gives engineers and their leaders the ability to build privacy tools in-house or with a third party without hiring a whole bunch of external privacy engineers. There is no way to hire privacy engineers with 10 years of experience because there simply is not that much talent in the market. It's a new field, right? So what I'm trying to do is create that skill for people to train existing engineers, upskill them, help retain the engineers you have, keep them happy, help those engineers get promoted, and create a win-win scenario where it's right for the customers, it's right for the companies, and it's right for the engineers across the board.
SPEAKER_02Yeah. Um, I also know that you have another book coming out around uh privacy by design. So now that you shared with us that your mom is very tech savvy, we're gonna bring her on after we read both and do a live book review with your mom. Hope you're prepared for that.
SPEAKER_00Maybe uh it might take more than one hour. My mom has a lot of sharp opinions about this topic, but uh the privacy by design work has been folded into the certification for data protocol. So it's gonna be a more hands-on certification lag. While the book that's coming out, yeah, the book that's coming out in four days is a more sort of academic book where you can actually learn while reading. So we've kind of split between having a more hands-on certification as well as a book that is more along the lines of a textbook. So happy to talk about both or either.
SPEAKER_02Awesome. Well, before before we do that, I have two questions that just I was thinking while you were talking about this. And it once I read your book, and full disclosure, since it's not out yet, I can read it. Um hopefully this will be in there. But let's see what you say to this. So first is what are your thoughts on current regulatory framework in regards to privacy? And then the second part of that is, you know, because you work at Uber, because you've worked in all these big things, I think you'd be great at answering. And you sort of talked on it a little bit, but how do you balance privacy and information sharing with partners and vendors?
SPEAKER_00So it's interesting when the way the question has been framed, how do you balance privacy and data sharing? The fundamental reality of the internet is data interoperability, which is making sure that you can use somebody else's data and you can share it in a different context. And oftentimes people place privacy and data sharing as if they are contradictory to each other, where you cannot have one with the other. And my response to that is you actually can. There are ways to build tools. And just as you use data to build tools that you sell to the customers or give them away for free, you can also productize privacy. There are techniques where you can say, here's a cohort of data. For me to do XYZ with data, how do I make sure that privacy is built into the data itself? So if when you read the book, you will see that I've drawn what is known as a sort of a data pipeline, which shows how when data enters the company, it spreads all over the place, which is why the internet never forgets, because the internet has a lot of places where the data lives. But you can essentially ingest data, you can build privacy protections into the data's definition itself at the point of ingest. And you can make sure that you track that data across your ecosystem, which means if an engineer wants to copy that data, if they want to share their data with a third party, if they want to feed that data into an AI model, that data has a label on the top of it that says this data is extremely sensitive. It contains SSNs or it contains health details, which means the permissions are very, very restrictive. Or the data can have a label that says this is aggregated anonymized data, which means you can have a higher retention period and a lower restriction period for access. You can build those definitions into the data. The same companies that have given us all these amazing products can also productize privacy. The only way we're gonna have regulation that meaningfully has an impact to protect customers is by treating privacy like a product, because products make money, products drive engagements, products get into roadmaps and OKRs. And I don't care what any executive or any company says, unless you treat privacy like an antiseptic product that competes with all the other products in the business, it's not gonna go anywhere. So my book, all my public conversations are about making privacy less this altruistic, honorable thing and more a product that you produce to protect your customers.
SPEAKER_01Yeah, and I think um that's it it it removes sort of that uh the ethical question behind it, right? Because people can, you know, whether you where wherever you come down on that, people can have their own opinions and and argue that. And I think it's a much more it's a harder thing to say, no, this is something we need to implement based on, you know, that this if you look at it from that ethical viewpoint, but if you look at it from what you were saying as a product, um it's it's I think it's just much more easier for people to grab um, you know, that type of concept.
SPEAKER_00Totally. And if I can just make one more point on that, you know, that old joke about why was the drunk guy looking for his keys under the lights, even though he lost them in the park. The reason he does that is because that's where the light is. That's what he can see. And I think people sometimes confuse incompetence, or sorry, incompetence for malfeasance. Like a lot of times when there are these privacy and security incidents, I'm not saying every single time, but a lot of times, it's because the volume of data is too high, the number of transactions very high, and the number of engineers too siloed, which means engineer A collected healthcare data to provide real meaningful customer support, but engineer B was not aware of why that data was collected, and they used it to target that customer with ads. This is how a lot of bad stuff happens. So creating visibility is extremely important. And I think that it's critical for employees or companies to build products out of privacy because otherwise these mistakes are waiting to happen any single day now.
SPEAKER_02Yeah, for sure. Um, I'd like to ask you a question that I've I've never asked anybody on our podcast ever before. I'm very uh my curiosity has piqued right now. Mine too. Depending how you answer, I'm either gonna start definitely asking people this or never asking it again. But um, what keeps you up at night?
SPEAKER_00I'm gonna reach back out to 2003 with Secretary Rumsfeld. I'm not sure how often engineers come on your podcast and quote Donald Rumsfeld. But when this this would be the first, probably. This would be the first one, but maybe not the last time though. He said there are known knowns, known unknowns, and unknown unknowns. And I would recommend people to check out that video clip. He was talking about what happens once you go into a foreign country. And I think the unknown unknowns keep me up at night. Uh, and people like me who go into cybersecurity and privacy have this defiance to them where we can essentially succeed against the system. The system incentivizes siloed engineers, and they incentivize engineers to not care what somebody else does. The incentive is you have your own tech stack, you have your own deployment pipeline, and you should release a product that drives engagement and you get that gets you promoted. The system is set up to let engineers alone and not have to worry about process. Privacy and security is orthogonal to that at the high level because you are basically forcing an engineer to understand how some other engineer might react to this data, right? So what keeps me up at night is are we as a society so accustomed to helping these engineers succeed by doing the wrong thing that it has now become very hard for us to do the right thing? So I need to make sure that my processes, my memos, my overall roadmaps, the tools that I build are sufficiently ingrained into the overall ecosystem of the organization, whatever that might be, to catch bad things before they happen. That's what keeps me up at night. Because I think the scale is the issue. Like we have a significantly vast scale to worry about in the tech sector. The customers want the app to launch quickly. They want the app to be personalized, they want it for free, they want it to be responsive to their needs, but they also feel leery about sharing data. Because guess what? Companies have done historically a not great job in protecting it. So this asymmetry between expectation and reality, as well as the incentives we have created, that creates the unknown unknowns. And that's what keeps me up at night, although not really, because I sleep really well. But if I were to wake up at two o'clock in the morning, that's what would wake me up.
SPEAKER_01That's what would do it. I love how you were like, first of all, great answer. I think Laura, you should um it was incredible. It was an absolutely incredible answer.
SPEAKER_02I just see that. Siri, Siri thought it was a great answer too. She just chimed in. I heard her. I think in the background she was just saying unknown nouns, no, nouns. Say that three times fast and that happens.
SPEAKER_01Um, but I love also how you were like, but I sleep great. Um how do you do that, by the way? Because I oh anyway, my dog wakes me up so early to to eat. She's she's insane. That's that's elderly dogs.
SPEAKER_00Yeah, sorry, my dogs are pretty elderly and they sleep on either side of me. So once they finally conk out, uh, I'm pretty done as well. Like I tend to adopt elderly rescue dogs and I don't have the patience for puppies. So when they go to bed, I go to bed as well.
SPEAKER_01Oh, perfect. That's amazing. Yeah, that's so nice. Well, I'm gonna go back to um uh a question because that kind of got me thinking about these new laws that are coming out um trying to regulate um privacy. So, what do you think about um more data protection laws, more privacy laws? Do you think they are uh impactful? Do you think they help the situation? Um, the type of laws that we're seeing in the US, obviously, because in Europe and in other places is very different. But in the US specifically, what is your opinion about that?
SPEAKER_00So I think it's hard to pass laws in the US. Obviously, it takes a long time to get to 60 in the Senate, as we probably have learned in the last few months.
SPEAKER_01Yes.
SPEAKER_00I think my concern my concern tends to be that on the one side, the laws are pretty high level because we as a society have built sort of this chasm between engineers on the one side, the people who write the code and the business leaders who want to monetize data. That's one side of the equation. On the other side is the vast and growing regulatory estate, which genuinely believes that the more laws we pass, the better off we are. And what concerns me is the contextual gap between the two. I was in a room full of engineers from across Silicon Valley when we had that exchange between Senator Hatch from Utah. He was a Senate president pro Tem at the time, and Mark Zuckerberg. And Senator Hatch asked Zuckerberg, How do you make money at Facebook? And Zuckerberg said, Senator, we're on ads. And I distinctly remember. A bit of a smirk on his face. And all the engineers who are in the room with me laughed out loud. They're like, this guy doesn't even know how the internet works. I'm like, this is not funny. This is a problem. The people who regulate us do not understand how we operate. And these people have regulatory power over us. So the joke is not on Senator Hatch, the joke is on us. So that's that's number one. That's what concerns me. But I feel like we also have an incredible opportunity where engineers can talk about how they build stuff on YouTube, on TikTok. They can talk on Stack Overflow and Quora. So I feel there is an incredible opportunity as we pass these laws, either at the state level or at the federal level, for both of these layers to talk to each other much more continuously, build a common shared vocabulary, and make sure that any law that gets passed is measurable. The concern I have is that people use words like big data, governance, compliance, but they don't actually know what these words mean and how they could help the business. You know, there is an incredible moment here where you could, as an example, somebody like me could say, rather than doing something for privacy, let's do it to make data quality better. The people who really have a vested interest in data tend to be the machine learners, the marketers, the data scientists. And their ability to get benefit from the data depends upon having a meaningful amount of manageable data that is high quality. Okay. So I can entice them to delete unneeded data so that it benefits them. It helps save on data storage costs. It reduces the amount of money we have to spend on encrypting data that we shouldn't have had in the first place. So I can get buy-in within the company to build better privacy without ever using the word privacy in my justification. I can have those guys and those gals on the ML side fight my battles for me. So I feel like what needs to happen when it comes to the laws is have the regulatory folks talk to the engineering folks and come up with intelligent tactical arguments that will effectively help the customers rather than waiting for this huge omnibus law that'll seem like it's this big deal. And then three or four months later, everybody's tired and goes home with no real protection for the customer.
SPEAKER_02Um random question just to chime in here. Do you exclusively use Uber or do you ever find yourself using Lyft?
SPEAKER_00Well, I tend to use every competitor app once a month just to see how they're doing. And I have a lot of friends who work for Doordash and Lyft and whatnot. But it would it would be a crime on my part when it comes to the intellectual level to not keep an eye on the competition because I feel like at the end of the day, keep the enemies close, right? Yeah, keep everybody close, but your enemies are close. I try not to use the word enemy, I think of them as adversaries, but I'm forward to working in those companies. Uh, but I also feel like at the end of the day, we share this internet. We have a vested interest in keeping the internet a safe place because if people shop less on the internet, if people use the internet with a place of distrust, it affects all of us pretty badly. It's like I don't want big tech to become big tobacco. So the more we think of each other as allies in this fight for security and privacy, the better off we will be collectively.
SPEAKER_02Okay. That's interesting. Um I appreciate that. And uh, I just I want to go to some things like everything you're saying is just honestly, you're you're so quick and you're so on point. And I have no arguments that it's honestly making me a little frustrated because I wanna, I wanna like, you know, good cop, bad cop with you, but I just agree with you every time. Um, so my question to you now is just gonna be on challenges. What do you think are your top three challenges? And then to expand on that further for people that are listening right now, that, you know, they may know the name Uber, they may like to read and be like, cool, I'm interested in this and I'll check out your books. They may know some of the Netflix, Nike places that you've worked at, but they may have a different version of data privacy or a different mindset. So not only is it what are your three challenges, but also what advice would you give to everyday people that aren't really engineers like you are and aren't really in the day-to-day granule aspect of it?
SPEAKER_00Perfect. That was the great question. By the way, we have 30 more minutes to play good cop, bad cop. So I'm enjoying this conversation, but I'm happy for any questions you have for me. Uh, I think when it comes to challenges, there are two fundamental challenges. Like we have agreed upon this idea that let's do security and privacy at the back end once everything is done. So I'm talking to my fellow engineers, executives, VCs, people who depend upon data to make money. There is an expectation that once all the engineers, once all the customers are done with the data, we can then clean it up, which means somebody else is going to clean it up. It's like that old joke, we're gonna get on a diet when tomorrow. It's like the same thing. So think of this as the horizontal funnel. When data enters the company, it's at the narrow end of the funnel on the left-hand side. And then data flows through the funnel, the data size grows and the funnel becomes broader on the right hand side. And we expect the combination of security and privacy tooling to make sure that nothing bad happens on the right hand side. It's a bit like trying to clean things up after they have grown in size and risk. So any tooling we build, any processes we build are found insufficient in the face of that challenge. So that is the first big challenge. By the time somebody like me gets hired at a company, I feel like the guy with the shovel walking by and the elephants at a circus where I have to clean up somebody else's mess. So that's challenge number one. And the big companies that have historically employed me have learned that lesson the hard way and they've had the resources to invest and fix things up. I'm concerned about the next Facebook, the next Google, because they will not have the resources and they will have a much more highly scrutinized regulatory environment to operate in. That's challenge number one. But an even bigger challenge is sometimes people in my domain, my field of work on the engineering side, treat security and privacy is as this noble calling. And I'm gonna use another quote, this time from Richard Nixon. I'm not sure how often engineers quote Richard Nixon, or how often anybody quotes Richard Nixon these days. But he said something interesting. He said that you campaign in poetry, but you govern in prose. Like you have to tell people a story and you have to inspire people to understand that doing this is important, not just from a right thing perspective, but a business perspective. So when I talk to the board at any company, or when I talk to VCs, or when I talk to people like yourselves, my message is shrinking the size of the data saves money. Shrinking the size of the data enables you to build trust and get into challenging foreign markets. Protecting your customers helps you showcase your products much more confidently. If you make that argument, you are much more likely to get the funding you deserve and much more likely to get the participation you crave. And that in the end will feel your cut make your customers feel more protected. So my concern is that we are creating the wrong incentives and we are not teaching our engineers to make the argument more cohesively. So those remain my biggest concerns right now, which again is why I wrote this book for the engineers and also for others in the company and the media and the regulatory, regulatory space.
SPEAKER_01Yeah. No, that's super interesting and really good points. And then also just like to go back to something you said earlier. I thought you made a really good point where the people making our like our the lawmakers making our regulatory laws, they really don't have well, they're like 80 years old, all of them. And like they don't have any idea how social media works or a lot of these companies work. Maybe not all of them are 80, but a good amount, right?
SPEAKER_00Like I mean, if I if I can jump in, I think the real challenge is maybe a layer deeper. And it often is easy to sort of poke fun at the government. I mean, everybody likes to make fun of the government and the people who run the government. I think the real challenge is not the age of the people, but the age of their ideas. If you look at how laws get passed in a country, and I'm not an attorney, I've never been elected to anything, so probably easier for me to talk about it than do something about it in this case. But what I would say is the efficacy of laws is seen through the lens of size, big immigration laws, big tax laws, big healthcare laws, you know, build back better. I don't know how long that law was when it was written. But the expectation is for something to truly fix a problem, it has to be big in size. And because a lot of our regulators and lawmakers tend to have come of age in the 60s, they are really in tune with this idea of size. But if you look at history and how it has pivoted, we have gone from biggest good to small is good, smaller chips, smaller cars, smaller homes, smaller pieces of data that combine with other data that makes meaningful change. So I would rather think of a privacy law that passes in small parts. That is a law that addresses what data erasure means, a law that talks about what data export means, a law that talks about data localization, for example. Those smaller laws may be easier to pass, easier to implement, easier to verify, and therefore easier to improve upon. And I feel like if you shoot for 10 small laws, you could maybe pass four or five small ones and actually make progress rather than waiting for this one big law, working on it for like nine months and having nothing pass and then nothing changes. So I feel like I tend to worry less about how old people are and I tend to worry about how old their ideas are. And I feel like there is a significant opportunity because this is the first time we are facing this challenge across the world at the same time. There are people in South Asia, South Latin, EU, and the US all worried about privacy and security. So I do not want to miss this moment. And I would, my dream um avocation would be to talk to people on the policy side, on the government relations side with the media and help shape this because I've literally had to do this for the last 10 years. And I feel like I've learned a few things along the last decade given that I got in so early.
SPEAKER_01Well, Nishant, you have our vote. Um and we no, I think you made some really, really good points there. Um so our next question, and um, and we'll probably let you back into your into your life after that one. Um, this is one of my favorite questions to ask people, but I'm actually very excited to see what you say because I feel like you have so much knowledge and experience. It's gonna be very interesting, so no pressure. Um, but what do you think people should uh so what do you think? You talked about what we we answered what is privacy. What do you think the future of data privacy looks like? And like maybe tell us bird's eye view. Like, let's get crazy. Let's imagine like 10, 20 years in the future. What do you think data privacy is gonna look like?
SPEAKER_00I think it's it's hard to predict 15 years out. So I'm gonna make a small joke before I answer your question more seriously. Okay. So two years ago, somebody asked me, What about this COVID thing? I'm like, a couple of days and we'll be home free. So I think I'm gonna eat some humble pie, put my inner Nostrodamas to sleep for a couple of moments. Just take a little mulligan on that one.
SPEAKER_02But this is why Gabby said like 10 to 15 years from now, because she was like, you know what? There's a range for time.
SPEAKER_00Yeah, yeah, we will people might forget that I said something stupid on this podcast by that point in 15 years. But I uh more seriously, I think this issue will become a lot more normalized. I feel like we have gotten to a place where we know that things work a certain way. Like I was an intern at Sprint in 2002, the cell phone company, and I remember an executive telling me that this whole mobile thing is in going anywhere. People need their mobile phones just to make phone calls. The idea of checking email on phones, that's never happening. So time takes its toll, not just on health and beauty, but also on predictions, and people often come to revise what they thought. I think in 15 years, what's going to happen is privacy is going to be recognized and security is going to be recognized as a basic human right. And companies that do those things correctly will benefit in ways that we don't always foresee. I remember, and I mean, I read about it, is that when initially seat belts were mandated, companies, car companies were opposed to it. And today we have car companies making their sales pitch based on safety measures. I was T-borned in a car two years ago, and the car hit me, and the car I was in got pushed at least 30 feet on the left-hand side on New Year's Day in 2019. And if not for the Toyota, yeah, if not for the brilliant design of the Toyota Corolla I was driving, I would have probably not made it. And this book would never have been written. So just as car manufacturers compete on the basis of security, there will be a time in 10, 15 years, hopefully sooner, when companies compete based on security and privacy. What I think people need to understand is legislation and regulation is downstream from culture. There will be a moment and there will be a combination of moments when people realize that A, lack of privacy and security harms companies' reputation. And B, there is a way to do this intelligently in a way that does not cost the companies money, but actually helps them make profits. And I feel that conversation will lead to enough social expectation that laws that will pass will be a lot more meaningful and companies will start doing the right thing because it benefits them financially. It's a bit like selling products that are more ethically procured. It's why companies sell stuff that has the word organic on it, right? Or it's a way why people buy products in small farmers' markets. I feel like we will get to the point where we will go from, oh my goodness, privacy and security is hard to privacy and security is easy, necessary, and profitable. That is my prediction because I feel like we've made enough progress on the automotive side of the house and we will see the similar progress on the privacy and security side as well.
SPEAKER_02I hope that software starts using the word organic, where they're like, our software is naturally developed in this state. It is organic built software.
SPEAKER_01I love it.
SPEAKER_00Well, we kept engineers happy and well trained and they built products with the customer safety in mind. I think that's that's the pitch I'm going with.
SPEAKER_01There you go. I love the translation.
SPEAKER_02Yes. They were free. Well, with that being said, thank you so much for coming on the show today. You have been great. I wish that we had more good cop, bad cop. It was all just fan club over here. I was fangirling pretty aggressively. Um, and it's been awesome. So thank you so much. We will have everybody check out your book. Um, I believe the book is released the same day we're airing this.
SPEAKER_01So where can people find it? So they can definitely.
SPEAKER_00I'm happy I'm happy to sort of give in a little sales pitch at the end. So the book is Data Privacy, a runbook for engineers. It's already available for pre-sale on Amazon. The official release is February 8th. And I just want to put in a little personal plug. Part of the reason I wrote the book during those tough days when the editor's comments were weighing me down is any money I make of the book I'm going to use to support animal charities, one of the big causes of my life is helping elephants and rhinos get out of captivity, making sure that dogs and high-kill shelters have a way out. So any money I make will be used to support those organizations. So the elephant behind me is one of one such recipient of that future benefit. So two causes close to my heart, which is protecting the customers' data and protecting animals. They're part of my life. So the book is available on Amazon, Barnes and Noble, any publication. And the real benefit here is that you can search for this book using my name on this website. I have a very unique name, which means my expectation of privacy is a little minimal because of the uniqueness of my name. So it, but on the other side, it makes the book very easy to find.
SPEAKER_02So everybody that's listening today, the day you are currently listening is February 8th. So today is actually the day that you can get the book. So the book is officially released today. Same with this episode. I mean, we couldn't have planned that any better, but it just worked out that way. So definitely buy the book. And again, thank you so much for coming on the show today.
SPEAKER_00Thank you for having me. This was a lot of fun.
SPEAKER_01So, Laura, we just talked to Nishant Bajaria. He is an uh expert, extraordinaire in data privacy. Tell us your tech takeaways.
SPEAKER_02I mean, I was beyond impressed with his background alone, all of the companies that he's worked for, and then having the time to put together two books and really getting out there and helping people. I think there's not enough people doing that. Um, we have so many educated people in the field, but to take the time to actually put a book together that is helping other people that want to get into the field, because as you mentioned, I mean, privacy has changed so much. No one is really coming in with 10 years of it of experience. I mean, the internet is 14 years old. So you look at something like that and you have to really be ready to adapt and be ready to learn that to have a book out there to be able to read it is definitely, I'm excited to read it and get my hands on the second one when that comes out as well. And I also think, again, it's interesting to hear, you know, you look at a company like Uber and you're thinking privacy. I think when people hear Uber, they're just like, oh yeah, a rideshare. And they're not thinking of, well, every time you open up that app, where is your data going? Who is seeing that? What's happening? And so it was interesting to me to really get his perspective on what that means and what is data privacy and how he defines privacy for sure.
SPEAKER_01Yeah, and I I really appreciated his optimistic outlook in in big tech and also just like in the future, you know, 10 10 years down the down the line, we won't hold it hold you to it, Nashant. Um, like uh, you know, saying this is already, this might be already embedded in companies where now we're looking at it at the back end, you know, kind of like um seatbelt with cars, like, you know, this is gonna be something that we won't have to really worry about, hopefully, um, because it's gonna be just so ingrained, like privacy will become at the forefront something that businesses are going to invest in. Um so, you know, hopefully that actually happens. And, you know, if um if nothing else, if you aren't even interested in data privacy at all, um, you know, buy his book for the elephants. What a great cause, you know. I do love that.
SPEAKER_02Not just the elephants, like there were several animals. I mean, canals are helped in it. All of it. And I love that. Any good cause, I think, is nice. Um, and so he was great. I loved it. If you want to hear more about Uber or Nishant or That Tech Pod, check us out at www.thattechpod.com. Don't forget to get your swagger. We have great clothes, merchandise, cups, mugs, mouse pads. Yeah, I don't know. We have everything.
SPEAKER_01Did someone buy a mouse pad? And we're like, who uses a memory pad?
SPEAKER_02And then emailed us and said, love your mouse pads. And then we're like, you know what?
SPEAKER_01Buy as many as you want.
SPEAKER_02Yeah, go crazy. Christmas. Get your mouse mouse pads. Remedy. Um, and don't forget to uh follow us on um, you know, subscribe to us, enter your email on our website, reach out to us at contact at thattechpod.com, follow us on LinkedIn slash that tech pod, teach us how to use Twitter. We still can't use it, at uh, you know, tweet at us that tech pod. I don't know, Gabby, what else should they do?
SPEAKER_01If you want to be a great sport and just help us out, um, you can go to uh Apple Podcasts or Spotify wherever you're listening to this podcast and give us a five-star rating and review. We would love you forever. And what it does is it helps the algorithm find, you know, people find us. If people are searching for, hey, I want to listen to uh a podcast about data privacy or uh e-discovery. We are more likely to show up in the searches if you give us those good reviews. Um, so we would love you eternally.
SPEAKER_02We will.
SPEAKER_01We will love you forever. See you next time.