Lessons Drawn From Cybersecurity In The Rise of Privacy Tech

The panel opens by treating privacy and security as overlapping but distinct disciplines. The speakers argue that practitioners need clear definitions inside their own organizations, while speaking plainly to journalists, consumers and executives who often do not separate the two. Privacy tech, in their framing, is technology aimed at privacy problems, and compliance tools are only one part of it. They also argue for setting privacy requirements early, before systems are built, in the same way security has moved left.

Much of the discussion borrows from the security field. Developers, the panel says, want products that are fast, durable and widely used, so privacy can be presented as part of product quality rather than a blocker. Privacy is described as controlled sharing with respect for context, not just secrecy. On sales, the speakers suggest identifying the person who truly benefits from a product rather than relying on job titles, and helping legal and procurement teams buy software-as-a-service. In communications, they stress that internal practice must match external messaging, that privacy claims need evidence, and that communications staff should join product reviews before launch.

The closing message is that privacy tech vendors face a skeptical audience, so every claim should be backed by documented behavior. Startups are advised to be candid about where they stand and to bring communications and legal input in early.