Episode
Privacy Theater Is Not Privacy Engineering: What It Actually Takes to Ship Safe AI
- Podcast
- Vanishing Gradients
- Published
- Apr 15, 2026
- Duration seconds
- 3991
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/vanishing-gradients-4989163/episodes/privacy-theater-is-not-privacy-engineering-what-it-actually-takes-to-ship-safe-ai/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/vanishing-gradients-4989163/privacy-theater-is-not-privacy-engineering-what-it-actually-takes-to-ship-safe-ai.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Katharine Jarmul , Privacy in ML/AI Expert & Author of Practical Data Privacy , joins Hugo to unpack why most AI privacy advice is theater: and what technical privacy actually looks like when you’re shipping LLMs, agents, and multimodal systems into the real world. In this episode, we dig into how to build defensible systems in an era of AI agents and multimodal models : why system prompts (and your entire agent harness!) should be considered public by default , and why “privacy observability” is as critical as data observability for anyone building with LLMs today. Multimodal is what changes the threat model: identifiers hide in images, audio, and metadata, not just text, and the old anonymization playbook doesn’t cover it. Vanishing Gradients is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. We Discuss: * No Convenience Tax , you don’t have to trade privacy for utility: high-utility AI products can be privacy-preserving through technical controls like privacy routing and input sanitization ; * Public Prompts and Harnesses : assume any instruction or secret in a system prompt or agent harness will be exfiltrated; don’t put sensitive info there in the first place; * Privacy Observability , tag and track data flows so information is used only for its original intended purpose: catch design flaws before they become legal problems; * Technical Privacy , implement mathematical and statistical constraints directly into ML systems and data flows so privacy is measurable and enforceable, not aspirational; * Tiered Guardrails , a three-layer approach: deterministic filters for hard rules, algorithmic models for nuanced classification, and internal alignment training for behavioral baselines; * Federated Le…