WhatsApp Private Processing
summary
WhatsApp runs a production confidential‑computing stack that powers an Incognito Chat product launched May 2026 and has operated at scale for over a year, using AMD CVMs with Nvidia Hopper GPUs in CC mode, attestation via RA‑TLS, an Oblivious HTTP relay and Cloudflare transparency logs. Deployment enforces artifact expiration (clients reject CVMs older than 90 days) plus 24‑hour revocation freshness, a binary‑transparency loader for model weights, and an open‑source attestation verifier.
AI-written summary · about
chapters (12)
- 0:00WhatsApp private processing intro
- 2:46Products on the platform
- 3:07Platform architecture
- 5:37Building trusted workloads
- 8:22Artifact injection and proofs
- 10:33Operational challenges
- 14:00Revocation mechanisms
- 17:12Incident response with revocation
- 18:19Bug bounty and transparency
- 20:26Future plans
- 21:51Strengthening platform
- 22:31Q&A
related talks
19mBuilding private products
19mPrivate Calling at WhatsApp
13mWhatsApp Key Transparency
20mWhat's Up WhatsApp? - Two Years After the Big Deal
24mWhatsApp with privacy? Privacy issues with IM E2EE in the Multi-device setting
29mPwning WhatsApp The Dark Side Of Web based Messaging Apps
39mUsing WhatsApp as a Command Line ( Breaking out of the walled Garden)
19mPrekey Pogo: Investigating Security and Privacy Issues in WhatsApp's Handshake Mechanism