Earlier this month, we published the TROPT Defining the Privacy Tech Landscape Whitepaper 2021, in which we define privacy technology, pulling from foundational privacy and technology concepts. We summarized how we went about defining privacy tech in our first blog post of this series and how we categorize the privacy tech landscape in the second blog post of this series.
We reached out to a range of B2B privacy tech users and buyers–from engineers to lawyers–to gather their insights and provide recommendations for other privacy tech key players, such as founders and investors.
The DevPrivOps (or Shift Left Privacy Tools for Developers) Trend
Perhaps one of the most exciting trends we’re seeing in the privacy tech space is the desire to solve privacy problems earlier on in the data lifecycle. We see the “shift left privacy” trend extend even before the ingestion point or the beginning of the data lifecycle. We’re seeing the trend move further left, before data is collected, shifting as early as the development lifecycle, when products are developed and critical decisions affecting privacy are made. Privacy tech users and buyers want visibility into how code and algorithms affect privacy. They want code governance tools for developers to use. In other words, they want to stop the privacy problems before they’re created.
Privacy Tech Buyers and Users’ Challenges & TROPT’s Recommendations
As shown in select figures below, buyers and users shared the types of privacy problems they’d like to solve through technology, which included: data minimization, retention, vendor management, de-identification, accountability tools, and “shift left” privacy tools for developers. They also shared factors that influence their interest in buying privacy tech, as well as challenges they’ve faced in navigating the privacy tech space.
TROPT recommends that B2B privacy tech buyers and users get vocal about the tools they use and need. They should identify and articulate their biggest privacy pain points as well as the value of solving these problems through privacy tech. They should also provide public feedback on what works and what doesn’t so that innovators can continue to improve these products. Finally, they should work cross-functionally within an organization to generate interest and ensure successful implementation.
In addition to the above challenges and recommendations, we cover more buyer-user feedback and TROPT recommendations in the 76-page whitepaper. If you want to dig deeper, you can download the full TROPT Defining the Privacy Tech Landscape Whitepaper 2021 here.