Latest / MBA Training Data / When privacy becomes a liability: what CDOs must own in 2026
Transcript
- 0:00Welcome to the Leaders Insights podcast.
- 0:07Today's episode, when privacy becomes a liability, what CDOs must own in 2026.
- 0:13Privacy breaches are no longer just fines and headlines.
- 0:16They're crashing stock prices and ending executive careers.
- 0:20So why are so many CDOs still treating privacy like a legal department problem?
- 0:25Because for a long time, it was.
- 0:27You had your DPO sitting near compliance, generating audit reports, and the CDO was focused on
- 0:32data products and analytics infrastructure.
- 0:36That separation made sense in 2019.
- 0:38It doesn't in 2026, when a single mishandled data flow can trigger regulatory action in
- 0:44four jurisdictions simultaneously and wipe 8 to 12% off your market cap before your comms
- 0:50team has drafted a response.
- 0:52Give me a concrete example of what that looks like at board level right now.
- 0:56Look at what happened to a major European retail bank earlier this year.
- 1:00They had a third-party data sharing arrangement that technically complied with GDPR but violated
- 1:05Brazil's LGPD and the updated California privacy regulations.
- 1:10The CDO had no visibility into that contract because it was structured as a vendor agreement,
- 1:15not a data agreement.
- 1:17The board found out through a regulator, not through internal reporting.
- 1:21That CDO is no longer in the role.
- 1:23So the CDO has to own the full data supply chain, including vendors.
- 1:28How do you operationalize that without turning the data office into a second legal team?
- 1:33You don't replicate legal.
- 1:34You instrument privacy into your data governance architecture.
- 1:38What that means practically is every data asset in your catalog carries a privacy classification,
- 1:44a consent lineage record, and a jurisdictional flag.
- 1:48When a new pipeline is proposed, the system automatically surfaces, which regulatory regimes
- 1:53apply, before a single line of code is written.
- 1:57Companies like Databricks and Calibra have built meaningful capability here in 2026,
- 2:02though I'd flag that their own materials tend to present that coverage as more complete
- 2:06than most enterprise implementations actually find it.
- 2:10What's the organizational model that actually works?
- 2:13Where does the CDO sit relative to the CISO and the DPO?
- 2:17The model I've seen hold up is a triad accountability structure.
- 2:20The CISO owns the perimeter and the threat surface.
- 2:24The DPO owns regulatory interpretation and individual rights.
- 2:28The CDO owns data flow governance, meaning what data exists, where it moves, who touches
- 2:34it, and for what stated purpose.
- 2:37The CDO is essentially the connective tissue.
- 2:40Without that role actively coordinating, you get security teams blocking data access with
- 2:45no business context and compliance teams approving data uses without understanding the technical
- 2:50reality.
- 2:51And for CDOs who are still being handed privacy as an afterthought, what's the argument they
- 2:56make to the CEO to get proper mandate?
- 2:59Show the CEO the insurance renewal.
- 3:02Cyber and data liability premiums have risen significantly across most sectors in 2026,
- 3:08and underwriters are now asking specifically about data governance maturity before quoting.
- 3:14Privacy isn't a cost center argument anymore.
- 3:17It's a balance sheet argument.
- 3:19Get in front of that conversation before your CFO does, and you own the agenda.
- 3:24Own the insurance conversation.
- 3:26That's the lever.
- 3:27Thanks for being direct about it.
- 3:29To go further, Leaders Insights offers strategic training programs, diagnostic tools, and an
- 3:34executive self-assessment designed for CMOs, CDOs, CFOs, and leaders aiming for board-level
- 3:41performance.
- 3:42Explore everything at MBA-training.com.
- 3:45Thank you for listening to the Leaders Insights podcast.
- 3:48See you tomorrow for another episode.