Accelerating Development
A Message from PrivacyCode President Kristy Edwards
Photo courtesy of #WOCinTech Chat
Developers, development managers, privacy engineers, privacy attorneys — tell me the same story about the litany of meetings they have trying to translate all the words and policies of privacy requirements into something usable for engineers.
They’re all spending an enormous amount of time not writing code, designing new features, or doing legal work. They feel increasingly stuck in these discussions as new requirements emerge from regulators and customers, and they’re unable to focus on the work that fulfills them. I’ve been there.
I understand PrivacyCode customers because I’ve been in their shoes. I led privacy teams, security teams, and product teams, and I know why so many cross-functional privacy efforts struggle to gain traction. Privacy work only moves forward when engineers and lawyers are able to communicate effectively with each other, and when product teams truly understand end-users. Until now there hasn’t been a single solution that could effectively bring all these disciplines together under the same set of expectations, metrics, and goals.
Developers want to do the right thing, to write code that enforces data minimization, consent, and responsible sharing, but legal policies don’t often specify how to do that. Every team involved in privacy work needs someone to show them using language, tools, and context they understand. Legal and governance teams usually explain policy and law with words, but engineering systems are driven by code. To move forward, privacy needs a translator.
My co-founder Michelle and I are building what we wish we’d had as privacy and product executives — a solution to bridge the gap between privacy policies and actual code.
PrivacyCode is a SaaS platform with a translation engine that turns complex privacy policies into a language developers understand, using agile methodologies. It provides context in a world they already know and integrates with tools they already use. This is the future of privacy engineering.
